Buying Committee Mapper
The Buying Committee Mapper agent identifies key stakeholders in purchasing decisions, assigns buying roles, and recommends persona-specific engagement strategies with multi-threading plans.
Overview
Agent ID: buying-committee-mapper
Output: Self-contained HTML document with stakeholder profiles, engagement strategies, and multi-threading sequences.
Execution Time: 20-30 seconds depending on company size
Requires: Any company (works for both public and private)
Sample Output
See it in action: Salesforce Buying Committee
This sample shows 5 identified stakeholders with buying roles, engagement strategies, objection handling, and a complete multi-threading sequence.
Value Proposition
Sales always asks "who do I call?" - this agent answers with not just names, but:
- Where the buying center is (via FAI geographic data)
- Who to engage (contacts with roles assigned)
- How to engage each person (persona-specific strategies)
- When to sequence the outreach (multi-threading plan)
Quick Start
1. Start a Committee Mapping Run
curl -X POST "https://phoenix.hginsights.com/api/agents/v1/agents/buying-committee-mapper/runs" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"input": {
"domain": "salesforce.com"
},
"params": {
"deal_context": "Selling data enrichment platform",
"product_category": "Sales Intelligence"
}
}'
Response:
{
"run_id": "550e8400-e29b-41d4-a716-446655440000",
"status": "queued"
}
2. Poll for Completion
curl "https://phoenix.hginsights.com/api/agents/v1/runs/{run_id}" \
-H "Authorization: Bearer YOUR_API_KEY"
3. Retrieve the HTML Brief
curl "https://phoenix.hginsights.com/api/agents/v1/runs/{run_id}/artifacts" \
-H "Authorization: Bearer YOUR_API_KEY"
Input Parameters
Required: Company Identifier
| Field | Type | Description |
|---|---|---|
domain | string | Company website domain (e.g., "salesforce.com") |
Optional: Context Parameters
| Field | Type | Default | Description |
|---|---|---|---|
deal_context | string | - | What you're selling and deal stage |
known_contacts | array | [] | Contacts you already know |
product_category | string | - | Product category for buyer mapping |
Buying Roles Mapped
| Role | Description | Typical Titles |
|---|---|---|
| Economic Buyer | Controls budget, final approval | CEO, CFO, COO |
| Technical Buyer | Evaluates technical fit, has veto | CIO, CTO, VP IT |
| User Buyer | Will use the product | Managers, end users |
| Champion | Internal advocate | VP Sales, VP RevOps |
| Blocker | Opposes the deal | Procurement, Legal |
| Influencer | Shapes opinions | Directors, Consultants |
HTML Output
The agent produces a self-contained HTML document that sales users can:
- View directly in a browser
- Share via email
- Print for meeting prep
- Save for offline reference
Brief Contents
- Header - Company name, industry, employee count, generation date
- Strategy Summary - High-level multi-threading approach
- Committee Gaps - Missing roles that need to be identified
- Stakeholder Cards - Each contact includes:
- Name, title, department
- LinkedIn URL and email (clickable for immediate outreach)
- Buying role and influence level
- Priorities and pain points
- Engagement strategy with messaging and proof points
- Potential objections with responses
- Next best action
- Multi-Threading Sequence - Step-by-step engagement plan
- Risk Assessment - Champion strength, blocker risk, access gaps
Use Cases
AE Outbound Prospecting
Identify the complete buying committee before outreach, ensuring you engage the right people from the start.
Meeting Preparation
Prepare for multi-stakeholder meetings with persona-specific strategies and objection handling.
BDR Targeting
Know exactly which personas to target and how to message each one.
Deal Strategy
Build consensus across the buying committee with a clear multi-threading plan.
Error Handling
| Scenario | Behavior |
|---|---|
| No contacts found | Returns HTML error page suggesting manual research |
| Very small company | Adjusts expectations, notes smaller committee expected |
| Private company | Proceeds without SEC data, notes limitation |
| Contact enrichment fails | Includes contact with available data |
MCP Tools Used
| Tool | Purpose |
|---|---|
company_firmographic | Company context and size |
company_fai | Identify buying centers by geography |
contact_search | Find contacts by title |
contact_enrich | Get LinkedIn URLs and emails |
sec_filing_section | Executive info (public companies) |
web_search | Contact background research |
Example: Python Integration
import requests
import time
API_KEY = "phx_your_api_key_here"
BASE_URL = "https://phoenix.hginsights.com/api/agents"
headers = {
"Authorization": f"Bearer {API_KEY}",
"Content-Type": "application/json"
}
def get_buying_committee(domain: str, deal_context: str = None) -> str:
"""Map buying committee for a target company."""
# 1. Start the run
payload = {
"input": {"domain": domain},
"params": {}
}
if deal_context:
payload["params"]["deal_context"] = deal_context
response = requests.post(
f"{BASE_URL}/v1/agents/buying-committee-mapper/runs",
headers=headers,
json=payload
)
response.raise_for_status()
run_id = response.json()["run_id"]
print(f"Started run: {run_id}")
# 2. Poll for completion
while True:
status_response = requests.get(
f"{BASE_URL}/v1/runs/{run_id}",
headers=headers
)
status = status_response.json()
print(f"Status: {status['status']}")
if status["status"] == "succeeded":
break
elif status["status"] == "failed":
raise Exception(f"Run failed: {status.get('error')}")
time.sleep(5)
# 3. Get artifacts
artifacts_response = requests.get(
f"{BASE_URL}/v1/runs/{run_id}/artifacts",
headers=headers
)
artifacts = artifacts_response.json()["artifacts"]
html_artifact = next(a for a in artifacts if a["artifact_type"] == "html")
return html_artifact["url"]
# Usage
brief_url = get_buying_committee("salesforce.com", "Selling data platform")
print(f"Brief available at: {brief_url}")
Best Practices
- Provide deal context - Helps the agent tailor strategies to your specific situation
- Include product category - Improves buyer role mapping accuracy
- Review engagement strategies - Customize for your specific solution
- Use LinkedIn URLs immediately - These are the most actionable fields for outreach
Next Steps
- POV Trigger Analyst - Identify buying triggers from financial data
- Account Research Brief - Comprehensive account intelligence
- API Reference - Complete endpoint documentation