TechcelerateJoin now
Menu
Knowledge base · Validating the idea · Guide 2 of 8

How to prove the problem is real, frequent and costly.

A problem worth building for is one people already spend time or money trying to solve. Here is how to gather evidence that yours is.

You cannot design a solution unless you understand the problem. Problem validation answers three questions: does this problem exist for a specific group of people, how often does it happen, and what does it cost them? Until you can answer all three with evidence, any product is a guess.

Why it matters

Plenty of problems are real but not painful enough to act on. People shrug, live with them and never buy anything. The ones worth building for are problems people are already trying to solve, with spreadsheets, workarounds, extra staff or a tool they resent. That existing effort is the strongest early sign that a better answer would be bought.

Step by step

  1. Write a problem hypothesis. Use the format: “[Specific customer] struggles to [task] when [situation], which costs them [time, money or risk].” Keep it about the customer, with no mention of your product.
  2. Do desk research first. Look for the problem in public: complaints in online communities and forums, negative reviews of existing tools, job adverts that describe the task, regulations that force people to do it, and industry reports. Note every source; this is evidence you can show later.
  3. Talk to people who have the problem. Run conversations about their past behaviour, not your idea. The customer discovery interviews how-to covers the questions and technique. The next guide covers finding the right people.
  4. Score each conversation. After every interview, rate the problem on frequency (how often), intensity (how much it hurts when it happens) and action (what they already do about it). A simple 1 to 3 scale for each is enough.
  5. Look for the cost. Ask how long the task takes, who does it, what goes wrong and what that costs. Hours multiplied by an hourly cost gives you a first value estimate, which becomes vital when you test pricing.
  6. Keep an evidence log. One row per piece of evidence, tagged by source and by which assumption it supports or weakens. Patterns matter more than any single quote.

Strong and weak evidence

EvidenceStrongWeak
How the problem comes upThey raise it unpromptedThey agree when you describe it
Current behaviourThey have built a workaround or pay for a toolThey say they would like something better
CostThey can put a number on time or money lost“It is a bit annoying”
PriorityIt is in their top three problems this quarterIt is on a long list of nice-to-haves
Follow-upThey ask to see what you build nextThey wish you luck

Worked example

Tom and Aisha founded LedgerLoop around a hypothesis: “Small accountancy practices struggle to collect receipts and bank statements from clients before quarterly deadlines, which costs them unbilled partner hours.” Desk research turned up regular complaints in practice-owner groups and several job adverts for “client document coordinators”. In 18 interviews, 13 practice owners raised the chasing problem before being asked, and nine had built their own email reminder templates. Most estimated four to eight hours a week spent chasing in peak months. Five said it was a top-three problem. The evidence was strong for practices with more than 200 clients and weak for sole practitioners, so they narrowed their focus to the larger group.

Common mistakes

  • Leading questions. “Would it help if…” invites a polite yes. Ask about the last time it happened instead.
  • Mixing segments. Averaging answers from very different customers hides the group that really feels the pain.
  • Stopping at the first yes. One enthusiastic person is an anecdote. Look for repetition across independent conversations.
  • Ignoring “doing nothing”. If most people tolerate the problem without any workaround, the pain may not be strong enough.
  • Confusing your problem with theirs. Your own experience is a starting point, not proof that others feel it the same way.

What to measure

  • Share of interviewees who describe the problem unprompted.
  • Share who already have a workaround or pay for an alternative.
  • Average frequency, intensity and action scores by segment.
  • Estimated cost of the problem per customer per month.
  • Share who rank it among their top three current problems.
With SkilledUp Life

Volunteer researchers can run desk research, maintain the evidence log and score interview notes consistently so patterns show up sooner.

How a volunteer team helps with validating the idea · The idea validation team ↗ · How SkilledUp Life works ↗

SkilledUp Life is exclusively for tech companies. Volunteers cannot be paid in any form, including stipends, gift vouchers or expenses. All volunteering is remote, and no promises of paid roles can be made.
Execution Sprint

Idea validation, systematically.

Reading is the start. Members tackle validating the idea in a time-boxed Execution Sprint, alongside tech founders who have built, failed and exited, and leave with measurable results.

Building a tech startup?

Join tech founders who put execution before investment.

Become a member