Demand-Led Product Ladder
Turn a proven content need into tools through progressively larger tests.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 97%
The Demand-Led Product Ladder moves from lived problem to content, lightweight utility, paid product, and only then a larger platform. Bright says The Break grew from financial mistakes and information she wished she had received, including tax, pensions, property, and budgeting. After publishing for that audience, she made a simple budgeting spreadsheet that she says drew about 20,000 downloads in two weeks. A planner then sold out within a day or two. Those behaviours supported her ambition to provide more tools, while the larger app remained in design and testing rather than being treated as inevitable. The mechanism is progressive commitment: each smaller artefact tests whether people want practical help before more time and money are spent. The signals are promising, but they do not by themselves prove retention, profitability, or suitability for every financial need.
Origin
Extracted from The Diary of a CEO
Core principles
- 01Start with a problem you understand rather than a product you want to build.
- 02Content response can reveal demand but should lead to a more concrete test.
- 03Simple tools test utility before expensive software development.
- 04Increase investment only as real behaviour supports the next step.
How to run it
- 1
Start with a witnessed problem
Choose a recurring problem you have experienced or repeatedly observed in a defined audience. Describe the costly mistake or unmet job in concrete terms.
Pro tip Bright began with financial gaps and mistakes she had personally encountered.
Watch out Personal experience does not make someone qualified to give regulated or individualised advice.
- 2
Teach before building
Publish useful explanations and observe which problems repeatedly earn attention, questions, or requests. Use the response to narrow the practical job a tool should perform.
Pro tip Keep educational claims within verified expertise and clearly mark general information.
- 3
Ship the smallest tool
Create a simple resource that helps users complete the job without a custom platform. Bright used an Excel budgeting template.
Pro tip Choose a familiar format that lets usefulness, not technology, carry the test.
Watch out Downloads can reflect curiosity rather than lasting value.
- 4
Test willingness to pay
Offer a bounded paid product that extends the same job and measure completed purchases. Treat sales as a stronger signal than views while still checking margins and refunds.
Pro tip Keep the paid test close to the validated use case.
Watch out A sell-out can result from deliberately limited supply and does not establish scalable demand.
- 5
Escalate investment carefully
Use the accumulated evidence to design and test a more capable product or platform. Validate the assumptions that the simpler tools could not answer before committing to a full build.
Pro tip Define the next uncertainty each prototype must resolve.
Watch out Do not treat an app as the destination if simpler tools already solve the audience's problem.
In the wild
Bright built financial content around lessons and mistakes she wanted others to avoid. She then made a budgeting spreadsheet, which she says received about 20,000 downloads in two weeks, followed by a planner that sold out in a day or two. The team was designing and testing an app as a longer-term possibility.
→ Each smaller release supplied behavioural evidence before the proposed app required a larger commitment.
A nutrition educator notices repeated requests for affordable weekly planning, publishes a practical series, tests a spreadsheet shopping planner, and sells a small printed planner before prototyping subscription software.
→ The creator learns whether people want the job solved before funding a recurring software product.
Common mistakes
Starting with the app
Bright's sequence used content, a spreadsheet, and a planner before the larger platform she described as a future dream.
Equating attention with retention
Strong download and sell-out claims indicate interest, but the transcript does not establish repeat use or long-term economics.
Overstepping financial expertise
Educational tools should not imply individualised, regulated, or universally suitable financial advice.
Is it for you?
Best for
Audience-led businesses that can teach around a recurring problem and deliver a lightweight tool before committing to a platform.
Not ideal for
Products requiring regulated advice, clinical validation, or safety-critical functionality that cannot be responsibly tested through simple consumer tools.
From the transcript
“that's why i created it”
“20 000 people download an excel spreadsheet”
“we've got the designs and we're doing some testing now”
From the episode
Patricia Bright: How She Made Her Millions