From Hiring Company to Buying Committee
Outcome: one to three named, verified contacts per surviving account, chosen from the reporting line in the post rather than guessed.
- Surface
- App and MCP server
- Level
- Intermediate
- Uses
- find_people_within_company · find_work_email · verify_email
- Credits
- ~4 per surviving company
- Prerequisite
- Lessons 03 and 04's gates applied
The gate has already run
Everything before this lesson was cheap and ran on everything. This lesson is the expensive part, and it runs only on accounts that survived lessons 03 and 04.
If you arrived here without applying those gates, go back. The cost difference is roughly four to one.
The post usually names your target
A job post is written by or for the hiring manager, and it frequently says who that is.
Look for the reporting line
“Reports to the VP of Engineering”, “works closely with the Head of RevOps”, “joins the Data team under…”. That named role is your first target.
Look for the team description
“Join our team of six” tells you the team size; “you’ll be our first data engineer” tells you far more.
Look for named tools
The stack this person will work with — including internal tools that detection cannot see.
Look for the problem statement
“Help us scale onboarding as we grow from 20 to 60 reps” is the message you were going to have to guess at.
Extract these verbatim and keep the quotes. Lesson 06 uses them.
When the post names nobody
Target the functional leader one level above the role being hired.
| Role being hired | Target |
|---|---|
| IC practitioner | The manager or director of that function |
| Manager | The VP or head of function |
| Director or VP | The C-level owner, or the CEO at smaller companies |
| ”First X hire” | Whoever currently owns the problem — often a founder or an adjacent leader |
That last row is the interesting one. A first-of-its-kind hire means nobody owns the function yet, so the buyer is whoever has been absorbing the work — usually one level up and in an adjacent function.
Not the recruiter
The recruiter or talent partner named on a post cannot buy your product, has no budget, and will not forward your message — you are one of many vendors who found their name on a public posting. Exclude recruiting and talent titles explicitly from your people search, or they will appear at the top of every result because they are the most visible person attached to the role.
How many contacts
| Company size | Contacts | Who |
|---|---|---|
| Under 50 | 1 | Founder or the functional lead |
| 50–200 | 2 | Hiring manager and their leader |
| 200–1,000 | 2–3 | Hiring manager, their leader, sometimes the practitioner lead |
| 1,000+ | 3 | And confirm the right business unit — large companies hire the same role in several places |
Enrich and verify
Standard path on the selected contacts only: find work email, verify, keep valid. See Waterfall Enrichment for the mechanics and lesson 06 of Automated Outbound for the pre-send discipline.
Record contact_source and the posting URL that triggered the account. Both are needed later — the first to compare outcomes, the second because your message will reference the post.
Do this now
Confirm the gates ran
Count the surviving accounts before spending anything.
Extract from the posts
Reporting line, team size, named tools, problem statement — verbatim, with quotes.
Choose the target per account
From the reporting line where available, one level up otherwise.
Exclude recruiting titles
Explicitly, in the search filter.
Find people at the selected roles
Capped by company size.
Enrich and verify
Valid only.
Compute coverage
Accounts with at least one verified contact ÷ surviving accounts.
Check your work
- Person-level work ran only on gated accounts
- Reporting lines were extracted from posts where present
- Recruiters are excluded by filter, not by review
- Contact count is capped by company size
- Posting URL and contact source are recorded per row
Where this breaks
Large companies post the same role in several business units, and the hiring manager for one has no authority over the others. A message referencing “the platform engineer role you’re hiring for” sent to the wrong division’s leader lands as a mistake. Above about a thousand employees, confirm the business unit from the posting before choosing a contact — or restrict the play to companies small enough that there is only one.
Further automation
The extraction step produces stack data as a by-product, and it covers exactly the internal tools that public-site detection cannot see. Storing named tools per account builds a stack dataset for free alongside the hiring signal — useful for the displacement play in Automated Outbound lesson 12.
Next lesson
06 — Writing the hiring-trigger message, using the post without quoting it back at them.
Reference for this lesson: find_people_within_company, find_work_email, verify_email, Waterfall Enrichment.