Process
MVP Development Process
Most MVP projects slip because the process is vague. Discovery never ends, design is never approved, and engineering starts on a moving target. This is the process we use to ship production MVPs in 15–21 days — and the checkpoints you should demand from any team.
What this process is for
This is for a first version users can log into, complete one job, and (if you are charging) pay. It is not a process for a 40-feature platform, a hardware program, or an undefined R&D spike. If you cannot name the one job v1 does, stop and write that sentence before you hire anyone.
Step 1 — Scope the loop (before anyone designs)
Write the user, the job, the success metric, and an explicit out-of-scope list. A good scoping call produces a feature list you can price. A bad one produces a mood board and a 'we'll see' hourly estimate. We do this in a 30-minute call plus a short written recap. If the recap does not match what you thought you bought, do not kick off.
- →One primary user type for v1
- →One core action that proves the product
- →Channels: web, iOS, Android — only what the loop needs
- →Integrations named (Stripe, Auth, maps) vs deferred
- →Fixed price tied to that list, plus what triggers a change order
Step 2 — Design sprint (days 1–5)
Screens for the happy path, empty states, and the two error cases that will actually happen (failed payment, empty inbox). We do not design 80 screens. You approve the flow before heavy engineering. If you keep adding screens here, the 21-day clock is already lying.
Step 3 — Build sprint (days 6–18)
Auth, data model, the core feature, then payments and notifications if they are in scope. Daily updates in Slack. Cuts happen in public: if a nice-to-have threatens launch, it moves to v1.1. This is the opposite of silent agencies that go dark for three weeks and then surprise you.
Step 4 — Launch and handoff (days 18–21)
QA on real devices or production URLs, store submission when mobile, environment variables, and a repo you admin. Two weeks of bug-fix support is part of the package — not a goodwill gesture. After that, continuous development is a separate retainer if you want it.
Where timelines stretch
Two-sided marketplaces, three-sided delivery, MLS/PMS integrations, and anything that needs a legal review (health, lending) take longer. The process stays the same; the build sprint gets more calendar days. Anyone promising Uber-with-drivers-and-restaurants in 14 days is selling a demo.
FAQ
How long does the MVP development process take?
A tightly scoped product: 15–21 days after kickoff. Marketplace, AI with RAG, or regulated domains: 4–8 weeks. The process steps do not change — the build window does.
Do you include product strategy?
Yes, as part of scoping — cutting features, not writing a 40-page strategy deck. If you need weeks of research, that is a different engagement.
What happens after launch?
You own the code. We fix bugs for two weeks. Then you can continue with us on a retainer or take the repo to another team.
Related
Want this process on your product?
Book a free scoping call. We write the v1 list, confirm a fixed price, and can start within a few days.
Book a Free Call →