Problem Statement

A problem statement is the pitch-deck slide and underlying narrative that defines the specific customer pain a startup is solving and why it matters now. It names who has the pain, how widespread it is, how painful it is today, what workarounds the customer currently uses, and the timing case, typically delivered as the second or third slide of a pitch deck (after the title slide and sometimes the elevator-pitch slide) because it frames everything that follows. It is the slide most founders underweight, and the one most investors use to decide whether the rest of the deck is worth reading before they ever reach the Traction Slide.

The components of a strong problem statement: the specific customer (who has this problem, named precisely, like "B2B SaaS founders at companies under 50 employees," not "businesses"), the specific pain (what hurts about the current state, in concrete terms), the workarounds (what people do today to cope, which establishes that the problem is real because people are spending time/money on it), the cost of the problem (a number where possible, such as hours lost, dollars wasted, opportunities missed), and why now (what changed in technology, regulation, behavior, or market that makes this solvable now when it wasn't before). The weak version: "Companies struggle with marketing." That's not a problem statement, it's a category. The strong version: "When B2B SaaS founders need to write a pitch deck, they spend 40+ hours over 2 to 3 weeks and produce a deck that's mostly a remix of templates they found on Google, because there's no tool that captures their specific business model and translates it into investor-grade narrative." That's investable: specific customer, specific pain, specific cost, implicit "why now" (AI tools can now do this). The diagnostic that catches weak problem statements: would a sophisticated customer in your target segment read this and nod, or shrug? If they shrug, the problem isn't specific enough.

What founders get wrong: Describing the problem from the founder's perspective rather than the customer's. The founder writes "current solutions are inadequate" because the founder is annoyed by the alternatives; the customer might not be annoyed by the alternatives at all, just frustrated by a specific moment in their workflow. Anchor the problem statement on what the customer feels, not on what the founder noticed.

Related: Pitch Deck · Solution Slide · Jobs To Be Done · Value Proposition

FAQ

What is a problem statement in a pitch deck?
The slide and underlying narrative that defines the specific customer pain a startup is solving: who has it, how widespread it is, how painful it is, what workarounds customers currently use, and why it matters now. Typically the second or third slide, framing everything that follows.

What makes a strong problem statement?
Specificity. A specific customer (named precisely, not "businesses"), a specific pain (in concrete terms), specific workarounds (proving the problem is real), a specific cost (a number where possible), and a specific "why now" (what changed to make this solvable now). The weak version sounds like a category; the strong version sounds like a particular person on a particular Tuesday.

Should the problem statement come before or after the solution?
Before, almost always. The deck structure is problem then solution, because the investor needs to feel the problem before they care about the solution. Founders who jump to the solution first leave the investor unable to evaluate whether the solution matters. Set up the pain; then earn the relief.