How to Write the Problem Slide on Your Pitch Deck

The problem slide is the most important slide in your pitch deck. It sets up everything that follows — the solution, the market, the business model, and the ask. If an investor does not believe the problem is real, painful, and widespread, nothing else in your deck will land. If they do believe it, they will lean forward for the rest of the presentation.

Most founders get the problem slide wrong in predictable ways. They describe a problem too abstractly, too technically, or too broadly. They confuse a market observation ("the logistics industry is fragmented") with a felt problem ("small trucking operators spend 12 hours a week doing paperwork that could be automated"). This guide explains how to write a problem slide that works.

The One Test Every Problem Slide Must Pass

Before writing a single word, apply what YC partner Paul Graham calls the "hair on fire" test. Would someone with this problem drop everything to try your solution the moment they heard about it? A vitamin problem is nice to have — someone might solve it someday when they get around to it. A painkiller problem creates urgency. A "hair on fire" problem is one where the customer is desperate.

The problem slide must establish that your target customer has a hair-on-fire problem. Not a mild inconvenience. Not a general inefficiency. A specific, recurring pain that costs time, money, or both — and that existing solutions fail to address adequately.

What Belongs on the Problem Slide

The best problem slides do three things: they identify the specific person who has the problem, they describe the pain in concrete terms, and they establish that the problem is large enough to matter. You do not need all three elements in a single slide if the narrative across your first three slides delivers all of them — but all three must be present somewhere before the solution slide.

Specific person. "Small business owners" is too broad. "Restaurant owners with three or fewer locations who manage inventory manually" is specific. Specificity signals that you have done customer research. Investors know that vague problem definitions usually mean vague product thinking.

Concrete pain. Quantify the cost wherever possible. "Restaurants waste an average of 4-8% of food revenue on spoilage because inventory is tracked manually" is a problem statement. "Inventory management is inefficient" is an observation. The difference is whether an investor can immediately picture a real business owner experiencing real pain.

Scale. The problem has to exist at a scale that justifies a venture-funded company. The classic way to signal this is with a data point — number of businesses, annual spend on workarounds, or size of the market currently trying and failing to solve this problem.

Four Problem Slide Formats That Work

The statistic + story format. Open with a striking number, then make it human with a customer vignette. "43% of small business owners say cash flow management is their biggest operational challenge. Maria runs a three-person catering company in Austin. She loses two or three jobs every quarter because she can't offer net-30 payment terms to corporate clients without risking her ability to pay suppliers." The statistic establishes scale; the story creates empathy.

The before/after format. Show the current painful workflow on the left side of the slide, the desired state on the right. This works especially well for tools that replace manual processes — accounting, document review, scheduling, compliance. Keep each side to three to five bullet points.

The cost quantification format. Lead with the dollar cost of the problem. "U.S. companies lose $1.8 trillion annually to employee disengagement. For a 200-person company, that translates to approximately $1.1 million in lost productivity per year." This works when the problem has well-documented economic cost and your target buyer cares primarily about ROI.

The single customer quote format. A single, powerful quote from a target customer — ideally one the investor can imagine encountering — can carry an entire problem slide. "I spend 90 minutes every morning reconciling last night's sales data by hand. My accountant calls it the most expensive spreadsheet in the city." Only use this format if the quote is real, specific, and universally relatable to your target audience.

What Does Not Work on a Problem Slide

Jargon. If your problem slide requires the reader to understand industry terminology to grasp why the problem matters, you will lose investors who don't have that background. Your solution slide can use jargon if necessary; the problem slide should not.

Vague market observations. "The market is fragmented," "legacy solutions are outdated," and "the industry hasn't been disrupted" are the most common weak problem formulations. These observations may be true but they do not establish pain. Fragmentation is not pain. Outdated software is not pain. The cost of fragmented, outdated software on a specific user's productivity — that is pain.

Competitor bashing. The problem slide is not the place to criticize competitors. It is the place to establish that a problem exists. Why existing solutions fall short belongs in the competitive analysis slide or the solution slide.

Your solution embedded in the problem. A common mistake is letting your solution creep into the problem slide. "There is no easy way to do X, which is why we built Y" should be two slides. Keep the problem slide purely about the problem. Make the investor sit with the pain for one full slide before you offer relief.

Learning from the Best

Airbnb's 2009 problem slide established three things on a single slide: 1) Price: hotel rooms are expensive. 2) Experience: hotels are impersonal. 3) Supply: millions of untapped rooms exist in people's homes. Three data points, zero jargon, immediately understood by anyone who had ever stayed in a hotel.

Stripe's problem framing — at a time when setting up online payments required dealing with banks, payment processors, and fraud management — distilled the problem to a number: it took the average developer six months to set up payment processing. One metric. Everyone who had tried to build a payments integration understood immediately.

Square's problem slide showed a small business owner unable to accept credit cards because the hardware cost $400 and required a merchant account. The problem was visible in the product photo: a $0 card reader plugged into an iPhone headphone jack. Sometimes the solution communicates the problem better than any words.

Testing Your Problem Slide

After you write your problem slide, run two tests. First, show it to someone who has never heard of your company and ask them to describe the problem back to you in their own words. If they can't, the slide is not clear enough. Second, show it to a target customer and ask if they recognize themselves in the problem description. If they say "yes, that's exactly my situation," you have found the language that will resonate in investor meetings as well.

A well-written problem slide does not require an explanation. It does not require you to say "let me explain why this is a problem." The investor should feel the problem before you say a word.

Connecting Problem to the Rest of Your Deck

The problem slide is the foundation your entire deck is built on. The solution slide answers it. The market size slide quantifies how many people have it. The traction slide shows that customers have already started paying to solve it. The team slide explains why your founders understand it better than anyone else.

If your problem slide is weak, every other slide suffers. If it is strong, every slide that follows feels like the inevitable consequence of an obvious truth.

Pitchgrade's pitch deck review tool provides structured feedback on whether your problem slide is specific, credible, and scalable — the three qualities that determine whether your deck gets a reply.