Positioning, the core flows and the MVP scope, decided in writing before a screen is drawn. You start the build knowing what is in, what waits and why.
What you leave withIn writing, before the build
4 documents, each signed off with you. They are yours to keep, and the build starts from the last one.
Four steps, one teamFrom the first talk to the build
ListenStart from what you already know
We start with you: the idea, the people it is for and what you have learned so far.
MapSee the market the way your users do
The market, the alternatives your users have today and the flows that matter most.
DecideDraw the line for the first version
We draw the MVP line together and put every decision in writing.
Hand overCarry the plan into the build
The plan goes straight into the build, with the same team carrying it.
QuestionsAbout product strategy
Can we start with strategy on its own?
Yes. It is also the first stage of Zero to launch, and if you continue, the plan carries straight into the build with the same team.
What do we have at the end?
Your positioning on one page, the core flows mapped end to end, the MVP line and a build plan, all written down and signed off.
How long does it take?
On its own, it depends on the product, and we set the timeline when we scope the work. Inside Zero to launch it is the first stage of about 12 weeks from kickoff to launch.
I already have a build quote. Can you look at it?
Yes. We go through it with you and show what is really in scope before you sign anything.
How do we know the scope is right?
We draw the MVP line together. Every decision is written down, with what waits and why, before the build starts.
I already have a live product. Is this for me?
Yes, and we start from what is live. For funded products that is Relaunch, which opens with a two-week audit and a written plan.



