A job posting is a company describing, in public, in its own words, a problem it just funded. It names the initiative ("build our RevOps function"), the stack ("HubSpot administration required"), the timing (posted Tuesday) and often the pain verbatim ("bring order to our reporting"). No other signal hands outbound this much context for free - and yet most teams scroll past postings daily while paying for colder data. This playbook works the signal end to end, in a week, with the pillar's scoring discipline and the Pipeline agent's actual method.
Why postings are the underrated signal
Run the comparison against the signal-quality axes from the pillar. Strength: a company hiring a role that owns your problem has budgeted for the problem - hiring is the most expensive commitment a company makes to an initiative. Freshness: postings are dated, and open ones are current by definition. Specificity: the requirements section is a needs analysis the company wrote about itself - the tools they run, the gaps they feel, the scale they operate at. Where intent data infers interest through three layers of resolution, a posting is the company speaking on the record.
Step one: define the tell
The tell is the posting pattern that predicts need for what you sell, and getting it sharp is most of the playbook's skill. Three layers compose it: roles (which titles own or feel your problem - buyers of RevOps tooling watch for RevOps and MOps roles; agencies watch for first marketing hires), requirements text (phrases in the description that name your category, your competitors, or the pain you solve - "consolidate our reporting", "administer HubSpot", "own outbound"), and context filters (company size, geography, industry - your ICP applied to the employer, not the role). Write the tell down precisely; a vague tell produces the generic list this playbook exists to avoid.
Step two: sweep and score
Sweep the posting sources for the tell across your target window - the last 14 days is the sweet spot; older postings may be filled, and staleness defeats the point. Then score, mechanically:
| Factor | High | Low |
|---|---|---|
| Specificity | Names your category, stack or pain verbatim | Generic role boilerplate |
| Freshness | Posted this week | Older than the window, possibly filled |
| Seniority | Director+ role - a funded function, not a backfill | Junior backfill |
Then apply the pillar's convergence rule: check the scored accounts against your other signal families - a posting plus rising intent plus a recent raise is the strongest account outbound ever sees, and it jumps the queue. As a mission this whole step is one run: sweep, score, converge, dedupe against accounts already worked - the arithmetic exact, per the sandbox rule.
Step three: from posting to person
The posting names a role; outbound needs its humans - and the listing's recruiter is usually the wrong one. Two people matter: the hiring manager the role reports to (they own the initiative and feel the gap today - the posting's reporting line or the org's structure reveals them) and the funding executive one level up, who approved the headcount and cares about the outcome. Identify both, then verify every address before it touches a sequence - the non-negotiable stage from the email verification guide. An unverified list built from postings is still an unverified list.
Step four: the evidence-first opener
The opener writes itself from the evidence, and the craft is restraint: reference the posting (public, professional, fair game), connect it to the problem the hire will face, and offer something useful to that problem - per the full rules in personalization with evidence. The shape that works: "You are hiring a [role] - teams making that hire usually hit [specific problem]. [One useful sentence about it.]" What never works: implying surveillance ("I have been watching your job board"), or pitching the hire itself rather than the initiative behind it. The touch lands best while the posting is open - the hire's future problems are this quarter's argument for your category.
Step five: make it a standing machine
One sweep is a list; a weekly sweep with memory is a machine. The standing version: every week, sweep the tell, score, converge, drop accounts already contacted (the dedupe that keeps the machine polite), verify the new humans, draft the openers with the evidence attached, and park the batch for approval. Track it on the program's four numbers - meetings from posting-sourced accounts is the outcome metric. The Pipeline shelf carries this as a runnable mission; scheduled, it is the closest outbound gets to compounding interest.
The funnel math
The working checklist
Frequently asked questions
Why are job postings a good outbound signal?
A posting is a company publicly describing a problem it just funded - naming the initiative, stack and pain in its own words, with a date. It is the rare signal that is simultaneously strong, fresh, specific and free.
Who should outreach target from a posting?
The hiring manager who owns the initiative and the executive who funded the headcount - almost never the recruiter on the listing. The posting’s reporting line usually reveals both.
How fresh must a posting be to act on?
Work a 14-day window: the initiative is newly funded and the pain current. Older postings risk being filled, and the evidence-first opener loses its “this week” force.
Is referencing a job posting in cold email acceptable?
Yes - postings are public, professional information a company chose to publish. Reference the posting and the initiative it implies; never imply surveillance of individuals or use anything non-public.
What results should the funnel produce?
Run your own numbers in the calculator above - the leverage points are the tell’s precision (qualification rate) and the opener’s quality (reply rate). Measure the program on meetings from posting-sourced accounts.
Sources
- Google - Email sender guidelines (the sending rules step four operates under)
- Gartner - B2B buying journey research (why the funding executive matters)
Every playbook on this blog ships as a runnable mission.
Open a workspace and the playbook library is waiting - describe the outcome and the agents carry it end to end, on your plan's monthly credits.