Sales AI Skill

Buying Committee Identification

Map and identify all stakeholders involved in a purchase decision to ensure complete buying committee coverage. Use when mapping stakeholders, identifying decision-makers, building multi-threaded engagement, or tracking buying committee roles. Triggers on p...

Buying Committee Identification

Map the complete decision-making unit to ensure no critical stakeholder is missed.

Workflow

  1. Research target account to identify all likely stakeholders based on industry, company size, and solution type.
  2. Classify each stakeholder by role in the buying process (economic buyer, champion, influencer, user, blocker).
  3. Find specific individuals filling each role using data enrichment and org chart tools.
  4. Track engagement level with each stakeholder across all touchpoints.
  5. Calculate buying committee coverage score and identify gaps.
  6. Develop multi-threading strategy to engage uncovered stakeholders.
  7. Monitor for stakeholder changes (role changes, departures) and update map accordingly.

Buying Committee Role Taxonomy

BUYING COMMITTEE ROLES (MEDDICC Framework)
=============================================

1. ECONOMIC BUYER (Budget Authority)
   Definition: Has final financial authority to approve the purchase
   Typical Titles: CEO, CFO, VP Finance, Business Unit President
   Concerns: ROI, total cost of ownership, budget impact, strategic alignment
   What They Need From You:
     - Clear business case with quantified financial impact
     - Total cost comparison (not just list price)
     - Risk mitigation (implementation risk, change management)
     - Executive-level references from peer companies
   Engagement Strategy:
     - Keep conversations high-level and financial
     - Use data and benchmarks rather than feature details
     - Executive-to-executive introductions preferred
     - Provide board-ready business case templates
   Red Flag: Economic buyer not engaged until late stage = high risk

2. CHAMPION (Internal Advocate)
   Definition: Internally advocates for your solution and helps you navigate
   Typical Titles: Varies by solution (Director, Manager, Team Lead)
   Concerns: Solving their pain, career advancement, team efficiency
   What They Need From You:
     - Talking points for internal advocacy
     - ROI data and business case materials
     - Competitive comparisons to counter objections
     - Executive summary they can share with leadership
   Engagement Strategy:
     - Deep relationship building with personal motivation understanding
     - Weekly check-ins during active deal
     - Provide "armament" for internal meetings
     - Help them succeed internally (they win when you win)
   Red Flag: Champion is friendly but not advocating internally

3. TECHNICAL EVALUATOR (Security/IT Review)
   Definition: Assesses technical fit, security, and integration capability
   Typical Titles: CTO, IT Director, Security Manager, Engineering Lead
   Concerns: Technical compatibility, security compliance, data privacy, scalability
   What They Need From You:
     - Technical documentation and architecture overview
     - Security whitepaper and compliance certifications (SOC 2, ISO 27001)
     - API documentation and integration examples
     - Technical reference calls with peer companies
   Engagement Strategy:
     - Engineer-to-engineer conversations
     - Technical deep-dive sessions and sandbox access
     - Security questionnaire completion
     - Proof of concept / technical validation
   Red Flag: Technical evaluator raises concerns not addressed promptly

4. END USER (Day-to-Day User)
   Definition: Will use the product daily; influences satisfaction and adoption
   Typical Titles: Individual Contributors, Team Members, Analysts
   Concerns: Ease of use, learning curve, impact on daily workflow, support
   What They Need From You:
     - Product demo showing user-friendly interface
     - Training resources and onboarding plan
     - Peer testimonials from similar roles
     - Free trial or sandbox access to try themselves
   Engagement Strategy:
     - Product-focused demos showing real workflows
     - User community access and peer connections
     - Hands-on trial experiences
     - Success stories from users at similar companies
   Red Flag: End users resist adoption = post-sale churn risk

5. INFLUENCER (Advisor/Consultant)
   Definition: External or internal advisor who influences the decision
   Typical Titles: External Consultants, Industry Analysts, Internal Subject Matter Experts
   Concerns: Best practice alignment, vendor reputation, long-term viability
   What They Need From You:
     - Industry analyst reports (Gartner, Forrester)
     - Market position and competitive analysis
     - Customer success metrics and benchmarks
     - Long-term product roadmap
   Engagement Strategy:
     - Thought leadership content and industry insights
     - Analyst relationship leverage (if applicable)
     - Transparent roadmap sharing
     - Third-party validation and testimonials
   Red Flag: Influencer has negative view of your company or category

6. BLOCKER (Veto Power)
   Definition: Has implicit or explicit veto power over the decision
   Typical Titles: Legal, Compliance, Security, Procurement, IT Governance
   Concerns: Risk, compliance, standardization, vendor consolidation
   What They Need From You:
     - Legal/compliance documentation
     - Data processing agreements and privacy policies
     - Vendor risk assessment documentation
     - Standardization rationale (why your product vs. existing tools)
   Engagement Strategy:
     - Proactively address compliance before it becomes an issue
     - Provide all required documentation upfront
     - Connect with their peers who've already approved
     - Patience — blockers move slowly but are essential
   Red Flag: Blocker not identified until contract stage = deal delay

Committee Mapping by Company Size

BUYING COMMITTEE COMPOSITION BY COMPANY SIZE
===============================================

STARTUP (10-50 employees):
  Committee Size: 2-4 people
  Roles Present:
    - CEO/Founder: Economic Buyer + Champion (combined)
    - Head of relevant department: End User + Technical Evaluator
    - Optional: External advisor/consultant
  Dynamics: Fast decisions, fewer stakeholders, CEO is often the decider
  Multi-threading: Lower priority — usually 2 threads sufficient
  Decision Timeline: 1-4 weeks
  Risk: Low committee complexity but high dependency on single person

SMB (51-250 employees):
  Committee Size: 4-7 people
  Roles Present:
    - CEO or COO: Economic Buyer
    - VP/Director of relevant function: Champion
    - IT Manager or CTO: Technical Evaluator
    - 2-3 End Users from affected teams
    - Optional: Legal/Compliance for larger deals
  Dynamics: Moderate process, some formality, champion critical
  Multi-threading: Essential — need Economic Buyer + Champion minimum
  Decision Timeline: 2-8 weeks
  Risk: Medium — if champion and economic buyer misaligned, deal stalls

MID-MARKET (251-2,500 employees):
  Committee Size: 7-12 people
  Roles Present:
    - VP or SVP: Economic Buyer (or CFO for large deals)
    - Director: Champion
    - IT Director/CTO: Technical Evaluator
    - Security/Compliance: Blocker
    - 3-5 End Users from multiple teams
    - Procurement: Blocker (for deals >$50K)
    - Optional: External consultants
  Dynamics: Formal process, RFPs common, multiple evaluation criteria
  Multi-threading: Critical — must cover all 6 role types
  Decision Timeline: 4-16 weeks
  Risk: High — missing any role = deal risk; procurement can kill deals

ENTERPRISE (2,500+ employees):
  Committee Size: 12-20+ people
  Roles Present:
    - C-level executive: Economic Buyer
    - VP/Director: Champion(s) — often multiple
    - IT/Security/Engineering: Technical Evaluators (multiple teams)
    - Legal/Compliance/Procurement: Blockers (multiple)
    - 5-10 End Users across departments/regions
    - External consultants and internal advisory boards
  Dynamics: Highly formal, steering committees, legal review required
  Multi-threading: Absolutely critical — must have executive sponsor + champion + technical coverage
  Decision Timeline: 8-24+ weeks
  Risk: Very high — any single blocker can halt deal for months

Coverage Scoring & Gap Analysis

BUYING COMMITTEE COVERAGE SCORE
==================================

For each role type, track engagement level:
  Fully Engaged (4): Met 2+ times, shared information, showed interest
  Partially Engaged (3): Met 1 time, basic interaction
  Acknowledged (2): Identified but not yet engaged
  Unknown (1): Role identified but no person mapped
  Missing (0): Role not identified in account

Coverage Score = Sum of engagement levels / (6 roles × 4 max) × 100

COVERAGE TIERS:
  80-100%: Full coverage — ready for proposal/negotiation
  60-79%: Good coverage — 1-2 gaps to fill before advancing
  40-59%: Partial coverage — significant gaps; risk if moved forward
  <40%: Insufficient coverage — do NOT advance deal; fill gaps first

GAP ANALYSIS TEMPLATE:
  ╔═══════════════════╦═══════════╦═══════════════════╦════════════════╗
  ║ Role              ║ Engaged   ║ Person Identified ║ Gap Action     ║
  ╠═══════════════════╬═══════════╬═══════════════════╬════════════════╣
  ║ Economic Buyer    ║ [0-4]     ║ [Name / Unknown]  ║ [Action]       ║
  ║ Champion          ║ [0-4]     ║ [Name / Unknown]  ║ [Action]       ║
  ║ Tech Evaluator    ║ [0-4]     ║ [Name / Unknown]  ║ [Action]       ║
  ║ End Users         ║ [0-4]     ║ [Name / Unknown]  ║ [Action]       ║
  ║ Influencer        ║ [0-4]     ║ [Name / Unknown]  ║ [Action]       ║
  ║ Blocker           ║ [0-4]     ║ [Name / Unknown]  ║ [Action]       ║
  ╚═══════════════════╩═══════════╩═══════════════════╩════════════════╝

COMMON GAP ACTIONS:
  - Ask champion: "Who else needs to be involved for this to move forward?"
  - Research org chart to find person in role
  - Request introduction from engaged stakeholder
  - Direct outreach with value-specific message for that role
  - Executive-to-executive introduction for economic buyer gaps

Multi-Threading Strategy

MULTI-THREADING EXECUTION PLAN
================================

Phase 1: MAP (Week 1-2)
  [ ] Research account org chart and identify all stakeholders
  [ ] Classify each by buying committee role
  [ ] Score current engagement level for each
  [ ] Identify critical gaps (Economic Buyer and Blocker = highest priority)
  [ ] Create visual buying committee map in CRM

Phase 2: ENGAGE (Week 3-6)
  [ ] Prioritize outreach by role importance:
      1. Economic Buyer (if not engaged) — most critical gap
      2. Blocker (Legal, Security, Procurement) — prevent late-stage surprises
      3. Technical Evaluator — technical validation
      4. End Users — adoption assurance
  [ ] Craft role-specific messaging for each stakeholder type
  [ ] Leverage champion for introductions where possible
  [ ] Track all engagement on committee map

Phase 3: ALIGN (Week 7-10)
  [ ] Ensure all stakeholders have consistent understanding of solution value
  [ ] Address role-specific objections before they escalate
  [ ] Create mutual action plan with input from all roles
  [ ] Confirm economic buyer has business case and budget approval
  [ ] Verify technical evaluator has completed security/technical review

Phase 4: CLOSE (Week 11+)
  [ ] Champion presents internally with full committee support
  [ ] Economic buyer approves based on business case
  [ ] Blockers sign off on legal/compliance
  [ ] Procurement completes vendor evaluation
  [ ] Contract executed and deal closed

MULTI-THREAD BEST PRACTICES:
  - Never bypass champion — always coordinate through them
  - Each stakeholder gets value-relevant messaging (not generic sales pitch)
  - Track committee engagement in CRM; update after every touchpoint
  - Alert if any engaged stakeholder becomes unresponsive (potential blocker)
  - If deal stalls, diagnose which committee member is the bottleneck

Edge Cases

Integration Points