MVP or full build? A founder's guide to scoping your firs...

Nobody agrees what MVP means

The word has been stretched until it means both “a rough test” and “the real product but cheaper”. Founders usually mean the second. Developers usually hear the first.

That gap is where a lot of disappointment gets manufactured — the founder expecting version one and the team building a probe. So we try not to use the word at all.

Ask what you’re trying to learn

A first release is an instrument for answering a question. Write the question down before scoping anything: will these people pay for this? Will they use it weekly? Can we deliver the service profitably at this level of automation? The scope then becomes obvious — build only what’s needed to answer it, and be ruthless about the rest.

If you genuinely already know the answer — you have a waiting list, or you’re replacing a system you already run — you’re not building an MVP. You’re building version one of a real product, and pretending otherwise means shipping something you’ll immediately have to rebuild.

The one-workflow rule

The most reliable scoping heuristic we’ve found: a first release covers one complete workflow for one type of user, end to end, including how money moves.

Complete matters more than broad. Half of three workflows teaches you nothing, because nobody can finish anything — and unfinished journeys generate feedback about the gaps rather than the idea.

What we cut, and what we never cut

Things that can wait: admin UIs (run scripts for a while), second user types, integrations that aren’t load-bearing, notifications beyond the critical one, native apps when a good mobile web experience will do.

Things we never cut: authentication done properly, the payment path, error monitoring, and a data model you can extend without a migration nightmare. Cutting foundations isn’t speed, it’s debt at a punitive rate.

Decide with a number, not a vibe

If the honest answer to “what happens if nobody wants this” is a shrug and a real budget loss, scope small and test first.

If you’d build it anyway because it’s replacing something that already costs you money every month, skip the test and build properly. Either way, the word MVP never has to enter the conversation.