How small can the first product be?
The smallest useful first product is not the one with the fewest screens. It is the smallest responsible way to test an important uncertainty. A prototype can show whether someone understands an offer; it cannot, by itself, show that they will pay or that delivery is viable.
Choose the decision before the features
Write down the decision you want the test to inform. Perhaps you need to know whether customers can complete a task, whether they value the result enough to pay or whether a service can be delivered within a viable cost. Each question needs different evidence.
If comprehension is the problem, a clickable prototype may be enough. If willingness to pay is uncertain, a clearly described paid pilot may be more useful. If delivery cost is the risk, test the hardest part of the workflow rather than polishing the easiest part to demonstrate.
Bring technology into scope early
Product choices and technical feasibility should be considered together before financial modelling treats a build estimate as dependable. Identify integrations, data requirements, security needs, ongoing running costs and what happens when an external service fails. Compare building with buying or adapting an existing tool.
This reflects the programme’s early joint Product and Technology work: feasibility and build costs inform scope rather than arriving only at a later stress test. Experts help participants assess choices and do their own work; participation is not a promise of a bespoke finished product.
Reduce automation, not responsibility
A manual service behind a simple interface can reveal what customers need before you automate it. Explain any limitations honestly and measure the manual effort. Do not present founder-intensive delivery as scalable economics until you have tested how the work could be repeated.
Small does not mean exempt from privacy, accessibility, contractual or safety obligations. Choose the data you genuinely need, protect it appropriately and avoid experiments that expose people to unacceptable harm. For an existing business, the right first test might be a better booking process or a stock-control improvement rather than a new product at all.
A next step you can take
- Complete: “We need evidence of ___ before we commit to ___.”
- Separate essential safeguards and the core test from features that can wait.
- Set a time and spending limit, define the evidence to collect and decide in advance what would justify a larger build.
Explore the Pentacorn Method or see how these questions fit into the eight-week programme.