Battlecards, personas, discovery frameworks, and objection handling. Built from scratch for a specific product and competitive landscape.
Companies selling complex technical products often lose winnable deals because their AEs can't speak credibly about what they're selling. The gap shows up as surface-level discovery questions, missing competitive context, slow ramp times for new reps, and enablement content written by people who've never been on a technical sales call.
AI tools like Klue, Crayon, and Steve increasingly handle ongoing battlecard maintenance. The foundational library still needs to be built by a person who understands the product, the competitive landscape, and how technical buyers actually evaluate.
A sales enablement library is a coordinated set of strategic content that gives AEs everything they need to run technical sales conversations: how the product is positioned, who the buyers are, what to ask, how to handle objections, and how to win against specific competitors.
The components reinforce each other—a persona guide tells an AE who they're talking to, the discovery framework tells them what to ask, the battlecards tell them how to handle competitive context as it surfaces, and the objection handling document tells them how to respond when the conversation hits friction.
Each library is built from scratch for a specific product and competitive landscape. The standard components:
One per major competitor (typically up to five). Each is a one-to-two page reference an AE can scan in under sixty seconds during a live call, covering positioning, where the competitor wins, where we win, trap-setting questions, objection handling specific to that competitor, proof points, and an AE quick-reference of three sentences a rep can use directly.
Two to four guides, one per priority buyer type. Each covers the buyer's role, what they care about, what they don't care about, what they fear, how they evaluate technical products, who else they need to convince internally, and how to talk to them in ways that respect their time and intelligence.
A structured set of discovery questions segmented by buyer type and deal stage. Designed so an AE can pick the right question for the moment rather than running a generic checklist.
Top 15–20 objections specific to the product and category, each with a response pattern. Not a script—a pattern AEs can adapt to the conversation.
The technical questions AEs get on calls but can't always answer accurately. Written so a rep can speak credibly without needing to pull in an SE for every conversation.
One coordinated story that ties the above together into a deal-stage-appropriate narrative.
Everything organized so a new AE can ramp by reading the library rather than shadowing for three months.
Typical engagement: 6–8 weeks.
Delivered as documents. CRM or enablement platform integration is the buyer's responsibility.
Battlecard-only or persona-only engagements: starting at $7,500.
I'm Karen Spinner. I've spent fifteen years writing for technical B2B audiences, including sales enablement and competitive content for the Adobe Digital Experience division (Commerce, Experience Platform, Marketo Engage, and Workfront), Confluent, ChargePoint, and other B2B tech companies.
A few sentences are useful to start: product, top two or three competitors, current state of enablement content, sales team size. Responses typically within 48 hours.