Direct answer: Reference the role by title, number or age, then connect it to what you do in the same breath. "Noticed the senior QA role has been open five weeks. Those roles are our specialty, typically filled in three." Open roles are the single best first line source for recruiters because they are public, current, verifiable and exactly the pain you solve. No other signal maps this cleanly from their problem to your service.
Key takeaways
- The open role is proof of budget, pain and timing in one public fact.
- Specificity levels: title beats count beats vague "your openings."
- Role age is the sharpest angle: an old posting is a wound.
- The connection to your service must land in the same line or the next.
What are the strongest role reference patterns?
The title reference: "The Head of Data role caught my eye." Shows you read, not scraped. The count reference: "Four engineering openings this month reads like a scale up push." Frames their hiring as a story. The age reference: "Six weeks is a long time for a platform lead posting." Names the pain directly, works best when tactful. The pattern reference: "Third sales role this quarter. Growth or churn, either way that is a lot of hiring." Bold, memorable, for confident senders. Each pattern then bridges: one clause connecting the observation to your lane.
Where does the role data come from at volume?
Job boards, career pages and LinkedIn postings, refreshed weekly, matched to your target list. Manually, this is the most tedious research in outbound and the first thing owners abandon in a busy month. In SDR GROW, the lead engine attaches live openings to each mapped company as standard, so every drafted first line in the 16 touch flow can cite the roles without anyone browsing job boards at midnight. The sequence's later touches update too: a company that posts three new roles at your touch 6 deserves a touch 7 that mentions it.
How specific is too specific?
Public facts only, stated plainly. Role titles, posting dates, counts: fair game, it is on their careers page. Guessing at internal drama ("heard your last hire quit") crosses into creepy even when true. The line is simple: reference what they published, not what you inferred.
Checklist: role based first lines
- Role verified live this week, not last month.
- Title spelled exactly as they posted it.
- One observation, one bridge to your service.
- Age references kept tactful, factual, never mocking.
- Sequence updates when their postings change.
Example
Generic: "We help companies like yours find great talent." Role tied: "The DevOps posting hit five weeks yesterday. We filled two identical roles in your market this quarter, both in under four. Worth a look at how?" The second email got this reply: "How did you know it has been five weeks? Yes, call me." The prospect experienced research as care. That is the entire mechanism.
Mistakes to avoid
- Citing expired postings. Nothing says mass sent list like a filled role.
- Listing every opening they have. One role, referenced well, beats an inventory.
- The observation with no bridge. "You have roles open" plus silence helps nobody.
- Copying the posting's own buzzwords back at them. Translate to plain speech.
FAQ
What if they post roles anonymously through agencies already??
That is a signal too, the best one: they buy recruitment services. Your first line becomes about capacity or specialty, not discovery.
Do hiring managers find role references invasive??
Almost never. The posting is a public request for help. Answering it specifically is the least invasive outreach there is.
How fresh must the data be??
Checked within the week of sending. Weekly refresh is the minimum standard a system should hold.
Related reading
Ready to build predictable pipeline for your agency?
Book a Strategy Call →