Write a cold email from a hiring signal
Turn "they're hiring for X" into a short, relevant first email that doesn't sound like a template.
Ten companies that are hiring for a role your product helps with, and a reviewed first email and follow-up for each, ready to load into your sequencer.
Tools you need
Step-by-step workflow
Decide which hires signal a need for what you sell
A job post is a public statement of a problem. Pick 2–3 roles where a new hire means the company is about to feel the pain your product solves.
Find 10 companies hiring for those roles right now
In Apollo, filter companies by job postings for your chosen titles, your industry and your company size. Keep only posts from the last 30 days. Save 10 companies and one decision-maker at each, usually the hiring manager's manager.
Hiring-signal email kit
A spreadsheet with a role-to-problem map, a 10-company tracker with follow-up dates, and every prompt from this workflow.
Pull the pain out of the job post
Open each job post and paste the text into your AI assistant. You want their words, not yours.
Draft the email
Keep it under 90 words. Lead with what you noticed, connect it to a likely problem, offer one useful thing and ask a soft question. Generate three versions and pick one.
Review, then send
Read every email before it goes out. Check the name, the role and that nothing was invented. Load the 10 emails into your sequencer with one follow-up 3–4 business days later.
Turn this into a system
Once this workflow is working manually, connect it into an automated GTM playbook or stack.
Trigger outbound prospecting sequences based on verified hiring, leadership changes, or funding rounds rather than static buyer lists.
Modular outbound pipeline generation architecture with AI waterfall enrichment and multi-inbox rotation under $500/mo base software cost.
Want this running for you?
GPTify builds it on your tools, with a fixed scope and price.
Frequently asked questions
Is it okay to mention the job post in the email?
Yes, as long as you use it to show relevance, not to prove you were watching them. "Saw you're hiring a RevOps lead" is fine. Quoting their job post back at them line by line is not.
How many emails should I send per day this way?
Quality beats volume here. Ten well-researched emails a day is a good start. To run this at scale, see the Signal-Based Prospecting playbook.
Can I automate the whole thing?
Steps 2–4 can be automated with an enrichment and sequencing setup. Keep a human review before sending.
Related workflows
All workflows →Turn a LinkedIn post into a first message
Use what prospects already said in public to start a real conversation, not a pitch.
Research an account in 10 minutes
Decide if an account is worth your time, who to contact and what to say, before you write a single email.
Prep a discovery call brief in 10 minutes
Walk into every first call knowing the company, the people and the three questions that matter.