We investigate how you work today, abstract the underlying problem, and build with you the software your team actually adopts. A senior team, working your hours.
Every project has hundreds of small decisions the client never sees. These are the rules we make them by.
We don't write code until both sides know what has to be built.
There is no assembly line with a start and an end. There is a cycle that turns: we discover, prototype, build and accompany. Every turn leaves evidence, and that evidence changes the next one.
We sit with whoever serves the customer and whoever enters the data. We come out with the underlying problem written in plain language and prioritised with you.
At the end of every turn there is something you can open and use, and a review where you decide what comes next. We test it with whoever will operate it: if they hesitate, we change the screen, not the training.
Before we start we agree on how we know it is finished. No delivery ships without a risk review, and every review leaves a rule written into the system.
We are there when the team starts using it, and we measure how they use it. That opens the next turn.
Every business rule is written as a test that runs itself again on every delivery. This one caught something.
The client is not named. The problem and the result are real.
Ski equipment rental · Patagonia · ~8,000 bookings per season
Every booking went through a spreadsheet and WhatsApp. In high season the counter sold gear that was already committed.
Discovery with the counter team, and out of it the online store in three languages, the counter console, and the mechanism that keeps them in sync.
Customers book and pay on their own, in their language, and the system refuses to sell before it will oversell.
We work under NDAs. If you want to talk to this client, we'll arrange it.
Screens nobody has to decode: every action where you look for it, named the way your team names it.
Systems that carry the real operation: secure, documented and ready to grow.
Building exactly what was needed, not one feature more.
Training and presence through launch, until the team works without asking us.
Maximiliano Noseda
Software Architect
Ezequiel Surace
Software Architect
Iván Greve
Frontend Engineer
Facundo Chervin
Backend Engineer
Santiago Berraondo
Product Manager
Built for the way you actually work, not the way a generic product assumes you do.
The software your team uses every day to do their work.
What your customers see, use and sign up for, from any device.
So your systems share the same information instead of different versions of it.
For your team away from the office or your customers on their phone.
Infrastructure, backups and alerts that reach you before a customer does.
Go · PostgreSQL · TypeScript · React · Astro · Next.js · AWS · Docker
A vendor delivers what you asked for. We find out first what was actually needed, and we stay until the tool is in use.
It is part of the method. At every turn's review we re-prioritise together: the new work comes in and something of lower value goes out. A mid-course change is not a problem, it is information we did not have before.
We still start with discovery. If a single module or one automation is enough, that is what we propose.
We support adoption, measure real usage and keep evolving the tool with your team.
We're in Argentina: one to two hours from US Eastern, four to five from Western Europe. Real overlap with both, no overnight handoffs.
Everything in the lab starts by listening. One hour is enough to understand how you work today and to decide together whether there is anything worth building.
We listen to your operation: how work comes in, who is involved at each step, and where it stalls.
The first hypotheses about where the problem actually sits.
A diagnosis of your situation and, if it makes sense to continue, what the first step would be.
If another team is a better fit for your case, we'll tell you in that same meeting · hello@kyojinlabs.com