Map buying committee roles, priorities, and objections

Build a structured profile of enterprise buying committee members, their evaluation criteria, and likely roadblocks. Use this before sales cycles or messaging reviews.

Prompt

Prompt
Act as an enterprise B2B market researcher. Before generating the analysis, ask me 3 numbered questions to understand my product: 1. What product or service are you selling? 2. What typical industry or company size are you targeting? 3. What is the approximate contract value or implementation scope? Wait for my response. After I answer, provide an analysis mapping key committee personas (such as Business Champion, Finance, IT/Security, Procurement, and End User). For each persona, outline their primary goal, their top two evaluation criteria, and their most critical objection. Output format: A markdown table with columns Persona, Primary Goal, Top Evaluation Criteria, and Core Objection, followed by a bulleted checklist of 3 high-impact proof points to prepare before kickoff.

Example output

Example for: an enterprise customer support AI platform sold to fintech companies

PersonaPrimary GoalTop Evaluation CriteriaCore Objection
Customer Support VP (Champion)Lower ticket resolution time and reduce agent burnoutAutomation rate, agent workflow integrationThe AI will hallucinate and frustrate high-value customers.
Chief Financial OfficerProtect operating margins and ensure predictable costsCost-per-resolution vs head count, payback windowThe recurring API and platform costs will scale faster than labor savings.
Chief Information Security OfficerPrevent data exposure and maintain regulatory complianceSOC 2 Type II, PII masking, local data residencyCustomer financial data will be exposed or stored in third-party model training sets.
Head of ProcurementEnsure vendor viability and minimize contract lock-inFavorable payment terms, SLA penalty structuresCustom integrations create vendor lock-in with ambiguous annual renewal hikes.
Support Team Lead (End User)Minimize daily disruption and manual ticket triageInterface usability, override simplicityThe software will add extra verification steps to every routine ticket.
Required Proof Points to Prepare Before Kickoff
  • Redacted SOC 2 Type II summary report confirming zero data retention for model training.
  • Unit economics spreadsheet demonstrating payback within 6 months based on historical ticket volumes.
  • Live side-by-side demonstration showing human agent override controls taking fewer than two clicks.
Written by AI from this prompt. Your results will vary.

Paste into ChatGPT, Claude, or Gemini. The model will pause and ask 3 brief scoping questions before generating the table. Follow up by asking for specific collateral recommendations for the toughest persona.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Research