Validation / 2 min read
Write a startup problem statement that stays specific
Define who has the problem, when it happens, what it costs, and why existing alternatives fall short.
By PitchPal · Practical founder guide
Name a situation, not a theme
“Healthcare is inefficient” is too broad to test. A better problem statement identifies a person, a recurring task, and a consequence. For example: “Small clinic receptionists spend time calling patients after late cancellations because the calendar has no usable waiting list.” This is a hypothesis until you observe it.
Attach evidence carefully
Use interview notes, workflow records, or pilot observations to support the claim. If three clinics reported the issue, say three clinics; do not describe the entire sector as proven. Estimate time or cost only when you can explain how you measured it.
Keep your solution out of the first sentence
If the statement says customers “need a chatbot,” you have already selected an implementation. They may need fewer missed appointments, not a particular interface. Separate the desired outcome from the tool so you can compare a simple reminder, a manual service, and a more complex product.
Make the statement falsifiable
State a segment and frequency you can investigate. If the issue happens only during one annual event, the economics differ from a daily workflow. Revisit the statement when evidence changes. A narrower problem can be more commercially useful than a broad statement no one can challenge.
Your next steps
- Name the person and recurring task.
- Describe a measurable consequence.
- Cite the evidence scope honestly.
- Keep implementation choices separate.
Sources & further reading
Sources support the concepts. Hypothetical examples and calculations are teaching material, not measured market statistics.
Turn the thinking into a clear pitch.
Bring your own facts and assumptions to the one-minute coach.
Work on your pitch