The problem this solves
Companies hiring for growth and demand-gen roles are announcing the exact moment outbound vendors dream of: new budget, new mandate, and a leader staffing up who is about to make a wave of tooling and agency decisions. The trigger is public, refreshes continuously, and expires fast - a posting from six weeks ago reads as old news in an email, while one from last week reads as attentiveness.
Working the trigger manually means a standing weekly grind: sweep the postings, dedupe the staffing-agency noise, figure out who the hiring manager actually is, find and verify their email, write a first touch that references the specific posting, and load everything into the sending tool. Each step is manageable; the chain is a recurring half-week, which is why teams run it twice with enthusiasm and then quietly stop, leaving a perpetually refreshing trigger unworked.
The failure mode of automating it carelessly is worse than not doing it: unverified emails bouncing off a fresh domain, or a template that name-drops the wrong posting. The play needs the whole chain automated and the launch withheld, so a human confirms the batch before the domain takes any risk. That combination is what this mission delivers in a single pass.
How the mission runs
- Sweep 14 days of postings with Hiring Data. The agent collects every company that posted a growth or demand-generation role in the last 14 days, collapsing duplicates and staffing-firm reposts to the true employer. Each surviving company is paired with the specific posting that qualified it, kept verbatim for the copy step.
- Find the hiring manager with Email Finder. For each company, Email Finder identifies the hiring manager behind the role - the growth or marketing leader building the team - and returns their work email. This is the person for whom the posting is current, personal news rather than trivia.
- Verify before the campaign exists. Email Verification confirms every address, and only deliverable contacts proceed. Trigger-based campaigns tempt teams to rush the list straight to send; the verification gate is what lets speed and domain safety coexist in the same play. Exceptions are reported rather than discarded.
- Write the posting-referenced first touch. Each lead gets a first touch drafted around their actual posting - the role, what it implies about the team's direction, and why that makes the conversation relevant now. The reference is specific enough that the email could only have been written this week, for them.
- Assemble in Instantly and leave it paused. Lead list and sequence are created as a campaign in Instantly and deliberately left paused, with a summary of what went in: companies, roles that triggered them, verification results, and copy samples. You review the batch in Instantly and press launch yourself.
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 paused campaign in Instantly containing every qualifying company from the last 14 days of growth-role postings: verified hiring-manager emails, a first touch per lead referencing their specific posting, and a plain summary of the batch - what triggered each lead, what failed verification, and sample copy. Launch is one reviewed click, and re-running the mission biweekly turns the play into a standing trigger engine.
Make it yours
- Change the tracked roles to whatever function predicts need for your product - RevOps, sales leadership, content, or data hires.
- Narrow to companies above a size floor so the campaign skips teams too early to buy, keeping the batch dense.
- Run weekly with a 7-day window instead, trading batch size for triggers that are never more than a week old at send time.
Frequently asked questions
Why does the campaign stay paused instead of launching?
Because the last check belongs to a human. The agent has verified the emails and grounded the copy, but you confirm the batch matches your bar - and your domain - before anything sends. The pause converts a risky automation into a reviewed one at the cost of a single click.
How does the mission avoid emailing about expired postings?
The sweep window is 14 days at run time, so every referenced posting was live within the past two weeks. Launching promptly after review keeps the reference fresh; if a batch sits too long, re-running the mission is cheap and produces a current one.
What if the same company posts roles repeatedly?
Companies already contacted in previous batches are recognized and excluded from new ones, so a serial poster is not serially emailed. Re-runs deliver only new triggers, which is what makes the biweekly cadence sustainable without list fatigue creeping in across a long-running program.