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.
Why does this insight matter?
- 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
Insight Subtypes and Usage
- Subtype:
buyingCommitteeContactNames
This subtype returns enriched profiles for contacts that likely contribute to or influence the purchasing decision.
API Controls
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.
Autobound uses proprietary logic to identify the most relevant adjacent decision-makers based on title, reporting structure, and company affiliation.
Generate Content API
To require buying committee context in your content:
{
"enabledInsights": ["buyingCommitteeContactNames"]
}
To suppress this insight:
{
"disabledInsights": ["buyingCommitteeContactNames"]
}
What the Output Includes
Each returned contact contains:
email
linkedinUrl
subTitle
(e.g., "VP of Sales at Qlik")summary
(if available)location
(city, state, country)workHistory
(current and past roles)skills
,awards
,certifications
,education
profileId
,linkedinUrn
, and other metadata
All contacts returned are:
- Currently employed at the same company as the original prospect
- Likely to be involved in evaluation or decision-making
Example Output Snippet
[
{
"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 Usage in Outreach
"Also noticed Michael (CIO) and Keith (VP Sales Ops) are likely involved—let me know if looping them in makes sense..."
Base URL
https://api.autobound.ai/api/external/generate-insights/[CURRENT ENDPOINT VERSION]
Authentication
All requests must include:
X-API-KEY: YOUR-API-KEY-HERE
Updated about 9 hours ago