Buying Committee
This insight identifies up to 10 likely decision-makers or influencers at the same company as your prospect. These individuals are inferred to be part of the buying committee based on title, department, and seniority.
This insight identifies up to 10 likely decision-makers or influencers at the same company as your prospect, inferred to be part of the buying committee based on title, department, and seniority.
Why This Insight Matters
- Helps you multi-thread outreach by surfacing other relevant contacts
- Increases the chance of landing a response by engaging more stakeholders
- Gives you ammunition to name-drop contextually (if appropriate)
- Reveals organizational structure and possible decision dynamics
- Can inform tone, messaging depth, and content strategy
Available Subtypes
| Signal | Subtype Enum | Description |
|---|---|---|
| Buying committee | buyingCommitteeContactNames | Enriched profiles for contacts likely to influence purchasing |
Response Fields
Contact Object
| Field | Type | Example | Description |
|---|---|---|---|
email | string | "[email protected]" | Contact email |
linkedinUrl | string | "linkedin.com/in/michael-gibeault..." | LinkedIn profile URL |
Contact Data
| Field | Type | Example | Description |
|---|---|---|---|
data.firstName | string | "Michael" | First name |
data.lastName | string | "Gibeault" | Last name |
data.subTitle | string | "Chief Information Officer at Qlik" | Title and company |
data.summary | string | "Experienced IT Leader..." | Profile summary |
data.profileId | string | "michael-gibeault-9773357" | LinkedIn profile ID |
Location
| Field | Type | Example | Description |
|---|---|---|---|
data.location.city | string | "Boston" | City |
data.location.state | string | "Massachusetts" | State |
data.location.country | string | "United States" | Country |
Additional Fields
| Field | Type | Example | Description |
|---|---|---|---|
data.skills | array | ["ERP", "SAP", "Project Management"] | Listed skills |
data.workHistory | array | — | Current and past roles |
data.awards | array | — | Awards received |
data.certifications | array | — | Professional certifications |
data.education | array | — | Education history |
Full JSON Response Example
[
{
"email": "[email protected]",
"linkedinUrl": "linkedin.com/in/michael-gibeault-9773357",
"data": {
"firstName": "Michael",
"lastName": "Gibeault",
"subTitle": "Chief Information Officer at Qlik",
"summary": "Experienced IT Leader...",
"location": {
"city": "Boston",
"state": "Massachusetts",
"country": "United States"
},
"skills": ["ERP", "SAP", "Project Management"],
"workHistory": [],
"profileId": "michael-gibeault-9773357"
}
}
]Example Output
"Also noticed Michael (CIO) and Keith (VP Sales Ops) are likely involved—let me know if looping them in makes sense..."
API Usage
Generate Insights API
To retrieve the buying committee, provide either a prospect's email or LinkedIn URL. The system will resolve the associated company and return up to 10 qualified stakeholders.
{
"insightSubtype": "buyingCommitteeContactNames",
"contactEmail": "[email protected]"
}Only one of contactEmail or contactLinkedinUrl is required. If both are provided, resolution accuracy improves.
Generate Content API
{
"enabledInsights": ["buyingCommitteeContactNames"],
"disabledInsights": []
}Coverage
- Refresh: Daily
- Coverage: 50-75% of companies
- Best for: Multi-threading, account-based selling, stakeholder mapping
Updated 8 days ago
