Who this is for
Pre-seed and seed founders writing slide 2 (the problem slide) for the first or second time, plus Series A founders rebuilding their deck for an institutional round. If your problem slide currently leads with your solution, your industry, or a quote from a trend report, this page is for you. If you've never been told to your face which slide killed a meeting, the problem slide is the most likely culprit, investors rarely volunteer that diagnosis but they almost always disengage here when they disengage early.
What investors look for
VCs spend less than 30 seconds on a problem slide. They are scanning for three things: a customer they recognize, a pain they can size, and a reason the pain has not already been solved. The slide is doing its job when an investor can repeat back, in their own words, who hurts and how badly without re-reading the slide. On the Deckmetric methodology this rolls up into the Captivate dimension of the CVM framework, specifically the customer-pain-credibility sub-score. Decks scoring 80+ on Captivate almost always name an ICP, quantify the cost, and give a one-line reason the problem persists.
Common mistakes
1) Problem-as-feature-gap: describing the problem as the absence of your product ("there's no good way to do X") signals nobody else cared enough to build it. 2) Problem-too-small: TAM math hinging on a pain only 200 companies feel, with no expansion path. 3) Problem-already-solved: closest analog is a $10/mo SaaS that 60% of your ICP already pays for, with no "why this is different" beat. 4) Customer-in-jargon: writing the pain in your terms ("poor data hygiene") instead of the customer's ("the rep loses two hours every Monday rebuilding the pipeline by hand"). 5) Unsourced numbers: a single "$48B problem" claim with no derivation reads as a content-marketing quote, not first-hand evidence.
Three template patterns that work
Pattern A, One-sentence + three beats: "<who> wastes <how much> doing <what> because <why>," followed by three single-line evidence beats (a customer quote, a status-quo cost, and a stat). Pattern B, Day-in-the-life: a four-line vignette of a named persona living the problem this morning, ending on the cost of the status quo. Pattern C, Before/after split: left half shows the workflow today (with a measurable cost in hours or dollars); right half shows the workflow with the underlying friction removed (no product mention, that's the next slide). All three patterns finish on a one-line answer to "why hasn't this been solved already?", that sentence is what separates a believable problem slide from a generic one.
How Deckmetric scores this slide
Inside the Deckmetric CVM rubric (full breakdown at /methodology), the problem slide rolls up into the Captivate dimension, specifically the customer-pain-credibility, problem-size-defensibility, and persistence-rationale sub-scores. Slides that name a specific ICP, quantify the cost of the status quo, and give a one-line reason the problem still exists typically score 80+ on Captivate. Slides written as feature-gaps or unsourced market headlines almost always score below 60 here, which alone is enough to drop the overall CVM headline below the 70 threshold investors expect. See the full rubric at /methodology to understand exactly how the sub-scores compose.