Scoping an MVP founders actually ship

Every founder we meet has the same product in their head: the complete one. The MVP conversation is never about adding — it is about subtracting until what's left can be built in weeks, put in front of strangers, and still prove the core promise. Most teams get this wrong not because they lack discipline, but because they lack a decision rule.

The one-sentence test

Before touching a backlog, write the product's promise as a single sentence: "[Audience] can [outcome] without [pain]." Every candidate feature then answers one question — does removing it break the sentence? If the sentence survives, the feature waits.

• Breaks the sentence → build it in v1, however hard it is.
• Supports the sentence → stub it: manual process, spreadsheet, human-in-the-loop.
• Decorates the sentence → cut it and write it down for later. Later usually never comes, and that's fine.

The MVP isn't the smallest product you can build. It's the smallest product that makes someone change their behaviour.

— from our discovery workshop notes

Scope by walking the critical path

List the steps a first-time user takes from landing to value. That path — signup, first action, first result — is the MVP. Everything off the path (settings, roles, exports, dark mode) is not. In practice the critical path for a B2B SaaS looks like five to seven screens, which is why our typical MVP ships in 8–12 weeks.

Stubs are a feature

Teams feel embarrassed shipping manual workarounds. Don't be. A "concierge" onboarding done by a human over email tells you exactly what the automated version must do — and costs nothing to change. We routinely launch with an admin panel that is literally a database client:

// v1 "billing system": a nightly job and a spreadsheet
export async function reconcileInvoices() {
  const open = await db.invoice.findMany({ where: { status: "open" } });
  await sheet.append(open.map(toRow)); // finance reviews by hand
}

Nobody churned because reconciliation was a spreadsheet. They would have churned waiting three extra months for the "real" one.

The cut list is the deliverable

End every scoping session with two artifacts: the build list and the cut list, with a reason next to each cut. The cut list is what keeps scope honest when a stakeholder re-opens a debate in week six — the decision and its rationale are already written down.