Portability note: This skill is model-portable and has no VPS-only dependencies. The optional .agents/product-marketing-context.md / .claude/product-marketing-context.md lookup is a convenience: if the file is absent, gather context via the questions below instead.
Sales Enablement
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.
Single-voice craft (do NOT parallelize)
Sales collateral is one coherent persuasive voice per asset — the voice of a rep who knows the buyer's pain and can close. Do NOT fan out a deck or one-pager across parallel sub-agents: a multi-author deck reads as a feature list stitched by committee, exactly the "wrote the wrong deck" failure reps rewrite before sending. Build each asset linearly, end to end, in one hand.
Craft upgrades:
- Earn every slide/section before adding the next. Write the story arc first (problem → cost → shift → your way → proof → path), then fill copy. If a slide doesn't advance the close, cut it — a tight 8-slide deck beats a complete 14-slide one.
- One buyer, one verb, one number per claim. Replace abstractions with the buyer's own language plus a concrete metric: not "AI-powered analytics" but "cut your monthly close from 9 days to 2." Every claim names the persona it's for (see the Customization-by-Buyer table) and ties back to revenue, efficiency, or risk.
- Read it aloud as the rep mid-call. If a line can't be said naturally in a live call or scanned in 3 seconds on a follow-up, it's marketing prose, not a sales tool — rewrite it shorter and in second person ("you," "your team").
Before Starting
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Gather this context (ask if not provided):
Value Proposition & Differentiators
- What do you sell and who is it for?
- What makes you different from the next best alternative?
- What outcomes can you prove?
Sales Motion
- How do you sell? (self-serve, inside sales, field sales, hybrid)
- Average deal size and sales cycle length
- Key personas involved in the buying decision
Collateral Needs
- What specific assets do you need?
- What stage of the funnel are they for?
- Who will use them? (AE, SDR, champion, prospect)
Current State
- What materials exist today?
- What's working and what's not?
- What do reps ask for most?
Core Principles
Sales Uses What Sales Trusts
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.
Situation-Specific, Not Generic
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.
Scannable Over Comprehensive
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.
Tie Back to Business Outcomes
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%."
Sales Deck / Pitch Deck
10-12 Slide Framework
- Current World Problem — The pain your buyer lives with today
- Cost of the Problem — What inaction costs (time, money, risk)
- The Shift Happening — Market or technology change creating urgency
- Your Approach — How you solve it differently
- Product Walkthrough — 3-4 key workflows, not a feature tour
- Proof Points — Metrics, logos, analyst recognition
- Case Study — One customer story told well
- Implementation / Timeline — How they get from here to live
- ROI / Value — Expected return and payback period
- Pricing Overview — Transparent, tiered if applicable
- Next Steps / CTA — Clear action with timeline
Deck Principles
- 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.
- One idea per slide. If you need two points, use two slides.
- Design for presenting, not reading. Slides support the conversation — they don't replace it. Minimal text, strong visuals.
Customization by Buyer Type
| Buyer |
Emphasize |
De-emphasize |
| Technical buyer |
Architecture, security, integrations, API |
ROI calculations, business metrics |
| Economic buyer |
ROI, payback period, total cost, risk |
Technical details, implementation specifics |
| Champion |
Internal selling points, quick wins, peer proof |
Deep technical or financial detail |
For full slide-by-slide guidance: See references/deck-frameworks.md
One-Pagers / Leave-Behinds
When to Use
- Post-meeting recap — Reinforce what you discussed, keep momentum
- Champion internal selling — Arm your champion to sell for you
- Trade show handout — Quick intro that drives follow-up
Structure
- Problem statement — The pain in one sentence
- Your solution — What you do and how
- 3 differentiators — Why you vs. alternatives
- Proof point — One strong metric or customer quote
- CTA — Clear next step with contact info
Design Principles
- One page, literally. Front only, or front and back maximum.
- Scannable in 30 seconds. Bold headers, short bullets, whitespace.
- Include your logo, website, and a specific contact (not info@).
- Match your brand but keep it clean — this is a sales tool, not a brand piece.
For templates by use case: See references/one-pager-templates.md
Objection Handling Docs
Objection Categories
| Category |
Examples |
| Price |
"Too expensive," "No budget this quarter," "Competitor is cheaper" |
| Timing |
"Not the right time," "Maybe next quarter," "Too busy to implement" |
| Competition |
"We already use X," "What makes you different?" |
| Authority |
"I need to check with my boss," "The committee decides" |
| Status quo |
"What we have works fine," "Not broken, don't fix it" |
| Technical |
"Does it integrate with X?," "Security concerns," "Can it scale?" |
Response Framework
For each objection, document:
- Objection statement — Exactly how reps hear it
- Why they say it — The real concern behind the words
- Response approach — How to acknowledge and redirect
- Proof point — Specific evidence that addresses the concern
- Follow-up question — Keep the conversation moving forward
Two Formats
- Quick-reference table for live calls — objection, one-line response, proof point. Fits on one screen.
- Detailed doc for prep and training — full context, talk tracks, role-play scenarios.
For the full objection library: See references/objection-library.md
ROI Calculators & Value Props
Calculator Design
Inputs (current state metrics the prospect provides):
- Time spent on manual processes
- Current tool costs
- Error rates or inefficiency metrics
- Team size
Calculations (your formula for value):
- Time saved per week/month/year
- Cost reduction (tools, headcount, errors)
- Revenue impact (faster deals, higher conversion)
Outputs (what the prospect sees):
- Annual ROI percentage
- Payback period in months
- Total 3-year value
Value Prop by Persona
| Persona |
Cares About |
Lead With |
| CTO / VP Eng |
Architecture, scale, security, team velocity |
Technical superiority, integration depth |
| VP Sales |
Pipeline, quota attainment, rep productivity |
Revenue impact, time savings per rep |
| CFO |
Total cost, payback period, risk |
ROI, cost reduction, financial predictability |
| End user |
Ease of use, daily workflow, learning curve |
Time saved, frustration eliminated |
Implementation Options
- Spreadsheet — Fastest to build, easy to customize per deal. Works for inside sales.
- Web tool — More polished, captures leads, scales better. Worth building if deal volume is high.
- Slide-based — ROI story embedded in the deck. Good for executive presentations.
Demo Scripts & Talk Tracks
Script Structure
- Opening (2 min) — Context setting, agenda, confirm goals for the call
- Discovery recap (3 min) — Summarize what you learned, confirm priorities
- Solution walkthrough (15-20 min) — 3-4 key workflows mapped to their pain
- Interaction points — Questions to ask during the demo, not just at the end
- Close (5 min) — Summarize value, propose next steps with timeline
Talk Track Types
| Type |
Duration |
Focus |
| Discovery call |
30 min |
Qualify, understand pain, map buying process |
| First demo |
30-45 min |
Show 3-4 workflows tied to their pain |
| Technical deep-dive |
45-60 min |
Architecture, security, integrations, API |
| Executive overview |
20-30 min |
Business outcomes, ROI, strategic alignment |
Key Principles
- Demo after discovery, not before. If you don't know their pain, you're guessing which features matter.
- Customize to their use case. Use their terminology, their data (if possible), their workflow.
- Leave time for questions. A demo where the prospect doesn't talk is a demo that doesn't close.
For full script templates: See references/demo-scripts.md
Case Study Briefs (Sales Format)
How Sales Case Studies Differ
Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.
Structure
- Customer profile — Industry, company size, buyer role
- Challenge — What they were struggling with (2-3 sentences)
- Solution — What they implemented (1-2 sentences)
- Results — 3 specific metrics (before/after)
- Pull quote — One sentence from the customer
- Tags — Industry, use case, company size, persona
Organization
Organize case studies so reps can find the right one instantly:
- By industry — "Show me a case study for healthcare"
- By use case — "Show me someone who used us for X"
- By company size — "Show me an enterprise example"
Proposal Templates
Structure
- Executive summary — Their challenge, your solution, expected outcome (1 page max)
- Proposed solution — What you'll deliver, mapped to their requirements
- Implementation plan — Timeline, milestones, responsibilities
- Investment — Pricing, payment terms, what's included
- Next steps — How to move forward, decision timeline
Customization Guidance
- Mirror their language from discovery calls
- Reference specific pain points they mentioned
- Include only relevant case studies (same industry or use case)
- Name the stakeholders you've spoken with
Common Mistakes
- Too long — If it's over 10 pages, it won't get read. Aim for 5-7.
- Too generic — Templated proposals signal low effort. Customize the exec summary at minimum.
- Burying the price — Don't make them hunt for it. Be transparent and confident.
Sales Playbooks
What Goes in a Playbook
- Buyer profile — Who you're selling to, their goals and pains
- Qualification criteria — BANT, MEDDIC, or your framework
- Discovery questions — Organized by topic, not a script
- Objection handling — Top 10 objections with responses
- Competitive positioning — How you win against each competitor
- Demo flow — Recommended sequence for each persona
- Email templates — Follow-up, proposal, check-in, breakup
When to Build
- New product launch — Reps need a single source of truth
- New market segment — Different buyers need different approaches
- New hire ramp — Playbooks cut ramp time significantly
Keeping It Living
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.
Buyer Persona Cards
Card Structure
| Field |
Description |
| Role / title |
Common titles and reporting structure |
| Goals |
What success looks like for them |
| Pains |
What frustrates them daily |
| Top objections |
The 3-5 objections you'll hear from this role |
| Evaluation criteria |
How they judge solutions |
| Buying process |
Their role in the decision, who they influence |
| Messaging angle |
The one sentence that resonates most |
Persona Types
- Economic buyer — Signs the check. Cares about ROI and risk.
- Technical buyer — Evaluates the product. Cares about capabilities and integration.
- End user — Uses it daily. Cares about ease and workflow fit.
- Champion — Advocates internally. Needs ammunition to sell for you.
- Blocker — Opposes the purchase. Understand their concern to neutralize it.
Output Format
Deliver the right format for each asset type:
| Asset |
Deliverable |
| Sales deck |
Slide-by-slide outline with headline, body copy, and speaker notes |
| One-pager |
Full copy with layout guidance (visual hierarchy, sections) |
| Objection doc |
Table format: objection, response, proof point, follow-up |
| Demo script |
Scene-by-scene with timing, talk track, and interaction points |
| ROI calculator |
Input fields, formulas, output display with sample data |
| Playbook |
Structured document with table of contents and sections |
| Persona card |
One-page card format per persona |
| Proposal |
Section-by-section copy with customization notes |
Verify before delivering (run this checklist on every asset)
- Format match — the deliverable matches the asset type's row above (a deck is slide-by-slide with speaker notes, an objection doc is a table, etc.).
- Every claim is grounded — each metric, logo, case-study result, ROI figure, or analyst mention comes from context the user provided. NEVER invent customer names, numbers, quotes, or proof points. If a slot needs proof the user hasn't supplied, insert an explicit
[PLACEHOLDER: add real metric/customer/quote] and list these gaps at the end — do not fabricate to fill them.
- Scannable test — a rep can find any answer in under 3 seconds; headers bold, bullets short, one idea per slide/section.
- Persona alignment — copy emphasizes/de-emphasizes per the target buyer (technical / economic / champion / end user).
- Scope discipline — produced only the asset(s) the user asked for; did not silently expand into adjacent assets or rewrite the user's product positioning.
State which checklist items passed and list any [PLACEHOLDER] gaps the user must fill.
Task-Specific Questions
If context is missing, ask:
- What collateral do you need? (deck, one-pager, objection doc, etc.)
- Who will use it? (AE, SDR, champion, prospect)
- What sales stage is it for? (prospecting, discovery, demo, negotiation, close)
- Who is the target persona? (title, seniority, department)
- What are the top 3 objections you hear most?
Related Skills
- competitor-alternatives: For public-facing comparison and alternative pages
- copywriting: For marketing website copy
- cold-email: For outbound prospecting emails
- revops: For lead lifecycle, scoring, routing, and pipeline management
- pricing-strategy: For pricing decisions and packaging
- product-marketing-context: For foundational positioning and messaging
1---2name: mk-sales-enablement3description: "Create B2B sales collateral that reps actually use — decks, one-pagers, objection docs, demo scripts, ROI calculators, playbooks, persona cards, proposals. EN triggers: 'sales deck', 'pitch deck', 'one-pager', 'leave-behind', 'objection handling', 'deal-specific ROI', 'demo script', 'talk track', 'sales playbook', 'proposal template', 'buyer persona card', 'help my sales team', 'sales materials', 'what should I give my sales reps', 'sales enablement'. FR triggers: 'deck de vente', 'pitch deck', 'one-pager', 'gestion des objections', 'script de démo', 'playbook commercial', 'modèle de proposition', 'fiche persona acheteur', 'matériel de vente', 'aide mon équipe commerciale', 'calculateur ROI'. Use for any asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitor-alternatives. For marketing website copy, see copywriting. For cold outreach emails, see cold-email."4metadata:5 source: https://skillmd.com/skills/agentik-os/mk-sales-enablement6 version: 1.2.07---89> **Portability note:** This skill is model-portable and has no VPS-only dependencies. The optional `.agents/product-marketing-context.md` / `.claude/product-marketing-context.md` lookup is a convenience: if the file is absent, gather context via the questions below instead.1011# Sales Enablement1213You 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.1415## Single-voice craft (do NOT parallelize)1617Sales collateral is **one coherent persuasive voice per asset** — the voice of a rep who knows the buyer's pain and can close. Do NOT fan out a deck or one-pager across parallel sub-agents: a multi-author deck reads as a feature list stitched by committee, exactly the "wrote the wrong deck" failure reps rewrite before sending. Build each asset linearly, end to end, in one hand.1819**Craft upgrades:**20- **Earn every slide/section before adding the next.** Write the story arc first (problem → cost → shift → your way → proof → path), then fill copy. If a slide doesn't advance the close, cut it — a tight 8-slide deck beats a complete 14-slide one.21- **One buyer, one verb, one number per claim.** Replace abstractions with the buyer's own language plus a concrete metric: not "AI-powered analytics" but "cut your monthly close from 9 days to 2." Every claim names the persona it's for (see the Customization-by-Buyer table) and ties back to revenue, efficiency, or risk.22- **Read it aloud as the rep mid-call.** If a line can't be said naturally in a live call or scanned in 3 seconds on a follow-up, it's marketing prose, not a sales tool — rewrite it shorter and in second person ("you," "your team").2324## Before Starting2526**Check for product marketing context first:**27If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.2829Gather this context (ask if not provided):30311. **Value Proposition & Differentiators**32 - What do you sell and who is it for?33 - What makes you different from the next best alternative?34 - What outcomes can you prove?35362. **Sales Motion**37 - How do you sell? (self-serve, inside sales, field sales, hybrid)38 - Average deal size and sales cycle length39 - Key personas involved in the buying decision40413. **Collateral Needs**42 - What specific assets do you need?43 - What stage of the funnel are they for?44 - Who will use them? (AE, SDR, champion, prospect)45464. **Current State**47 - What materials exist today?48 - What's working and what's not?49 - What do reps ask for most?5051---5253## Core Principles5455### Sales Uses What Sales Trusts56Involve 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.5758### Situation-Specific, Not Generic59Tailor 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.6061### Scannable Over Comprehensive62Reps 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.6364### Tie Back to Business Outcomes65Every 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%."6667---6869## Sales Deck / Pitch Deck7071### 10-12 Slide Framework72731. **Current World Problem** — The pain your buyer lives with today742. **Cost of the Problem** — What inaction costs (time, money, risk)753. **The Shift Happening** — Market or technology change creating urgency764. **Your Approach** — How you solve it differently775. **Product Walkthrough** — 3-4 key workflows, not a feature tour786. **Proof Points** — Metrics, logos, analyst recognition797. **Case Study** — One customer story told well808. **Implementation / Timeline** — How they get from here to live819. **ROI / Value** — Expected return and payback period8210. **Pricing Overview** — Transparent, tiered if applicable8311. **Next Steps / CTA** — Clear action with timeline8485### Deck Principles8687- **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.88- **One idea per slide.** If you need two points, use two slides.89- **Design for presenting, not reading.** Slides support the conversation — they don't replace it. Minimal text, strong visuals.9091### Customization by Buyer Type9293| Buyer | Emphasize | De-emphasize |94|-------|-----------|--------------|95| Technical buyer | Architecture, security, integrations, API | ROI calculations, business metrics |96| Economic buyer | ROI, payback period, total cost, risk | Technical details, implementation specifics |97| Champion | Internal selling points, quick wins, peer proof | Deep technical or financial detail |9899**For full slide-by-slide guidance**: See [references/deck-frameworks.md](references/deck-frameworks.md)100101---102103## One-Pagers / Leave-Behinds104105### When to Use106107- **Post-meeting recap** — Reinforce what you discussed, keep momentum108- **Champion internal selling** — Arm your champion to sell for you109- **Trade show handout** — Quick intro that drives follow-up110111### Structure1121131. **Problem statement** — The pain in one sentence1142. **Your solution** — What you do and how1153. **3 differentiators** — Why you vs. alternatives1164. **Proof point** — One strong metric or customer quote1175. **CTA** — Clear next step with contact info118119### Design Principles120121- One page, literally. Front only, or front and back maximum.122- Scannable in 30 seconds. Bold headers, short bullets, whitespace.123- Include your logo, website, and a specific contact (not info@).124- Match your brand but keep it clean — this is a sales tool, not a brand piece.125126**For templates by use case**: See [references/one-pager-templates.md](references/one-pager-templates.md)127128---129130## Objection Handling Docs131132### Objection Categories133134| Category | Examples |135|----------|----------|136| Price | "Too expensive," "No budget this quarter," "Competitor is cheaper" |137| Timing | "Not the right time," "Maybe next quarter," "Too busy to implement" |138| Competition | "We already use X," "What makes you different?" |139| Authority | "I need to check with my boss," "The committee decides" |140| Status quo | "What we have works fine," "Not broken, don't fix it" |141| Technical | "Does it integrate with X?," "Security concerns," "Can it scale?" |142143### Response Framework144145For each objection, document:1461471. **Objection statement** — Exactly how reps hear it1482. **Why they say it** — The real concern behind the words1493. **Response approach** — How to acknowledge and redirect1504. **Proof point** — Specific evidence that addresses the concern1515. **Follow-up question** — Keep the conversation moving forward152153### Two Formats154155- **Quick-reference table** for live calls — objection, one-line response, proof point. Fits on one screen.156- **Detailed doc** for prep and training — full context, talk tracks, role-play scenarios.157158**For the full objection library**: See [references/objection-library.md](references/objection-library.md)159160---161162## ROI Calculators & Value Props163164### Calculator Design165166**Inputs** (current state metrics the prospect provides):167- Time spent on manual processes168- Current tool costs169- Error rates or inefficiency metrics170- Team size171172**Calculations** (your formula for value):173- Time saved per week/month/year174- Cost reduction (tools, headcount, errors)175- Revenue impact (faster deals, higher conversion)176177**Outputs** (what the prospect sees):178- Annual ROI percentage179- Payback period in months180- Total 3-year value181182### Value Prop by Persona183184| Persona | Cares About | Lead With |185|---------|-------------|-----------|186| CTO / VP Eng | Architecture, scale, security, team velocity | Technical superiority, integration depth |187| VP Sales | Pipeline, quota attainment, rep productivity | Revenue impact, time savings per rep |188| CFO | Total cost, payback period, risk | ROI, cost reduction, financial predictability |189| End user | Ease of use, daily workflow, learning curve | Time saved, frustration eliminated |190191### Implementation Options192193- **Spreadsheet** — Fastest to build, easy to customize per deal. Works for inside sales.194- **Web tool** — More polished, captures leads, scales better. Worth building if deal volume is high.195- **Slide-based** — ROI story embedded in the deck. Good for executive presentations.196197---198199## Demo Scripts & Talk Tracks200201### Script Structure2022031. **Opening** (2 min) — Context setting, agenda, confirm goals for the call2042. **Discovery recap** (3 min) — Summarize what you learned, confirm priorities2053. **Solution walkthrough** (15-20 min) — 3-4 key workflows mapped to their pain2064. **Interaction points** — Questions to ask during the demo, not just at the end2075. **Close** (5 min) — Summarize value, propose next steps with timeline208209### Talk Track Types210211| Type | Duration | Focus |212|------|----------|-------|213| Discovery call | 30 min | Qualify, understand pain, map buying process |214| First demo | 30-45 min | Show 3-4 workflows tied to their pain |215| Technical deep-dive | 45-60 min | Architecture, security, integrations, API |216| Executive overview | 20-30 min | Business outcomes, ROI, strategic alignment |217218### Key Principles219220- **Demo after discovery, not before.** If you don't know their pain, you're guessing which features matter.221- **Customize to their use case.** Use their terminology, their data (if possible), their workflow.222- **Leave time for questions.** A demo where the prospect doesn't talk is a demo that doesn't close.223224**For full script templates**: See [references/demo-scripts.md](references/demo-scripts.md)225226---227228## Case Study Briefs (Sales Format)229230### How Sales Case Studies Differ231232Marketing case studies tell a story. Sales case studies arm reps with fast-access proof. Keep them short, outcome-focused, and tagged for retrieval.233234### Structure2352361. **Customer profile** — Industry, company size, buyer role2372. **Challenge** — What they were struggling with (2-3 sentences)2383. **Solution** — What they implemented (1-2 sentences)2394. **Results** — 3 specific metrics (before/after)2405. **Pull quote** — One sentence from the customer2416. **Tags** — Industry, use case, company size, persona242243### Organization244245Organize case studies so reps can find the right one instantly:246- **By industry** — "Show me a case study for healthcare"247- **By use case** — "Show me someone who used us for X"248- **By company size** — "Show me an enterprise example"249250---251252## Proposal Templates253254### Structure2552561. **Executive summary** — Their challenge, your solution, expected outcome (1 page max)2572. **Proposed solution** — What you'll deliver, mapped to their requirements2583. **Implementation plan** — Timeline, milestones, responsibilities2594. **Investment** — Pricing, payment terms, what's included2605. **Next steps** — How to move forward, decision timeline261262### Customization Guidance263264- Mirror their language from discovery calls265- Reference specific pain points they mentioned266- Include only relevant case studies (same industry or use case)267- Name the stakeholders you've spoken with268269### Common Mistakes270271- **Too long** — If it's over 10 pages, it won't get read. Aim for 5-7.272- **Too generic** — Templated proposals signal low effort. Customize the exec summary at minimum.273- **Burying the price** — Don't make them hunt for it. Be transparent and confident.274275---276277## Sales Playbooks278279### What Goes in a Playbook280281- **Buyer profile** — Who you're selling to, their goals and pains282- **Qualification criteria** — BANT, MEDDIC, or your framework283- **Discovery questions** — Organized by topic, not a script284- **Objection handling** — Top 10 objections with responses285- **Competitive positioning** — How you win against each competitor286- **Demo flow** — Recommended sequence for each persona287- **Email templates** — Follow-up, proposal, check-in, breakup288289### When to Build290291- **New product launch** — Reps need a single source of truth292- **New market segment** — Different buyers need different approaches293- **New hire ramp** — Playbooks cut ramp time significantly294295### Keeping It Living296297Playbooks 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.298299---300301## Buyer Persona Cards302303### Card Structure304305| Field | Description |306|-------|-------------|307| Role / title | Common titles and reporting structure |308| Goals | What success looks like for them |309| Pains | What frustrates them daily |310| Top objections | The 3-5 objections you'll hear from this role |311| Evaluation criteria | How they judge solutions |312| Buying process | Their role in the decision, who they influence |313| Messaging angle | The one sentence that resonates most |314315### Persona Types316317- **Economic buyer** — Signs the check. Cares about ROI and risk.318- **Technical buyer** — Evaluates the product. Cares about capabilities and integration.319- **End user** — Uses it daily. Cares about ease and workflow fit.320- **Champion** — Advocates internally. Needs ammunition to sell for you.321- **Blocker** — Opposes the purchase. Understand their concern to neutralize it.322323---324325## Output Format326327Deliver the right format for each asset type:328329| Asset | Deliverable |330|-------|-------------|331| Sales deck | Slide-by-slide outline with headline, body copy, and speaker notes |332| One-pager | Full copy with layout guidance (visual hierarchy, sections) |333| Objection doc | Table format: objection, response, proof point, follow-up |334| Demo script | Scene-by-scene with timing, talk track, and interaction points |335| ROI calculator | Input fields, formulas, output display with sample data |336| Playbook | Structured document with table of contents and sections |337| Persona card | One-page card format per persona |338| Proposal | Section-by-section copy with customization notes |339340### Verify before delivering (run this checklist on every asset)3413421. **Format match** — the deliverable matches the asset type's row above (a deck is slide-by-slide with speaker notes, an objection doc is a table, etc.).3432. **Every claim is grounded** — each metric, logo, case-study result, ROI figure, or analyst mention comes from context the user provided. NEVER invent customer names, numbers, quotes, or proof points. If a slot needs proof the user hasn't supplied, insert an explicit `[PLACEHOLDER: add real metric/customer/quote]` and list these gaps at the end — do not fabricate to fill them.3443. **Scannable test** — a rep can find any answer in under 3 seconds; headers bold, bullets short, one idea per slide/section.3454. **Persona alignment** — copy emphasizes/de-emphasizes per the target buyer (technical / economic / champion / end user).3465. **Scope discipline** — produced only the asset(s) the user asked for; did not silently expand into adjacent assets or rewrite the user's product positioning.347348State which checklist items passed and list any `[PLACEHOLDER]` gaps the user must fill.349350---351352## Task-Specific Questions353354If context is missing, ask:3553561. What collateral do you need? (deck, one-pager, objection doc, etc.)3572. Who will use it? (AE, SDR, champion, prospect)3583. What sales stage is it for? (prospecting, discovery, demo, negotiation, close)3594. Who is the target persona? (title, seniority, department)3605. What are the top 3 objections you hear most?361362---363364## Related Skills365366- **competitor-alternatives**: For public-facing comparison and alternative pages367- **copywriting**: For marketing website copy368- **cold-email**: For outbound prospecting emails369- **revops**: For lead lifecycle, scoring, routing, and pipeline management370- **pricing-strategy**: For pricing decisions and packaging371- **product-marketing-context**: For foundational positioning and messaging