What is it?
A problem statement frames customer pain clearly before you build a solution.
Idea & product
Problem statement builder
A problem statement frames customer pain clearly before you build a solution.
Fill the blocks, add evidence, and write a final paragraph the team can reuse.
Guide
Make the problem sharp and provable
Why it matters
Without it, MVP scope drifts and pitches stay solution-first and fuzzy.
How it works
Fill the blocks, add evidence, and write a final paragraph the team can reuse.
Go deeper
Why you’ll love this
Before building a solution, make customer pain sharp and provable.
How to jump in
-
Who and what pain
Segment plus concrete problem.
-
Context and impact
Where it happens and the cost of inaction.
-
Evidence and final line
Proof plus a pitch/MVP paragraph.
What you walk away with
- Five-part frame
- Sample included
- Markdown export
- Local docs
Where it shines
Product kickoff
Align the team on one problem.
Before MVP scope
Start scope from a clear pain.
Problem slide
Direct input for the pitch.
Quick answers
Different from value proposition?
This focuses on pain; value proposition connects pain to the product.
How long should it be?
Keep blocks short; one final paragraph is enough.