The problem this solves
Most stalled deals are single-threaded. One champion carries the case internally, the economic buyer has never heard the pitch, the technical evaluator gets pulled in late with objections nobody prepared for, and procurement appears in the last week with a process of its own. Mapping the committee early is the fix everyone agrees on and almost nobody does, because it means researching four people at one company for every account in the pipeline.
The map is only useful if it is reachable. Names and titles on an org chart are a start; verified emails and direct numbers turn the chart into a plan. And the map belongs in the CRM, on the company record, where the account owner and the manager reviewing the deal can both see who is covered and who is missing.
How the mission runs
- Read the account and the purchase. The Prospecting Agent profiles <company.com> with firmographics - size, structure, locations, functions - and reads the <product category> in your prompt to decide which functions will own each role in the committee. A data product, for example, puts the economic buyer in the revenue or marketing leadership and the technical evaluator in operations or IT.
- Identify one person per role. People search finds the most senior fitting person for each of the four roles, with title, tenure and reporting line where available. Where the company is small enough that one person holds two roles, the sheet says so rather than inventing a fourth name.
- Verify emails and find direct numbers. The email finder and verification produce a deliverable address for each person, and the phone finder adds direct or mobile numbers where findable. Verification status and number type are recorded per contact so a rep knows which channel to lead with.
- Deliver the sheet and the HubSpot contacts. An account sheet in Google Docs lays out the four roles with each person's title, contact details, likely concerns and a suggested first message per role. The four people are added to HubSpot under the company as a reviewed batch, with the committee role stored on each contact.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
A Google Doc account sheet for <company.com> with the buying committee mapped by role - economic buyer, technical evaluator, champion and procurement - each with name, title, verified email, direct number where found, and a note on what that role will care about, plus the same four people created in HubSpot under the company with their committee role set. Gaps are stated explicitly where a role could not be identified.
Make it yours
- Map committees for every account on list <name> in one mission and get one sheet per account in a Drive folder.
- Add a fifth role - the executive sponsor or the end-user lead - when your sales process needs it.
- Skip the CRM write and deliver only the sheet when the account is still being qualified.
Frequently asked questions
How does the agent decide who the economic buyer is?
From the product category and the company's structure: it looks for the most senior leader of the function whose budget the purchase would come from, and it notes the reasoning on the sheet so you can override it.
What if procurement is not a visible function at the company?
At smaller companies the sheet names the finance leader or the COO as the likely procurement owner and marks the role as inferred.
Will this create duplicates in HubSpot?
Existing contacts are matched by email and updated with the committee role; only genuinely new people are created, and you see the batch before it is written.