The Buying Committee From a Job Post
Outcome: ten hiring companies turned into named, verified contacts in the function you sell to, for roughly 34 credits.
- Surface
- MCP server
- Level
- Beginner
- Uses
- search_linkedin_job_openings · enrich_linkedin_page · find_people_within_company · find_work_email
- Credits
- ~34 per 10 companies
- Prerequisite
- Lesson 03
Why job posts are the best cold signal
A job post is a budget commitment with a date on it. It tells you the company has money for that function, that the function is growing, and often which tools they run — none of which a firmographic filter can give you.
It is also cheap to search and fast to detect, which is why it is the workhorse signal across this whole library.
The chain
search_linkedin_job_openings
Roles matching your function, in your geographies, recent.
enrich_linkedin_page
The hiring company. Cheap, and it is what qualifies the account.
Free filter
Size, geography, and not a recruiting agency. Do this before the next step.
find_people_within_company
The functional leader — from the reporting line in the post where it names one.
find_work_email + verify_email
On the selected contacts only.
The prompt
Using the SyncGTM MCP server, find companies hiring RevOps roles in the UK
and Ireland, posted in the last 30 days.
Steps:
1. search_linkedin_job_openings. Cap at 40 postings.
2. Deduplicate to unique companies.
3. enrich_linkedin_page for each company.
4. Show me the companies with headcount, industry and the roles they posted.
Stop there — do not find any people yet.Then, after you have cut the list:
For these 10 companies: [...]
1. find_people_within_company — RevOps or Sales Ops, director level and above.
Exclude anyone with a recruiting or talent title.
Cap at 2 people per company.
2. find_work_email, then verify_email.
Return: company, person, title, email, status, and the role they posted.The two-stage stop is the same discipline as the previous lesson. Company enrichment is cheap and people are not, so you look at the accounts and cut them before spending anything at the person level.
Cut before you spend
| Cut | Why |
|---|---|
| Recruiting and staffing agencies | They post constantly and will dominate an unfiltered list |
| Companies outside your size band | The role exists but the account does not qualify |
| Companies already customers or in an open deal | Route to the owner instead |
| Postings older than 30 days | The role may be filled |
| Reposts of the same role | One vacancy, not three |
Forty postings typically becomes ten to fifteen real accounts. Everything after that runs on the survivors.
Read the reporting line
The post often names your target directly: “reports to the VP of Revenue Operations”, “works closely with the Head of Sales”. That named role is who to contact.
Where it names nobody, target the functional leader one level above the role being hired.
Never the recruiter. They cannot buy, and they will not forward it.
Cost
| Step | Rows | Cost | Total |
|---|---|---|---|
| Search openings | 40 | — | ~2 |
| Enrich companies | 15 | ~0.5 | 8 |
| Free filter | 15 → 10 | 0 | 0 |
| Find people, 2 each | 20 | ~0.3 | 6 |
| Email + verify | 20 | ~1.3 | 18 |
| ~34 |
Ten qualified accounts with twenty verified contacts and a specific, dated reason to write to each.
Do this now
Define your role search
Function, seniority, geographies, 30-day window.
Run the search and stop
Read the companies.
Cut agencies, wrong-size and existing accounts
Read the postings for reporting lines
And for named tools — free stack data.
Find people at the named or inferred role
Excluding recruiters, capped at 2.
Enrich and verify
Write from the post
The consequence, not the fact — see Hiring Signals lesson 06.
Check your work
- You reviewed the company list before enriching people
- Recruiting agencies are excluded
- Contacts come from the reporting line where the post named one
- No recruiter is in the contact list
- Cost matched the estimate
Where this breaks
Job posts stay live after the role is filled in many systems, so a message referencing “the RevOps role you’re hiring for” can arrive after the person started. Use the posted date, hold to a 30-day window, and re-check the posting is live before a batch goes out — it is the one error that makes the whole approach look automated.
Further automation
Run it weekly with a seen/unseen filter so you only process postings you have not seen before. That turns an occasional exercise into a standing lead source at a fraction of the cost — Hiring Signals lesson 08 builds it.
Next lesson
07 — Prompting that does not waste credits, the discipline behind every chain in this course.
Reference for this lesson: search_linkedin_job_openings, enrich_linkedin_page, find_people_within_company, Hiring Signals.