Create Sales Collateral for B2B Reps

Sales Enablement produces B2B sales collateral reps actually use - decks, one-pagers, objection docs, demo scripts, ROI calculators, case study briefs, proposals, playbooks, and persona cards - built to help close deals rather than drive top-of-funnel traffic.

Use this when building decks, one-pagers, objection-handling docs, or demo scripts, when a sales team needs collateral tailored to stage, persona, or use case, or when the asset needs to help reps close rather than generate awareness. Before starting, it checks for an existing .agents/product-marketing-context.md (or the older .claude/ path) and only asks about what that file doesn't already cover: value proposition and differentiators, sales motion (self-serve, inside, field, or hybrid, deal size, cycle length, buying personas), the specific collateral needed and its funnel stage or user, and what currently exists and what reps ask for most.

Four core principles run through every asset: sales uses what sales trusts (involve reps in creation, use their language, test drafts with top performers - if reps rewrite the deck before sending it, it's the wrong deck); situation-specific, not generic (tailor to persona, deal stage, and use case); scannable over comprehensive (reps need an answer in 3 seconds, not 30); and tie every claim to a business outcome (replace "AI-powered analytics" with "cut reporting time by 80%"). Collateral-specific structures include: a sales deck's 10-12 slide story arc (problem, cost of inaction, market shift, approach, product walkthrough, proof points, case study, implementation timeline, ROI, pricing, next steps), customized by buyer type; a one-pager's five-part structure (problem, solution, 3 differentiators, one proof point, CTA) kept to one page front-and-back; an objection doc's five-part response framework (the objection as reps actually hear it, the real concern behind it, response approach, proof point, follow-up question) across six categories - price, timing, competition, authority, status quo, technical; an ROI calculator's inputs (current-state metrics), calculations (time, cost, and revenue impact), and outputs (annual ROI, payback period, 3-year value); a demo script's five-part flow (opening, discovery recap, 15-20 minute solution walkthrough, interaction points, close); a sales-format case study's structure (customer profile, challenge, solution, 3 before/after metrics, pull quote, retrieval tags); a proposal's five sections (executive summary, proposed solution, implementation plan, investment, next steps), kept to 5-7 pages; a playbook's contents (buyer profile, qualification criteria, discovery questions, top 10 objections, competitive positioning, demo flow, email templates), reviewed quarterly with an assigned owner so it doesn't go stale; and a buyer persona card's seven fields (role/title, goals, pains, top 3-5 objections, evaluation criteria, buying process, and the one-sentence messaging angle that resonates most), built for five persona types - economic buyer, technical buyer, end user, champion, and blocker.

Each collateral type has its own deeper reference file - deck-frameworks.md, one-pager-templates.md, objection-library.md, demo-scripts.md - and the skill names its neighbors explicitly: competitor-alternatives for public comparison pages, copywriting for marketing website copy, cold-email for outbound prospecting, revops for lead lifecycle and pipeline management, pricing-strategy for packaging decisions, and product-marketing-context for the foundational positioning this skill reads from first.

B2B sales and sales-enablement teams producing rep-facing collateral for a specific stage, persona, and use case - AEs, SDRs, champions, or prospects - who need each asset delivered in its right output format, from a slide-by-slide deck outline with speaker notes to a persona card or a table-format objection doc.