How to scope a lean MVP or first version on one page
Short answer: a lean MVP scope is one page. It names the buyer, the one result they pay for, the few steps the software must do to deliver that result, and a list of everything you’re leaving out. Every line on it should trace back to something a buyer has paid for or asked for twice, or, for a tool your own team will use, a job that costs you hours every week. Everything else waits, or gets done by hand. If it doesn’t fit on one page, it isn’t lean yet.
Why most MVPs aren’t minimum
Most first builds start as a feature list. Then the list grows. Every meeting adds a “while we’re at it”. By the time it goes to a developer, it’s the whole vision with a small price hoped for.
I spent two years selling offshore development to businesses in Australia and Japan. Developers quote what you describe. A long list gets a long quote. A one-page scope gets a smaller one you can check.
There are three ways a scope gets too big.
Problem 1: you’re scoping for a buyer you’ve imagined
If nobody has paid yet, you don’t know which features matter. So everything feels like it matters. You’re building for a buyer you’ve imagined.
The fix: sell it first. Get at least one buyer to pay, pre-pay or sign a letter of intent for the result. Then scope only what that buyer needs to get it.
Problem 2: you’re scoping the app, not the result
Your customer doesn’t need 100% of your app. They need the part that solves their problem. Everything else can wait, or be done by hand.
Logins, dashboards, admin screens, reports, settings and notifications all feel essential. Most of them aren’t what anyone is paying for.
The fix: prove it by hand. Write down the result in one sentence, then ask what one person could deliver by hand next week. The software only has to do the steps you can’t do by hand.
Problem 3: nothing is written down as “not now”
A scope that only lists what’s in will keep growing. Every “could we also” lands in the build, because nothing says it shouldn’t.
The fix: build only what’s been paid for, and write the rest down. Only what someone will pay for this month. Park the rest. A “not now” list is the most useful part of the page.
What goes on the one page
Six short sections. If any one runs past a few lines, cut it.
- The buyer. Who pays, in one line. A type of business or person, not “everyone”.
- The result. What they get, in one sentence a buyer would repeat.
- The proof. Who has paid, pre-paid or signed, and for what.
- The must-do steps. The few things the software has to do so the buyer gets the result. Three to five is plenty.
- Done by hand for now. The steps you or your team will do manually until they repeat every week.
- Not now. Everything you’re leaving out, by name.
If you’re a business owner scoping an internal tool, the buyer is the team who’ll use it, and the proof is the hours or errors it saves today. The page is the same.
A made-up example
This isn’t a real client. It shows the shape, not the answer.
A business wants an app that books, reminds and invoices clients for training sessions. The first list has 14 features: client accounts, a calendar, reminders, payments, invoices, reports, a mobile app, an admin panel, ratings and more.
On one page it becomes:
- Buyer: small training businesses that run group sessions.
- Result: fewer no-shows and invoices that go out the same day.
- Proof: three businesses have paid a deposit for a pilot.
- Must-do steps: book a session, send a reminder the day before, send an invoice after.
- Done by hand for now: reports, refunds and changes to bookings.
- Not now: mobile app, ratings, client accounts, admin panel.
Fourteen features became three. The rest waits until the same manual step repeats every week.
Another made-up example, for an internal tool: a plumbing business wants a job app with 12 features. On one page: the team (office staff and plumbers); the result (quotes out the same day); the proof (two weeks of timing how long quotes take now); must-do steps (photo and voice note from site, draft quote, send); by hand for now (follow-ups); not now (client portal, stock tracking, dashboards).
How to write yours in an hour
Pen and paper is fine.
- Write the result in one sentence. If a buyer wouldn’t repeat it, rewrite it.
- List every feature you’ve thought of. All of them. Get it out of your head.
- Mark each one. Has someone paid for this, or asked for it twice? If not, it goes on the “not now” list.
- Move what’s left to “by hand” where you can. Ask of each: could one person do this by hand for the first five buyers?
- What’s left is your must-do list. If it’s more than five steps, go back to step 3.
- Check it fits on one page. If it doesn’t, you’re still scoping the vision.
When something moves from “by hand” to “build”
Every manual step you repeat is a feature someone has already paid for. When paying customers need the same manual step every week, build that step, nothing else.
Time each manual step while you do it. The steps that take the longest and repeat the most are what you automate first. The ones that never repeat stay manual, or stay on the “not now” list.
Sell the result by hand first. Build only what you keep repeating.
FAQ
How many features should an MVP have? As few as it takes for a buyer to get the result they paid for. For most first builds, that’s three to five steps, not a feature list.
What if a buyer asks for a feature on the “not now” list? Write it down and count it. One ask is a note. When paying buyers keep asking for the same thing, it moves up. Asked twice by someone who’s paid is a good line.
Isn’t a manual version unprofessional? Your buyer cares about the result, not how it gets done behind the scenes. If a buyer won’t pay for the manual version, they won’t pay for the app.
Can I give this one page to a developer? Yes. That’s the point. A one-page scope gets you a quote you can check, and it makes two quotes easy to compare.
I’m a business owner, not a founder. Does this still apply? Yes. Swap “buyer” for the team who’ll use it, and “proof” for the time or money the tool will save. Run the job by hand or on tools you already pay for until the same step repeats every week.
The examples in this guide are made up. Use your own buyers and your own steps.
Want this page written with you, plus a build, buy, wait or stop call? That’s part of the Build Case.