sales-enablement · 스킬 지원 에이전트
영업 미팅에서 사용할 제품 소개 자료, 한 장짜리 설명과 데모 순서를 정리합니다.
기능은 많은데 고객에게 어떤 순서로 보여줘야 할지 막막할 때 활용합니다. 상대가 해결하려는 문제와 확인하고 싶은 근거를 중심으로 자료를 구성합니다.
고객군과 미팅 목적을 알려주면 소개, 데모와 예상 질문을 연결할 수 있습니다. 실제 성과 수치와 사례만 사용하도록 요청하세요. 결과물을 그대로 보내기보다 고객 상황과 제공 범위를 검토하고 필요한 부분을 조정합니다.
sales-enablement로 소규모 팀에 문서 서비스를 소개할 한 장짜리 자료를 구성해줘. 문제, 기능, 활용 예시와 도입 전에 물어볼 질문을 넣어줘.
받을 수 있는 결과소개 자료·데모 순서·예상 질문 답변
스킬 지원 에이전트가 필요합니다. 실제 PDF·슬라이드 제작과 고객에게 보내는 작업은 별도입니다.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/coreyhaines31/marketingskills 에서 skills/sales-enablement 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 sales-enablement 스킬을 인식하는지 확인해줘.
“sales-enablement 스킬을 사용해줘. 입력 자료: 제품·고객 문제·실제 사례·미팅 목적”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘소개 자료·데모 순서·예상 질문 답변’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 실제 설치·실행 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- 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,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' '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 public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. 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.3.2 --- # 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. ## Before Starting **Check for product marketing context first:** 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. Gather this context (ask if not provided): 1. **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? 2. **Sales Motion** - How do you sell? (self-serve, inside sales, field sales, hybrid)--- 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,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' '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 public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. 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.3.2 --- # 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. ## Before Starting **Check for product marketing context first:** 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. Gather this context (ask if not provided): 1. **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? 2. **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 3. **Collateral Needs** - What specific assets do you need? - What stage of the funnel are they for? - Who will use them? (AE, SDR, champion, prospect) 4. **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%." ### Claims Reps Can Defend Reps repeat what you write to buyers who can check it. Anything a buyer can disprove in a minute costs more than it gains. - **"Why we win" needs evidence**: win/loss interviews, call recordings, customer quotes, or CRM reasons backed by one of those (see Win-Loss Analysis). Without it, write advantages as hypotheses for reps to test, and say what evidence would confirm them. - **Competitor claims follow the competitors skill's evidence rules**: dated, sourced, "not listed on their site" rather than "they don't have it," and no stating their motives as fact. Reps can reason about why a competitor did something, labeled as a guess. - **Include where you lose.** A competitive doc that admits when the competitor is the better fit is one reps will trust in front of a buyer. --- ## Sales Deck / Pitch Deck ### 10-12 Slide Framework 1. **Current World Problem** — The pain your buyer lives with today 2. **Cost of the Problem** — What inaction costs (time, money, risk) 3. **The Shift Happening** — Market or technology change creating urgency 4. **Your Approach** — How you solve it differently 5. **Product Walkthrough** — 3-4 key workflows, not a feature tour 6. **Proof Points** — Metrics, logos, analyst recognition 7. **Case Study** — One customer story told well 8. **Implementation / Timeline** — How they get from here to live 9. **ROI / Value** — Expected return and payback period 10. **Pricing Overview** — Transparent, tiered if applicable 11. **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](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 1. **Problem statement** — The pain in one sentence 2. **Your solution** — What you do and how 3. **3 differentiators** — Why you vs. alternatives 4. **Proof point** — One strong metric or customer quote 5. **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](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: 1. **Objection statement** — Exactly how reps hear it 2. **Why they say it** — The real concern behind the words 3. **Response approach** — How to acknowledge and redirect 4. **Proof point** — Specific evidence that addresses the concern 5. **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](references/objection-library.md) ### Live Deal Objection When a rep brings one objection from a live deal ("the CFO just said Acme is half the price, I have a call in an hour"), answer that deal. Don't hand back a generic doc. 1. **Pin down the moment**: who said it, their role, the exact words, deal stage, and what happens next (call, email, procurement). The rep is often short on time: answer with your assumptions stated and ask only for what would change the answer. 2. **Name the likely concern behind it** and say what in the deal points to it. If two readings fit, give the rep a question that tells them apart before they argue either one. 3. **Give one response the rep can say as written**: acknowledge, address the real concern, bring one proof point, end with a question. 4. **Use only proof the rep can stand behind.** Pull from the objection library, case studies, and battle cards. If nothing fits, say so and suggest the claim to verify. Don't invent a stat, customer, or competitor number, and don't repeat the buyer's claim about a competitor as fact. "Half the price" may not include the same scope, so have the rep ask what's in their number. 5. **Say when not to fight.** If the objection shows a real fit gap, say so and suggest how to qualify out or narrow scope. Afterward, suggest the rep log the objection and how it went. Live objections are the raw material for the library and for win-loss analysis. --- ## Battle Cards A battle card is a reusable one-competitor guide for reps, used across many deals. For a single live objection, use Live Deal Objection. For public comparison pages, see competitors. Every line follows Claims Reps Can Defend. **Ask which competitor.** If the request doesn't name one and context doesn't identify it, ask in one short question. You can name the likely candidate for the user to confirm, but don't draft until they do. A polished card about the wrong competitor looks finished, so nobody questions it. ### Structure 1. **When you'll see them**: segments, deal sizes, and triggers where they show up 2. **Why buyers consider them**: their real appeal, in the buyer's words 3. **Where they're strong**: honest, so reps aren't blindsided 4. **Where we win, and for whom**: tied to evidence (see Claims Reps Can Defend) 5. **Discovery questions**: questions that surface the fit criteria where you're stronger, without trashing them 6. **Top objections**: with one-line responses and proof 7. **When to walk away**: deal profiles where they're the better fit 8. **Last verified**: date, and what changed since the previous version ### Keeping It Current - Re-verify pricing and packaging quarterly, and whenever reps hear something new in deals. - Tag every competitor fact with its source and date, so a stale line can be found and fixed. - One page. If reps can't find the answer mid-call, cut until they can. Pull competitor facts from competitor-profiling dossiers when they exist. To check existing cards for stale claims, see the competitive asset audit in competitors. --- ## Win-Loss Analysis Win-loss analysis turns CRM outcomes, call transcripts, and buyer interviews into an evidence-backed answer to "why do we win and lose, against whom?" It's the evidence that battle cards and "why we win" sections need. ### Workflow 1. **Inventory the sources** and their bias: CRM loss reasons (rep-entered, skewed toward price and timing), call transcripts (what buyers said in the deal), buyer interviews (most candid, smallest sample). 2. **Include wins.** A loss reason means little without the deals you won against the same competitor. 3. **Segment before you count.** Split by competitor, segment, deal size, and stage lost. "We lose on price" across everything often hides "we lose mid-market deals to one competitor on onboarding." 4. **Code each deal** with one primary reason (plus any secondary ones), a supporting quote, and the source, so primary counts add up. Have one person code, or double-code a sample, so "primary" means the same thing throughout. 5. **Report counts with sample sizes.** "6 of 9 losses to Acme cite onboarding time" beats "onboarding is a top theme." State n every time. Small slices are directional, and under ~5 deals it's a signal to watch, not a finding. 6. **Turn findings into assets.** A deal with only a one-word CRM reason is low-confidence: confirm it with transcripts or interviews before it changes a battle card. Then update battle cards, the objection library, and discovery questions, and send product gaps to the product team. **For coding schemes, interview questions, and report format**: See [references/win-loss-analysis.md](references/win-loss-analysis.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 1. **Opening** (2 min) — Context setting, agenda, confirm goals for the call 2. **Discovery recap** (3 min) — Summarize what you learned, confirm priorities 3. **Solution walkthrough** (15-20 min) — 3-4 key workflows mapped to their pain 4. **Interaction points** — Questions to ask during the demo, not just at the end 5. **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](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 1. **Customer profile** — Industry, company size, buyer role 2. **Challenge** — What they were struggling with (2-3 sentences) 3. **Solution** — What they implemented (1-2 sentences) 4. **Results** — 3 specific metrics (before/after) 5. **Pull quote** — One sentence from the customer 6. **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 1. **Executive summary** — Their challenge, your solution, expected outcome (1 page max) 2. **Proposed solution** — What you'll deliver, mapped to their requirements 3. **Implementation plan** — Timeline, milestones, responsibilities 4. **Investment** — Pricing, payment terms, what's included 5. **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 | | Live objection | Likely concern, one response the rep can say as written, proof, follow-up question | | Win-loss report | Scope, findings with counts and quotes, by-competitor breakdown, asset updates | | 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 | --- ## Task-Specific Questions If context is missing, ask: 1. What collateral do you need? (deck, one-pager, objection doc, etc.) 2. Who will use it? (AE, SDR, champion, prospect) 3. What sales stage is it for? (prospecting, discovery, demo, negotiation, close) 4. Who is the target persona? (title, seniority, department) 5. What are the top 3 objections you hear most? --- ## Tool Integrations For partner sales enablement, see the [tools registry](https://github.com/coreyhaines31/marketingskills/blob/main/tools/REGISTRY.md): | Tool | What It Does | Guide | |------|-------------|-------| | **Introw** | Partner engagement tracking, deal registration, mutual action plans | [introw.md](https://github.com/coreyhaines31/marketingskills/blob/main/tools/integrations/introw.md) | --- ## Related Skills - **competitors**: For public-facing comparison and alternative pages - **competitor-profiling**: For the competitor dossiers that feed battle cards - **customer-research**: For running buyer interviews and broader voice-of-customer research - **copywriting**: For marketing website copy - **cold-email**: For outbound prospecting emails - **revops**: For lead lifecycle, scoring, routing, and pipeline management - **pricing**: For pricing decisions and packaging - **product-marketing**: For foundational positioning and messaging
Original skill: coreyhaines31/marketingskills/skills/sales-enablement/SKILL.md Source: https://github.com/coreyhaines31/marketingskills/blob/dda3841f0b294e01e93b1541486beefbfab0915e/skills/sales-enablement/SKILL.md License: MIT MIT License Copyright (c) 2025 Corey Haines Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.