Sales Enablement

Sales Enablement

Step 0 (always first): Load brand context

Before producing any deliverable, look for a brand-context.md file in the user's project root (also check ./.claude/brand-context.md and ./docs/brand-context.md). It holds the company's ICP, positioning, messaging pillars, citable proof, voice, banned words, and compliance constraints.

• If it exists: read it in full and treat it as binding for this run. Hand its contents to every specialist agent you route work to, alongside the task brief. Its "Rules for agents reading this file" section overrides an agent's own defaults.
• If it does not exist: say so, point the user at the template (templates/brand-context.md), and offer to generate a filled draft by interviewing them or by reading their website and existing content. Then proceed with explicitly-labelled assumptions — never silently invented ones.

Non-negotiable regardless of which path applies: do not invent customer names, metrics, funding, integrations, certifications, or outcomes. Only proof recorded in brand-context.md (or supplied directly in the request) may be used as fact. Where a claim would help but no evidence exists, emit a [NEEDS INPUT: …] marker in the deliverable rather than a plausible-sounding guess.

What This Is

Sales Enablement brings together sales strategists, discovery coaches, outbound specialists, pipeline analysts, proposal architects, solutions engineers, and enablement content creators to accelerate deal velocity and maximize win rates. This skill orchestrates your revenue team to execute high-impact outbound campaigns, run disciplined discovery conversations, build data-driven deal strategies, and create compelling proposals that win competitive deals. Whether you're prospecting net-new accounts, accelerating stalled deals, gating a demo, running a proof of concept, answering a vendor security review, building sales battle cards, or executing sales sequences, Sales Enablement routes your request to the right specialist and ensures consistent pipeline progression.

The Team: 7 Specialist Agents

How to Use

Routing User Requests

Prospecting & Outbound → Outbound Strategist

• "Build an outbound campaign targeting CFOs in enterprise SaaS companies"
• "Create a 5-touch email sequence for cold outreach"
• "Develop account selection criteria and scoring for prospecting prioritization"
• "Design a multi-channel prospecting plan (email, LinkedIn, phone) with messaging"

Discovery Conversations → Discovery Coach

• "Coach me on running a discovery call using MEDDPICC framework"
• "Build a discovery call guide with situational questions for IT directors"
• "Create a qualification checklist to identify qualified opportunities early"
• "Develop objection-handling scripts for common prospect pushback"

Deal Acceleration → Deal Strategist

• "Build a deal strategy map for our largest opportunity (all stakeholders, blockers, win conditions)"
• "Create a win-loss scenario analysis for a competitive deal we're behind in"
• "Develop a stakeholder alignment strategy for a multi-buyer procurement"
• "Build an executive sponsor engagement plan to unblock a stalled deal"
• "Write a mutual action plan for this deal, planned backward from the customer's go-live date"
• "Grade our close plan — is it Shared, Co-owned and Current, or just sitting in the CRM?"
• "This deal has a champion and keeps slipping — diagnose whether it is status quo or indecision"

Pipeline Management → Pipeline Analyst

• "Run a pipeline health analysis and identify deals at risk of slipping"
• "Build a weighted revenue forecast with best-case, likely, and downside scenarios"
• "Create a deal prioritization framework (opportunity size, closing probability, buyer fit)"
• "Identify stalled deals and recommend acceleration tactics"

Sales Proposals → Proposal Architect

• "Design a proposal template that maps our solution to customer requirements"
• "Create an ROI calculation model that quantifies customer value and ROI"
• "Build a competitive positioning statement to differentiate against key competitors in proposals"
• "Design a proposal structure (problem → solution → ROI → implementation → next steps)"

Technical Evaluation, Demos & Proofs of Concept → Solutions Engineer

• "Plan a demo for a VP Engineering and a security lead — what do we show and in what order?"
• "Scope a proof of concept with success criteria the buyer's evaluator will sign"
• "Answer this vendor security questionnaire from what we can actually evidence"
• "The buyer says we can't meet their data-residency requirement — how do we answer honestly?"
• "Why do we keep winning the POC and losing the deal?"

Sales Enablement Content → Sales Enablement Content Creator

• "Build battle cards for our top 3 competitive threats (strengths/weaknesses, win strategies)"
• "Create case studies and customer proof stories for sales use"
• "Write objection handler scripts for common prospect concerns"
• "Develop pitch scripts for elevator pitch, 5-minute pitch, and 30-minute pitch"

Execution Model

Phase 1: Pipeline Intelligence (1-2 weeks)

• Outbound Strategist conducts ICP analysis: define ideal customer profile (company size, industry, use case, budget range, buying process)
• Analyze competitor alternatives and win/loss patterns
• Research account selection criteria and build target account list
• Develop persona profiles for each buyer role involved in decision
• Create initial messaging framework addressing buyer's top 3 priorities

Phase 2: Campaign Development & Enablement (2-4 weeks)

• Outbound Strategist designs multi-touch sequence (email, LinkedIn, phone, event) with personalization hooks
• Sales Enablement Content Creator develops supporting collateral (one-pagers, customer proof, competitive briefing)
• Discovery Coach creates discovery call guide with MEDDPICC framework and situational questions
• Deal Strategist outlines deal progression stages and success criteria for each stage
• Pipeline Analyst establishes pipeline baseline and forecasting model

Phase 3: Execution & Coaching (ongoing)

• Outbound campaign execution with weekly performance reviews (response rate, meeting bookings, conversion to qualified opportunity)
• Sales team runs discovery calls using provided framework and scripts
• Deal Strategist reviews large opportunities and coaches on stakeholder mapping, objection handling, and win strategy
• Proposal Architect works with reps to customize proposals that specifically address customer's stated requirements
• Pipeline Analyst reviews pipeline weekly with forecast accuracy and deal progression

Phase 4: Optimization & Learnings (continuous)

• Weekly review of what's working: which outbound messages drive meetings, which discovery questions surface budget, which proposal formats lead to signatures
• Monthly deal review: which deals are progressing as expected, which are stalled, which need executive intervention
• Quarterly sales enablement refresh: update messaging based on competitive landscape, new objections encountered, new customer success stories
• Annual pipeline review: evaluate win rates by deal size, sales stage progression metrics, sales cycle length trends

Sales Methodology & Frameworks

Outbound Prospecting Model

• Account selection (based on ICP: company size, industry vertical, use case fit, buying signal indicators)
• Multi-touch sequence: 3-5 touches over 2-4 weeks, multi-channel (email + LinkedIn + phone)
• Personalization: personalize at account level (company event, hiring trend, earnings announcement) not generic list
• Messaging: lead with problem (customer pain), not solution (your feature)
• Call-to-action: low-friction first ask (quick call, send an article, attend webinar, not demo request)
• Timing: mix of touch types, not all email day 1-5, day 7, day 14; vary channels

Discovery Conversation Framework (MEDDPICC)

• Metrics: What success metrics matter to the buyer (time savings, revenue, cost reduction)?
• Economic buyer: Who controls budget and makes yes/no decision? (Not just champion who bought from you.)
• Decision criteria: What is the buyer evaluating on (price, security, integration, speed, user experience)?
• Decision process: What are the buyer's formal steps to decide (RFP, vendor comparison, trial, executive sign-off)?
• Pain: What problem does the buyer have today that we solve? What's the cost of the pain?
• Implication: What are the downstream implications of the pain (hidden costs, productivity loss, compliance risk)?
• Champion: Who internally is advocating for us and why? Do they have budget influence?
• Commitment: What commitment did the buyer make to next step and timeline? (Not "let me think about it," but specific date.)

Deal Progression Stages

1. Early Funnel: Qualified opportunity, discovery call completed, pain and buyer identified, 20% close probability
2. Mid Funnel: Solution mapped to requirements, ROI quantified, multiple stakeholders engaged, 50% probability
3. Late Funnel: Proposal submitted, competitive position understood, executive sponsor aligned, 80% probability
4. Closed Won: Customer signed, implementation started
5. Closed Lost: Deal stalled >30 days or lost to competitor

Proposal Development Process

• Understand buyer's RFP/requirements (what did they ask for, what are the evaluation criteria)
• Map your solution to their specific requirements (not generic feature list, but specific feature + their use case)
• Quantify ROI and value (timeline to payback, annual value, cost avoidance)
• Address competitive positioning (why you beat alternatives on their stated evaluation criteria)
• Structure for buyer journey (executive summary for CFO, detailed technical specs for IT, change management for operations)
• Include risk mitigation (implementation support, training, success metrics, SLA guarantees)

Competitive Win/Loss Analysis

• Track which competitors we lose to most frequently (by deal size, industry, buyer persona)
• Analyze our win rates: against each competitor, by deal size, by vertical
• Conduct win/loss interviews with customers (why did you choose us, not competitor?)
• Identify where we're strong vs. weak vs. different from competitors
• Update battle cards with competitive positioning and win strategies

Routing by Sales Motion

Enterprise Deal (>$100K ACV)

• Deal Strategist leads multi-stakeholder engagement strategy
• Proposal Architect customizes proposal to address economic buyer's ROI requirements
• Sales Enablement Creator develops case studies from similar-sized deals
• Pipeline Analyst provides weekly deal progression reviews and forecast confidence
• Success metric: 90-day sales cycle, 70%+ win rate against identified competitors

Mid-Market Deal ($25-100K ACV)

• Outbound Strategist drives initial pipeline building and qualification
• Discovery Coach ensures discovery calls capture decision process and budget authority
• Deal Strategist builds win strategy for complex multi-buyer deals
• Proposal Architect creates value-based proposal with ROI scenarios
• Success metric: 60-day sales cycle, 50%+ win rate in competitive deals

SMB Deal (<$25K ACV)

• Outbound Strategist drives high-volume prospecting and self-qualification
• Discovery Coach ensures quick qualification for speed
• Sales Enablement Creator provides pitch scripts and objection handlers
• Proposal Architect uses standardized proposal template with light customization
• Success metric: 30-day sales cycle, 40%+ win rate, high conversion rate from opportunity to close

Expansion Revenue (existing customers)

• Deal Strategist focuses on stakeholder alignment within existing customer organization
• Proposal Architect emphasizes customer success stories and expansion ROI
• Sales Enablement Creator highlights customer success proof and new use-case stories
• Pipeline Analyst tracks expansion pipeline velocity and renewal health
• Success metric: 90%+ renewal rate, 20%+ expansion rate

Output Standards

Sales Content Quality Checklist

Outbound Messaging

• Subject line captures attention without being salesy (e.g., "Quick question on your inventory system" vs. "Let's talk about our platform")
• Opens with specific detail about prospect's company (recent news, hiring pattern, tool usage) showing personalization
• Leads with customer pain or value, not your feature or company
• Call-to-action is low-friction and specific (e.g., "Can we set up 20 minutes Friday?" vs. "Let's grab a call soon")
• Each touch in sequence provides new reason to engage (new article, new connection point, third-party social proof)
• Tests for word count: <50 words in email opens, <100 words in full email

Discovery Questions

• All questions are open-ended (invite explanation, not yes/no)
• Questions follow logical flow: business context → pain/problem → current approach → gaps/implications → priorities
• Includes both situational questions (understand their world) and diagnostic questions (uncover pain)
• Avoids leading questions that telegraph your solution
• Questions are tailored to buyer role (IT director asks different than procurement director)

Sales Proposals

• Executive summary on page 1: situation (their world) → complication (their pain) → resolution (our approach) → ROI (specific savings/revenue)
• Problem statement uses customer's own words and metrics from discovery
• Solution maps directly to stated requirements (requirement A → our feature B → customer benefit C)
• ROI calculation is specific and conservative: timeline → cost avoidance + revenue/productivity → total value → payback period
• Competitive positioning explains why us vs. alternatives on their stated evaluation criteria (not feature table comparison)
• Implementation timeline and success metrics reduce buyer risk perception
• Call-to-action is specific next step and date (not "let's discuss further")

Battle Cards

• One-page format per competitor
• Company overview (funding, market position, key customers)
• Strengths vs. us (where they beat us, how to position against it)
• Weaknesses vs. us (where we beat them, proof points to highlight)
• Ideal customer profile for competitor (which customer types are their best fit)
• Win strategy by scenario (if locked in stage, if early evaluation, if we're trailing)
• Customer proof (case studies, customer testimonials, third-party validation)

Deal Strategy Document

• Deal overview: opportunity size, stage, key stakeholders, success criteria, close date
• Stakeholder map: role, buying influence, priority, risk/support level, engagement strategy
• Current state: what are they using today, pain with current approach, budget for solving
• Win criteria: what does the buyer need to see/believe to choose us
• Competitive landscape: who else are they evaluating, how are we differentiated
• Objection handling: likely concerns and planned responses
• Risk/mitigation: what could derail the deal and how we'll prevent it
• Next steps: specific actions by date with clear owners

Pipeline Forecast

• Stage-by-stage summary (early/mid/late funnel) with deal count, average deal size, total pipeline value
• Probability-weighted forecast (early funnel 20%, mid funnel 50%, late funnel 80%)
• Best-case scenario (all in-funnel deals close at expected value)
• Likely scenario (hit 70% of target, deals slip 1 stage)
• Downside scenario (hit 50% of target, 50% of deals slip)
• Deal-by-deal color coding (red = at risk, yellow = watch, green = on track)
• Month-by-month cash flow projection

Deliverable Specifications

Outbound Campaign

• Target account list (50-200 companies based on ICP criteria)
• Persona profiles (buyer roles, titles, priorities, buying behavior)
• Messaging framework (pain statements, value propositions, company research hooks)
• 5-touch sequence (email 1, LinkedIn connection, email 2, phone call, email 3)
• Personalization playbook (how to customize at account level without breaking scale)
• Supporting collateral (one-pager, case study, webinar link, article)
• Tracking dashboard (response rate by email, meeting booking rate, conversion to qualified opportunity)

Discovery Guide

• Discovery framework document (MEDDPICC overview, how to apply)
• Role-specific discovery guides (CFO questions different from IT director)
• Situational question bank (30-50 questions covering business context, pain, current approach, priorities)
• Diagnostic question bank (25-35 questions to uncover deeper implications and blockers)
• Objection handler scripts (top 10 objections and response frameworks)
• Discovery notes template (standardized format for documenting opportunity info)
• Post-call summary template (what was learned, next steps, risk assessment)

Deal Strategy

• Deal overview document (opportunity summary, stakeholder map, success criteria, risk assessment)
• Win-loss scenario analysis (if we're ahead: how to maintain lead; if tied: how to differentiate; if behind: how to recover)
• Stakeholder engagement plan (who to engage, when, with what message/proof)
• Objection handling document (likely concerns by stakeholder role and planned responses)
• Competitive positioning (how we beat each competing alternative on their evaluation criteria)
• Next steps and owners (specific actions, by date, with accountability)

Proposal Template

• Cover page (company logo, proposal title, customer name, date)
• Executive summary (situation → complication → resolution, 1-page, decision-maker focused)
• Needs analysis (customer's current state, pain with current approach, success criteria)
• Solution overview (how our approach addresses stated needs, high-level timeline)
• Detailed solution specification (by requirement: requirement → our approach → customer benefit)
• ROI/Financial impact (cost avoidance, revenue opportunity, payback period, conservative assumptions)
• Implementation & success metrics (timeline, milestones, training, support, success metrics)
• Pricing & terms
• Next steps (signature process, implementation kickoff timeline)

Sales Battle Cards

• One-page per competitor (covers competitive positioning, strengths/weaknesses, win strategy)
• Competitive matrix (side-by-side feature/capability comparison)
• Win strategy guide (if we're ahead vs. tied vs. behind)
• Customer proof library (case studies from customers who chose us over competitor)
• Objection handlers (common objections raised by competitor and responses)

Sales Enablement Library

• Case study library (3-5 detailed case studies by customer segment/use case)
• Pitch scripts (elevator pitch, 5-minute pitch, 30-minute pitch)
• One-pagers and cheat sheets (product features, competitive positioning, ROI calculator)
• Objection handler scripts (top 15-20 objections and response frameworks)
• Discovery call guide and success templates
• Proposal template and customization guidance
• Customer success stories for sales use (short proof point documents)

Quality Review Process

Before enabling sales team with any content:

1. Accuracy Check: All claims substantiated, no overstated capabilities, competitive comparisons factual
2. Buyer Lens: Does this resonate with the buyer's stated priorities? Or does it push what we want to talk about?
3. Sales Usability: Is this too wordy/corporate? Can a rep actually use this in a conversation?
4. Messaging Consistency: Does this align with positioning and messaging from marketing?
5. Compliance Review: Are all claims substantiated? Are required disclaimers included?
6. Proof Check: Do we have customer proof to back up the claims we're making?

Success Metrics by Sales Motion

Outbound Campaign

• Email open rate: 20-30% (benchmark varies by list quality and industry)
• Response rate: 5-10% of opened emails result in reply or meeting
• Meeting booking rate: 3-5% of prospects contacted result in meeting
• Qualified opportunity rate: 40-50% of meetings convert to qualified opportunity
• Pipeline generated: $X in new pipeline per dollar of outbound investment

Discovery Execution

• Discovery completion rate: 90%+ of qualified opportunities have documented discovery call within 7 days of first contact
• Documented metrics: 80%+ of discovery calls document buyer's key metrics (cost, revenue impact, timeline)
• Budget identified: 70%+ of mid-funnel deals have documented budget range
• Decision process mapped: 80%+ of mid-funnel deals have documented decision process and timeline
• Objection handling: Sales team confidently handles objections without escalation

Deal Acceleration

• Average deal velocity: early funnel → closed won in 60-90 days (depends on deal size)
• Stage progression: 70%+ of deals move to next stage within expected timeframe
• Stalled deal recovery: 40-50% of >30 day stalled deals re-accelerate with strategy intervention
• Win rate: 50-70% close rate on opportunities in late funnel (depends on competitive intensity)

Pipeline Health

• Forecast accuracy: 80%+ accuracy on 30-day pipeline forecast
• Stage-by-stage conversion: early→mid 40%, mid→late 50%, late→close 80%
• Average deal size growth: grow deal size by 15-20% year-over-year
• Sales cycle compression: reduce average sales cycle by 10-15% per year

Proposal Effectiveness

• First-look approval rate: 70%+ of proposals approved by customer on first submission
• Revision cycles: average 1.5 revision cycles per deal (not 3+)
• Proposal response time to signature: 10-15 business days (not 30+)
• Competitive win rate: 60%+ of competitive deals go our way

Tools & Systems

Sales Pipeline Tools

• CRM system (Salesforce, HubSpot, Pipedrive) with standardized opportunity data
• Deal management board (Kanban view showing opportunities by stage)
• Forecast dashboard (pipeline by month, win probability, cash flow projection)
• Activity tracking (calls logged, emails sent, meeting notes documented)

Sales Enablement Platform

• Proposal/contract management (PandaDoc, Proposify, Coda)
• Battle card and content repository (wiki, shared drive, Sharepoint)
• Sales collateral library (case studies, one-pagers, pitch decks, objection handlers)
• Sales training platform (modules on discovery, MEDDPICC, objection handling, competitive positioning)

Communication Tools

• Email tracking (Outreach, SalesLoft, Groove for sequence automation and metrics)
• Meeting scheduling (Calendly, Chili Piper for inbound sales productivity)
• CRM-integrated communication (email, SMS, LinkedIn from within CRM)

Pipeline Integrity Standards

Qualified Opportunity Definition

• Company fits ICP (company size, industry, use case match)
• Identified pain that our solution solves
• Identified buyer/decision-maker engaged in conversation
• Budget exists or identified (rough estimate, not formal approval needed)
• Timeline identified (month/quarter, not "TBD")
• Competition understood (we know what else they're evaluating)

Stage Advancement Criteria

• Early Funnel: Discovery call completed, pain documented, timeline identified
• Mid Funnel: Solution mapped to requirements, ROI validated, multiple stakeholders engaged
• Late Funnel: Proposal submitted, decision process understood, executive sponsor aligned
• Closing: Negotiating terms, legal approval, final pricing/discount approval
• Closed: Contract signed, implementation start date confirmed