The problem this solves
A job posting is a public statement of an unsolved problem. When a company posts a <role>, the manager who wrote the posting has a workload that exceeds the team, a budget approved for at least one salary, and a strong incentive to hear about anything that closes the gap before the hire starts. That manager is the buyer, and the posting is the opener.
Reaching them requires two joins that job boards do not offer: the posting to the company's size and country, and the posting to the person who will manage the hire. Without the second, outreach goes to a generic address or a recruiter. With it, the first email can quote the posting to the exact person who approved it, which is the difference between a cold email and a relevant one.
How the mission runs
- Pull this month's postings for the role. The Prospecting Agent searches hiring data for <role> and its common variants posted in the last 30 days, then keeps postings at companies headquartered in <country>. Each posting's title, date, location and description snippet are kept on the row.
- Filter companies to the size band. Firmographics confirm each company has 50-1000 employees. Very large companies are excluded because a single posting there says little about the budget owner, and very small ones because the founder is the hiring manager and a different playbook fits them.
- Identify the hiring manager. People search finds the VP or Director of the function the role sits in, using the posting's department and seniority to decide which function that is. Where the posting names a manager or team lead, that person is preferred and the VP is noted as a second contact.
- Verify and deliver to Instantly. Emails are found and verified, and only deliverable contacts are loaded into Instantly as a lead list named <name>, with the posting title and date as custom fields so the sequence can reference them. Nothing is sent; the list waits for you to attach a campaign.
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
An Instantly lead list named <name> holding one verified hiring manager per company that posted a <role> in <country> this month, each with the posting title, posting date and company size as custom fields ready for merge tags. The report shows the count of postings found, companies inside the size band, and verified contacts, plus the companies where no manager could be identified.
Make it yours
- Use the Personalization playbook for job-post openers to write the first touch from each posting's language before attaching the campaign.
- Deliver to Lemlist or Apollo instead of Instantly, or to HubSpot when the sequence runs from the CRM.
- Run it weekly and only companies with new postings are added, which turns the list into a standing signal feed.
Frequently asked questions
How does the agent decide which function the role belongs to?
From the posting's department field and title, mapped to a function such as marketing, sales, engineering or operations. The mapping is shown per row so you can correct an odd case.
Will the same company appear twice if it posted the role in two cities?
No. Postings are grouped by company, and the row notes how many matching postings exist, which is itself a useful signal of urgency.
Can I include companies outside the size band with a flag?
Yes. Ask the agent to keep them and mark them, and they appear at the bottom of the list with the band noted.
Can the posting text be attached to each lead?
Yes. The description snippet is stored as a custom field and the full posting link is kept beside it, so the sequence can quote the exact language the manager used and the rep can read the whole posting before a call.