- Prosyo Docs
- Playbooks
- Playbook: Hiring-signal outreach
On this page
Target companies that are hiring for the problem you solve. A job post is a public statement of pain and budget.
Best for: SaaS, agencies, recruiting, outsourcing · Plan: any · Setup time: about 30 minutes
Why it works#
When a company posts a job for "SDR", "RevOps Manager" or "Content Marketer", it's telling you:
- they have the problem your product solves,
- they have budget for it,
- someone senior is thinking about it right now.
Signals by offer#
| You sell | Look for job posts like | Reach out to |
|---|---|---|
| Outbound / sales tools | SDR, BDR, Head of Sales Development | VP Sales, Head of Growth, Founder |
| Marketing agency | Content Marketer, Performance Marketer | CMO, Head of Marketing |
| RevOps / CRM consulting | RevOps Manager, Salesforce Admin | CRO, VP Sales |
| Dev agency / outsourcing | Senior Engineer, CTO | CTO, Founder |
| Recruiting | Any role that's been open 30+ days | Hiring manager, Head of Talent |
| Security / compliance | Security Engineer, Compliance Manager | CISO, CTO |
1. Build the list#
- On LinkedIn Jobs, search for the role, for example
"SDR", and filter by location, date posted (past week) and company size. - Note the companies. Many teams keep a simple spreadsheet: company, job title, job URL.
- In Sales Navigator, find the hiring manager (the title in the table above) at each company.
- Import them into a list: "Hiring signal – SDR – [week]".
- Create a custom field
hiring_rolein Settings → Custom fields and fill it with the role they're hiring for: map a column to it when you import a CSV, or edit it in each person's side panel.
Automate it. Feed your hiring-signal source (Clay, a job-board tool or a spreadsheet) into Prosyo with a custom trigger. A trigger adds people to a list but can't fill custom fields, so send each role to its own list and campaign (for example "Hiring signal – SDR") and write the role straight into that campaign's copy.
2. Sequence#
| # | Step |
|---|---|
| 1 | Visit profile |
| 2 | Connection request (with note) |
| 3 | If accepted (wait 7 days) → continue if not |
| 4 | LinkedIn message (only people who accepted) |
| 5 | Delay 3 days |
| 6 | Email (needs a mailbox, so leave it out on Starter; skipped for people without an email) |
| 7 | Delay 4 days |
| 8 | LinkedIn message (only people who accepted) |
Turn on Cancel an invitation if not accepted till (see Settings below). A LinkedIn message waits until the person accepts your invite. Once Prosyo withdraws the invite, the LinkedIn messages are skipped and the email still goes out.
Copy#
Connection request
Hi {{first_name|there}}, saw {{company_name|your team}} is hiring a {{custom.hiring_role|new team member}}. Building the same function is what I spend my days on. Would be good to connect.LinkedIn message 1
Thanks for connecting, {{first_name|there}}. Quick question on the {{custom.hiring_role|new}} role: is the goal to add capacity, or to fix something that isn't working today?Subject: {{custom.hiring_role|new hire}} at {{company_name|your team}}
Hi {{first_name|there}},
Noticed the {{custom.hiring_role|open}} role. Hiring usually takes 60–90 days, and ramping another 90.
Some teams use us to get results in the meantime, or to make the new hire productive from day one.
Worth a 15-minute chat before you make the hire?
{{sender.first_name}}LinkedIn message 2
{{first_name|Hi}}, no pressure at all. If it helps, I can share what a strong first 90 days looks like for a {{custom.hiring_role|new hire}} in this role. Happy to send it over.3. Rules#
- Never criticize their hiring ("you don't need to hire").
- Position as "in the meantime" or "make the hire succeed".
- Move fast. Job posts go stale in 3–4 weeks.
Settings#
Recommended limits · Cancel an invitation if not accepted till on, 7 days (the same as the wait in step 3) · Turn off remaining steps when they reply on.
Metrics to watch#
| Metric | Target |
|---|---|
| Acceptance | 25%+ |
| Reply rate | 8%+ |
| Share of lists refreshed weekly | 100%. Stale job posts kill replies. |
Tools used in this playbook#
Custom triggers · Custom fields · Recruitment playbook · B2B service providers
