Module 7 · Step 22 · about 60 min

Ship it: the minimum viable business product

By the end of this moduleAn MVBP definition that passes three conditions, a user flow of ten steps or fewer, and a build plan you can execute in weeks with no-code or AI tools.

Minimum viable business product

Your most important assumptions, combined into one simple but complete product that can be sold. Not a demo. Not a prototype. Sold. The goal is to go to market quickly without overspending, and to learn from money changing hands, which is the only feedback that cannot be polite.

Three conditions

If any of the three is missing it is not an MVBP. A free beta fails the first. A pitch deck fails the second. A one-off consulting project fails the third.

Customers pay for it. Money, not interest.
It provides value to the customer. They get the benefit from your spec, in a form they can feel.
It creates a feedback loop. You learn from every use and every payment, and the product gets better.

Why minimum is the hard part

The endowment effect: people attach more value to things they own than to similar things they do not. Founders own their feature list, so every cut feels like a loss. It is not. Every feature you keep is a feature you have to build, support and explain before you have learned whether anyone cares. Less is more here, and it will feel wrong the whole time.

How to build one

Start from the assumptions you still need to test. The MVBP exists to test them with real customers.
Define the user flow: from the trigger in your journey map to the moment of value, in ten steps or fewer.
Build with minimal effort. No-code and AI tools now cover most first versions. I built the first version of PMFtracker over a weekend that way. Then iterate on it recurringly, weekly, from what customers do.

Worked example

What minimum looked like at FOUND

The recruitment platform could have launched with profiles, matching, messaging, employer dashboards and billing. It launched with vetted candidate profiles and a manual match by a human. Employers paid. Candidates got value. Every match taught us something. Three conditions, one feature, a spreadsheet behind the curtain. The matching algorithm came a year later, built on what the spreadsheet had learned.

Exercise · 45 min

Define your MVBP

Test the three conditions honestly, write the flow, then decide what you are building this month.

Saved in this browser

The MVBP in one sentence

The smallest complete product that can be sold to the beachhead.

Customers pay for it: how and how much?

It provides value: which benefit from the spec, felt where?

It creates a feedback loop: what do you learn from each use?

User flow, ten steps or fewer

	Step	What the user does	What they get
1
2
3
4
5
6
7
8
9
10

What you are cutting, and why it hurts

Build plan: tools, who, by when

No-code, AI-assisted, or by hand. Weeks, not months.

Feeds your pitch deck: PoC and Plan slide

Checkpoint

Tick only what is true. Nobody is grading this. The next module assumes it.

All three conditions are answered with specifics, not intentions.
My user flow has ten steps or fewer and ends in a moment of value.
I have cut at least one feature I love.