Problem and Solution Slides in a Pitch Deck: How to Write Them (with Examples)

What You'll Learn

• ✓Frame the problem in the ideal customer's voice with specific pain and cost
• ✓Write a solution slide that describes what changes for the customer, not just what the product does
• ✓Evaluate problem/solution fit from an investor's perspective
• ✓Avoid the five most common mistakes on these slides
• ✓Apply the patterns to your own deck with before/after examples

Direct Answer: The Job These Two Slides Do

Investors spend 4-7 seconds per slide on a first-pass read. The Problem and Solution slides have 8-14 seconds combined to convince them the space is worth investing in. These slides are not where you describe your product in detail — that comes later. They are where you answer one question: 'Is this a real, big, specific problem that someone is willing to pay to solve?' The Problem slide should accomplish three things: (1) name the specific customer who has this problem, (2) describe the pain in concrete, quantifiable terms, and (3) establish that current solutions are inadequate. The Solution slide should accomplish two: (1) describe the transformation — what changes in the customer's life — and (2) hint at why your approach is defensibly better, without getting into technical detail. The single biggest mistake on these slides is abstraction. 'Small businesses struggle with cash flow' is a problem only at the level of abstraction where it's been known for a century. 'Landscaping companies with 3-8 employees wait 45-60 days for customer payments while paying weekly payroll' is a problem that narrows the investable space into a knowable market. The second biggest mistake is describing the product as the solution. 'We built an AI cash flow tool' is a product. 'Landscapers get paid on day 3 instead of day 50' is a solution. Investors are evaluating the gap you create in the customer's life, not the technology you use to create it.

What the Problem Slide Must Establish

The Problem slide establishes four claims, explicitly or implicitly: 1. A specific customer exists and is knowable. This is the ICP (Ideal Customer Profile). Not 'small businesses' — 'bookkeeping firms with 3-15 employees serving residential real estate clients in secondary markets.' The narrower the ICP, the more testable and investable the thesis. Broad ICPs signal that you haven't done the customer discovery. 2. The pain is significant and quantifiable. Investors want a number: 'costs 14 hours per week,' 'results in 20% revenue loss,' 'increases churn by 8 percentage points,' 'requires hiring a $70K/year specialist.' Without a number, the pain feels hypothetical. With a number, investors can model the willingness to pay. 3. The pain is repeated, not one-time. Subscription businesses require recurring pain. If your problem is 'buying a house is stressful,' customers buy houses every 7-10 years — hard to build a SaaS company. If your problem is 'payroll is run every two weeks,' customers feel pain 26 times per year. 4. Current solutions are inadequate for specific reasons. 'Spreadsheets' is not a solution; it's a workaround. 'QuickBooks' is a tool customers already have but doesn't solve this specific problem. Show you understand the existing alternatives and why they fall short — this proves you've done the work. Weak problem slide: 'Small businesses struggle with invoicing. Many use spreadsheets. This is inefficient and error-prone. Better tools are needed.' Strong problem slide: 'Landscaping companies (2-15 employees, $500K-5M revenue) send 200-500 invoices per month manually, wait 45-60 days for payment, and write off 3-5% of revenue to collections. Most use QuickBooks for accounting but manage invoicing in a mix of spreadsheets, paper notebooks, and text messages — resulting in 8-12 hours per week of admin time per owner and an estimated $15K-$80K per year in uncollected invoices.' The strong version is longer but investable. The weak version could describe 400 different companies.

What the Solution Slide Must Establish

The Solution slide establishes three claims: 1. What specifically changes for the customer. Not what the product does — what the customer's life or business looks like now. 'Landscaping owners close their week in 20 minutes instead of 8 hours' is a solution claim. 'Our platform uses AI to automate invoicing' is a product claim. 2. The magnitude of improvement. Quantify. '10x faster,' '70% reduction in DSO,' 'from 8 hours to 20 minutes,' '$40K in recovered revenue per year.' Investors model the value proposition; without numbers, they can't. 3. A signal of defensibility. You're not explaining your technical moat yet (that's a later slide). But your solution should hint at WHY your approach is harder to replicate — 'first vertical AI trained on landscaping-specific terminology,' 'integrations with 12 trade-specific software stacks,' 'network effects from connecting landscapers to customer payment platforms.' One phrase of defensibility prevents the 'why can't Intuit just build this?' concern from forming. Weak solution slide: 'Our AI-powered platform automates invoicing for small businesses. It saves time and reduces errors. Integrates with QuickBooks.' Strong solution slide: 'GreenFlow connects landscaping companies to their customers through an AI platform that generates, sends, and collects invoices automatically. Customers pay in 3-7 days on average (vs. industry 45-60 days). Owners spend 20 minutes per week on invoicing (vs. 8-12 hours). Integrated payment processing and Net-15 financing reduce A/R writeoffs to under 1%. Built on proprietary NLP trained on 2M landscaping job tickets.' The strong version communicates the transformation (3-7 days vs. 45-60), the magnitude (20 min vs. 8-12 hours), and the defensibility (proprietary NLP on industry-specific data) — all in under 80 words.

Using the Customer's Voice

The most powerful problem slides use direct customer quotes. Not paraphrased pain — actual words the customer used. Weak: 'Our customers report significant frustration with invoicing.' Strong: "'I spend every Sunday night from 7pm to midnight doing invoices. By the time I'm done, I'm too angry to eat dinner with my wife.' — Mike, owner of Green Peak Landscaping, Atlanta GA, 6 employees" The quote does several things simultaneously: - Proves you've talked to real customers - Names a specific ICP ('Mike, landscaping owner, Atlanta') - Establishes emotional weight (Sunday night, too angry to eat) - Implies scale (this is one of dozens you've interviewed, not your cousin) Investors read customer quotes and immediately think: 'How many Mikes are there?' If 10,000 landscaping companies in the US have an owner who spends Sunday nights doing invoices, the market is knowable and the pain is real. Three rules for customer quotes on the Problem slide: 1. Include the customer's name, company, role, and specific market. Anonymization reduces credibility. If the customer agreed to the quote, they'll agree to attribution. 2. The quote should be specific, not generic. 'I spend every Sunday night' is specific. 'Invoicing is hard' is generic. 3. Use the quote to frame the pain, not to validate the solution. A common mistake is using quotes that praise your product ('Green Peak says they love GreenFlow'). Those belong on a Traction or Customer Love slide. Problem-slide quotes should describe the before state. Where to find quotes: 20+ customer discovery interviews before fundraising. If you haven't done these interviews, you're not ready to raise. Alternate: use aggregate data from a customer survey. 'In a survey of 147 landscaping owners, 82% said invoicing consumed more than 6 hours per week; 63% described it as their most-hated recurring task.' The survey number can substitute for an individual quote if you prefer statistical framing, but the individual voice usually lands harder.

The Five Most Common Mistakes

Mistake 1: Problem is too broad. 'Small businesses need better software.' This is true at such a high level of abstraction that no investor can evaluate it. Narrow to a specific ICP with specific pain. If you can't narrow, you haven't done enough customer work. Mistake 2: Solution is a feature list. 'Our platform includes: AI invoicing, payment processing, customer portal, analytics dashboard, mobile app, API integrations, ...'. Investors don't read feature lists. They read for transformation: what does the customer's life look like after using this? If you list 8 features, you sound like a me-too product. If you describe 2 transformations, you sound like a focused company. Mistake 3: No customer voice. The founder describes the problem in third-person. 'Landscapers struggle with cash flow' vs. 'Mike (landscaper, Atlanta) waits 52 days for a $4,200 invoice while paying $3,800 in weekly payroll.' The second version is the same fact with the specificity that makes it investable. Mistake 4: Ignoring existing solutions. 'There is no solution to this problem today.' Almost always untrue. Customers have workarounds — spreadsheets, part-time hires, outsourced bookkeeping, accepting the pain. Naming the workarounds shows you understand the competitive landscape. Not naming them suggests you don't know, which makes investors assume the problem isn't that big. Mistake 5: Solution describes product, not transformation. 'We built an AI platform for invoicing.' So what? Investors want to know what changes for the customer. 'Landscaping owners close their books in 20 minutes instead of 8 hours — reclaiming 40+ hours per month that now goes to sales and family time.' That's the transformation. The product is the vehicle. Bonus mistake: using words that have lost meaning. 'AI-powered,' 'platform,' 'disruptive,' 'revolutionary,' 'seamless.' Every deck uses these words. They convey nothing. Use plain English that describes specifically what happens.

Pitch Deck Context: Where These Slides Fit

The standard 10-slide pitch deck (Guy Kawasaki's original framework, refined by Sequoia and others) places Problem at slide 2 and Solution at slide 3, right after the Title slide. This positioning tells you something: if you don't hook the investor on slides 2-3, they stop reading. Typical 10-slide structure: 1. Title — company name, tagline, your name, contact info 2. Problem — who has what specific pain 3. Solution — what changes for them 4. Market Size — TAM/SAM/SOM 5. Product — how the solution actually works (screenshots, demo) 6. Business Model — how you make money 7. Traction — metrics, customers, growth 8. Competition — landscape and differentiation 9. Team — why this team can execute this specific plan 10. Ask — how much you're raising, at what valuation, use of funds Timing on slides 2-3: A Sequoia pitch review of 350 decks found that 68% of rejections happened before slide 4. The Problem and Solution slides either open the investor's wallet or close it. There is no third outcome. Three implications: 1. Don't bury the lede. The most important sentence in your Problem slide should be the first sentence on the slide. Don't set up context for three bullets before naming the pain. 2. Design matters on these slides more than on later slides. A dense, word-heavy Problem slide loses the investor before they've read the pain. Use whitespace. Use one large customer quote. Use a single striking number ('Landscaping companies lose $4.2B/year in uncollected invoices'). 3. The Problem and Solution slides should foreshadow later slides. Problem should hint at market size (implying there are many Mikes). Solution should hint at business model (implying customers will pay for this specific outcome). This layered storytelling makes each subsequent slide feel inevitable.

Before and After: Real Examples

Before — Problem slide (weak): 'Scheduling is broken for service businesses. Most use paper calendars or basic apps. This leads to inefficiency and customer dissatisfaction. Better solutions are needed for the modern service economy.' After — Problem slide (strong): 'Mobile mechanics (solo operators doing on-site oil changes, brake jobs, diagnostics) book 80% of their work via text. 30% of appointments are missed or rescheduled because customers lose the thread in their messages. A typical mechanic loses $1,200/month to no-shows and same-day cancellations — on $8,500/month gross revenue. Existing scheduling apps (Calendly, Acuity) require customers to download apps or use web portals the mechanic's 50-year-old customer base won't use.' Why the after is stronger: specific ICP (mobile mechanics, solo), specific behavior (text-based booking), specific pain (30% no-shows, $1,200/month loss), and specific reason existing solutions fail (customer demographics don't use app-based scheduling). Before — Solution slide (weak): 'Our platform uses AI to automate scheduling for service businesses. Features include: calendar sync, automated reminders, payment processing, and customer history. Easy to use and affordable.' After — Solution slide (strong): 'TextBook replaces the scattered text chain with a shared message thread that acts as the calendar itself. Customer books by replying with date/time via normal SMS. Mechanic confirms with one tap. Automatic reminders 24 hours and 2 hours before. No app download. No portal. Just text. Mobile mechanics report: no-shows down from 30% to 6%, scheduling time down from 12 hours/week to 90 minutes. $14K/year in recovered revenue.' Why the after is stronger: describes transformation (text stays text, no apps), quantifies magnitude (30% → 6%, 12 hours → 90 minutes), hints at defensibility (the ICP-specific insight — they won't use apps — is the moat), and ties back to the Problem slide numbers ($1,200/month → $14K/year). This pattern repeats across verticals. The specific details change, but the structure — specific ICP, quantified pain, named workarounds, transformation-framed solution, defensibility hint, magnitude-matched numbers — is what makes the slides investable.

Check Your Understanding

More Guides