The Pitch Deck Problem Slide: How to Articulate Pain That Makes Investors Lean In

The Problem Comes First

Your investor does not care about your solution until they care about your problem. They do not care about your team until they understand what problem those people are solving. They do not care about your market size until they know whether that market is worth anything.

The Problem slide sets the frame for everything that follows. It establishes why your company exists. It establishes the prize. It establishes the urgency.

If your Problem slide fails to move the investor, nothing else matters. A perfect Solution slide, a massive market, and a world-class team all become irrelevant if the investor does not feel the problem in their gut.

What Makes a Good Problem Statement

A good problem statement has three qualities: it is specific, it is quantified, and it is felt.

Specific, Not Abstract

Abstract: "Businesses waste time on manual processes."

Specific: "UK mid-market accountancies spend 40 per cent of their time on manual reconciliation instead of client advisory work."

Abstract problems are forgettable. They apply to everyone and no one. Specific problems stick because they apply to a particular group of people in a particular situation doing a particular task.

Quantified

A good problem statement answers three questions:

Frequency: How often does this problem occur? Daily? Weekly? Quarterly?

Magnitude: What is the cost, in time or money, each time the problem occurs?

Population: How many people or organisations experience this problem?

Example: "A 200-person software company spends 80 hours per quarter on manual access provisioning (frequency). Each hour costs the company 75 pounds in lost productivity (magnitude). There are 50,000 software companies in the UK between 100 and 500 people (population). This means the total addressable market for access management is roughly 300 million pounds per year."

That is quantification. You have taken something abstract (manual access provisioning wastes time) and made it concrete (it costs 300 million pounds per year across the UK market).

Felt, Not Just Understood

A good problem statement makes the investor feel the problem. Not just understand it intellectually. Feel it.

Intellectual: "Accountants spend time on manual reconciliation instead of advisory work."

Felt: "Sarah is a partner at a mid-market accountancy. She knows her firm has the expertise to do high-value advisory work for clients. But instead of doing advisory work, she spends 40 per cent of her week manually reconciling invoices. This means her firm leaves money on the table. She is frustrated. Her team is frustrated. Every reconciliation error makes her look bad to clients."

The felt version puts the investor in the shoes of the customer. It explains not just the economic problem but the emotional problem. The problem of doing work you do not want to do instead of work you do want to do. The problem of leaving money on the table.

Quantifying the Pain

Investors think in numbers. Specifically, they think in numbers that translate to market size. If you cannot quantify your problem, you cannot convince them that your market is large enough to be worth their time.

Time Cost

Convert wasted time into pounds.

Example: "Sales reps at enterprise software companies spend 12 hours per week on manual CRM data entry instead of selling. At a fully loaded cost of 120 pounds per hour, that is 90,000 pounds per year of lost selling time per 50-person sales team."

A VC reads this and thinks: "Okay, so a 50-person sales team costs the company 90,000 pounds per year in lost selling efficiency due to CRM data entry. That is a material cost. A buyer would pay to solve this."

Error Cost

Quantify the cost of errors.

Example: "Manually entered customer data has a 5 per cent error rate. For a SaaS company with 10,000 customers, that is 500 customers with incorrect information in the billing system. Each error costs the company 500 pounds in lost revenue, refunds, or customer churn. That is 250,000 pounds per year."

Opportunity Cost

Quantify what a customer cannot do because they are stuck solving the problem.

Example: "A product manager at a mid-market SaaS company spends 30 per cent of her time manually updating spreadsheets instead of analysing customer data to inform product roadmap decisions. If she spent this time on product strategy, the company could ship 20 per cent more valuable features. At an average SaaS company, this translates to 500,000 pounds in incremental annual recurring revenue left on the table."

Frequency Multiplication

Take the unit cost of the problem and multiply by how often it occurs.

Example: "Every time a contract amendment is processed, it takes 8 hours of legal review. A typical enterprise processes 200 contract amendments per year. That is 1,600 hours per year of legal time. At a cost of 250 pounds per hour for legal staff, that is 400,000 pounds per year."

The Before/After Frame

One of the most powerful ways to articulate a problem is to show the before state and the desired after state. This frame makes the problem emotionally clear and explains why someone would care about fixing it.

The Before State

Describe what the customer's world looks like when they are experiencing the problem.

Example: "Before: Our customer, a fast-growing SaaS company, has 15 different tools for HR, recruiting, onboarding, and payroll. When a new employee is hired, HR has to manually enter their information into each system. This takes six hours. During that time, the new employee cannot access email, software licenses, or office equipment. Onboarding is delayed. The employee's first week is chaotic."

The After State

Describe what the customer's world looks like when the problem is solved.

Example: "After: The customer connects their recruiting tool, HRIS, payroll, and equipment management to our system. When a new hire is marked as hired in the recruiting tool, all systems are automatically updated in real-time. The new employee gets their email and software licenses before their first day. Equipment is ordered and waiting. Onboarding is smooth."

Why Before/After Works

Before/after frames work because they contrast two states. The investor can see what is broken and what could be. This gap between current state and desired state is the entire reason your company exists.

Customer Evidence

The strongest Problem slides include evidence from actual customers or potential customers that the problem is real and urgent.

Customer Quotes

Include a quote from a customer or prospect describing the problem in their own words.

Example quote: "We spend 40 hours per week on manual data entry across our four finance team members. It is tedious, error-prone, and keeps us from doing the analysis work that actually creates value for the business." – CFO, mid-market SaaS company

A quote from a real customer is more credible than a statement from you. It shows that you have talked to customers. It shows that the problem is real.

Customer Count

If you have talked to customers, say so. Even at the seed stage.

Example: "We have spoken to 50 CRO leaders at enterprise software companies. Every single one cited CRM data entry as one of their top three operational frustrations."

Evidence of Searching for Solutions

Show that customers are already trying to solve this problem with workarounds or existing tools.

Example: "Customers told us they have tried three different spreadsheet-based systems, two automation tools, and one bespoke integration to solve this problem. None of them have worked well enough that the problem goes away."

This is powerful because it shows that customers care enough to spend money and time on solutions, even imperfect ones. It means they will care about your solution.

Strong vs Weak Problem Slides: Examples

Weak Problem Slide

Headline: "Sales teams spend too much time on manual CRM data entry."

Body: "CRM data entry takes time away from selling."

Why it is weak: Vague. Does not quantify. Does not feel like a real problem. Does not specify which sales teams or which CRMs. An investor reads this and thinks "so what?" and moves on.

Strong Problem Slide

Headline: "Sales reps at enterprise software companies spend 12 hours per week on manual CRM updates instead of selling. That is 90,000 pounds per year of lost selling time per 50-person team."

Body: "We spoke to CROs at 20 enterprise software companies. Every single one said that CRM data entry is their top operational frustration. The typical comment: 'My reps know they should update the CRM immediately, but it is painful and slow, so they do it at the end of the day. By then, context is lost, accuracy suffers, and deals slip through the cracks.'"

Why it is strong: Specific (enterprise software companies, 12 hours per week). Quantified (90,000 pounds per year). Felt (context is lost, deals slip through cracks). Evidenced (20 companies said this is their top frustration). An investor reads this and thinks "okay, this is a real problem that costs real money and affects real companies."

Another Strong Example

Headline: "Manual invoice processing costs mid-market accounting firms 400,000 pounds per year in lost billable hours and reduces cash collection by 15 per cent."

Body: "The typical mid-market accounting firm (20-50 partners) processes 500 invoices per month. Each invoice requires: manual data entry (20 minutes), review by a partner (10 minutes), follow-up for payment (15 minutes per invoice on average due to late payments). That is 22.5 hours per invoice on average. At a billable rate of 250 pounds per hour, that is 5,625 pounds of cost per invoice, or 2.8 million pounds per year in total cost for invoice processing. The average firm only recovers 1.5 million pounds of this through billable hours (because customers will not pay for invoice work). The remaining 1.3 million pounds is absorbed as overhead. Additionally, late collections are a significant problem: the average invoice takes 45 days to collect (vs 30-day terms). This delays cash and creates working capital pressure."

Why it is strong: Specific (mid-market accounting firms, 500 invoices per month). Detailed quantification (22.5 hours per invoice, 250 pounds per hour billable rate, 2.8 million pounds per year cost). Addressed multiple pain points (time cost, cash collection delay). Clear economic impact (1.3 million pounds absorbed as overhead).

Common Problem Slide Mistakes

Mistake 1: Identifying a Problem That Is Not Painful Enough

Not all problems are worth solving. A VC looks at a problem and thinks: "Would a buyer pay to solve this? How much would they pay?"

If the answer is "maybe 500 pounds," it is not a venture-scale problem. If the answer is "500,000 pounds or more," it is venture-scale.

The rule of thumb: the problem must cost the buyer more than 50,000 pounds per year to justify the sales conversation and implementation cost of a SaaS solution.

Mistake 2: Being Too Broad

Bad: "Businesses waste time."

Good: "E-commerce companies with 50-500 employees spend 30 per cent of their operations team's time on manual inventory reconciliation."

Broad problems apply to everyone and therefore to no one. Specific problems are more credible and more memorable.

Mistake 3: No Evidence

If you have not talked to customers about this problem, say so. But if you have, show it. A quote, a customer count, a story. Something that proves the problem is real.

Mistake 4: Making It Personal Instead of Economic

Bad: "Developers hate writing tests."

Good: "When developers do not write tests, production bugs cost the company 100,000 pounds per incident (downtime, customer churn, reputation). At a typical 50-person engineering team, there are 10-15 production incidents per year caused by insufficient test coverage."

A VC does not care if developers hate writing tests. A VC cares if insufficient testing costs the company 100,000 pounds per incident.

Mistake 5: Solving a Problem That Is About to Be Solved by Someone Else

If the problem is being addressed by a much larger company, tread carefully. A VC might think "why should I invest in you when Google, Microsoft, or Salesforce will solve this themselves?"

Acknowledge this directly in your Why Now slide. Explain why a big company has not solved this yet, or why their solution is inadequate for your target market.

The Psychological Impact of a Great Problem Slide

A great Problem slide does something specific to the investor's brain. It creates tension. It creates a gap between the current state (broken) and the desired state (fixed). Your entire pitch deck is the story of how you close that gap.

When an investor finishes your Problem slide, they should want to know: "How is this company going to fix this? What is the solution? Why are they the ones to do it?"

That is when you move to the Solution slide. You have already won their attention. Now you need to hold it.