All notes
Process
6 min read
How I ship an MVP in ten days
Not by typing faster. By deciding faster, and letting the agents do the rest.
People assume the speed comes from the agents typing for me. It does not, or not mostly. Typing was never the slow part. Deciding was, and waiting on decisions was slower still.
Day one is all decisions
Before a single file exists I write the brief as if I were handing it to a new engineer: who the product is for, the three things it must do, and the things it must not try to do yet. Then I ask an agent to turn it into a plan of small tasks, and I argue with the plan until it is right.
One page of brief, no more
A data model I can draw on a napkin
A plan of 30 to 40 tasks, each finishable in an hour
The middle is a loop
Each task goes the same way: the agent writes the tests, then the code, then I read both. If I cannot explain a line, it does not merge. Most days that loop runs twenty or thirty times.
The agent is a fast junior with perfect recall. It still needs a senior to say no.
The last two days are for people
Onboarding, empty states, the first email, the error that says what to do next. The parts nobody demos and everybody notices. That is where I slow down on purpose.
People assume the speed comes from the agents typing for me. It does not, or not mostly. Typing was never the slow part. Deciding was, and waiting on decisions was slower still.
Day one is all decisions
Before a single file exists I write the brief as if I were handing it to a new engineer: who the product is for, the three things it must do, and the things it must not try to do yet. Then I ask an agent to turn it into a plan of small tasks, and I argue with the plan until it is right.
One page of brief, no more
A data model I can draw on a napkin
A plan of 30 to 40 tasks, each finishable in an hour
The middle is a loop
Each task goes the same way: the agent writes the tests, then the code, then I read both. If I cannot explain a line, it does not merge. Most days that loop runs twenty or thirty times.
The agent is a fast junior with perfect recall. It still needs a senior to say no.
The last two days are for people
Onboarding, empty states, the first email, the error that says what to do next. The parts nobody demos and everybody notices. That is where I slow down on purpose.
People assume the speed comes from the agents typing for me. It does not, or not mostly. Typing was never the slow part. Deciding was, and waiting on decisions was slower still.
Day one is all decisions
Before a single file exists I write the brief as if I were handing it to a new engineer: who the product is for, the three things it must do, and the things it must not try to do yet. Then I ask an agent to turn it into a plan of small tasks, and I argue with the plan until it is right.
One page of brief, no more
A data model I can draw on a napkin
A plan of 30 to 40 tasks, each finishable in an hour
The middle is a loop
Each task goes the same way: the agent writes the tests, then the code, then I read both. If I cannot explain a line, it does not merge. Most days that loop runs twenty or thirty times.
The agent is a fast junior with perfect recall. It still needs a senior to say no.
The last two days are for people
Onboarding, empty states, the first email, the error that says what to do next. The parts nobody demos and everybody notices. That is where I slow down on purpose.

Written by Kai Moreno
Independent product engineer, Lisbon
Ready to ship?
Let’s build together.
From the first version to production, at a startup’s speed and with a senior engineer’s care. Tell me about your product.
2 builds open for December
Ready to ship?
Let’s build together.
From the first version to production, at a startup’s speed and with a senior engineer’s care. Tell me about your product.
2 builds open for December
Ready to ship?
Let’s build together.
From the first version to production, at a startup’s speed and with a senior engineer’s care. Tell me about your product.
2 builds open for December