Why most MVPs take 4 months instead of 3 weeks
It is almost never the code. It is the scope. Founders arrive with a product that does eleven things and a deck that promises fourteen. The MVP that actually gets built is the one that does one job for one user in one loop.
This is the worksheet we run in every Discovery call. Fill it in honestly and you will end up with a scope that a good engineer can ship in three weeks.
Step 1: The One-Job Statement
Complete this sentence without using the word “and”:
[User] hires [product] to [verb + outcome] when [trigger moment].
Examples that pass:
- A Shopify merchant hires PostQueue to schedule a week of social posts when they launch a new drop.
- A freelancer hires Postly to send invoices from a branded email address when they onboard a client.
Examples that fail:
- “Small businesses use our platform to manage marketing, sales and analytics.” (Three jobs, no trigger.)
If you can’t write it, you are not ready to scope. Talk to five more users first.
Step 2: The Loop Map
Every product that makes money has four moments. Write one sentence for each. Anything not on this list is not in the MVP.
| Moment | Question | Your answer |
|---|---|---|
| Acquire | How does the user find out this exists? | |
| Activate | What is the first thing they do that delivers value? | |
| Pay | When and how does money change hands? | |
| Return | Why do they come back tomorrow / next week? |
The activate moment is your MVP. Everything else exists to get people to it and to charge them for it.
Step 3: The Cut List
Take every feature on your list and ask the four questions. One “no” and it goes to v2.
- Does the activate moment break without it? If the user can still get the core value, cut it.
- Will a paying user notice its absence in week one? Not a prospect. A paying user.
- Can a human do it manually for the first 50 customers? Onboarding, exports, “AI insights”, admin dashboards: do them by hand first.
- Does it need to exist before you charge? Billing yes. Team roles no.
Typical survivors: one auth method, one core workflow, one payment path, one email, one admin view. Typical casualties: settings pages, integrations, roles and permissions, analytics dashboards, mobile apps, dark mode.
Step 4: The 3-Week Calendar
| Week | Focus | Done means |
|---|---|---|
| 1 | Foundations | Auth, data model, billing skeleton, deploy pipeline live on a real URL |
| 2 | The activate moment | Core workflow end-to-end with real data, ugly but working |
| 3 | Money and polish | Payments live, onboarding email, error states, analytics events, launch checklist |
If week 1 slips, do not extend. Cut from week 3.
Red flags you are scoping a v2
- The word “platform” appears in your One-Job Statement.
- More than one user type needs to log in on day one.
- You need an integration to deliver the activate moment.
- You are designing the pricing page before the product exists.
- The cut list has fewer than 5 items on it.
What to do next
Write your One-Job Statement, your Loop Map and your Cut List on one page. That page is your brief. Send it to whoever is building, us or anyone else, and you will save yourself a month of back-and-forth.
If you want a second pair of eyes on the scope, book a free 30-minute discovery call. We do this for every project, no strings.