A business idea can be interesting without being worth building. The gap between those states is evidence: evidence that the problem matters, that a reachable customer will pay, that the company can deliver at sensible economics, and that the founders have a credible reason to pursue it.
The framework below is designed to make that assessment explicit. It does not produce certainty, and it should not be presented as a record of outcomes that have not been published. Its value is in exposing weak assumptions before they become expensive commitments.
1. How severe is the problem?
Start with the consequence of leaving the problem unsolved. Does it cost the customer money, time, access, confidence, or opportunity? Is it frustrating but optional, or does it block something they already intend to do? Severe problems create urgency. Mild problems require exceptional convenience, distribution, or frequency to support a business.
Look for existing effort
Customers reveal severity through what they do now. Spreadsheets, manual coordination, repeated calls, high fees, workarounds, and risky shortcuts all show that the problem is real enough to attract effort. A complaint without any attempt to solve it is weaker evidence.
2. Will the customer pay for a better outcome?
Interest is not demand. Ask what budget already pays for the problem, who controls that budget, and what a purchase must replace or improve. Willingness to pay depends on the value of the outcome, the credibility of the provider, the cost of switching, and the risk of being wrong.
The strongest early evidence is behavioural: a deposit, a paid pilot, a signed agreement, or a customer choosing the offer over a real alternative. Surveys can help with language, but they cannot carry the whole decision.
3. How often does demand occur?
Frequency shapes retention, acquisition economics, and the operating model. A rare high-value transaction can support a company, but each sale may require renewed trust and distribution. Recurring demand can produce stronger retention, but only if the product keeps delivering enough value to deserve renewal.
Separate the frequency of the problem from the frequency of payment. A company setup may be infrequent while the operating obligations that follow are recurring. Equipment access may be temporary, event-based, or repeated. Software may be used daily but paid monthly or annually.
4. Can the customer be reached efficiently?
Distribution should be tested as early as the offer. Where does the customer look for help? What creates trust? Is the channel controlled by the company, rented from a platform, or dependent on a partner? How long is the sales cycle, and what evidence does the buyer need before deciding?
A market is not a channel
A large number of potential customers says nothing about the cost of reaching them. A narrower audience with a clear moment of need may be more valuable than a broad audience that is difficult to identify or persuade.
5. What operational complexity sits behind the promise?
Map the work required to deliver one successful customer outcome. Include people, inventory, software, third parties, support, exceptions, and the time between payment and completion. Then ask what changes at ten, one hundred, or one thousand customers.
This is where the difference between registration and operation becomes important. Building a company requires repeated delivery, not only a legal entity and a persuasive offer.
6. Does regulation reshape the business?
Regulation may affect licensing, customer eligibility, claims, data, payments, ownership, staffing, or geography. Identify which decisions belong to the company and which depend on an authority, institution, or professional standard. Never build a guarantee around an outcome controlled elsewhere.
The question is not simply whether regulation exists. It is whether the team can understand it, maintain current knowledge, design compliant operations, and absorb the time and cost it adds.
7. How much capital is required before evidence arrives?
Some ideas can be tested manually with a small service. Others require inventory, technical development, regulatory work, or physical infrastructure before the first customer can receive value. Estimate the capital required to reach each meaningful proof point, not only the amount needed to launch the final vision.
- Cost to test whether the problem and customer are correctly defined.
- Cost to test willingness to pay and a workable acquisition channel.
- Cost to deliver the first complete customer outcome.
- Cost to demonstrate repeatability rather than one exceptional result.
8. How quickly can the central risk be validated?
Every idea has a riskiest assumption. It may be customer demand, technical feasibility, approval, delivery cost, retention, or trust. Design the first test around that assumption. Building easier features while the central risk remains unknown creates motion without learning.
Choose evidence that can change the decision
A useful test has a threshold. Decide what result would justify continuing, changing the offer, or stopping. Without that discipline, founders can reinterpret every result as encouragement.
9. What is the founder advantage?
Founder advantage is not confidence. It is a relevant edge in insight, access, execution, distribution, technical ability, credibility, or endurance. The advantage should improve the probability of solving this problem for this customer, not merely make the idea feel personally attractive.
Experience across sectors can help founders recognise recurring operating questions, but it does not remove the need to learn a new industry. The article on what different industries teach company builders explains which principles transfer and which constraints remain specific.
Turn the framework into a decision
Scorecards can organise thinking, but the conclusion should remain a reasoned judgment. State the strongest evidence, the largest unknown, the next test, the capital exposed before that test, and the condition that would cause the team to stop. That creates a decision process rather than a collection of optimistic notes.
A worthwhile idea does not need perfect answers. It needs a problem that matters, a credible route to customers, workable delivery, acceptable constraints, and a fast path to better evidence. The company portfolio shows how those questions appear in business services, software, and experience-led wellness.