Watkins Bay
Menu
All insightsStartups

Problem first: how founders test whether a problem is worth solving

Most startups do not fail because they cannot build a product. They fail because the problem was not painful enough. Here is a research-led way to test a problem before you commit years to it.

LRLilly Ryan Associate Analyst4 min read

Key points

  1. Test the problem before building the product; it is cheaper and faster.
  2. A strong problem is painful, frequent, owned by a specific buyer and already costing money.
  3. Use interviews about recent, specific events rather than hypothetical surveys.
  4. Ask for small commitments to separate real demand from polite interest.

Founders tend to fall in love with solutions. It is understandable: building is energising, and a working prototype feels like progress. But a product only matters if it solves a problem people care about enough to change their behaviour and, eventually, pay.

Testing the problem first is cheaper than testing a product. This article sets out a simple method for doing it well.

Why the problem comes first

New businesses face steep odds. US Bureau of Labor Statistics data show that roughly one in five new business establishments closes within its first year, and only about half are still operating after five years. Those figures cover all kinds of businesses, not just venture-backed startups, but the lesson carries over: time and money run out quickly when demand is weaker than expected.

Investors look for the same evidence. In a survey of 885 institutional venture capitalists published in the Journal of Financial Economics, Paul Gompers and colleagues found that VCs weigh the team most heavily, but they also assess the market, the product and customer traction. A founder who can show that a problem is real and urgent is answering one of the first questions any investor will ask.

Four tests for a problem

A useful problem tends to pass four tests.

  • Pain: Does the problem cost the customer money, time, revenue or reputation? Mild irritation rarely justifies a purchase.
  • Frequency: Does it happen often enough to stay top of mind? A problem that appears once a year is easy to tolerate.
  • Ownership: Is there a specific person who feels the pain and has the authority, or budget, to fix it?
  • Current spend: Are people already spending money or effort on workarounds? Spreadsheets, manual processes and hired help are all signs of demand.

If a problem fails two or more of these tests, it may still be interesting, but it is unlikely to support a business on its own.

How to gather evidence

Start with conversations, not surveys. Surveys tell you what people think they would do; conversations reveal what they actually do. Aim for twenty to thirty interviews with people who match your intended customer, and ask about recent, specific events: “Tell me about the last time this happened. What did you do? What did it cost?”

Look for patterns rather than single stories. Record how often the problem occurs, what workarounds people use and what they already pay. Note who else is involved in the decision.

Then test commitment. Ask for something small that costs the customer something real: a follow-up meeting with their manager, access to their data, a letter of intent or a paid pilot. Polite interest is common. Commitment is rare and far more informative.

Signals that you are on to something

Strong signals include people describing the problem before you raise it, asking when they can try your solution, or offering to pay for an early version. Weak signals include generic praise, “I’d definitely use that”, and enthusiasm from people who do not own the budget.

Be honest about what you find. Some of the most valuable founder decisions are the ones made early: narrowing to a smaller segment with sharper pain, or walking away before the cost of being wrong grows.

Different markets, same discipline

The method works across regions, but the context differs. In the United States, the size of the domestic market means a narrow niche can still be large. In Australia, a niche may be too small on its own, so founders often need to test early whether the same problem exists in other markets. In Europe and much of Asia, language, regulation and procurement norms can change how a problem shows up, even when the underlying need is similar.

Frequently asked questions

How many customer interviews are enough?

There is no magic number, but many founders find patterns emerge after twenty to thirty interviews within a single customer segment. If answers are still scattered after that, your segment may be too broad.

Should I show a prototype during problem interviews?

Generally not at first. Showing a solution early shifts the conversation to feedback on your idea. Focus on understanding the problem, then introduce a prototype in later conversations.

What if customers say the problem matters but will not pay?

Treat that as important evidence. The problem may be real but low priority, the buyer may be someone else, or the budget may sit in another part of the organisation. Dig into who pays for the current workaround.

References

General information only. This article reflects the author’s views at the time of writing. It does not take into account your objectives, financial situation or needs, and it is not financial, legal or tax advice or a recommendation to invest. Figures are from the sources named and may change. See our terms of use.

A new insight every Monday.

Startups, venture capital, economic impact and the trends behind them. Get Adam’s weekly notes by email through Start Up Growth Hacking, or follow by RSS.