Sales Enablement That Reps Actually Use

Open Highspot right now. Sort by "least viewed in the last 90 days." That's your enablement library.

The 47-slide master deck PMM spent six weeks building? Last opened by the rep who downloaded it once at SKO and hasn't touched it since. The "competitor positioning hub" with 14 sub-pages? Two views, both from the PMM checking it still loads. Meanwhile, your top three AEs are running their own deck (built in a Google Slides file they share with each other on Slack) and pulling 130% of quota with it.

If your enablement only works for the bottom half of the team, it's not enablement. It's a compliance program with a Highspot login and a quarterly attestation.

This piece is about what survives contact with a real pipeline review. Five assets reps actually open, share with buyers, and quote on calls. The metrics that prove they're working. And the rituals that keep the whole thing from collapsing back into deck-as-deliverable theater.

Why Most Enablement Fails

The pattern is depressingly consistent.

PMM gets the brief: "We're losing to Competitor X. We need a battlecard." Three weeks of work. Interviews with two AEs (the ones who reply to Slack). A polished 6-page PDF with competitor pricing, feature matrices, and a SWOT that looks like a McKinsey deliverable. It ships. Sales leadership presents it once at the next SKO. Eighteen days later, AEs are off-script because the official narrative doesn't survive a real call where the buyer says, "Yeah but we already use Competitor X for the Slack integration, so..."

I call this deck-as-deliverable thinking, and it's the diagnosis behind almost every dead enablement asset I've ever seen.

The symptoms:

• No ride-along. PMM wrote the asset without sitting on five live calls first. So the language is what PMM thinks reps should say, not what reps actually say when a CFO pushes back at minute 38.
• No rep-language input. The objection responses sound like they were written at a desk by someone who hasn't taken a sales call in three years. Because they were.
• Deliverable, not adoption. Success was defined as "asset shipped" not "asset used in 60% of competitive deals within 30 days."
• No update loop. The asset shipped in February. By July, pricing has changed twice, the competitor launched two new features, and the original PDF is actively misleading. Nobody owns updating it.

The fix isn't more decks. It's fewer, sharper, and built from the field outward.

The 5 Enablement Assets Reps Actually Use

Across maybe 40 sales orgs I've watched up close, the same five assets keep surviving. Everything else is noise.

1. The 1-Pager Battlecard

One page. PDF. Sits in the rep's inbox, not buried in Highspot four clicks deep.

Structure:

• Competitor name + one-line positioning (how they pitch themselves, in their words)
• 3 landmines: places this competitor will hurt us if we don't defuse early
• 3 trap-setting questions: questions to ask the buyer that surface where we win
• Our win story: one customer, one paragraph, named AE who closed it

That's it. No SWOT. No 14-row feature matrix. No "market overview" preamble. The rep is preparing for a 30-minute discovery call in the parking lot of their kid's soccer game. They need ammo, not an MBA case study.

The trap-setting questions are the part most PMMs skip and the part top reps love most. "Ask them how they handle [thing competitor does poorly]" beats "We're better at [thing]" every time, because it makes the buyer discover the gap themselves.

2. The 12-Slide Demo Deck

Not 47. Twelve.

One slide per buying-committee persona pain. So if you sell into a buying committee of CRO, RevOps Director, and CFO, that's three persona sections, three to four slides each. Built for screen-share at minute 22 of a discovery call, not for training a new hire from scratch.

The tell that you've over-built it: any slide that exists "for context" or "for the appendix." Cut it. If a rep wouldn't actually click to it on a live call, it's not part of the demo deck. It's a different asset for a different job.

The other tell: the deck has the company's brand-refresh logo at the top of every slide and a footer with the tagline. Nobody cares. Reps hide your branding when they share-screen anyway.

3. The Objection Handling Cheat Sheet

The top 8 objections. The actual rep language that closed them. Pulled from Gong call recordings, not invented at a desk.

Format that works:

Objection: "Your pricing is 2x what Competitor Y charges."
Don't say: "We deliver more value." (dies on the call)
Try: "Yeah, our list is higher. The customers who pick us
over Y usually have [specific situation]. Can I ask — are
you running [thing]?" (reframes as fit, not price)
Closed by: Sarah K, $180K Acme deal, Q3

Three things make this asset different from every dead "objection handling guide" I've ever seen:

1. The "don't say" line. PMMs are allergic to telling reps what not to say. Reps love it. The corporate-speak response is what they've been taught for years and it stops working.
2. The actual closing line, in rep voice. Not the polished version. The version with "yeah" and "can I ask" because that's what works on calls.
3. The named AE who closed it. This is the social proof that makes other reps trust the asset. "Sarah closed Acme with this" beats "industry research shows."

4. The ROI Calculator

Excel. Or a simple web tool. Not a 30-page custom value engineering deliverable that takes RevOps 12 hours per deal.

The job of an ROI calculator is to give the rep something the buyer can take into a CFO meeting and not get laughed out of the room. So inputs the buyer cares about (current spend, headcount, deal volume, whatever drives their math), and an output the CFO will sign off on (NPV over 3 years, payback period, fully-loaded TCO comparison).

The trap is making it too sophisticated. If a rep needs a 45-minute training session to use the calculator, it dies. If the rep can fill it in during a 10-minute prep before the next call, it lives.

Most ROI calculators die because PMM (or Product Marketing leadership) wants to model 23 variables. Reps want 5. Build for 5. If the deal needs 23, that's what RevOps and Solutions Engineering are for.

5. The Customer Story Library

Searchable. By industry, deal size, and competitor displaced. With the AE who closed it tagged for a warm intro.

This is the asset that punches the hardest above its weight, because the question "Do you have a customer like us?" gets asked on roughly 80% of competitive calls, and a rep who can answer "Yes, Acme Corp, 400 employees, displaced [Competitor Y] last quarter, here's the 90-second story and I can connect you with the AE who ran the deal" wins on credibility alone.

What kills most customer story libraries:

• Stories are written like case study marketing collateral (3,000 words of brand-safe puffery)
• No filtering by deal size or competitor
• AE who closed the deal isn't tagged, so the rep can't get a real perspective fast
• Stories aren't refreshed. Half of them reference customers who churned 18 months ago

Fix: a structured 1-page format per story (industry, company size, what they were using before, why they switched, what changed, named AE), refreshed every 6 months, retired after 18 months unless the customer's still expanding.

How to Design for Adoption

Adoption is the only metric. Repeat that until it's tattooed on the inside of your eyelids.

The only reliable way to design for adoption is to start in the field and end in the field. Specifically:

Ride along on 5 calls before you write anything. Not "review the recording later." Actually be on the call, on mute, taking notes. You are looking for: the language reps actually use, the objections that actually come up (not the ones leadership thinks come up), the moments where the rep visibly fumbles for ammo and pivots. Those fumble moments are your asset spec.

Ask the top reps what they actually say. Not "What objections do you hear?" That produces a list of categories. Instead: "Walk me through the last time a buyer asked about [Competitor X]. What did you say, word for word?" Write it down verbatim. That language is your draft copy.

Ship the asset as a 4-minute Loom plus a 1-pager. Not a 30-minute deck walkthrough at the all-hands. Reps will skip the meeting. They will play the Loom at 1.75x speed while making coffee. The Loom should answer: what is this asset, when do I use it, what do I say. The 1-pager is what they screenshot and put in their notes.

Test with one rep before the broad rollout. Pick a rep who'll actually push back. Have them use the asset on three live calls. Iterate. Then ship to the team. The asset that survives one rep's real pipeline is 10x more likely to survive the team's.

This whole workflow is closer to how you'd run discovery for a positioning doc that sales will actually use than how a junior PMM thinks enablement should work. The shape is the same: live calls in, polished asset out, never the reverse.

Enablement Metrics That Matter

If you can't measure it, you can't defend the budget. Here's the short list of metrics that actually prove enablement is working.

Asset usage in Highspot/Gong (or whatever your tool is). Specifically: opens, time-on-asset, share-with-buyer rate. The share-with-buyer rate is the underrated one. A rep who shares your battlecard with a champion is signaling that the asset is good enough to put their name behind.

Win-rate movement on deals that used the asset vs. didn't. This requires Gong or Highspot tagging deals with which assets were touched. Yes, it's correlation, not causation. But a 12-point delta in competitive win rate between deals that used the new battlecard vs. deals that didn't is enough signal to defend the program at the next QBR.

Ramp time for new hires. Target: productive in 90 days, not 180. "Productive" defined as: hitting 60% of full quota, certified on the demo, has closed at least one deal solo. If your ramp is still 180 days after enablement investment, the assets aren't doing the work. Probably because they're built for tenured reps, not new hires.

Self-reported rep confidence by competitor. Quarterly 5-question survey. "On a scale of 1-5, how confident are you handling Competitor X?" Track the trend. If confidence drops, an asset is stale or a competitor moved.

The one metric I'd avoid leading with: "decks shipped per quarter." That's the metric that produces 47-slide masterpieces nobody opens. Output volume isn't the goal. Adoption is.

The "Monthly Product Update" Trap

Every PMM eventually gets the request: "Hey, can you run a monthly 60-minute product update call for sales? Just walk through what shipped, what's coming, the pricing changes."

Don't.

Here's what happens. Month 1: 80% attendance, energy is high, reps ask good questions. Month 2: 50% attendance, half the room is on email. Month 3: 20% attendance, the questions stop, you're presenting to four faces and a sea of black Zoom squares. Month 4: leadership asks why the call is poorly attended. Now you're defending a thing that's been quietly dead for two months.

The job to be done (keep sales current on product changes) is real. The format is wrong.

Replace it with:

• A 5-bullet Slack post in #sales-product channel for any update that's actually rep-relevant.
• A 90-second Loom for anything that needs visual context.
• A 14-day SLA between feature ship and rep-facing update. Faster than that, you're spamming. Slower, reps hear it from a customer first and lose credibility.

If a feature can't be summarized in 5 bullets and a 90-second Loom, it's probably not yet rep-ready anyway. Wait. Update the messaging when the feature has actually shipped to enough customers that reps will see it in deals.

The corollary: kill any recurring meeting whose attendance has dropped below 40% for three consecutive months. The attendance number is the org telling you the meeting doesn't justify the time. Listen.

Certification Rituals That Work

Certifications get a bad rap because most of them are quiz-badge theater. Multiple choice. Open book. Pass rate of 98%. The badge means nothing.

What works: role-play the demo with a PMM and a sales manager scoring it. Pass = you can run the demo cold, in front of two skeptical observers, in 25 minutes, handling at least 3 objections without breaking flow.

Real teeth attached:

• No cert = no inbound MQLs routed to you. This is the lever that makes certification actually mean something. Reps who can't run the demo don't get the leads. Watch how fast certification rates climb.
• Recert every 6 months. Markets move. Competitors launch. The certification that meant something in March is stale by September.
• Public scorecard. Not the individual scores. Those are between rep and manager. But the team's overall cert rate, posted in the sales leadership Slack channel weekly. Peer pressure works.

The thing that kills certification programs: making them feel like school. The thing that saves them: making them feel like a real-world test the rep needs to pass to get the good leads. Reps respond to incentives, not curriculum.

The Win/Loss Feedback Loop

The last piece, and the one that keeps enablement from calcifying into broadcast mode, is a real win/loss feedback loop.

Monthly cadence:

• 5 win interviews, 5 loss interviews. Buyer side, not just internal stakeholder.
• Patterns shared in a single Slack doc, posted in the field channel within 7 days of the last interview.
• Assets updated within 14 days of pattern identification.

Three patterns in three months means an asset rebuild, not a tweak. If "buyers keep saying our pricing model is confusing" shows up in five loss interviews, the pricing slide in the demo deck needs a rewrite by next sprint, not a Q3 roadmap line item.

This is also where you find the gaps your existing assets don't cover. An objection that keeps closing deals (or losing them) but isn't in the cheat sheet? Add it next week. A competitor that keeps showing up but isn't on a battlecard? That's your next asset, prioritized over whatever the planning doc said.

The goal is to make enablement feel like a two-way conversation between PMM and the field. Not a broadcast. The faster the loop, the more reps trust the assets, the higher adoption climbs.

For a deeper dive on running these conversations, the win/loss interviews without the BS playbook covers how to actually get useful answers out of buyers (hint: don't ask them why they bought).

What This Looks Like in Practice

A PMM doing enablement well in 2026 ships maybe 5-7 living assets per quarter. Not 47. Each one has:

• A clear job: what call moment it fixes
• A named asset owner with a refresh cadence
• An adoption metric tracked in Highspot/Gong
• A retirement date if metrics don't hold

That same PMM is on five live calls a month, in #sales-product daily, and runs win/loss interviews monthly. They show up to QBR with a slide that reads "12-point lift in competitive win rate, 90-day ramp down from 180, 73% asset adoption," not "shipped 14 deliverables this quarter."

The reps fight to keep their assets, because they helped build them and they actually work in pipeline. That's the goal. Every other enablement metric is a proxy for that one.

If your reps aren't opening the asset, sharing it with buyers, or quoting it on calls, it doesn't exist. Stop shipping decks. Start shipping things reps fight to keep.

Learn More

• Product Marketing Manager Job Description
• Positioning Doc That Sales Will Actually Use
• Win/Loss Interviews Without the BS
• Launching a Feature Sales Doesn't Care About