Sales Enablement

---
name: sales-enablement
description: >
  Use this skill for creating sales collateral and materials that help sales teams close deals. Triggers on: pitch deck, one-pager, sales deck, battle card, objection handling, talk track, demo script, sales playbook, buyer persona card, proposal template, ROI calculator, proof of concept, competitive positioning for sales, and any request to build a document that a sales rep would use in a customer conversation. Distinct from marketing website copy and cold email outreach.
---

# Sales Enablement

## Mandatory Content Standards

- Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.
- Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.
- Use short sentences. One idea per sentence. One focus per paragraph.
- Use active voice. Never passive constructions.
- Address the reader directly using "you" and "your."
- Use bullet points only when they genuinely improve readability.
- No em dashes. Replace with commas, parentheses, semicolons, or new sentences.
- End every sentence with a period.
- End every sentence with a period.
- No hashtags, emojis, or asterisks.
- No filler phrases like "in conclusion" or "in summary."
- No warnings or disclaimers.
- No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "cutting-edge," "transformative."
- Use specific examples, data points, and scenarios.
- Pose at least one thought-provoking question.
- Keep paragraphs short. Headers scannable. Structure mobile-friendly.
- Every section connects to a practical next step.

---

## What Sales Enablement Is and Is Not

Sales enablement produces materials that help salespeople have better conversations with buyers. That is the job. It is not about generating brand awareness. It is not about educating the market. It is about giving a specific rep the right artifact at the right moment in a deal to move the conversation forward.

The materials look different depending on the deal stage. A prospect who just booked a discovery call needs different preparation than a procurement team reviewing a contract. A mid-market rep selling a $15,000 product needs different tools than an enterprise rep managing a $500,000 account.

The question every piece of sales enablement should answer before you write the first word: what specific moment in the sales process will this document help a rep navigate?

If you cannot answer that question, you are about to create something that will sit in a shared Google Drive folder and never get used.

---

## Pitch Deck Structure

A pitch deck for sales is not a brand presentation. It is a structured conversation guide. The slides exist to keep the conversation on track, not to be read aloud word for word.

Most pitch decks fail because they spend too much time on the company and not enough time on the customer's problem. A buyer sitting in a demo does not care about your founding story. They care about whether you can solve the specific problem they brought to you.

Here is a pitch deck structure that works for B2B mid-market and enterprise sales:

**Slide 1: Situation acknowledgment.** Open with something that shows you understand the buyer's world. Reference their industry, company size, or a specific challenge you know they face. "Companies at your stage typically see X problem when they try to do Y." This signals preparation and earns the right to continue.

**Slide 2: The problem you solve.** Describe the problem concisely. Use language the buyer uses, not your internal terminology. Quantify the cost of the problem where possible. "Manual invoice processing takes an average of 14 days and costs finance teams approximately $12 per invoice in labor" is more compelling than "inefficient processes slow teams down."

**Slide 3: How the landscape usually fails.** Briefly explain why existing approaches (spreadsheets, legacy tools, doing nothing, or your competitors) fall short. Do not name competitors by name here. Focus on category shortcomings.

**Slide 4: Your approach.** Explain your solution's core mechanism. Focus on how it works at a conceptual level, not a feature list. "We connect directly to your ERP so that every invoice is automatically matched against your PO database" is an approach. "We offer bi-directional ERP integration" is a feature.

**Slide 5: Proof.** One or two specific customer examples with quantified results. "Apex Manufacturing reduced invoice processing time from 14 days to 2 days and saved $240,000 in labor costs in the first year." Named customers with real numbers beat stock testimonials every time.

**Slide 6: Why now.** This slide earns its place only if there is a genuine reason urgency exists, whether that is a regulatory change, a technology shift, or something specific to the buyer's situation. Manufactured urgency destroys trust.

**Slide 7: The ask.** What do you want the buyer to do next? A specific next step with a timeline. Not "let us stay in touch" but "I would like to schedule a 30-minute technical review with your IT lead next week."

Keep the deck under 12 slides. If you need more than 12 slides to make your case, you have not made your case.

---

## One-Pager Design

A one-pager is a single-page document that a rep can send before or after a meeting to anchor the buyer's understanding of what you do and who you do it for. It must work without a salesperson explaining it.

The one-pager has five components:

**Headline.** One sentence that names the problem you solve and who you solve it for. "We help mid-market logistics companies eliminate manual freight reconciliation" is a headline. "The leading platform for supply chain optimization" is not.

**Problem statement.** Two to three sentences on what breaks when the problem is not solved. Include a data point if you have one. Buyers who recognize their situation in a problem statement keep reading.

**Solution description.** Three to five sentences on how your product addresses the problem. Avoid jargon. Use outcomes, not features.

**Social proof.** Two or three customer logos with one short result each. "Acme Corp cut audit prep time by 60 percent" takes up four words and does more work than a paragraph of marketing copy.

**Call to action.** One specific action with contact information. "Schedule a 20-minute call with our team at calendly.com/yourlink."

Design the layout so the most important information appears in the top half of the page. Many buyers will only read that far. If your strongest proof point is at the bottom, move it up.

---

## Objection Handling Documents

Objections are predictable. Every sales team faces the same six to ten objections on most deals. The reps who handle objections well have thought through their responses in advance. The reps who stumble are improvising.

An objection handling document gives reps prepared, tested language for every common objection. It is not a script. It is a framework that structures their thinking so they respond confidently without sounding rehearsed.

Build the document this way:

For each objection, capture four things:

1. The exact language the buyer uses. Not a paraphrase. The actual words. "We already have something that does that" is different from "we tried something like this before and it didn't work."

2. What the objection usually signals underneath the surface. "We don't have budget" often means "I'm not convinced this is worth prioritizing." Knowing the real concern changes how you respond.

3. The acknowledgment. Every objection response starts with acknowledging the concern, not immediately countering it. Buyers who feel defended against stop talking. Buyers who feel heard keep engaging.

4. The redirect. One or two clarifying questions that move the conversation forward. "What would need to be true for this to be a priority in Q3?" is a better response to a budget objection than a discount offer.

The most common B2B objections to cover:

- "We don't have budget right now."
- "We're already using [competitor]."
- "We tried something like this before and it didn't work."
- "We need to talk to more stakeholders."
- "Your price is too high."
- "We're not ready to make a decision yet."
- "We're too small for this."
- "We can build this ourselves."
- "We need to see more proof."
- "We need to think about it."

Run quarterly sessions where reps submit new objections they encountered. Update the document. Sales conversations evolve as markets change, and your objection handling document needs to evolve with them.

---

## Demo Scripts

A demo script is not a transcript of every click in the product. It is a structured narrative that connects product capabilities to the buyer's specific situation. Reps who treat a demo as a feature tour lose buyers. Reps who tell a story through the product keep them engaged.

Structure a demo script in three acts:

**Act 1: Situate the buyer (2 to 3 minutes).** Before showing anything, confirm what you know about their situation. "Based on our discovery call, your team is spending about 8 hours per week on manual reconciliation and you're running into problems when volumes spike at month-end. I'm going to show you specifically how we address that. Does that still match what you're trying to solve?" This keeps the demo relevant and gives the buyer a chance to refine the focus.

**Act 2: Show, narrate, and connect (15 to 20 minutes).** Walk through three to five core use cases, not a comprehensive product tour. For each use case:
- Name the problem. "Let me show you how the month-end reconciliation works."
- Show the product doing the relevant thing.
- Connect it back to their situation. "This is where your team would save those 8 hours. The system pulls the data automatically so nobody has to touch the spreadsheet."
- Pause and ask a micro-confirmation question. "Does this workflow fit how your team currently handles it, or are there differences I should know about?"

**Act 3: Nail the next step (5 minutes).** End every demo with a specific ask, not an open question. "Based on what you saw, does this solve the core problem you described?" If yes: "What would need to happen on your end to move this into a technical evaluation?" If hesitation: "What's still unclear for you?"

Write demo scripts for three to five distinct use cases or buyer types. A CFO demo and a Director of Operations demo for the same product should feel like different conversations, because they are.

---

## Talk Tracks

A talk track is the structured spoken narrative a rep uses for a specific conversation type. Discovery calls, cold calls, follow-up calls after proposals, and executive business reviews all need different talk tracks.

A well-written talk track has three properties:

It sounds like a human, not a call center script. If you read it aloud and it sounds wooden, rewrite it. Reps will not use something that makes them sound robotic.

It is flexible, not rigid. A talk track is a guide, not a transcript. It gives reps a throughline they can adapt based on how the conversation unfolds.

It asks more than it tells. The best discovery talk tracks are mostly questions. The rep's job in discovery is to understand the buyer's situation, not to present.

Here is a discovery talk track framework:

Opening (30 seconds): Establish the reason for the call and set an agenda. "Thanks for making time. I have about 40 minutes blocked. I'd like to spend most of it hearing about what you're trying to solve, then show you a few things if it's relevant, and figure out together whether there's a fit. Does that work?"

Problem exploration (10 to 15 minutes): A sequence of open questions that move from current state to problem to impact. "Walk me through how your team handles X today." Then: "Where does that process break down?" Then: "What's the cost of that when it breaks?"

Solution fit check (5 to 10 minutes): Test whether your solution addresses what you just heard. "Based on what you described, we work with teams in a similar situation by doing Y. Does that resonate with what you're dealing with?"

Qualification (5 minutes): Cover the BANT or MEDDIC criteria naturally. Who else is involved in this decision? What does your timeline look like? Is there budget allocated for this type of project?

Next step (5 minutes): Propose a specific next step based on what you learned. Not "I'll send you some information" but "It sounds like the best next step is a technical call with your IT lead. Can we get that on the calendar before we hang up?"

---

## Sales Playbooks

A sales playbook is a comprehensive operational guide that covers how your sales team approaches every stage of the deal. It is the document a new rep reads in week one and a seasoned rep references when a deal gets unusual.

A complete playbook covers:

**ICP definition.** Who is the ideal customer? Include firmographic criteria (company size, industry, geography, tech stack) and pain-based criteria (the specific situations that indicate fit). Include disqualification criteria. Not every company that wants to buy from you should.

**Persona cards.** For each buying role (economic buyer, technical buyer, champion, influencer), describe their responsibilities, their typical concerns, their success metrics, and the language that resonates with them.

**The sales process.** Stage by stage, what does the rep do, what does the buyer do, and what signals indicate readiness to advance? Tie each stage to CRM fields and required documentation.

**Qualification framework.** Whether you use BANT, MEDDIC, SPICED, or your own framework, document it clearly. Reps should be able to complete qualification by the end of discovery without having to remember a list from memory.

**Competitive positioning.** For each major competitor, cover where you win, where they win, and how to handle comparisons. Keep this section updated quarterly.

**Objection handling.** Reference the standalone objection handling document.

**Proof library.** A curated set of case studies, testimonials, and reference customers organized by industry, company size, and use case. When a buyer asks for proof from their specific vertical, the rep should not have to dig through a shared folder.

**Pricing and packaging guidance.** What can reps offer? What requires deal desk approval? What are the standard discount levels by deal size?

**Resources and tools.** Links to the demo environment, the proposal template, the ROI calculator, the contract template, and the CRM guide.

A playbook that nobody reads is a playbook that does not exist. Write it in plain language. Break it into short sections with clear headers. Keep it under 30 pages. Update it quarterly.

---

## Buyer Persona Cards

A buyer persona card is a one-page reference document that helps a rep prepare for a conversation with a specific type of buyer. It is not a demographic profile. It is a preparation tool built around how this person thinks about their job, their challenges, and a purchase decision.

Each persona card covers:

**The role.** Job title, typical team structure, and what they are measured on. A VP of Finance's success metrics (cost reduction, forecast accuracy, audit readiness) are entirely different from a VP of Engineering's (system reliability, shipping velocity, technical debt ratio).

**Their primary concerns.** What keeps this person up at night? What would make their quarter better? What would get them in trouble with their boss?

**Their typical objections.** Which objections does this persona raise most often? A CFO and a Head of IT reviewing the same product will object differently.

**The language that works.** Specific words and phrases that this persona responds to. For a CFO, that might be "payback period," "cost per unit," and "audit trail." For a Head of IT, it might be "API documentation," "uptime SLA," and "SSO support."

**What they need to champion.** If this person loves your product and wants to push it through internally, what do they need to make the case? A ROI summary for the CFO to take to the board. A security overview for IT to share with the CISO. A workflow diagram for Operations to show their team.

**The questions to ask.** Five to seven discovery questions tailored to this persona's world. Not generic questions. Specific ones that surface the concerns this person actually has.

Build persona cards for every major buying role in your deals. Distribute them as part of the sales playbook and update them when you see patterns in win/loss data.

---

## Proposal Templates

A proposal is often the document that determines whether a deal closes or stalls. Most proposals are built by reps from scratch, which means they take too long to produce, they vary wildly in quality, and they are often missing the information that moves the buyer to a decision.

A strong proposal template includes:

**Executive summary.** Two to three paragraphs written for the economic buyer, summarizing the problem being solved, the proposed solution, and the expected outcome. This person may only read this page.

**Situation summary.** A reflection of what you learned during discovery. Buyers who see their specific situation described accurately feel understood. This is your opportunity to demonstrate that you listened.

**Proposed solution.** Describe what you are proposing, why it fits the situation, and what makes it different from alternatives the buyer might consider.

**Scope and deliverables.** Exactly what is included. Exactly what is not. Ambiguity in this section causes problems at contract signature and during implementation.

**Implementation timeline.** A realistic view of what happens after the contract is signed. When does the buyer see value? What do they need to provide?

**Investment summary.** Pricing presented clearly with no hidden structure. Include the ROI calculation if you have it. "This investment of $48,000 annually will eliminate an estimated $120,000 in manual labor costs based on your current team size and processing volume" is a compelling frame.

**Next steps.** Specific actions for both sides with named owners and dates. "We will send the contract by [date]. Your team will provide the IT security review by [date]. Target signature is [date]."

**Appendix.** Reference case studies, technical documentation, security certifications, or anything the buyer might need but does not belong in the main body.

Train reps to customize the executive summary and situation summary for every proposal. Template the rest. Customization signals effort. Efficiency protects rep time.

---

## ROI Analysis Frameworks

An ROI framework gives buyers a structured way to quantify the value of your product in their specific context. It shifts the conversation from "how much does it cost" to "what is the expected return on this investment."

Build a simple ROI model that a rep can complete in 15 minutes during or after a discovery call:

**Step 1: Identify the cost drivers.** What is the buyer currently spending on the problem your product solves? This includes direct costs (software, labor, vendor fees) and indirect costs (time spent, error correction, opportunity cost).

**Step 2: Quantify current state.** Use numbers the buyer provided during discovery. "Your team spends 8 hours per week on this. That is 400 hours per year. At an average fully-loaded cost of $75 per hour, that is $30,000 per year in labor cost."

**Step 3: Project the improvement.** How much of that cost does your product eliminate or reduce? Be conservative. Buyers distrust optimistic projections. If your product typically reduces the time spent by 70 percent, use 60 percent in the model.

**Step 4: Calculate net value.** Subtract your product cost from the projected savings. "You save $18,000 in labor costs and invest $12,000 in our platform. Net first-year value is $6,000." In year two, when there is no implementation investment, the return improves significantly.

**Step 5: Present the payback period.** "Based on your numbers, you recover the investment in approximately 7 months." A short payback period reduces budget risk and makes it easier for the champion to justify internally.

Put the ROI model in a shared Google Sheet that the rep and the buyer fill out together during discovery. Collaborative models are more persuasive than models delivered after the fact, because the buyer owns the inputs.

---

## Battle Cards

A battle card is a one-page competitive reference document that a rep can review before a call where a specific competitor is likely to come up. It is not a smear document. It is a preparation tool that helps reps respond to competitive comparisons with confidence and accuracy.

A battle card for each competitor covers:

**Where you win.** The three to five scenarios where your product clearly outperforms this competitor. Be specific. "When the buyer's team is non-technical, our no-code setup process outperforms Competitor X's API-first approach" is specific. "We have a better user experience" is not.

**Where they win.** The scenarios where this competitor genuinely has an advantage. Reps who pretend a competitor has no strengths lose credibility when the buyer knows better. Acknowledging a competitor's strengths and then redirecting to where your advantages matter most is a stronger position.

**Their common claims and your responses.** If Competitor X typically says "we have more integrations," what is your honest, accurate response? Prepare it in advance.

**Proof points.** One or two customers who switched from this competitor to you with a specific result. "Beacon Software moved from Competitor X after their team hit the API rate limits on a peak usage day. They've been on our platform for 18 months without a single downtime incident."

**What to do when this competitor is in the deal.** Specific tactical advice. Which questions to ask to expose the competitor's weaknesses. Which product capabilities to emphasize. Whether to offer a comparison demo or a side-by-side trial.

Update battle cards quarterly. Competitor products change. Pricing changes. Win/loss patterns change. A battle card built on last year's competitor reality is worse than no battle card, because it gives reps false confidence.

---

## Making Enablement Materials Actually Get Used

The most common sales enablement failure is not bad content. It is content that never reaches the rep at the moment they need it.

Build distribution into your process:

- Store materials in a single location that reps know and use. If reps cannot find something in 30 seconds, they will not use it.
- Tag materials by use case, stage, and buyer persona so reps can search, not browse.
- Introduce new materials in a live session, not just a Slack announcement. Walk through the content. Answer questions. Show reps when and how to use it.
- Gather feedback 30 days after launch. Which materials are reps actually using? Which are they ignoring? Why?
- Retire outdated materials. A shared folder full of old decks and stale case studies forces reps to guess which version is current.

The ultimate measure of sales enablement quality is not how much content exists. It is win rate and deal velocity among reps who use the materials compared to those who do not. Track that. Build more of what moves the number.