The problem this solves
A company posting SDR openings is announcing a bet on outbound growth, and the VP of Sales behind those reqs is in build mode: evaluating tools, designing process, and unusually receptive to anything that makes the new team ramp faster. The trigger is public and precisely timed. The catch is that its value evaporates in about two weeks, and by the time a human researcher has found the postings, identified the VPs, and written twenty genuinely specific emails, the moment has usually passed.
The specificity bar is what makes this slow. An email that merely says 'saw you are hiring SDRs' is a template wearing a trigger; the version that works pairs the posting with one real insight about the company - something from their announcements, their positioning, their trajectory - that proves a person paid attention. That second ingredient requires actual research per company, and research per company is exactly what does not scale by hand.
Speed without review is its own trap, though. First-touch cold email carries your name and your domain; twenty emails written fast should still pass through human judgment before any of them sends. Drafts in your own Gmail are the right resting state: fully prepared, zero committed. You keep the judgment and the send button; the agent absorbs everything upstream of them.
How the mission runs
- Find the fresh SDR openings with Hiring Data. The agent sweeps Hiring Data for companies that recently posted SDR roles, keeping the window tight so every trigger is warm. Duplicate postings and staffing-agency listings are collapsed to the real employer, and each company is captured with the posting text that qualified it.
- Identify the VP Sales with Email Finder. For each of the 20 companies, Email Finder locates the VP of Sales or nearest sales leader and returns a verified work email. The person opening SDR reqs owns the outbound build, which makes them the one contact for whom this trigger is genuinely their news.
- Research one real insight per company. Web Research digs into each company for a single specific, current insight - a launch, a funding note, an expansion, a positioning shift - that can sit alongside the posting reference. One well-chosen insight per email is the difference between a trigger template and a message that reads as attention.
- Draft the first touch. The agent writes each email to connect the posting to the insight to your relevance, in a few tight sentences. No two drafts share an opener, because no two companies share the same evidence. The copy aims for the tone of a sharp colleague rather than a campaign.
- Stage everything in Gmail for review. All 20 emails are created as drafts in your Gmail, addressed and ready. Nothing sends. You review each one against your own read of the account, edit where your knowledge beats the research, and release them on your own timing.
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
Twenty Gmail drafts, each addressed to a VP of Sales at a company with a fresh SDR opening, each referencing the actual posting and one researched company-specific insight. The drafts arrive with the evidence behind them summarized in the mission thread, so review is fast: open, judge, send or skip, one by one. The whole batch exists inside the window while the trigger is still current.
Make it yours
- Track AE or sales-leadership openings instead of SDR roles when your product serves the closing motion, keeping the same research-and-draft treatment for every trigger.
- Localize the sweep to your sales territory so every draft can carry a region-aware line, then rotate through neighboring regions on a weekly cycle for full coverage.
- Ask for a follow-up draft per contact three business days behind the opener, staged in the same batch for a two-touch play.
Frequently asked questions
Why drafts instead of sending automatically?
First-touch cold email is where your judgment adds the most and errors cost the most. Drafts give you the compression benefit - research and writing done - while keeping the send decision human. Teams that build trust with the output over several batches often move to lighter-touch review, on their own terms.
How current are the postings being referenced?
Hiring Data is swept at run time with a tight recency window, so every referenced posting was live when the mission ran. Reviewing and sending the drafts promptly keeps the reference timely, which is most of the trigger's power in the first place.
What if the researched insight is wrong or stale?
Each draft shows its insight plainly, and the mission thread records where it came from, so a bad one is visible in seconds during review. Edit the line or skip the draft; nothing has sent. In practice the review pass exists precisely to catch the occasional miss before it carries your name.