Ask a room full of sales reps about the 10/20/30 rule and most of them can recite it without pausing: ten slides, twenty minutes, thirty-point font. Guy Kawasaki's formula has survived close to two decades of presentation advice for a reason — it's memorable, it's specific, and it forces discipline onto people who'd otherwise build a forty-slide monster. So why does following it to the letter so often produce a B2B sales deck that quietly underperforms?

Because the rule was never written for what a B2B sales deck actually has to do.

The Rule Was Built for a Room You're Not In

Kawasaki designed 10/20/30 for venture pitches — a founder, live, in front of investors, for a fixed slot of time. Every assumption baked into the rule depends on that setup: one audience, present at once, hearing the pitch delivered by the person who built it. Thirty-point font works because someone is narrating the details out loud. Twenty minutes works because that's the meeting length. Ten slides works because that's what a single sitting can absorb.

A B2B sales deck rarely gets that room. In my experience building decks for sales teams across very different sales motions, the far more common path looks like this: you present to two people, they like it, and then it gets forwarded to a VP who wasn't there, a procurement lead who skims it during a commute, and a technical evaluator who reads only the slides relevant to their function. Nobody in that second wave hears your narration. They read the deck cold, out of order, sometimes weeks after your live pitch.

Gartner's research on B2B buying behavior puts a number on why this matters: buyers spend only a small share of their total purchase time actually meeting with vendors, and when they're comparing several suppliers at once, any single vendor gets an even thinner slice of that time. Most of the buying process happens without you in the room — which means the version of your deck that survives isn't the one you presented, it's the one that gets read unaccompanied.

Twenty Minutes Assumes One Meeting. B2B Sales Has Many.

The time constraint in Kawasaki's rule assumes a single, bounded pitch slot. A B2B sales cycle isn't one meeting — it's a sequence of them, often with different subsets of a buying committee in the room each time, and frequently with the same deck reused, trimmed, or annotated between sessions.

This is where a flat twenty-minute target stops being useful and starts being a constraint that fights the sale. A discovery-stage deck genuinely might run under twenty minutes. A late-stage deck presented to a technical evaluation team, where the audience wants proof of integration depth and security posture before they'll sign off, often needs more room than that — not because the presenter rambles, but because skipping the proof to hit a time target just moves the same questions into a slower, less controlled follow-up email thread. The number that should scale isn't slide count. It's how much unaccompanied reading the deck needs to survive at each stage.

Thirty-Point Font Is a Rule for a Narrator, Not a Reader

This is the part of 10/20/30 that causes the most quiet damage in B2B contexts. Kawasaki's font rule exists so a founder doesn't read text off the screen at investors — it forces spoken delivery. But a deck built at thirty-point font, stripped down to headline phrases, is nearly useless to the procurement lead or technical stakeholder who receives it as a forwarded PDF with no narrator attached.

I wouldn't recommend abandoning restraint altogether — a slide crammed with paragraph text is its own failure mode, competing with whatever the presenter is saying in the room. But a B2B deck usually needs to do two jobs at once: work live, with a presenter narrating the headline point, and work cold, with enough supporting detail in smaller type or a caption that a reader encountering it alone can reconstruct the argument. Some sales teams solve this by keeping two versions — a lean live deck and a denser "leave-behind" — but that doubles the maintenance burden and the two versions tend to drift out of sync within a quarter. The more durable fix is building each slide with a headline claim large enough to carry the live pitch, and a smaller supporting line underneath dense enough to carry the slide once you're gone.

What Actually Determines Whether a B2B Deck Works

If slide count, meeting length, and font size aren't the right constraints, what replaces them? The more useful question isn't "how short can this be," it's "can this deck make its case to someone who never met me."

The habit that transfers best from consulting-style decks is writing each slide title as a claim, not a label — a sentence a reader can absorb without opening the chart underneath it. Stack just the titles end to end and read them as a paragraph. If they don't form a coherent argument on their own, the deck has a structural problem that no amount of trimming to ten slides will fix, and no amount of padding to twenty-five will either.

The second habit worth borrowing is treating every claim as something that has to survive being read without you. That means the cost-of-inaction slide states an actual number, not a vague "the problem is expensive" line the presenter was going to explain verbally. It means the proof slide names what was validated and how, not just a client logo grid. A deck that only makes sense with narration attached is a deck that dies the moment it gets forwarded — and in B2B sales, it almost always gets forwarded.

The Structure That Replaces a Fixed Slide Count

Rather than a hard number, a B2B sales deck tends to hold up when it moves through a sequence where each section earns the next one:

  • The cost of the current approach — specific enough that the reader recognizes their own situation
  • Why that cost persists — the gap competitors or internal fixes haven't closed
  • What changes with your approach — stated as an outcome, not a feature list
  • Evidence it holds up — proof relevant to the stakeholder reading this particular version
  • What adoption actually requires — timeline, effort, and who does what
  • The specific next step — not "let's discuss," but a named action and date

Some of these compress into a single slide for an early-stage pitch. For a technical stakeholder reading the deck alone three weeks into evaluation, the evidence section might need to expand into several. The sequence stays the same; the depth at each stage is the variable, and that variable should track who's reading it and when in the cycle they're reading it — not a fixed number decided before you knew either.

Where a Fixed Number Still Earns Its Place

None of this means structure doesn't matter, or that a forty-slide deck is fine because "context is complicated." The same logic that applies to fundraising decks applies here: a slide only belongs if it answers the question the previous one raised, and padding toward a round number is exactly as damaging as cutting something essential to hit one. The discipline behind 10/20/30 — don't add a slide just because you have the material — is worth keeping. It's the specific numbers that stop being load-bearing once the audience stops being a single room.

The same applies to the one part of a B2B deck every reviewer eventually gets to: the growth or traction proof. Picking the one metric the rest of the pitch actually depends on, rather than stacking several charts that each dilute the others, matters just as much in a sales context as it does when pitching investors — a buying committee reading the deck cold will remember one number, not four.

Building for the Meeting You Won't Be In

Kawasaki's rule isn't wrong so much as it's answering a question B2B sales rarely asks. The better test for a sales deck isn't whether it fits ten slides or twenty minutes — it's whether it still makes sense to someone reading it alone, out of order, without you there to fill in the gaps verbally.

Next time you're building one, try reading your deck start to finish as if you'd never seen it before and nobody's in the room to explain it. Whatever breaks in that read-through is the actual problem — the slide count was never it.