What actually fits in a 21-day MVP

Twenty-one days is not a slogan. It is a constraint I hold on purpose, because it forces a choice most founders keep putting off: what does this product need to do on day one, and what can wait.

Here is what fits, what I cut, and how I decide. If you read one thing, read the scope call section. That is where the project is won or lost.

What fits in 21 days

A real product with one flow that works end to end. Not a mockup. Not a click-through. A thing your users can sign up for, use, and pay for.

• One core flow, built for real — the single path that proves your idea.
• Accounts and login, so users have their own data.
• A database that holds the real thing, not fake rows.
• Payments, when the product needs to take money on day one.
• A clean interface in your brand, deployed to a live link.
• One AI feature, when it earns its place in the core flow.

That list is enough to launch, get real users, and learn something true. Most products that fail did not fail because they lacked a settings page. They failed because the one thing they were for never got tested.

What I cut, every time

These are not bad features. They are features that do not belong in the first three weeks. They cost days and prove nothing until you have users.

• Admin dashboards. I can run your database by hand until you have volume.
• Roles and permissions beyond user and owner. Add them when a team asks.
• Onboarding tours and empty states with art. Ship the flow first.
• Second and third sign-in methods. Email or one provider is plenty.
• Analytics dashboards you build yourself. Use an off-the-shelf tool.
• Native mobile when the web works. A good responsive site reaches everyone faster.

Every one of these becomes easy to add once you know users want it. Before that, it is a guess you paid for.

How the scope call works

We get on a call before you pay anything. You tell me the idea. I ask one question over and over: what has to be true for a user to get value the first time they open this?

The answer to that question is the MVP. Everything else is the roadmap. I write both down in front of you, so we agree on the line before I write any code.

Sometimes the honest answer is that your idea does not fit in 21 days. A marketplace with two sides, live matching, and payouts is not a three-week build. When that happens, I tell you on the call. Then we cut to the half that proves the idea, and the rest waits.

I would rather lose the sale than promise a date I will miss. A missed launch costs you more than a smaller one.

Why the deadline stays real

The deadline holds because the scope is fixed and I own the whole build. There is no handoff between a designer, a backend team, and a frontend team, each waiting on the last. One person builds it, so there is no queue.

You see a live staging link from the first few days. You can click the real thing as it grows. If something is wrong, you say so that day, not at a reveal in week eight. Small corrections cost minutes. Late ones cost weeks.

Scope creep is the one thing that breaks a 21-day build. So we agree that new ideas go on the roadmap, not into this build. They are not lost. They are next.

What you have on day 21

A live product. A repo you own. One flow that works, that real users can touch, that can take money. Thirty days of fixes on me, because bugs in what I built are mine.

From there you know something you could not know before: whether people use the thing. That is the only report that matters, and you get it in three weeks instead of six months.