How We Scope an MVP (And Why It's Not a Questionnaire)

Every MVP conversation starts the same way: someone has an idea, a rough sense of what it should do, and a deadline that's usually tighter than it should be. The instinct — for a lot of dev shops — is to hand that person a form. Fill in your features, pick a budget tier, submit.

We don't do that, and it's not a branding choice. It's because a form can't tell the difference between a feature you need and a feature you think you need.

Why a conversation beats a questionnaire

A questionnaire assumes you already know exactly what to build. Most founders don't — not because they haven't thought about it, but because the answer usually depends on things a form can't ask about: who the first ten users actually are, what "done" looks like for the thing you're trying to validate, and which parts of the idea are the actual bet versus just assumed infrastructure.

That's why scoping starts as a real conversation, not a checklist. We talk through the business, the users, and the goal behind the goal — what you're actually trying to learn or prove by shipping this thing. That context changes what belongs in v1 and what doesn't, every time.

What "lean" scoping actually produces

"Lean" doesn't mean vague. By the end of a scoping conversation, you should walk away with something concrete:

• A requirements doc that reflects what you actually said, not a generic template
• A scope and timeline you can hold us to
• Tech recommendations that fit the product, not whatever stack we feel like using that month

That's the same shape of deliverable regardless of whether you're building a marketplace, an internal tool, or a consumer app — the content changes, the structure doesn't.

The part people underestimate: cutting scope

The hardest part of scoping an MVP isn't adding features — it's cutting them without cutting the thing you're actually trying to test. Almost every idea has a "nice to have" wearing a "must have" costume. Part of the job is telling the difference, out loud, before it costs you a sprint.

If you're sitting on an idea and trying to figure out what actually belongs in a first version, that's exactly the conversation we'd have. Let's talk.