The Sales Enablement Playbook: What BDRs and AEs Actually Use

Most sales enablement libraries are a graveyard. Slide decks from three product launches ago. A case study written by someone who never spoke to the customer. A competitive battlecard so outdated it still lists a competitor that got acquired in 2023. And somewhere in a shared drive folder nobody opens, a 47-page sales playbook that took marketing six weeks to build and sales opened exactly once.

I have inherited a lot of these libraries. And I have built a few from scratch that actually got used. The difference is not production quality. It is not design. It is whether the content was built with sales, for sales, around the specific moments where sales actually needs help.

This is a practical guide to building sales enablement that does not collect dust. It covers battlecards, objection handling, case studies, and proposal support — with specific frameworks you can take and use today.

Start with the moments that matter

Before you build a single asset, map the three to five moments in your sales cycle where deals slow down or die. Not the full funnel — the specific friction points. In most B2B organizations those moments are: the first outbound touch that gets ignored, the discovery call where the rep cannot articulate differentiation under pressure, the multi-stakeholder deal where the champion cannot sell internally without your help, and the final stage where procurement raises price or a competitor gets brought in.

Every piece of enablement content should be traceable back to one of these moments. If you cannot name which moment a piece of content serves, you should not build it yet. The sales team does not need more content. They need the right content at the right stage, formatted so they can use it in thirty seconds or less.

If a rep cannot find what they need in thirty seconds, it does not exist. Discoverability is not a nice-to-have — it is the whole game.

Battlecards: the one page that wins deals

A battlecard is not a comparison chart. A comparison chart lists features side by side and pretends objectivity. A battlecard is a competitive weapon — a single page that gives a rep exactly what to say when a specific competitor comes up in a deal, with enough context to handle the conversation confidently without sounding scripted.

What a good battlecard contains

Their real strengths. Do not soft-pedal this. If the competitor has a genuinely better product in a specific area, your rep will find out in the deal. Better they hear it from you first with context than from the prospect with no response prepared. List two or three things the competitor actually does well and be honest about it.

Where they break down. Not features — situations. The competitor works well for X type of customer at Y scale. When the deal looks like Z, here is what their customers run into. Specific, sourced where possible, grounded in what your sales team actually hears on calls.

Your three talking points. Not ten. Three. The three things that matter most when this competitor is in the room. Framed as responses to what the prospect is likely to say, not as feature statements.

The landmine questions. Two or three questions the rep can ask that naturally surface the competitor's weaknesses without seeming like a takedown. Questions that make the prospect think rather than questions that make the rep look defensive.

Battlecard Template

Competitor: [Name] — One Page, Active Voice, No Fluff

Their Strengths

Be honest. 2-3 things they genuinely do well. Removes the credibility risk of pretending they have none.

Where They Break

Situation-based, not feature-based. "When a customer needs X, they typically hit Y wall at Z stage." Sourced from real deal intel.

Our 3 Points

The three things to land in any competitive conversation. Framed as responses, not monologue. Conversational, not slide-speak.

Landmine Questions

"Have you asked them how they handle X when Y happens?" Questions that open the prospect's mind without making the rep look threatened.

When to Use This Card

Discovery. Multi-stakeholder deals. Procurement stage. Be specific about the moment — reps should not have to figure that out.

Last Updated

Date and owner. If there is no date, the rep will not trust it. If there is no owner, it will never get updated.

Build one battlecard per meaningful competitor. Prioritize by deal frequency, not by who you think is the biggest threat. The competitor that shows up in 40% of your deals matters more than the market leader who rarely appears at your price point.

Objection handling: the script that does not sound like a script

The goal of objection handling is not to overcome objections. That framing puts the rep in an adversarial position with the prospect. The goal is to understand what is behind the objection and respond to that — because most objections are not what they appear to be on the surface.

"Your price is too high" is rarely about price. It is usually about one of three things: the prospect cannot see enough value to justify the number, they have a reference price from a competitor, or they need help making the internal case. Each of those requires a completely different response. A rep who has only been trained on "here is how to handle the price objection" will not know which of these they are actually dealing with.

The four objections that appear in almost every B2B deal

Objection: "Your price is too high."

First response: "Compared to what?" Not defensively. Genuinely. You need to know if this is a budget constraint, a competitive reference point, or an internal approval problem before you say anything else. The answer shapes everything. If it is a competitive reference: "I would like to understand how they are pricing it — sometimes what looks like an apples-to-apples comparison has meaningful differences in what is actually included." If it is an internal approval problem: "It sounds like the value is there for you — where does the friction sit internally? Let me see if I can help you build the case."

Note: Never discount before you diagnose. Discounting without understanding the objection trains the buyer to use price as a lever in every deal.

Objection: "We are happy with our current vendor."

This is an early-stage objection and almost never true in the way it sounds. Happy customers do not take sales calls. Respond with curiosity, not challenge: "That is great to hear. Most of the clients I work with said the same thing before we started talking. What I find is that there are usually one or two things that are working less well than they would like — areas where the current setup is more of a workaround than a solution. Would you be open to sharing what those are for you?" Then stop talking.

Note: The instinct is to pitch. Resist it. Ask one question and listen. The prospect will usually tell you exactly where the opening is.

Objection: "We do not have the budget right now."

Separate timing from interest. "I hear you on timing — is the constraint this fiscal year specifically, or is this more about overall prioritization right now?" If it is timing: "Would it be useful to keep this moving slowly so you are positioned when budget opens? The last thing I want is for you to have to restart the evaluation from scratch in Q1." If it is prioritization: "That makes sense. Help me understand what is above this on the list — sometimes there are ways to frame this that connect it to those priorities directly."

Note: A prospect with no budget and genuine interest is a future deal. Treat them accordingly. Stay in contact without pressure.

Objection: "We need to think about it."

This is a signal that something is unresolved, not a signal to wait. "Of course — what specifically do you want to think through? I ask because I want to make sure you have everything you need to make a good decision, and sometimes there are questions I can answer now that would save time." If they cannot name what they need to think about, the real issue is usually risk — they are not confident enough in the decision to move forward. Address the risk directly: "Sometimes when I hear this, it is because something still feels uncertain. What would need to be true for this to feel like an obvious yes?"

Note: Never just say "sounds good, I will follow up next week." That is how deals stall for months.

Case studies: the asset almost everyone builds wrong

The standard B2B case study follows a formula that makes procurement happy and tells sales almost nothing useful. Problem. Solution. Results. Logo. It reads like a press release because it usually is one.

The case studies that actually get used in deals look different. They are short — one page or less in a deal context. They are told from the customer's perspective, not the vendor's. And they are indexed not by industry or company size but by the specific problem the prospect is facing right now.

The case study format that works in a live deal

The situation in one sentence. Not their industry or their size. The specific situation they were in before they bought. "A professional services firm with a 30-person marketing team and no attribution model, trying to justify a $2M marketing budget to a skeptical CFO." A rep in a deal with that exact profile will reach for that story immediately.

The moment they knew something had to change. A specific event or realization, told in the customer's words where possible. This is the part that creates emotional resonance. A prospect recognizes their own situation in it. That recognition is worth more than any ROI statistic.

What we actually did. Not "we implemented our platform." The specific things that happened. Which team was involved. How long it took. What the first 90 days looked like. Prospects want to know what buying from you actually feels like, not what your solution theoretically does.

One specific outcome with context. Not five metrics. One number, with enough context to make it believable. "Pipeline influenced by marketing increased from 18% to 61% of total pipeline over 14 months — which changed the conversation in the boardroom completely" is more powerful than a generic percentage improvement with no frame of reference.

One sentence from the customer. A real quote, in real language, that no PR team touched. If your customer would not say it in a conversation, it should not be in the case study.

Internal selling: the asset nobody builds

In enterprise B2B, the person you sell to is rarely the person who signs. Your champion has to sell internally — to their CFO, their IT team, their procurement function, sometimes their board. Most marketing teams build content for the first sale. Almost nobody builds content for the second sale, the one that happens inside the customer's organization without you in the room.

Build a one-page internal justification document your champion can take into that conversation. It should cover: the business problem in financial terms their CFO will recognize, the cost of inaction stated specifically, a clear ROI model with conservative assumptions, risk mitigation language for the skeptics, and a short list of reference customers they can speak to. This is not a proposal. It is ammunition for your internal champion. It should read like something they wrote, not something a vendor sent them.

The deal does not close in your meeting. It closes in the conversation your champion has with their CFO at 7pm on a Tuesday. Build for that moment.

The maintenance problem: why enablement libraries die

Building the assets is the easy part. Keeping them current is where almost every sales enablement function fails. A battlecard that is six months out of date is worse than no battlecard because it gives the rep false confidence going into a competitive deal.

The fix is not a bigger review process. It is ownership and triggers. Every piece of enablement content needs one owner — a specific person who is accountable for keeping it current, not a committee. And every piece needs a defined trigger for review: a new competitor funding round, a lost deal where the asset came up, a product update that changes the comparison. When the trigger happens, the owner updates the asset. That is the whole process.

Run a quarterly audit — sixty minutes, every quarter, with one person from sales and one from marketing. Go through the library. Kill anything that has not been used. Update anything that is stale. Add one new asset based on the most common conversation happening in deals right now. Sixty minutes, four times a year, will keep a library alive longer than any governance process you can build.

The goal is not a comprehensive library. The goal is a small set of assets that every rep trusts, every rep knows how to find, and every rep reaches for automatically when the moment calls for it. Ten assets that get used beat a hundred that do not.

— Erik R. Miller