Inside a 21-day MVP: day one is clickable, day 21 is live
Day one ends with something clickable. Day 21 ends in production, in your accounts. What lands in each week of a 21-day MVP, and what gets cut to make the date true.

On this page3 sections
A 21-day MVP is not a stunt. It is what a hard scope cut on day zero and a report every 48 hours produce between them. The date holds because the scope is small and fixed, not because anyone works weekends. Here is the actual shape of the three weeks.
Week one: something clickable, then auth and the data model
Day one ends with something clickable: the core flow stubbed from sign-in through to the thing you charge for. The rest of the week is auth, the data model, and the first real version of the one flow that matters. Every 48 hours a two-minute Loom lands, showing what changed, what is next, and what decision is blocking us.
Week two: payments, admin, and the ways users misbehave
Payments go in, then the admin surface, then the second-priority flows, then the edges where real people behave badly: empty states, declined cards, retries, the back button pressed at the worst moment. Anything discovered mid-build is scoped and priced in writing before it is built. That is why the number at the end matches the number you agreed at the start.
Week three: launch is a process, not a day
- Deployment to production infrastructure in your accounts.
- Testing against real flows, including the unhappy paths.
- Handover: readable code, documentation, and a walkthrough.
- Two weeks of included fixes begin the moment you launch.
Every build then includes the 30-day scaling programme at no extra cost: monitoring, performance work, a written technical debt assessment, and a 90-day roadmap we write with you. Whether you keep us on after that is a decision you make with the list in front of you.
Three weeks from now
Bring the scope and we will tell you what has to come out of it.
Twenty minutes, free. We will say whether your first version fits 21 days at $3,999, or whether it needs a written milestone plan instead — and we would rather tell you that before you pay than after.
More field notes
All articles
What an AI agent actually costs to build, and to run
Published quotes for one AI agent run from five figures to six. What actually moves the price, the running costs most quotes leave out, and how to scope one agent so the number holds.

AI agent or automation? A five-minute test for your workflow
Most jobs pitched as AI agents are workflows with one judgement step. A five-question test to tell which you need, and why the answer that holds up in production is usually both.

Why most AI agent projects never make it past the pilot
Gartner expects over 40% of agentic AI projects to be canceled by the end of 2027. The demo was never the problem. The five gaps between a pilot and production, and the checklist we run before an agent goes live.