Plays / New Head of Sales, Broken Pipeline, Wrong Tools for the Stage
cold email · Series A / Series B
New Head of Sales, Broken Pipeline, Wrong Tools for the Stage
Target
Head of Sales / VP Sales / CRO
Company size
35–150 employees
Stage
Series A / Series B
Test batch
50 contacts
Expected reply
4-8%
Expected meetings
1-2%
Setup time
1w
Time to meetings
6w
Context
How this is usually done. And how this play runs instead.
The manual approach
- 01
Manually scroll LinkedIn for recent job changes in sales leadership
- 02
Note down companies that seem like they might have pipeline problems
- 03
Look up the contact, find an email, put it in a spreadsheet
- 04
Send a broad outreach about "fixing outbound"
- 05
Send from your personal inbox to seem less spammy
- 06
Check for replies over the week, follow up when you remember
- 07
Miss the window — a new VP Sales is only in fix-it mode for 4–6 months
How this play runs
- 01
LinkedIn tenure data surfaces sales leaders hired in the last 6 months — automatically
- 02
BuiltWith confirms they are running both a sequencing tool and a data tool — the compound signal
- 03
SDR job postings confirm urgency before a single message goes out
- 04
Message references the specific inherited stack situation, not a generic pain point
- 05
Sent from a dedicated outreach domain — deliverability is managed, not assumed
- 06
Replies hit Slack with timing context — you know how fresh the lead is
- 07
Every reply actioned same day, no leads dropped, Ridgeview referral channel layered in
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 Sales Navigator with hire date data
LinkedIn Sales Navigator / Apollo.ioHire date is the core filter. LinkedIn Sales Navigator is the most reliable source — it surfaces "started role X months ago" data directly. Apollo can supplement for company filtering but lags on tenure accuracy.
Tech stack detection for the compound signal
BuiltWith / ClearbitThe high-value version of this play targets companies running both a sequencing tool (Salesloft, Outreach) AND a data tool (Apollo, ZoomInfo). Two outbound tools at a company this size without results is the tell. BuiltWith is the primary detection source.
LinkedIn Jobs check for SDR attrition signal
LinkedIn Sales Navigator / PhantombusterAn open SDR or BDR JD at a company with a new Head of Sales is the clearest compound signal in this play. It means the new leader has already had turnover or has identified that the existing team is not working. Check LinkedIn Jobs at the company level.
Email finding waterfall
Apollo.io / Hunter.io / Dropcontact / NeverBounceVP-level contacts at this size company are findable via standard email patterns. Apollo usually hits first for US-headquartered companies. Always verify before enrolling.
Warmed sending domain
Instantly / Smartlead / MailreachA senior sales leader receives heavy vendor outreach. Domain reputation is the difference between landing in the inbox and being filtered before they see it.
CRM with outbound pipeline stage
Attio / HubSpot / SalesforceThis play closes at higher ACV than the VP Marketing play. Pipeline tracking matters more. A Cold Outbound stage ensures every reply becomes a properly attributed deal and does not get lost.
Reply routing to Slack
n8n / Zapier / MakeA new Head of Sales making vendor decisions in their first few months moves fast. A reply caught hours late often goes cold. 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.
Head of Sales hire < 6 months
Source: LinkedIn Sales Navigator
Salesloft or Outreach in tech stack
Source: BuiltWith
Apollo or ZoomInfo also in stack
Source: BuiltWith
Open SDR/BDR job posting
Source: LinkedIn Jobs
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.
Seed List Pull
LinkedIn Sales Navigator→ 150–200 raw accountsBuild a saved search in Sales Navigator filtered by title, seniority, headcount, and hire date. LinkedIn Sales Nav is the most reliable source for recent job changes — which is the core signal for this play.
Build and review the saved search before exporting. Narrow or widen the title filter based on how the results look.
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.
Funding Stage Confirmation
Crunchbase→ Stage and raise date confirmedPull funding stage and last raise date from Crunchbase. Confirms the company is in the right stage window and the raise is recent enough to still be in the buying cycle for new infrastructure.
Flag unusual funding histories — bridge rounds, down rounds, or stale data — for manual review before enrolling.
SDR Attrition Detection
LinkedIn Jobs + LinkedIn profiles→ Pipeline urgency confirmedCheck LinkedIn Jobs for open SDR/BDR postings at each company. Then scan current employee profiles for short SDR tenures (under 8 months). A new sales leader plus high SDR attrition is the strongest urgency combination.
This step needs human review. Attrition signals are easy to misread at scale — spot-check 5–10 companies before finalising the scores.
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→ 50 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
Head of Sales, VP Sales, or CRO who joined a company within the last 6 months and inherited an outbound motion that is not working. Headcount 35–150. Revenue $8M–$35M ARR.
The compound signal that defines this play: a recent senior sales hire at a company running both a sequencing tool (Salesloft or Outreach) AND a data tool (Apollo or ZoomInfo), plus visible SDR attrition. All the tools are there. The results are not. A new leader just arrived to fix it.
Why This Audience
A new Head of Sales inherits three problems at once: a pipeline that was undersized before they arrived, a rep team that needs quick wins to stay motivated, and board pressure to show results. Their first instinct is to hire more SDRs or swap the CRM. Both are wrong.
The problem is almost always upstream: list quality, ICP targeting, and the enrichment logic connecting the data tool to the sequences. Fix the infrastructure and the same reps start converting.
The angle is not "your reps are bad." It is "your reps are working the wrong accounts." That framing lands without triggering defensiveness and points toward a solution the new leader can own as their fix.
ICP Scoring Breakdown
| Signal | Points | |--------|--------| | Head of Sales hire less than 3 months ago | 40 | | Head of Sales hire 3–6 months ago | 30 | | Salesloft or Outreach confirmed in stack | 25 | | Apollo or ZoomInfo also in stack | 20 | | Open SDR/BDR JD at company | 15 | | Company headcount 50–100 (sweet spot) | 10 |
Threshold: enroll at 55+. This list is small and targeted. Quality over volume — every contact should be in a genuine pipeline-fix window.
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], Congrats on the [Company] role. I will be direct: we work with new sales leaders who have inherited an outbound motion that is not generating what it should. The usual situation: the tools are there — Salesloft, ZoomInfo, whatever came before you — but the lists are broad, the sequences are generic, and there is no scoring layer connecting the two. The reps are working hard on the wrong accounts. We build the enrichment and scoring layer. Usually 6–8 weeks to the point where the list quality stops being the question. Is that the right problem right now? CJ SortedGTM
[First name], The reason outbound lists at companies your size are usually broad: the data sources are good but there is no scoring model running on top of them. Without a model weighting by tech stack signals, hiring activity, and funding recency, every account that fits a rough filter gets treated equally. The SDRs feel the randomness even if they cannot name it. The sequences run. The replies do not. The scoring layer alone typically cuts the prospecting list by 40% and focuses the team on accounts most likely to convert. 20 minutes to show you what that looks like? CJ
[First name], Last one. Either the timing is off or it is not the right problem for the next 90 days — both are valid. If pipeline infrastructure becomes urgent: sortedgtm.com. Stack assessment is free and usually surfaces 2–3 things worth fixing immediately, whether you work with us or not. Good luck with the ramp. 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
50 contacts
Expected replies
4-8%
Expected meetings
1-2%
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 target a new Head of Sales specifically, not an existing one?
A new sales leader in their first 6 months is in fix-it mode. They have a mandate to show results, inherited a pipeline that is not performing, and have not yet formed the vendor loyalties that make an incumbent harder to displace. The urgency and openness to outside help is higher than at any other point in their tenure. After 6 months they have usually committed to their own plan.
What does the compound tech stack signal tell you?
A company running Salesloft plus ZoomInfo at 50 employees is not understaffed on tooling. They have made the investment. The fact that a new sales leader arrived anyway means the results did not match the spend. That is exactly the gap we fill. A company with no outbound tooling at all is a different conversation with a longer sales cycle.
How do you identify SDR attrition signals?
Open SDR or BDR JDs on LinkedIn Jobs at a company with a new Head of Sales is the primary indicator. Cross-referencing the company's current employee page for short-tenure SDR profiles adds confirmation. A company that has posted an SDR JD within 60 days of a new sales leader starting is the highest-signal combination in this play.
Why does this play close at higher ACV?
A new Head of Sales at a Series B company is not buying a point solution. They are buying a complete infrastructure build plus ongoing management — the full engagement model. The urgency is higher and the budget authority is clearer than at the VP Marketing stage. The right close from this play is typically worth 2–3x a VP Marketing close.
How does the Ridgeview referral angle fit in?
Ridgeview makes reps better at selling. SortedGTM makes the pipeline those reps work better. A new Head of Sales who has engaged Ridgeview for rep coaching is a natural warm introduction opportunity. If the company is already a Ridgeview client, route through a warm intro instead of cold outreach — the conversion rate is significantly higher.
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.