How to Write a Problem Statement for Your Startup
Define the problem you're solving clearly. Framework for writing problem statements that resonate with customers and investors.
A clear problem statement is the foundation of everything else—your product, your pitch, and your positioning. Here's how to write one that resonates.
Structure
**Who** — Who has the problem? Be specific. "Small e-commerce owners" not "businesses."
**What** — What is the problem? Be concrete. "Waste 10+ hours/week on manual inventory" not "inventory is hard."
**Why** — Why does it matter? What's the cost? "This costs them sales and causes stockouts."
**How big** — How many people face this? "2M SMBs" or "$5B market." Adds credibility.
Example
"Small e-commerce owners [who] waste 10+ hours/week on manual inventory [what]. This costs them sales and causes stockouts [why]. 2M SMBs face this [how big]."
What to Avoid
**Vague** — "People need better tools" could mean anything. "SMBs lose 15% of revenue to inventory errors" is specific.
**Feature-focused** — "We'll build an app" is not a problem. "They waste 10 hours/week" is.
Test with Customers
**Do they say "yes, that's me"?** If they don't recognize themselves in your problem statement, you're not solving the right problem—or you're targeting the wrong people.
**Next Steps**: Use [Luxara](/app) to validate your problem and get a roadmap. Talk to 10–20 potential customers before you refine further.
Turn this guide into an execution plan
Use Luxara to compare directions, estimate costs, and export a practical roadmap.
Start free Compare plans