TL;DR
- The problem slide is the most important slide in your deck. If investors don’t feel the problem, nothing that follows matters.
- Most founders describe a situation, not a problem. These are completely different things.
- Duygu’s Law of Problem Clarity: if your problem slide needs more than one sentence, it’s not a problem slide yet.
- The test: read it to someone in your target market and watch their face. If they nod, you have it. If they tilt their head, you don’t.
- Quantify, humanize, and make it undeniable. Those are the three jobs of a problem slide.
Here is the slide investors look at first. Not the team slide. Not the traction slide. The problem slide.
Because if they don’t feel the problem in the first 30 seconds, they will never care about your solution. Your market size won’t matter. Your team credentials won’t matter. Your hockey stick projection definitely won’t matter.
The problem slide is the foundation everything else is built on. And it’s the slide most founders get wrong.
Why most problem slides don’t work
The most common mistake is confusing a situation with a problem.
A situation is something that exists. A problem is something that hurts.
“The project management software market is fragmented” — that’s a situation. Nobody lies awake at night because the market is fragmented.
“Operations managers at 50-person companies spend Monday mornings manually reconciling three tools that were never designed to work together, and they’ve been doing it every week for three years” — that’s a problem. That person exists. That Monday morning exists. That frustration exists.
Investors fund solutions to problems, not observations about situations. The faster your problem slide makes them feel the pain, the faster they lean forward.
Duygu’s Law of Problem Clarity
If your problem slide needs more than one sentence to explain the problem, you don’t have a problem slide. You have a paragraph.
This is the single most reliable test for whether your problem slide is working.
One sentence. Undeniably true. Immediately felt by anyone in your target market.
That’s the standard. Everything else is a draft.
Why one sentence? Because investors scan. Because a problem that requires explanation is a problem that hasn’t been distilled yet. Because if you can’t say it in one sentence, you probably don’t fully understand it yourself — and investors will sense that.
The one-sentence constraint also forces you to identify what’s actually wrong, rather than what’s merely inconvenient or suboptimal. Inconvenience is not a problem worth funding. Pain is.
The three jobs of a problem slide
A great problem slide does three things simultaneously.
Job 1: Make the problem undeniable.
The investor should read your problem statement and think “yes, that’s true” before they think anything else. Not “interesting” — not “maybe” — just immediate recognition.
The way to achieve this is specificity. Vague problems feel theoretical. Specific problems feel real.
“Businesses struggle with data management” is not undeniable. Everyone nods and nobody feels anything.
“Finance teams at Series B companies spend an average of 11 hours per week manually reconciling data across tools that cost them $80,000 per year and still don’t talk to each other” is undeniable. Anyone who has worked in that finance team knows exactly what that Monday morning feels like.
Job 2: Quantify the pain.
Numbers make problems real. They also signal that you’ve done the research — that you haven’t just observed the problem from the outside but have actually measured it.
The best problem quantifications involve time, money, or frequency. Ideally all three.
- Time: “11 hours per week”
- Money: “$200,000 in lost productivity annually per company”
- Frequency: “This happens every single billing cycle, for every customer”
You don’t need all three. One strong number is better than three weak ones. But at least one number should be on your problem slide.
Where do you get the number? Customer discovery interviews. Industry research. Your own experience inside the problem. If you’ve spoken to 40 potential customers and 35 of them mentioned the same pain point, that’s your data point. “35 of 40 operations managers we interviewed cited this as their top weekly frustration” is a number.
Job 3: Humanize it.
Data makes the problem credible. A human being makes it real.
The most effective problem slides pair a specific, quantified statement with a brief human portrait. Not a case study — a portrait. One sentence about the person who has this problem.
“Maria runs operations for a 60-person logistics company. Every Monday she spends three hours fixing errors that last week’s software created. She’s been doing this for two years. She knows there has to be a better way. There isn’t one. Yet.”
That’s five sentences, which is too long for a slide — but the idea translates into a single human image that makes the number stick. Investors remember people. They don’t remember market statistics.
The problem slide test
Before your problem slide leaves your laptop, run this test.
Read it out loud to someone who works in your target market. Not your co-founder. Not your advisor. Someone who is your actual potential customer.
Watch their face.
If they nod — if their expression shifts to recognition, if they say “oh god yes” or “that’s exactly what we deal with” — you have a problem slide.
If they tilt their head — if they ask a clarifying question, if they say “interesting” with a slight pause — you have a draft. Go back.
If you don’t have access to a target customer right now, use this written test instead. Read your problem statement and ask: is this something my target customer complains about unprompted? Would they bring this up if I asked them about their biggest frustrations at work? Would they describe it using the same words I used?
If the answer to any of those is no, the slide isn’t ready.
What a strong problem slide looks like — examples
Weak: “The hiring process is broken for both candidates and companies.” Why it fails: Too broad. Universally known. No specificity, no quantification, no human portrait. Could be on anyone’s deck.
Stronger: “Engineering managers at high-growth startups lose an average of 6 weeks per open role to a hiring process built for enterprise companies with dedicated HR teams they don’t have.” Why it works: Specific target (engineering managers at high-growth startups), specific pain (6 weeks), specific cause (process mismatch), implied solution (something built for their reality).
Weak: “Small businesses can’t access the same financial tools that large companies use.” Why it fails: Observation, not problem. Nobody feels pain reading this.
Stronger: “A 10-person e-commerce company gets rejected for a business credit card 73% of the time — not because their business is failing, but because the approval criteria were written for businesses 10 times their size.” Why it works: Specific number (73%), specific human situation (rejection), specific injustice (wrong criteria), immediate emotional response.
Weak: “There is no good solution for remote team communication.” Why it fails: This was Slack’s problem in 2013. In 2026 it’s not a credible problem statement. Also vague.
Stronger: “Customer success teams at B2B SaaS companies spend 40% of their time in tools designed for sales teams — answering questions those tools were never built to help them with.” Why it works: Specific role, specific percentage, specific cause, clear solution space.
Common problem slide mistakes
Describing the symptom instead of the cause. “Our customers are losing revenue” is a symptom. The problem is what’s causing them to lose revenue. Investors want to fund solutions to causes, not band-aids for symptoms.
Making the problem about the market instead of the customer. “The $200B logistics industry is inefficient” is a market observation. “Individual freight brokers spend 4 hours per day on manual tracking calls that could be automated” is a customer problem. Fund the latter.
Using jargon that only insiders understand. Your problem slide will be read by generalist investors who may not know your industry. If understanding the problem requires industry knowledge, you need to add one sentence of context. But keep it brief — context is not the problem statement.
Combining two problems into one slide. Pick the primary problem. The one that, if solved, makes everything else easier. If you have two problems, you probably have two products — and that’s a different conversation.
Being too abstract. “Innovation is slow in enterprise software” is abstract. “The average enterprise software procurement cycle takes 18 months — meaning companies are buying solutions to problems they had 18 months ago” is concrete. Same idea, completely different emotional impact.
The problem slide in the context of the full deck
Your problem slide does not exist in isolation. It sets up everything that follows.
A strong problem slide makes the “Why Now” slide feel urgent rather than arbitrary. It makes the solution slide feel inevitable rather than promotional. It makes the market size slide feel credible rather than theoretical.
Think of the problem slide as the first domino. If it falls cleanly, the rest of the deck has momentum. If it doesn’t fall — if investors don’t feel the problem — every subsequent slide is pushing uphill.
This is why fixing a weak problem slide is almost always more valuable than fixing any other slide. Fix the foundation. The rest gets easier.
FAQ
How long should my problem slide be? One to three sentences maximum. One is ideal. If you need three, make sure each sentence earns its place — no filler, no context that the slide doesn’t need.
Should I use a statistic or a story? Both if you can fit it cleanly. The statistic makes it credible. The story makes it memorable. If you can only do one, use the statistic — investors are more persuaded by data than anecdote, especially at first read.
What if my problem is hard to quantify? Find a proxy. If you can’t measure the problem directly, measure its consequences. Time lost, money spent on workarounds, frequency of occurrence, rate of failure. Something is always measurable.
Can I have two problem slides? Generally no. Two problem slides signal two products or an unclear focus. If you genuinely have two distinct problems, structure them as cause and consequence on one slide — not as two separate problems.
What if investors already know the problem? Don’t skip the slide. Even if the problem is well known, your specific framing of it reveals how you think. The angle you choose — which customer, which consequence, which number — communicates your insight about the market.
The Pitch Deck Guide includes Duygu’s complete Problem Clarity framework — the exact methodology used across dozens of funded decks. Slide-by-slide, with real examples. One-time purchase, instant access.
Get the Pitch Deck Guide — $297
Written by Duygu Dulger, founder of Deck Studio and pitchdeckguide.com. I’ve built pitch decks for founders across 30+ countries raising from pre-seed to Series A.
