Writing the Hiring-Trigger Message
Outcome: a message per account that uses the posting as evidence of a situation, not as a fact to recite, and that passes the interchangeability test.
- Surface
- App
- Level
- Intermediate
- Uses
- AI copy column — no new data calls
- Credits
- ~1 per row
- Prerequisite
- Lesson 05's extracted post data
The mistake everyone makes
“I saw you’re hiring a Senior Data Engineer!”
The recipient knows. They wrote the post, or approved it. Telling them a public fact about their own company proves only that you can read a job board — and it is the exact opening every other vendor using the same signal has already sent them.
Reference the consequence, not the post
The post tells you a situation is coming. The message should be about the situation.
| Weak — recites the post | Strong — names the consequence |
|---|---|
| ”I saw you’re hiring three SDRs." | "Three SDRs starting in the same quarter usually means one person owns onboarding for all three at once." |
| "Noticed you’re looking for a data engineer." | "First data hire is normally when the reporting someone built in a spreadsheet stops holding." |
| "You’re hiring a Head of RevOps!" | "A first RevOps hire usually arrives to find four systems that disagree about the same account.” |
The formula: fact you did not state + implication you did state. They supply the connection, which is what makes it feel like understanding rather than monitoring.
You can reference the post without reciting it. “Your platform engineer posting mentions Airflow and dbt” works because the specific detail proves you read it rather than matched a keyword — and it goes somewhere, rather than stopping at the observation.
What to reference
| Detail from the post | How to use it |
|---|---|
| Named tools | Strongest. Specific, verifiable, implies a workflow you understand. |
| Team size | ”A team of six” grounds the consequence in their scale |
| The problem statement | Their own words about why the role exists — quote lightly |
| Number of roles | Volume implies scale pain |
| ”First X hire” | The strongest single detail available: nothing exists yet |
What to leave out
- The candidate profile, salary or benefits — none of it is your business
- Anything that reads as advice about their hiring
- Congratulations on growing the team
- The word “noticed”
Variants by role type
First-of-its-kind hire
Nothing exists yet. Angle: what the new person will spend their first quarter building, and how much of it they will not have to build.
Volume hire, several of the same role
Scale pain. Angle: what breaks when the team doubles — onboarding, consistency, reporting.
Leadership hire
Mandate and timeline. Angle: what leaders in that seat usually change in their first two quarters. Note that the new leader may not have started yet, so the message often goes to whoever hired them.
Backfill
Weakest signal. Usually not worth a message on its own — wait for a second signal.
Timing
The post is your window. Two rules:
- Under 30 days. After that, the role may be filled and your reference is stale.
- Not day one. A post that went live this morning has not yet produced the pressure your message describes. Two to three weeks in is a better moment.
Do this now
Build the evidence field
From lesson 05’s extraction: tools, team size, role count, problem statement, first-hire flag.
Write one variant per role type
Four short templates, human-written.
Generate only the consequence sentence
The rest of the message is written once.
Ban the recital phrases
“I saw you’re hiring”, “noticed you’re growing”, “congrats on the new role”.
Run on five rows and read aloud
Apply the interchangeability test
Could this sentence go to another company? If yes, rewrite the prompt.
Check the window
Drop anything over 30 days old.
Check your work
- No message recites the job post as news
- Every message names a consequence, not just a fact
- Role-type variants exist and are used
- Posts older than 30 days are excluded
- You read five messages aloud
Where this breaks
Referencing a role that has already been filled makes the whole approach look automated, because it is the one error a human researching the account would never make. Job posts stay live after the hire in many systems. Use the posted date, hold to a 30-day window, and re-check the posting is live before a batch goes out.
Further automation
The strongest version of this play messages the new hire rather than the hiring manager, once they start. Someone in their first 90 days in a newly-created role is evaluating everything, has a mandate, and has not yet chosen a vendor. Pair the job post with Job Changes & Champions to catch them.
Next lesson
07 — Score the signal and gate the spend, formalizing which accounts reach lesson 05 at all.
Reference for this lesson: AI agents, Company job listings, Automated Outbound, AI-Powered GTM.