I Read Three SaaS Onboarding Decks Cover to Cover. None of Them Taught Discovery.

Three sales onboarding decks landed in my inbox this month, from three different SaaS companies at three different growth stages, sent by three different ops leaders who all asked some version of the same question: does this look right? I read all ninety-plus slides of each, cover to cover. Between them: forty-one slides on product architecture, twenty-six on pricing and packaging, eighteen on competitive positioning, a dozen on "objection handling" that were really just rebuttal scripts to memorise. Across all three decks combined, I found four slides that mentioned discovery calls at all — and every one of those four was a bullet list of "good questions to ask," with no rubric, no grading criteria, and no distinction between a question that opens a conversation and one that just fills airtime before the pitch.

What ninety slides actually teach

Lay all three decks side by side and the shape is nearly identical, which tells you this isn't three companies making the same mistake independently — it's the industry-standard template.

Ninety-one slides, on average, and roughly one of them touches the single skill that determines whether any of the other information ever gets used well. A rep who knows the product cold and can recite the competitive battlecard from memory is still guessing in the first six minutes of a discovery call, because nobody taught them how to run one — only what to say if the prospect brings up a competitor by name.

Why this keeps happening

It's not that anyone decided discovery doesn't matter. It's that discovery is hard to put in a deck. Product features are static and slide-able — a screenshot, a bullet list, done. Discovery is a live, adaptive skill that changes shape depending on what the buyer says back, and a slide deck is a genuinely bad medium for anything that requires a response to another human being. So onboarding defaults to teaching what fits the medium — product, pricing, competitive facts — and quietly assumes discovery will get picked up by osmosis, from shadowing calls or absorbing a manager's style. Some reps do pick it up that way. Most don't, and the ones who don't rarely find out until they're already carrying a full quota and the gap shows up as a stalled pipeline instead of a training gap.

The four things a features walkthrough can never provide

A deck can teach a rep what your product does in an afternoon. It cannot teach discovery, because discovery isn't information to transmit — it's a skill to build. Here's what an actual discovery module needs that no amount of product slides will ever substitute for.

1. A named taxonomy of question types, not a bullet list of examples. "What's prompting you to look at this now" and "walk me through your current process" look interchangeable on a slide, but they're doing structurally different jobs — one surfaces urgency, the other surfaces process and stakeholders. Reps need the underlying category — opening, diagnostic, consequence, commitment — named and defined, so they can generate a good question in a moment the slide didn't anticipate, instead of reciting one that did.
2. Graded practice reps with feedback, not a video of someone doing it well. Watching a great discovery call is the same category of learning as watching a great tennis match — mildly informative, not transferable on its own. What builds the skill is running the call yourself, against a rubric, with someone telling you specifically where the question landed flat or where you talked past a signal, then running it again. A features deck has no mechanism for this at all; it's a one-way broadcast.
3. Exposure to buyer variance, not one clean script. A scripted discovery flow assumes the buyer answers roughly the way the training scenario assumed. Real buyers deflect, answer a different question than the one asked, or say something genuinely unexpected the rep has to diagnose in real time. Training that only ever rehearses the happy path produces reps who are fluent right up until the conversation goes somewhere the deck didn't cover — which, on a real call, is most of them.
4. A way to measure discovery skill on its own axis, separate from whether the rep hit quota that month. Quota attainment is downstream of a dozen variables — territory quality, timing, inherited pipeline, pricing changes. A rep can hit their number with mediocre discovery and miss it with excellent discovery, depending on what they were dealt. If discovery competency is never scored independently of the revenue outcome it eventually influences, the skill stays invisible right up until it becomes the whole explanation for a slipping team average — usually well after the rep who needed the coaching has already been written off as "not a fit" instead of "not yet trained."

What good would look like

None of this requires throwing out the product deck — reps still need to know the product. It requires treating discovery as a codified, gradeable competency with its own onboarding module, its own rubric, and its own certification bar, sitting next to the product curriculum rather than folded into four slides at the back of it. If you're building that module from scratch, the Discovery Questions Cheat Sheet and the Discovery Call Structure Cheat Sheet are reasonable starting scaffolds for the taxonomy piece — the part no deck I read this month had bothered to define.

The actual test

Next time someone hands you an onboarding deck to review, don't count the product slides. Count the ones that would let a rep get graded, fail, and try again on discovery specifically — separate from product knowledge, separate from the pitch. In the three decks I read this month, that number was zero, in a curriculum that ran to well over ninety slides each. The product will not sell itself in the first six minutes of a call. The conversation the rep runs before the product ever comes up will, and it's the one skill none of the three decks thought worth teaching on purpose.