A client emails back your 8-slide draft with one line: "This feels thin. Can we get it closer to 25?" You know the 8-slide version is stronger. You also know that saying so, flatly, is the fastest way to sound like you're protecting your own convenience instead of their outcome. So what actually happens next?

Most advice on this stops at "educate the client" or "trust the process," which is true and also useless the moment you're staring at a reply box. The more useful question isn't whether 8 beats 25. It's why the client landed on 25 in the first place — because that number is almost never really about slide count.

The client isn't attached to the number — they're attached to what it's covering for

Nobody wakes up wanting a 25-slide deck for its own sake. When a client pushes for more slides, it's usually standing in for one of three fears: that a stakeholder who isn't in the room will ask a question the deck can't answer, that leaving something out will read as "we didn't do the work," or that a competitor's deck looked more thorough. None of those fears are about slide count. They're about being caught unprepared in front of someone who wasn't part of the conversation you and the client have been having for weeks.

That's worth sitting with before drafting a response, because arguing "8 is better than 25" answers a question the client didn't actually ask. The real question is whether the deck can survive scrutiny it wasn't in the room for — and that's a solvable problem that has nothing to do with slide count.

The number is a symptom of a job the deck hasn't been assigned yet

A deck built for a single decision in a single sitting and a deck built to be reopened, forwarded, and picked apart later are doing two different jobs — and the slide count that's right for one is frequently wrong for the other. If the client's real audience is going to sit in a room and say yes or no on the spot, more slides usually dilutes the ask rather than strengthening it. If the deck is going to circulate afterward to people who weren't there, density stops being clutter and starts being the evidence those readers need to trust it without you in the room to explain it.

So the first real question to ask the client — before touching slide count at all — is what happens to this deck after the meeting ends. That single answer usually resolves the disagreement faster than any argument about ideal length, and it's the same distinction that decides whether a minimalist deck is actually helping or just hiding the proof someone needs.

Don't fight the number — split it into two documents

Here's where the tidy "just push back to 8" advice falls apart in practice: sometimes the client genuinely does need 25 slides' worth of material to exist, just not all of it delivered at 1-2 minutes per slide in a live room. The fix I've had the most success with isn't refusing the extra 17 slides. It's separating "what gets presented" from "what gets left behind."

  • Build the core deck to the length the room can actually absorb — for most 20-30 minute internal pitches, that's closer to 8-12 slides than 25.
  • Move the remaining material into a clearly labeled appendix: backup data, alternate scenarios, the detail a specific stakeholder is likely to ask about.
  • Present the core deck live. Hand over the full file, appendix included, so nothing the client worked on gets thrown away.

This works because it answers the client's actual fear — nothing got cut, it just got sequenced — without forcing the live audience to sit through 25 slides at 40 seconds each. It doesn't work when the deck has no live component at all and exists purely as a document someone reads cold; in that case the appendix split is unnecessary and you're better off just building the longer, denser version the client asked for.

Bring evidence instead of opinion into the conversation

"Fewer slides works better" lands as taste unless you can point to something outside your own preference. Dropbox's DocSend, which tracks how people actually interact with shared decks, found that pitch decks which went on to successfully raise funding held an investor's attention for over four minutes on average — while decks that failed to raise held attention for only about a minute and a half. That gap wasn't about slide count directly; it was about whether the deck earned continued attention once opened, and a deck padded to 25 slides to look thorough often loses that attention faster than a tight one does.

That statistic is worth bringing to the client precisely because it's not your opinion versus theirs — it reframes the disagreement from "designer preference" to "what actually holds a room." It's also exactly the kind of ammunition that matters most in front of executives, who — as it turns out — aren't judging slides on beauty or count at all; they're asking whether they can understand the point in ten seconds and use the slide to decide something. A 25-slide deck rarely passes that test better than a tight one does.

Sometimes 25 is genuinely the right number — and that's the complication

I wouldn't push this framework so far that "shorter is always right" becomes its own dogma, because it isn't. A board update going to people who'll pick it apart line by line, a technical handoff to an engineering team, a compliance review — these are jobs where 25 dense slides can outperform 8 clean ones, because the audience's job is to investigate, not decide in the room. The mistake isn't building a long deck for that audience. The mistake is building a long deck out of habit, for an audience that was only ever going to give it four minutes and a yes-or-no.

What actually separates a deck that earns its length from one that's just padded isn't the digit on the slide counter. It's whether every slide is there because the argument needed it, or because cutting it felt like leaving something out. That second reason is the one worth naming out loud with a client — not as a rule about numbers, but as the actual question behind the number they asked for.

Next time a client asks for more slides than the room can absorb, skip the debate about the right count entirely. Ask what happens to the deck after the meeting, and who's going to reopen it without you there to explain it. The slide count tends to answer itself once that's settled.