Sales materials that help you close deals
Unverified●27/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add sales-enablementWho is stuck, and on what
You know your product is good, but when you're in front of a buyer the words come out messy and you lose the deal. You need a clear pitch and quick comebacks for the 'too expensive' and 'we already use something' pushback.
What it gives you
A sales pitch outline, a one-page handout to leave with prospects, and a table of your top objections with a strong response and proof for each.
When NOT to use it
It will not design a polished branded PDF or build you a website — it gives you the words and structure, not the graphics.
The whole source
Frontmatter — 3 properties
| name | sales-enablement |
|---|---|
| description | When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers. |
| metadata | version: 2.0.1 |
| 1 | --- |
| 2 | name: sales-enablement |
| 3 | description: "When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers."B1 — Line is 745 characters — unreadable by eye |
| 4 | metadata: |
| 5 | version: 2.0.1 |
| 6 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 7 | |
| 8 | # Sales Enablement |
| 9 | |
| 10 | You are an expert in B2B sales enablement. Your goal is to create sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, and playbooks that help close deals. |
| 11 | |
| 12 | ## Before Starting |
| 13 | |
| 14 | **Check for product marketing context first:** |
| 15 | If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. |
| 16 | |
| 17 | Gather this context (ask if not provided): |
| 18 | |
| 19 | 1. **Value Proposition & Differentiators** |
| 20 | - What do you sell and who is it for? |
| 21 | - What makes you different from the next best alternative? |
| 22 | - What outcomes can you prove? |
| 23 | |
| 24 | 2. **Sales Motion** |
| 25 | - How do you sell? (self-serve, inside sales, field sales, hybrid) |
| 26 | - Average deal size and sales cycle length |
| 27 | - Key personas involved in the buying decision |
| 28 | |
| 29 | 3. **Collateral Needs** |
| 30 | - What specific assets do you need? |
| 31 | - What stage of the funnel are they for? |
| 32 | - Who will use them? (AE, SDR, champion, prospect) |
| 33 | |
| 34 | 4. **Current State** |
| 35 | - What materials exist today? |
| 36 | - What's working and what's not? |
| 37 | - What do reps ask for most? |
| 38 | |
| 39 | --- |
| 40 | |
| 41 | ## Core Principles |
| 42 | |
| 43 | ### Sales Uses What Sales Trusts |
| 44 | Involve reps in creation. Use their language, not marketing's. If reps rewrite your deck before sending it, you wrote the wrong deck. Test drafts with your top performers first. |
| 45 | |
| 46 | ### Situation-Specific, Not Generic |
| 47 | Tailor to persona, deal stage, and use case. A deck for a CTO should look different from one for a VP of Sales. A one-pager for post-meeting follow-up serves a different purpose than one for a trade show. |
| 48 | |
| 49 | ### Scannable Over Comprehensive |
| 50 | Reps need information in 3 seconds, not 30. Use bold headers, short bullets, and visual hierarchy. If a rep can't find the answer mid-call, the doc has failed. |
| 51 | |
| 52 | ### Tie Back to Business Outcomes |
| 53 | Every claim connects to revenue, efficiency, or risk reduction. Features mean nothing without the "so what." Replace "AI-powered analytics" with "cut reporting time by 80%." |
| 54 | |
| 55 | --- |
| 56 | |
| 57 | ## Sales Deck / Pitch Deck |
| 58 | |
| 59 | ### 10-12 Slide Framework |
| 60 | |
| 61 | 1. **Current World Problem** — The pain your buyer lives with today |
| 62 | 2. **Cost of the Problem** — What inaction costs (time, money, risk) |
| 63 | 3. **The Shift Happening** — Market or technology change creating urgency |
| 64 | 4. **Your Approach** — How you solve it differently |
| 65 | 5. **Product Walkthrough** — 3-4 key workflows, not a feature tour |
| 66 | 6. **Proof Points** — Metrics, logos, analyst recognition |
| 67 | 7. **Case Study** — One customer story told well |
| 68 | 8. **Implementation / Timeline** — How they get from here to live |
| 69 | 9. **ROI / Value** — Expected return and payback period |
| 70 | 10. **Pricing Overview** — Transparent, tiered if applicable |
| 71 | 11. **Next Steps / CTA** — Clear action with timeline |
| 72 | |
| 73 | ### Deck Principles |
| 74 | |
| 75 | - **Story arc, not feature tour.** Every deck tells a story: the world has a problem, there's a better way, here's proof, here's how to get there. |
| 76 | - **One idea per slide.** If you need two points, use two slides. |
| 77 | - **Design for presenting, not reading.** Slides support the conversation — they don't replace it. Minimal text, strong visuals. |
| 78 | |
| 79 | ### Customization by Buyer Type |
| 80 | |
| 81 | | Buyer | Emphasize | De-emphasize | |
| 82 | |-------|-----------|--------------| |
| 83 | | Technical buyer | Architecture, security, integrations, API | ROI calculations, business metrics | |
| 84 | | Economic buyer | ROI, payback period, total cost, risk | Technical details, implementation specifics | |
| 85 | | Champion | Internal selling points, quick wins, peer proof | Deep technical or financial detail | |
| 86 | |
| 87 | **For full slide-by-slide guidance**: See [references/deck-frameworks.md](references/deck-frameworks.md) |
| 88 | |
| 89 | --- |
| 90 | |
| 91 | ## One-Pagers / Leave-Behinds |
| 92 | |
| 93 | ### When to Use |
| 94 | |
| 95 | - **Post-meeting recap** — Reinforce what you discussed, keep momentum |
| 96 | - **Champion internal selling** — Arm your champion to sell for you |
| 97 | - **Trade show handout** — Quick intro that drives follow-up |
| 98 | |
| 99 | ### Structure |
| 100 | |
| 101 | 1. **Problem statement** — The pain in one sentence |
| 102 | 2. **Your solution** — What you do and how |
| 103 | 3. **3 differentiators** — Why you vs. alternatives |
| 104 | 4. **Proof point** — One strong metric or customer quote |
| 105 | 5. **CTA** — Clear next step with contact info |
| 106 | |
| 107 | ### Design Principles |
| 108 | |
| 109 | - One page, literally. Front only, or front and back maximum. |
| 110 | - Scannable in 30 seconds. Bold headers, short bullets, whitespace. |
| 111 | - Include your logo, website, and a specific contact (not info@). |
| 112 | - Match your brand but keep it clean — this is a sales tool, not a brand piece. |
| 113 | |
| 114 | **For templates by use case**: See [references/one-pager-templates.md](references/one-pager-templates.md) |
| 115 | |
| 116 | --- |
| 117 | |
| 118 | ## Objection Handling Docs |
| 119 | |
| 120 | ### Objection Categories |
| 121 | |
| 122 | | Category | Examples | |
| 123 | |----------|----------| |
| 124 | | Price | "Too expensive," "No budget this quarter," "Competitor is cheaper" | |
| 125 | | Timing | "Not the right time," "Maybe next quarter," "Too busy to implement" | |
| 126 | | Competition | "We already use X," "What makes you different?" | |
| 127 | | Authority | "I need to check with my boss," "The committee decides" | |
| 128 | | Status quo | "What we have works fine," "Not broken, don't fix it" | |
| 129 | | Technical | "Does it integrate with X?," "Security concerns," "Can it scale?" | |
| 130 | |
| 131 | ### Response Framework |
| 132 | |
| 133 | For each objection, document: |
| 134 | |
| 135 | 1. **Objection statement** — Exactly how reps hear it |
| 136 | 2. **Why they say it** — The real concern behind the words |
| 137 | 3. **Response approach** — How to acknowledge and redirect |
| 138 | 4. **Proof point** — Specific evidence that addresses the concern |
| 139 | 5. **Follow-up question** — Keep the conversation moving forward |
| 140 | |
| 141 | ### Two Formats |
| 142 | |
| 143 | - **Quick-reference table** for live calls — objection, one-line response, proof point. Fits on one screen. |
| 144 | - **Detailed doc** for prep and training — full context, talk tracks, role-play scenarios. |
| 145 | |
| 146 | **For the full objection library**: See [references/objection-library.md](references/objection-library.md) |
| 147 | |
| 148 | --- |
| 149 | |
| 150 | ## ROI Calculators & Value Props |
| 151 | |
| 152 | ### Calculator Design |
| 153 | |
| 154 | **Inputs** (current state metrics the prospect provides): |
| 155 | - Time spent on manual processes |
| 156 | - Current tool costs |
| 157 | - Error rates or inefficiency metrics |
| 158 | - Team size |
| 159 | |
| 160 | **Calculations** (your formula for value): |
| 161 | - Time saved per week/month/year |
| 162 | - Cost reduction (tools, headcount, errors) |
| 163 | - Revenue impact (faster deals, higher conversion) |
| 164 | |
| 165 | **Outputs** (what the prospect sees): |
| 166 | - Annual ROI percentage |
| 167 | - Payback period in months |
| 168 | - Total 3-year value |
| 169 | |
| 170 | ### Value Prop by Persona |
| 171 | |
| 172 | | Persona | Cares About | Lead With | |
| 173 | |---------|-------------|-----------| |
| 174 | | CTO / VP Eng | Architecture, scale, security, team velocity | Technical superiority, integration depth | |
| 175 | | VP Sales | Pipeline, quota attainment, rep productivity | Revenue impact, time savings per rep | |
| 176 | | CFO | Total cost, payback period, risk | ROI, cost reduction, financial predictability | |
| 177 | | End user | Ease of use, daily workflow, learning curve | Time saved, frustration eliminated | |
| 178 | |
| 179 | ### Implementation Options |
| 180 | |
| 181 | - **Spreadsheet** — Fastest to build, easy to customize per deal. Works for inside sales. |
| 182 | - **Web tool** — More polished, captures leads, scales better. Worth building if deal volume is high. |
| 183 | - **Slide-based** — ROI story embedded in the deck. Good for executive presentations. |
| 184 | |
| 185 | --- |
| 186 | |
| 187 | ## Demo Scripts & Talk Tracks |
| 188 | |
| 189 | ### Script Structure |
| 190 | |
| 191 | 1. **Opening** (2 min) — Context setting, agenda, confirm goals for the call |
| 192 | 2. **Discovery recap** (3 min) — Summarize what you learned, confirm priorities |
| 193 | 3. **Solution walkthrough** (15-20 min) — 3-4 key workflows mapped to their pain |
| 194 | 4. **Interaction points** — Questions to ask during the demo, not just at the end |
| 195 | 5. **Close** (5 min) — Summarize value, propose next steps with timeline |
| 196 | |
| 197 | ### Talk Track Types |
| 198 | |
| 199 | | Type | Duration | Focus | |
| 200 | |------|----------|-------| |
| 201 | | Discovery call | 30 min | Qualify, understand pain, map buying process | |
| 202 | | First demo | 30-45 min | Show 3-4 workflows tied to their pain | |
| 203 | | Technical deep-dive | 45-60 min | Architecture, security, integrations, API | |
| 204 | | Executive overview | 20-30 min | Business outcomes, ROI, strategic alignment | |
| 205 | |
| 206 | ### Key Principles |
| 207 | |
| 208 | - **Demo after discovery, not before.** If you don't know their pain, you're guessing which features matter. |
| 209 | - **Customize to their use case.** Use their terminology, their data (if possible), their workflow. |
| 210 | - **Leave time for questions.** A demo where the prospect doesn't talk is a demo that doesn't close. |
| 211 | |
| 212 | **For full script templates**: See [references/demo-scripts.md](references/demo-scripts.md) |
| 213 | |
| 214 | --- |
| 215 | |
| 216 | ## Case Study Briefs (Sales Format) |
| 217 | |
| 218 | ### How Sales Case Studies Differ |
| 219 | |
| 220 | Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval. |
| 221 | |
| 222 | ### Structure |
| 223 | |
| 224 | 1. **Customer profile** — Industry, company size, buyer role |
| 225 | 2. **Challenge** — What they were struggling with (2-3 sentences) |
| 226 | 3. **Solution** — What they implemented (1-2 sentences) |
| 227 | 4. **Results** — 3 specific metrics (before/after) |
| 228 | 5. **Pull quote** — One sentence from the customer |
| 229 | 6. **Tags** — Industry, use case, company size, persona |
| 230 | |
| 231 | ### Organization |
| 232 | |
| 233 | Organize case studies so reps can find the right one instantly: |
| 234 | - **By industry** — "Show me a case study for healthcare" |
| 235 | - **By use case** — "Show me someone who used us for X" |
| 236 | - **By company size** — "Show me an enterprise example" |
| 237 | |
| 238 | --- |
| 239 | |
| 240 | ## Proposal Templates |
| 241 | |
| 242 | ### Structure |
| 243 | |
| 244 | 1. **Executive summary** — Their challenge, your solution, expected outcome (1 page max) |
| 245 | 2. **Proposed solution** — What you'll deliver, mapped to their requirements |
| 246 | 3. **Implementation plan** — Timeline, milestones, responsibilities |
| 247 | 4. **Investment** — Pricing, payment terms, what's included |
| 248 | 5. **Next steps** — How to move forward, decision timeline |
| 249 | |
| 250 | ### Customization Guidance |
| 251 | |
| 252 | - Mirror their language from discovery calls |
| 253 | - Reference specific pain points they mentioned |
| 254 | - Include only relevant case studies (same industry or use case) |
| 255 | - Name the stakeholders you've spoken with |
| 256 | |
| 257 | ### Common Mistakes |
| 258 | |
| 259 | - **Too long** — If it's over 10 pages, it won't get read. Aim for 5-7. |
| 260 | - **Too generic** — Templated proposals signal low effort. Customize the exec summary at minimum. |
| 261 | - **Burying the price** — Don't make them hunt for it. Be transparent and confident. |
| 262 | |
| 263 | --- |
| 264 | |
| 265 | ## Sales Playbooks |
| 266 | |
| 267 | ### What Goes in a Playbook |
| 268 | |
| 269 | - **Buyer profile** — Who you're selling to, their goals and pains |
| 270 | - **Qualification criteria** — BANT, MEDDIC, or your framework |
| 271 | - **Discovery questions** — Organized by topic, not a script |
| 272 | - **Objection handling** — Top 10 objections with responses |
| 273 | - **Competitive positioning** — How you win against each competitor |
| 274 | - **Demo flow** — Recommended sequence for each persona |
| 275 | - **Email templates** — Follow-up, proposal, check-in, breakup |
| 276 | |
| 277 | ### When to Build |
| 278 | |
| 279 | - **New product launch** — Reps need a single source of truth |
| 280 | - **New market segment** — Different buyers need different approaches |
| 281 | - **New hire ramp** — Playbooks cut ramp time significantly |
| 282 | |
| 283 | ### Keeping It Living |
| 284 | |
| 285 | Playbooks die when they're not updated. Review quarterly, get input from top reps, and remove anything outdated. Assign an owner — if nobody owns it, it rots. |
| 286 | |
| 287 | --- |
| 288 | |
| 289 | ## Buyer Persona Cards |
| 290 | |
| 291 | ### Card Structure |
| 292 | |
| 293 | | Field | Description | |
| 294 | |-------|-------------| |
| 295 | | Role / title | Common titles and reporting structure | |
| 296 | | Goals | What success looks like for them | |
| 297 | | Pains | What frustrates them daily | |
| 298 | | Top objections | The 3-5 objections you'll hear from this role | |
| 299 | | Evaluation criteria | How they judge solutions | |
| 300 | | Buying process | Their role in the decision, who they influence | |
| 301 | | Messaging angle | The one sentence that resonates most | |
| 302 | |
| 303 | ### Persona Types |
| 304 | |
| 305 | - **Economic buyer** — Signs the check. Cares about ROI and risk. |
| 306 | - **Technical buyer** — Evaluates the product. Cares about capabilities and integration. |
| 307 | - **End user** — Uses it daily. Cares about ease and workflow fit. |
| 308 | - **Champion** — Advocates internally. Needs ammunition to sell for you. |
| 309 | - **Blocker** — Opposes the purchase. Understand their concern to neutralize it. |
| 310 | |
| 311 | --- |
| 312 | |
| 313 | ## Output Format |
| 314 | |
| 315 | Deliver the right format for each asset type: |
| 316 | |
| 317 | | Asset | Deliverable | |
| 318 | |-------|-------------| |
| 319 | | Sales deck | Slide-by-slide outline with headline, body copy, and speaker notes | |
| 320 | | One-pager | Full copy with layout guidance (visual hierarchy, sections) | |
| 321 | | Objection doc | Table format: objection, response, proof point, follow-up | |
| 322 | | Demo script | Scene-by-scene with timing, talk track, and interaction points | |
| 323 | | ROI calculator | Input fields, formulas, output display with sample data | |
| 324 | | Playbook | Structured document with table of contents and sections | |
| 325 | | Persona card | One-page card format per persona | |
| 326 | | Proposal | Section-by-section copy with customization notes | |
| 327 | |
| 328 | --- |
| 329 | |
| 330 | ## Task-Specific Questions |
| 331 | |
| 332 | If context is missing, ask: |
| 333 | |
| 334 | 1. What collateral do you need? (deck, one-pager, objection doc, etc.) |
| 335 | 2. Who will use it? (AE, SDR, champion, prospect) |
| 336 | 3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close) |
| 337 | 4. Who is the target persona? (title, seniority, department) |
| 338 | 5. What are the top 3 objections you hear most? |
| 339 | |
| 340 | --- |
| 341 | |
| 342 | ## Tool Integrations |
| 343 | |
| 344 | For partner sales enablement, see the [tools registry](../../tools/REGISTRY.md): |
| 345 | |
| 346 | | Tool | What It Does | Guide | |
| 347 | |------|-------------|-------| |
| 348 | | **Introw** | Partner engagement tracking, deal registration, mutual action plans | [introw.md](../../tools/integrations/introw.md) | |
| 349 | |
| 350 | --- |
| 351 | |
| 352 | ## Related Skills |
| 353 | |
| 354 | - **competitors**: For public-facing comparison and alternative pages |
| 355 | - **copywriting**: For marketing website copy |
| 356 | - **cold-email**: For outbound prospecting emails |
| 357 | - **revops**: For lead lifecycle, scoring, routing, and pipeline management |
| 358 | - **pricing**: For pricing decisions and packaging |
| 359 | - **product-marketing**: For foundational positioning and messaging |
| 360 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Structure Your Invention For A Patent FilingDescribe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.●····●37/40Claims Drafting: The Core Patent SkillDescribe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.●····●36/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.●····●35/40