How to Build a Problem Slide Investors Immediately Understand

Quick Answer

A strong problem slide makes clear who has the problem, what specifically is painful about it, and why existing solutions fall short. The job of the problem slide isn't to describe your product—it's to make the investor understand why something needs to change.

Why This Matters to Investors

While reading your problem slide, an investor is unconsciously trying to answer one question:

Is this actually a problem worth solving?

If they're not convinced, every slide that follows—solution, market, traction—loses its footing. If you convince them here, the rest of the deck only has to explain how you solve the problem you've already established.

3 Things a Strong Problem Slide Needs

What the Investor Is Really Asking

“Who has this problem—and is it painful enough to demand change?”

A specific customer— not "small businesses," but something identifiable, like "independent dental groups with 5–20 locations."
A specific pain— not "inefficient," but something measurable, like a "12–24 hour wait."
Why existing options fall short— if customers are already solving this some other way, explain why that isn't enough.

Here's what these three elements look like on an actual slide—a weak example, then a strong one.

✕ Weak

✕No named customer—“the industry” isn’t a customer
✕“Inefficient,” “expensive,” and “outdated” aren’t measurable
✕Solution language (“better technology”) creeps in before the problem is even explained
✕An investor is left asking “so what?”

✓ Stronger

✓A specific customer—“regional pharmacies”
✓A quantified pain—a “12–24 hour” wait
✓An explanation of why existing delivery networks fall short—they’re built for scheduled bulk routes
✓The investor naturally wants to know what happens next: how do you solve it?

Common Mistakes

Leading with the product — describing the technology or solution before the problem is even established.
Not naming who has the problem— a problem "everyone" has is a problem no one specifically has.
Relying on adjectives instead of evidence— words like "inefficient" or "frustrating" don't prove anything to an investor.
Reverse-engineering a problem to justify your solution — building the case for a problem you already wanted to build a product for, rather than a problem that actually exists.
Confusing a big market with a big problem— a large market size doesn't prove the problem is painful enough to act on.

Checklist

Have you specifically shown who has this problem?
Is the pain backed by numbers or specific examples?
Have you explained why existing options fall short?
Does the slide avoid opening with your product or technology?
Are you avoiding relying only on adjectives like “inefficient” or “frustrating”?
Does this problem exist independent of your solution?
Would someone seeing your company for the first time understand this problem immediately?

How VC Radar Looks at This

Is a specific customer identified?
Is the pain backed by numbers or specific examples?
Is it explained why existing options fall short?
Does the problem hold up independent of the solution?
Is it immediately clear to a first-time reader?

Is the problem obvious to someone seeing your startup for the first time?

VC Radar evaluates whether your problem slide is genuinely clear to an investor, along with 20+ other criteria.

Analyze Your Pitch Deck with VC Radar →

Related Guides