Plays / Hiring for RevOps or GTM, JD Open 45+ Days
cold email · Series A / Series B / Bootstrapped
Hiring for RevOps or GTM, JD Open 45+ Days
Target
VP Marketing / CRO / CEO / Founder
Company size
25–150 employees
Stage
Series A / Series B / Bootstrapped
Test batch
60 contacts
Expected reply
6-12%
Expected meetings
2-4%
Setup time
1w
Time to meetings
5w
Context
How this is usually done. And how this play runs instead.
The manual approach
- 01
Manually search LinkedIn Jobs for RevOps or Marketing Ops postings
- 02
Click through each one to check how long it has been open
- 03
Try to figure out who owns the function to send to
- 04
Send an email saying you can help with operations
- 05
Get filtered by an ATS or a recruiter who does not own the decision
- 06
Follow up twice then give up
- 07
Miss the signal entirely for most companies because the search is too manual to run weekly
How this play runs
- 01
LinkedIn Jobs monitoring surfaces RevOps, MarOps, and GTM Engineer JDs automatically with post date captured
- 02
The 45-day filter confirms the search is struggling — the company has acknowledged the problem and has not solved it
- 03
Hiring manager identified (not recruiter) before any message goes out
- 04
Opener references the specific role and the build-vs-operate distinction — not a generic ops pitch
- 05
Message arrives while the search is still open and alternatives are still on the table
- 06
Reply routing in Slack — response speed matters when someone is actively evaluating paths
- 07
This is the warmest signal in the playbook: self-selected need, budgeted solution, no hire yet
Before this play runs
Prerequisites
Everything below needs to be confirmed before the first contact is enrolled. Each gap creates a broken loop somewhere downstream.
LinkedIn Jobs monitoring for ops roles
LinkedIn Sales Navigator / Phantombuster / LinkedIn JobsMonitor for active job postings in these categories with post date older than 45 days. Target roles include Revenue Operations, Marketing Operations, GTM Engineer, Demand Generation Manager, and Sales Operations. Filter to companies in the 25-150 headcount range. Phantombuster or LinkedIn Sales Navigator can extract this data at scale.
JD age calculation
LinkedIn Jobs / custom script via PhantombusterThe 45-day threshold separates "we just posted this and have strong candidates" from "we have been trying to hire for this and struggling." You need to capture the post date, which LinkedIn includes in the job listing. This calculation should be part of the enrichment step.
Hiring manager identification
LinkedIn Sales Navigator / Apollo.ioFind who posted the JD or who owns the function the role reports into. For a RevOps JD, this is usually the CRO, VP Marketing, or CEO. For a Marketing Ops JD, it is VP Marketing. Do not pitch a recruiter or HR contact — they do not make the infrastructure decision.
Current ops hire check
LinkedIn company page / Apollo.ioConfirm the company does not already have someone in a RevOps, Marketing Ops, or GTM Engineering role. The JD may be an addition rather than a first hire. If the team already has ops coverage, the conversation changes significantly.
Tech stack check
BuiltWith / ClearbitKnowing what tools the company already has informs the message. A company with Apollo plus Salesforce that is hiring RevOps has a specific problem. A company with nothing is at a different stage. BuiltWith is the primary source.
Email finding waterfall
Apollo.io / Hunter.io / Dropcontact / NeverBounceVP Marketing and CRO contacts are generally findable via standard email patterns. Apollo hits first for US-headquartered companies.
Warmed sending domain
Instantly / Smartlead / MailreachA secondary domain warmed for 30+ days.
Reply routing to Slack
n8n / Zapier / MakeA hiring manager who is actively trying to fill an ops role will engage fast if the message resonates. Route to Slack within 60 seconds.
Setup time: approximately 1 week before sequences go live.
What triggers this play
Signal Detection
A contact needs at least one of these signals confirmed before entering the waterfall. Two signals puts them in the top tier and gets them enrolled first.
RevOps or MarOps JD open 45+ days
Source: LinkedIn Jobs
No current ops hire on the team
Source: LinkedIn company page
Company headcount 25–150
Source: LinkedIn / Apollo.io
The enrichment waterfall
From raw list to sequence-ready contacts
Each step filters or scores before the next runs. The final output is a list of contacts above the ICP threshold, verified, and ready to enroll. Human review points are marked.
Ops JD Monitoring
LinkedIn Jobs→ RevOps/MarOps/GTM JDs open 45+ daysDetect active job postings for Revenue Operations, Marketing Operations, GTM Engineer, and Demand Generation Manager that have been open for 45 or more days. LinkedIn Jobs includes the original posting date. The 45-day mark is when the signal becomes actionable — earlier, the company likely still has strong candidates in process.
Capture the exact posting date and calculate days open. Set 45 days as the minimum threshold. Run this check weekly to catch newly stale JDs.
Company Data Enrichment
Apollo.io→ Headcount, stage, and industry confirmedPull company headcount, funding stage, and industry from Apollo. Confirms the company is in the right size range (25–150 employees) and stage window for the engagement to make sense.
Filter out industries where this play does not apply: pure services firms, non-B2B companies, enterprise companies above 150 employees.
Hiring Manager Identification
LinkedIn Sales Navigator / Apollo.io→ Decision-maker contact identifiedFind who owns the function the open role reports into. For a RevOps JD, this is usually the CRO, VP Marketing, or CEO. For a Marketing Ops JD, it is the VP Marketing. Do not contact a recruiter or HR — they do not make the infrastructure decision.
Check who posted the JD on LinkedIn (it is sometimes shown). If not visible, find the most likely function owner. This is a judgment call and worth getting right — the wrong contact reduces reply rate significantly.
Tech Stack Detection
BuiltWith→ Tool signals scoredDetect which outbound and marketing tools are live on the company's domain. BuiltWith crawls publicly visible tech signals — tracking scripts, analytics tags, email platform headers. A company running Apollo or ZoomInfo has already decided outbound is worth paying for.
Decide which tools score as high signals for this specific ICP. Update the scoring weights after each run based on what converts.
Email Finding Waterfall
Apollo.io → Hunter.io → Dropcontact → Findymail→ 70–85% email coverageTry each provider in order. Apollo first (largest database, 1 credit). If not found, Hunter.io (pattern-based, reliable for common formats). If not found, Dropcontact (strong GDPR coverage, European contacts). If still not found, Findymail (highest accuracy, 2 credits). Stop at the first hit — only pay for what is found.
Set the waterfall order based on your audience geography. US-heavy: Apollo first. European mix: Dropcontact earlier in the chain.
Email Verification
NeverBounce / ZeroBounce→ Clean, sendable listRun all found emails through a verifier before enrolling. Separate into valid, risky (catch-all), and invalid. Send to valid. Decide on risky — catch-all addresses often work but carry slightly more bounce risk. Discard invalid entirely.
Review the risky/catch-all bucket before discarding — many valid contacts land there. For high-value accounts, a manual check on the catch-all domain is worth it.
ICP Scoring
Combined signal formula→ Score 0–100 per contactA weighted score across all signals present for this contact. Contacts above the threshold enter the sequence. Below-threshold contacts go to a watchlist — they re-enter when new signals appear.
Review the top 10 and bottom 10 scores before launching. Adjust weights if the distribution looks wrong. This model improves with every run as outcome data feeds back in.
Enroll in Sequence
Sending platform→ 60 contacts enrolledContacts above the ICP threshold enroll in the email sequence. Contacts below go to a watchlist — they re-enter when new signals appear.
Final review before launch. Check the list size, the score distribution, and the first few emails the system would send. Then launch.
Targeting logic
Who, why, and how to score them
Who This Play Is For
Any B2B company that has posted a Revenue Operations, Marketing Operations, GTM Engineer, or Demand Generation Manager JD that has been open for 45 or more days. Headcount 25–150. The contact is whoever owns the function the role would report into — VP Marketing, CRO, or the founder.
This is the warmest signal in the playbook. The company has already identified the problem, budgeted for a solution, and tried the most common path (hiring). The message does not have to convince them they have a gap. It only has to offer a different path.
Why This Audience
Most companies at the Series A to B stage go through the same sequence: feel the pain of not having GTM infrastructure, decide to hire someone to build it, post a JD, struggle to find the right person, wait 60–90 days, either eventually hire someone who can build or settle for someone who can only operate.
The 45-day mark is when the struggle becomes visible from the outside. At that point, the hiring manager is often open to hearing about alternatives — not because they have given up on the hire, but because the pain of the gap has been compounding for 45 days and they are looking for something that can run in parallel or fill the gap faster.
The alternative we offer is not a replacement for the hire. It is a way to have the infrastructure running while the search continues. In many cases, the build we do becomes what the new hire maintains — which often makes the spec easier and the hire faster.
This play has the highest expected reply rate in the playbook because the buyer has self-selected into a state of acknowledged need.
ICP Scoring Breakdown
| Signal | Points | |--------|--------| | GTM Engineer JD open > 30 days | 40 | | RevOps or Marketing Ops JD open > 60 days | 35 | | RevOps or Marketing Ops JD open 45–60 days | 25 | | Demand Gen Manager JD open > 60 days | 20 | | No current ops hire on the team | 20 | | Company headcount 30–100 (sweet spot) | 15 |
Threshold: enroll at 50+. Every company where a GTM Engineer or RevOps JD has been open for 30+ days with no ops hire on the team is at threshold.
Lessons From Running This Play
No runs logged yet. This section updates after each run with reply rate, disqualification reasons, and what changed in the sequence or targeting.
The sequence
3 touches. Sent from a dedicated outreach domain.
Short, direct, signal-led. No case studies, no 6-paragraph intros. Each touch has one job and one ask.
[First name], Noticed [Company] has been looking for a [Role] for a while. The roles that stay open longest are usually the ones where the spec requires someone to both build and operate from day one. Hard to find, and expensive when you do. An alternative worth considering: we do the building piece as a focused engagement, then hand it off to whoever you hire or to your existing team. Usually 4–6 weeks. The hire becomes a different and narrower spec. Worth a call? CJ SortedGTM
[First name], RevOps and Marketing Ops hires are usually great at operating a system that already exists. The problem at most companies at your stage is that the system does not exist yet — enrichment logic, ICP scoring, sequence infrastructure, CRM workflows. Building that from scratch requires a different skill set than maintaining it. Most candidates are not honest about which one they actually are. We build the system. Your hire walks into something that works. CJ
[First name], Last note. Either the hire is close or you have found another path. If the system still needs building before the right person arrives: sortedgtm.com. Stack assessment is free, 30 minutes, and we will tell you honestly what is worth building now versus what can wait. CJ
After a reply
What happens next. And who does it.
Most outbound playbooks stop at the sequence. This is where the work actually starts. Every reply flows through a closed loop — no manual logging, no inbox hunting, no dropped leads. The steps below are how we run it.
Reply detected
Sending platform
The sending platform fires a webhook the moment a reply comes in — positive, negative, or out-of-office. Every reply is captured regardless of type.
Slack alert fires
Automation layer → Slack
A structured message lands in the pipeline channel with the prospect's name, company, ICP score, reply text, and action buttons. No inbox-checking. No manual logging.
CRM deal auto-created
Automation layer → CRM
A deal is created in the Cold Outbound stage with all enrichment data pre-attached — tech stack signals, ICP score, company details, trigger signals. Zero manual data entry.
Human reviews and responds
humanYour team
A person reads the reply in Slack, uses the play's response template or writes something more specific, and sends. Speed is the variable — the reply window closes fast.
Qualification
humanYour team + CRM
Positive reply: a booking link goes out. Unclear: one clarifying question. Negative: deal closed with reason logged. Nothing sits unactioned at end of day.
Signal feedback loop
humanCRM → enrichment model
After each run, outcome data is reviewed and signal weights are adjusted based on what actually converted. The following month's list is sharper. This is the part that compounds.
The result
Steps marked human require a person. Everything else runs automatically. The motion does not depend on someone checking their inbox or remembering to update the CRM.
Expected outcomes
What the first run should produce.
Test batch
60 contacts
Expected replies
6-12%
Expected meetings
2-4%
Decision rule
One meeting from the first batch → expand to 200+. Zero replies after the full sequence → rewrite the message before expanding. Never scale a sequence that has not proven it can generate replies.
Questions
Common questions about this play.
Why does the 45-day threshold matter?
A job posting that has been open for 45+ days without being filled is a signal that something in the search is not working. Either the spec is too narrow, the salary range is below market, the problem is harder to hire for than expected, or the company has not found someone who can both build and operate. All of these conditions make the alternative-to-hiring message more likely to land.
Why is this a warm signal compared to the other plays?
A company that has posted a RevOps or Marketing Ops JD has already done three things: identified the gap, decided the solution is a hire, and committed budget. The only thing they have not done is fill the role. You are not convincing them they have a problem — you are offering a different path to solving it. That conversation is fundamentally easier than cold problem identification.
What if they fill the hire while we are in the sequence?
If they fill the role, the message loses relevance and you should suppress further sends. The sequence also changes — a company that just hired an ops person is potentially a different kind of buyer, interested in infrastructure setup rather than ongoing management. Flag and reroute rather than disenroll.
Should we target GTM Engineer JDs specifically?
Yes, and weight them higher than RevOps or Marketing Ops. A company posting a GTM Engineer JD has a sophisticated understanding of the problem. They are likely further along in their thinking about what they need and why. They are also a smaller and more targeted pool, which means the competition for their attention in the inbox is lower.
What is the right follow-up if they reply saying the role is almost filled?
Ask what system the new hire will be walking into. If the answer is vague or "they will build it," you have an opening. Offer to do a pre-hire infrastructure sprint so the new person arrives to something. This is a common scenario and worth having a response ready for it.
Run this play
Want us to build and run this for you?
We start with a stack assessment to confirm this play fits your situation and what infrastructure is already in place. Free, usually 30 minutes. You leave knowing exactly what to build first — whether you work with us or not.