A first version usually fails in one of two ways. Either it is so large that the money runs out before anyone uses it, or it is so thin that the people who try it have no reason to come back. Scoping is the work of finding the version in between, the smallest product that a real customer would use, pay for and recommend. This guide sets out how we do it with founders, and you can do most of it yourselves with a wall, a pack of sticky notes and an afternoon of being honest with each other.
Start With One Customer and One Job
Write a single sentence that names who the product is for and what it lets them do, such as "a letting agent can take a tenant from enquiry to signed lease without leaving the app". If the sentence needs the word "and" more than once, the first version is trying to serve two customers, and one of them should wait. Everything that follows is judged against this sentence, so it is worth arguing over until everyone involved agrees with it.
List Everything, Then Sort It Into Three Piles
Write down every feature anyone has mentioned, without judging any of them, and then sort the whole list.
| Pile | The test | Typical examples |
|---|---|---|
| In the first version | The customer in your sentence cannot finish the job without it | Signing up, the core task itself, paying, a receipt |
| Done by hand for now | It has to happen, but a person can do it behind the scenes while numbers are small | Approving new accounts, issuing refunds, sending a summary to each customer |
| Later | It is useful, but nobody would refuse to sign up for lack of it | A mobile app alongside the website, loyalty points, links to other tools |
The middle pile is the one most founders miss. A good deal of what looks like software in a young product can be a person with a spreadsheet while customer numbers are small, and doing the work by hand teaches you exactly what the automated version should do when its turn comes.
Protect the Parts That Are Hard to Change
Cutting scope means cutting features, and it should never mean cutting foundations. Four things have to be right however small the launch, because changing them once customers and their records depend on them is slow and risky.
- Accounts and permissions. Who can sign in, and what each kind of user is allowed to see and change.
- How the data is organised. The records the product keeps and how they relate to each other, since every later feature is built on them.
- Payments. How money is taken, refunded and reconciled, including what happens when a card is declined.
- Hosting and backups. Where the product runs, in whose name, and how it is restored if something is lost.
A small first version built on sound foundations grows by having things added to it, whereas one built on shortcuts grows by being rebuilt, usually at the moment the business can least afford the distraction.
Decide What "Worth Launching" Means
Before anything is built, agree the test the first version has to pass, and make it something you can watch customers do. Tests based on how the product feels to the team tend to move as the launch gets closer, while a test based on customer behaviour stays where you put it.
| A weak test | A test you can use |
|---|---|
| "It has all the main features" | A new customer completes the core job without contacting you |
| "The team is happy with it" | A stated number of people pay, or commit in writing to paying |
| "It looks professional" | People who tried it come back a second time without being asked |
Put the Later Pile in Order
Treat the later pile as a queue and put it in rough order now, which makes the first version far easier to agree because nobody is being told that their feature has been dropped. Keep the order loose, since what customers do after launch will rearrange it, and hold back enough budget to act on what you learn. Launch is where the spending on a product starts, and the founders who plan for that are the ones still building on it a year later.
A Checklist Before You Commit
- One sentence names the customer and the job, and everyone involved agrees with it.
- Every feature sits in one of the three piles, and the first pile is short enough to read aloud in one breath.
- All four foundations are in scope, and none has been traded away for a feature.
- The launch test is written down as something customers do.
- The later pile has a rough order and money set aside for it.
- You have seen the core job working as a prototype before paying for the full build.
Shaping the first version with the founder is how our app and platform development work begins, and we do it together so that the plan is yours as much as ours. If you already have a prototype and want to know what stands between it and real customers, that is our prototype to production service. In either case, get in touch and we will help you find the version worth launching.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation