I read a lot of decks. (Context for what shapes the read: I'm an operator angel writing into UK scale-ups.) Most of them — like most decks generally — are fine but not differentiated. The ones that get a "yes, let's talk" reply within the first five minutes have a particular shape. Worth walking through what that shape looks like, because the standard advice ("clear, compelling, evidence-based") isn't specific enough to be useful.
The structure I'm describing isn't novel. Plenty of decks follow some version of it. What separates the decks that work from the decks that don't isn't the structure — it's what each slide is doing inside the structure.
In order.
Slide 1 — Cover
The cover does one job: tell me what the company is, in one line, in plain English.
What kills most covers is jargon. "We're an AI-native customer success platform for high-growth SaaS companies" is words. It doesn't tell me what the product does or who it's for. The cover that works tells me the founder has been forced to articulate the company in clear English to actual customers, repeatedly, and has found a description that lands.
A line like "We help mid-market software companies catch customer churn before it happens" is better. I know what it does. I know who it's for. I can immediately decide if I'm interested enough to keep reading.
Slide 2 — Problem
The problem slide should be specific enough to make me uncomfortable. Generic problems get generic dismissals.
If your problem slide says "customer success teams are overwhelmed", that's not a problem. That's a statement about the world that no operator can argue with and that gives me no purchase on whether your specific solution matters.
If your problem slide says "mid-market customer success teams typically have 1 CSM per 80 accounts and miss 60% of churn signals because they're triaging based on instinct, not data" — now I'm listening. That's a specific operational pain. I can see why someone would pay for the fix. I can see why the team that built the solution probably knows what they're doing.
The strongest problem slides include numbers from real customer interviews, not industry analyst quotes.
Slide 3 — Insight
The insight slide is the one most decks don't have, and it's the slide that, more than any other, determines whether I'm interested in the company at all.
The insight is the non-obvious thing the founder has learned about the problem that the rest of the market hasn't internalised yet. It's what makes this team's solution likely to work where others haven't. It's the thing that, if true, explains why the opportunity is real.
For example: "The reason CS tools haven't worked is that they're built for the AE-to-CSM handover, not for the post-handover lifecycle. We rebuilt the data model around the handover-to-renewal arc, and the signal density is 4x what previous tools could capture."
That's an insight. It's specific. It's testable. It tells me something I didn't already know about the problem. The team that has this slide has done the thinking. The team that doesn't, hasn't.
If you don't have an insight slide, the deck won't be worse for it — it just won't generate the immediate "yes". Most operators reading the deck are looking for this slide more than any other.
Slide 4 — Product
The product slide should be a screenshot, not a description.
Show me the actual interface. Show me the actual output. Don't describe the architecture. Don't describe the philosophy. Show me what the customer sees.
The strongest product slides have a single annotated screenshot with three or four callouts to the most important elements. The weakest product slides have feature lists, architecture diagrams, or — most fatally — mock-ups of features that don't exist yet.
If the product is at a stage where there's no real screenshot to show, say so. "We're pre-product, here's the prototype" is a more credible position than a polished mock-up that pretends to be the live thing.
Slide 5 — Traction
Whatever traction you have, show it specifically. If you have customer logos, show them. If you have ARR, show it. If you have engagement metrics, show them with units and dates.
The patterns that kill the traction slide:
Vanity metrics with no commercial signal. "1.2 million users" without any indication of revenue, retention, or commercial intent. Pre-monetisation early-stage companies get a pass on this. Anyone past 12 months in market doesn't.
Cherry-picked vanity comparisons. "We grew 300% YoY" off a base that wasn't disclosed. Nobody believes this without the base.
Logo dumps with no context. Twelve logos, no indication of which are paying customers, which are pilots, which are LOIs, which are friends-and-family.
The strongest traction slides are honest about the stage. "We have £40k MRR across 12 paying customers, growing 15% MoM, with 2 enterprise deals in late-stage procurement" is more credible than "On track to £1m ARR by year-end" — even though the second number is bigger.
Slide 6 — GTM
The GTM slide is where most decks fall apart and most investors decide. I've written separately about why distribution risk is the only risk worth spending serious time on at pre-seed. The GTM slide is where the founder gets to demonstrate they've thought about distribution.
What I want to see: the specific motion by which customers are acquired. Inbound from content, outbound to a defined ICP, partnerships with specific named partners, a marketplace, a viral loop. Pick one as the primary motion and explain why it works for this product, this stage, this market.
What I don't want to see: "We'll do content marketing, paid ads, partnerships, and outbound." That's not a strategy. That's a list. It tells me the founder hasn't worked out which channel is going to be the primary engine and is hoping that doing all of them will be enough. It almost never is.
Slide 7 — Team
Two questions the team slide should answer.
Why this team? Why are these specific people the right ones to build this specific company? The answer should be directly related to the problem and the insight. If the founders have spent years inside the problem, the team slide should make that clear.
Why now? What about the current market makes this the right moment to build this? This is sometimes a separate slide. If the deck has it, great. If not, the team slide should at least gesture at it.
What kills the team slide: a lineup of LinkedIn-grade biographies that don't connect to the company being built. "Senior at Google, Stanford MBA, ex-McKinsey" is fine but doesn't tell me whether this person is the right one for this specific problem.
Slide 8 — Ask
What you're raising, at what valuation, against what milestones. Specific numbers.
The decks that don't get a yes from me are sometimes the decks that don't include the ask. Founders sometimes leave it out, hoping to negotiate later. That reads to investors as not having decided. Decide. Put it in the deck. Be willing to explain why those numbers are the right numbers.
Closing thought
A deck of eight slides done well is enough. Most decks I see are 20-30 slides because the founder is trying to pre-empt every possible question. They'd be better off with eight strong slides and a follow-up call where the questions get answered properly.
If you've got a deck that hits these eight points and you're raising into the kind of UK scale-up that I write into, send it. The bar I apply is whether the eight slides — read in order — make me want to keep reading. If they do, we'll talk. If they don't, I'll tell you which of the eight needs work, which is more useful feedback than a generic pass.