The JD is the intent signal.
A company hiring a CRM admin has no admin today. A company hiring an SDR manager is scaling outbound. Job posts publicize the stack, the gap, the buyer, and the budget. The most underused signal in B2B.
7-minute read · 1 anatomy table · 1 sequence template · 1 worked example
Open reqs are public gaps.
Every job description is, from the vendor's point of view, a public confession that the company is currently understaffed for the work the JD describes. A "Salesforce admin" job post means there is no Salesforce admin today. A "Director of Pipeline Operations" req means pipeline operations is currently broken or nonexistent. The role title is the gap statement and the JD body is the qualification call.
That confession includes specifics most cold lists do not have. Required tooling experience names the stack the company runs on. "Nice to have" lines hint at the upgrades the hiring manager already wants to make. The hiring manager is usually named or implied in the structure. And the urgency is implicit in the fact that the company is paying to advertise the role.
The window is wider than the funding or job-change signals. Senior roles take 60 to 120 days to fill. During that period the function is operating below capacity. Tools and services that bridge the gap, ideally on a scoped engagement that the procurement path can approve faster than a hire, have a clear ROI math to point at: the loaded cost of the role they have not yet filled.
The play scales because the personalization is structured. The JD names the stack, the gap, and the urgency in a format that is easy to parse, which means per-prospect handling time is low. A team can sustain 100 to 300 high-fidelity prospects a month off a single role keyword without burning out on per-prospect research.
The rest of this page is the anatomy of which JDs convert and which do not, the gap-pitch sequence that works, the composite case study of a managed-BDR firm that built a 1.5M ARR business off SDR job posts at Series A companies, and what running the play with help looks like.
The right role is a specific match.
The play converts at different rates depending on whether the role is a first-time hire, a backfill, or a scale-out. The table below is the calibration matrix. The "right offer shape" column is the wedge: it tells you whether to pitch the bridge engagement, the tool that augments the role, or the audit before the hire lands.
| JD type | Reply band | Right offer shape | Conversion |
|---|---|---|---|
| First-time hire (no incumbent) | 20 to 28% | Bridge engagement until the hire lands | 1 in 3 |
| Backfill at growing co | 14 to 20% | Bridge plus tooling pre-loaded for new hire | 1 in 5 |
| Scale-out (3rd hire+) | 10 to 16% | Augmentation, not replacement | 1 in 7 |
| Senior role replacing exec hire | 10 to 14% | Audit before the hire | 1 in 6 |
| Backfill at struggling co | 5 to 9% | Sell into the rebuild, not the role | 1 in 12 |
| Job that mentions specific tools | 18 to 26% | Pitch tied to the named tool | 1 in 4 |
The "first-time hire" case is the strongest. There is no incumbent vendor to displace and no implementation work to undo. The hiring manager is buying a function that does not yet exist inside the company, which means they are unusually open to creative offer shapes.
The trap is the senior role at the company that just lost an exec. The JD signals the budget exists, but the procurement path has cooled because the company is in transition. Default to the audit offer, not the bridge offer, until you understand the dynamic.
Reference the JD. Pitch the gap.
The structural reason JD-triggered outreach converts is that the personalization writes itself. The JD names the role, the stack, the required experience, and often the manager. Three sentences into the email and you have already cited four data points that no cold list would have.
The sequence is three touches over 12 days. The play is over by day 60 because the role is either filled or the company has dropped the search.
The loaded-cost frame in touch two is the conversion accelerant. Most hiring managers have not done the math on what their unfilled role is costing them per day; presenting that math, alongside a scoped offer that comes in below the salary line, reframes the procurement decision entirely.
What does not work is pitching the offer as a permanent replacement for the hire. The hiring manager is hiring the role for a reason, and your pitch landing as "you do not need to hire" reads adversarial. The bridge frame, explicitly time-bound to the search window, lets the offer co-exist with the hire decision instead of competing with it.
The managed-BDR firm that ran an entire business off SDR job posts.
Composite drawn from managed-BDR services running JD-triggered outbound as the sole motion. Specifics anonymized; the arc reflects what the play produces when the JD-offer match is clean.
The team was a 3-person managed-BDR service targeting Series A B2B SaaS companies hiring their first SDR. They had been running cold outbound to a list of recently-funded Series A companies with mixed results, sitting at 380K ARR after 11 months and not growing.
They switched to JD-only sourcing. Daily scrape of Greenhouse, Lever, and Ashby public boards filtering for "SDR" or "BDR" or "Sales Development Representative" at companies tagged Series A. Sent the founder-written sequence above within 48 hours of the post going live. The offer was a 90-day managed-BDR bridge priced at 8K monthly, framed against the loaded cost of an SDR hire which was running roughly 12K monthly fully loaded.
Reply rate landed at 21 percent. Of replies, 1 in 4 converted to a paid 90-day engagement at the 8K monthly rate. Retention past the 90-day mark to a renewing engagement was 60 percent, often because the SDR search had taken longer than the founder expected and the bridge had become the actual motion.
The team grew from 380K to 1.5M ARR in the following 14 months, all from JD-sourced prospects. They added a second role keyword (RevOps managers) in month 12, which roughly doubled the sourcing volume again. They have not bought a list since.
The scrape is the brittle part. The offer is the win.
The reason most founders do not run this play themselves is two-part: the ATS scrape needs maintenance as Greenhouse and Lever change their DOM, and the offer-shape design takes more thought than most founders give it. We handle both.
Four pieces, repeated weekly, indefinitely:
ATS scrape, stable
Greenhouse, Lever, Ashby, LinkedIn Jobs piped to a daily JD feed. Filtered to your role keyword and company-size band. We handle the scrape maintenance.
Hiring manager identification
Per JD: identify the hiring manager via LinkedIn structure, the company's career page, or backreference from the ATS. Verified email. Ready to send within hours of post-go-live.
Offer-shape design
The bridge engagement priced against the role's loaded cost. Service scope tied to the JD's responsibilities. The offer that makes the math obvious to procurement.
Sequence in your voice, JD-cited
Founder-written sequence sent from your domain with the JD specifics cited in line one. We draft, you sign off on the first ten, then we run.
The sizing call is short. You tell us the role you sell into, we tell you the JD volume against your ICP and the realistic conversion math on the bridge offer shape, and you decide whether running the play is worth the time.
Tell us the role. We will tell you the JD volume.
We will pull a sample week of JDs matching your role keyword across the Series A/B/C company-size band, send you the list, and walk through what the bridge offer shape would look like at your loaded-cost math. If the play pencils, we can talk about running it.
Book the sizing call →Free for founders. The sample JD list is yours either way.