Sales enablement that actually enables sales: a PMM's playbook

Somewhere right now, a product marketer is opening the analytics on a battle card she spent three weeks building.

Fourteen pages. Color-coded. Competitive intel, differentiators, objection scripts, all of it accurate.

She uploaded it to the portal, announced it in Slack, and ran a forty-five minute training.

Four downloads. Two of them are hers.

Most of us have a version of that number somewhere. We built something genuinely useful, it went into a folder nobody opens, and then we watched a deal get lost on a question we had already answered in writing.

The content wasn't the problem.

We write enablement at a desk. We shape it from product specs and analyst notes, we organize it the way we understand the market, and then we hand it to someone who has ninety seconds before a prospect says a competitor's name out loud.

Call that desk enablement. Thorough, accurate, and built for the person who made it.

---

Why the folder stays closed

Desk enablement is written for awareness. A battle card gets structured like a competitive analysis, opening with company background and funding history before it reaches anything a rep can say out loud.

Useful context. Terrible ammunition.

A rep in a live call has ninety seconds and needs the next sentence.

Then there's no way for anything to come back. We publish, sales uses it or doesn't, we publish more. Without a mechanism telling us which asset got used and whether it worked, we're guessing with confidence.

Findability is the quiet killer. Assets scatter across SharePoint, Drive, Confluence, Guru, and the portal somebody stood up in 2023 and abandoned by Q2.

Reps don't search mid-deal. They wing it or they ping a colleague.

If our best material takes longer than half a minute to find, it doesn't exist.

And it rots. A competitor ships something, pricing shifts, a new objection surfaces, and twelve reps are still carrying last quarter's answer into live calls. A rep quoting stale information is worse off than a rep who said nothing.

---

Riding along first

Before we build anything, we go on calls. Not to present. To listen to the conversation happening around the demo.

What gets asked in discovery, over and over? Where do deals stall, and what reason gets typed into the CRM?

Which competitor names come up, and what do prospects say about them? What did a rep actually say when someone asked why you instead of them?

That's the raw material. Everything we build should trace back to one of those moments.

Ten ride-alongs, five lost-deal debriefs, and an afternoon with the best-performing rep, before a word gets written.

Built for the ninety seconds

One test for every asset. When exactly will a rep reach for this?

If the answer is the night before a call, a one-pager works. If it's mid-conversation, it has to be readable in a glance. If it's after a loss, it's a debrief template.

Four formats carry most of the load.

The one-page positioning sheet is the most important thing we own. What we do, who it's for, and why we're a different choice from the two competitors reps meet most. Write it in language pulled from buyer calls rather than from the messaging doc.

Battle cards run one page per competitor, and that's the ceiling. Two sentences of context, when this name shows up, what to say, what to avoid saying, and the question that pulls the conversation back onto our ground.

The failure mode is completeness. Fourteen pages is a filing cabinet.

The objection library is the highest-return thing most of us never build. Take the objections reps hear most, sort them by deal stage, and for each one write the objection in the buyer's own words, what's underneath it, the reframe, and one proof point.

Stage matters more than teams expect. An objection in discovery is a different animal from the same words in a business-case review, and most companies have material for exactly one pitch.

Evidence cards are the fourth format, and they aren't case studies. Case studies live on the website. Evidence cards live in deals.

One paragraph each. The problem, the outcome, the industry, the company size, filed so a rep can find the right story in under a minute.

One place to look

Pick a place. Defend it.

The best teams run a single source of truth. One Notion space, one Guru library, one pinned channel. The format matters far less than the discipline.

Name files the way a rep would search for them. Competitive - Acme - Battle Card beats Q3 Competitive Intel v7 Final_FINAL every time.

Organize by deal stage instead of content type. Reps think in "I'm in discovery" and "I'm trying to close." Nobody has ever thought "I need a marketing asset."

The return trip

Build a way for signal to come back into every major asset.

The simple version is one channel where reps say what they used and whether it worked. Check it weekly, and answer. Nothing kills a feedback culture faster than silence.

The heavier version is a quarterly pull of ten or fifteen deals across wins, losses, and stalls, looking at which content got used, which objections nobody had covered, and which competitors never made it onto a card at all. (Win/Loss Analysis: The PMM's Most Underused Revenue Weapon covers the method.)

None of it works without a real relationship with a handful of reps, well past the stakeholder-update kind. People who'll test something rough, tell us it's wrong, and flag it before it's wrong in a hundred deals.

What sales counts

Stop counting content. "We published twelve battle cards this quarter" is an activity report.

Win rate overall, and win rate against the two competitors that show up most. Stage conversion, because good enablement should move deals out of evaluation and into a business case. Deal velocity, because a rep who already has the answer doesn't have to go find it.

Adoption is the early warning. When it's low, the cause is almost always findability, relevance, or format, and we should exhaust those three before deciding nobody cared.

The first month

Week one is research. No building. Five ride-alongs, ten lost-deal notes, three conversations with top reps, and a running list of every objection and competitor name that comes up.

Week two is the positioning sheet. One page. Ask three reps whether it matches how they actually talk, then rewrite it from what they say.

Week three is two battle cards, built for the competitors that show up in lost deals rather than the ones that worry marketing. Those are usually different names.

Competitive intelligence research informs the draft. Reps decide whether it's true.

Week four is the objection library, starting with the ten from week one.

Then look at what's getting used, and at what reps asked for that doesn't exist yet. That second list sets the next month.

---

What comes back up the pipe

It turns out the deliverable was never the point. Sales enablement isn't a service we provide to sales. It's the fastest read we have on whether our positioning survives contact with a buyer.

Every objection is a gap in the position. Every "why not you" is a difference we never made legible. Every "we went with them" is market research arriving free of charge.

Treat it as a two-way system and the battle card stops being the point. What comes back is worth more than what we sent down, and it feeds the messaging work, the positioning framework, and the pricing conversation.

Desk enablement gets four downloads.

Go sit in a deal.

What to do next

If reps are improvising because our material never reaches them in time, the repair starts upstream of the content. A positioning audit finds the claims that aren't landing in real conversations, and a messaging sprint turns them into language a rep will actually say.

If that's where you are, start here. The first conversation is free.