Plays / Founder About to Make Their First Sales Hire
cold email · Pre-Series A / Seed / Series A
Founder About to Make Their First Sales Hire
Target
Founder / CEO
Company size
8–35 employees
Stage
Pre-Series A / Seed / Series A
Test batch
50 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
Search LinkedIn for founders at the right company size — 45 minutes a morning
- 02
Save profiles one by one, find emails manually
- 03
Write semi-personalized emails referencing something generic
- 04
Send from the main Gmail account
- 05
Have a spreadsheet with 200 rows, half of them stale
- 06
See a reply 3 hours later on a phone, respond when you get a moment
- 07
Forget to follow up on half of them
How this play runs
- 01
Founder activity signals (LinkedIn posts, no sales hire confirmed) surface who is in the window
- 02
Enrichment confirms active founders and eliminates companies that have already made a sales hire
- 03
Opener references a specific recent post — actual personalization, not mail-merge
- 04
Sent from a domain built for outreach — not the one your company uses
- 05
Reply lands in Slack in 60 seconds regardless of where you are
- 06
CRM record created automatically — nothing to log
- 07
Feedback loop identifies which signal combinations actually convert
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 setup
LinkedIn Sales Navigator / Phantombuster / Clay LinkedIn enrichmentThe trigger signal is a first Account Executive or Senior AE JD posted in the last 30 days at a company with no current sales hires. LinkedIn Sales Navigator or a tool like Phantombuster can monitor this at scale. The JD age matters — after 30 days the timing window starts to close.
Confirm "first" sales hire
LinkedIn company page / Apollo.ioDistinguish a company genuinely making their first sales hire from one adding to an existing team. Check current employee list on LinkedIn for any AE, SDR, BDR, or Account Manager titles. If any exist, this is not the right timing signal.
Founder/CEO contact identification
LinkedIn Sales Navigator / Apollo.io / Hunter.ioAt this stage the founder is the decision-maker. Find them via LinkedIn, confirm they are still in an active selling role (no Head of Sales or VP Sales exists), and pull their email using a founder-specific finding order.
Founder email finding waterfall
Hunter.io / Findymail / Anymailfinder / Apollo.ioFounder emails are harder to find than corporate VP emails. Use this order and stop at first verified hit. Plan for a 15-25% invalid rate.
Email verification
NeverBounce / ZeroBounceFounder emails frequently change, especially at early-stage companies. Verify before sending. Invalid emails at this audience burn deliverability faster than at VP-level.
Warmed sending domain
Instantly / Smartlead / MailreachA secondary domain warmed for at least 30 days. Founders especially should not see outreach from your primary domain — it reads as automated and kills the personal tone this play requires.
Reply routing to Slack
n8n / Zapier / MakeFounders reply fast when the message lands, then move on. A slow response loses the window entirely. 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.
First AE job posting < 30 days old
Source: LinkedIn Jobs
No current sales hire confirmed
Source: LinkedIn company page
Founder active on LinkedIn (30d)
Source: LinkedIn
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.
First AE Job Posting Detection
LinkedIn Jobs→ First AE JDs posted < 30 daysDetect active Account Executive job postings published less than 30 days ago at companies with no current sales hire. This is the timing trigger for the play — the window between posting the JD and the hire starting is when the message is most relevant.
Confirm the JD is genuinely a first sales hire, not an addition to an existing team. Check the company employee page before enrolling.
Founder / CEO Identification
LinkedIn Sales Navigator / Apollo.io→ Founder contact identifiedFind the Founder or CEO at the company. Confirm they have no Head of Sales or VP Sales reporting to them — at this stage, they are still the primary sales function and the right person to receive this message.
Confirm the founder is the right contact. If a VP Marketing or Head of Revenue was recently hired, they may be the better contact instead.
Sales Function Check
LinkedIn company page→ Sales-function status confirmedScan the company's LinkedIn employee list for SDR, BDR, Account Executive, or VP Sales titles. Absence confirms the founder is still the primary sales function. Presence means this play's premise no longer holds.
Spot-check edge cases — fractional reps or advisors sometimes appear as employees. This affects the play's core premise, so get it right.
Founder Activity Check
LinkedIn→ Active founders flaggedCheck for LinkedIn posts in the last 30 days. A founder posting about product, customers, or industry problems is almost certainly still running sales. This is the highest-signal trigger in the play and cannot be skipped.
Review flagged founders before enrolling. Personalize the opener around a specific recent post when possible — this is the highest-leverage personalization in the play.
Revenue Signal Check
Crunchbase / Apollo.io→ Revenue range estimatedPull revenue estimates from Crunchbase or Apollo. Prioritize companies showing $3M–$10M ARR signals — above $12M they are likely already building infrastructure; below $2M the engagement timing is too early.
Revenue estimates are rough. Use as a tiebreaker on borderline accounts, not as a hard filter.
Email Finding Waterfall
Hunter.io → Findymail → Anymailfinder → Apollo.io→ 55–70% email coverageFounder email addresses are harder to find than corporate emails — expect a 20–30% miss rate even with a full waterfall. Hunter first (domain patterns, good for founders using [email protected] format). Findymail second (high accuracy). Anymailfinder third (good on small company domains). Apollo last (large database but lower accuracy on bootstrapped companies).
Review accounts with no email found before discarding. Some founder emails can be manually found via the company website or LinkedIn. Worth 5 minutes on your top 10 accounts.
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
Founder or CEO at a B2B company that has just posted their first Account Executive JD. They have been doing sales themselves and are about to hand it off. The window is 30 days — the time between the JD going live and the hire starting.
This is a timing play. The signal is not "founder doing sales" in the abstract. It is "founder about to stop doing sales and hand it to someone who will arrive to nothing." That specificity is what makes the message land.
Why This Audience
A founder hiring their first AE is at an inflection point. They have been doing sales themselves — closing deals through relationships, warm intros, network. Now they want to scale. The instinct is to hire someone to do what they have been doing. The problem is that what they have been doing is not repeatable infrastructure. It is personal capital.
The incoming AE will not have that capital. They will start from scratch — building lists, figuring out tooling, testing sequences — unless someone builds the infrastructure first.
The founder usually does not realize this until the rep's first 30 days are done and the pipeline report shows almost nothing. The message of this play is to help them avoid that outcome by solving it before the rep arrives.
The primary signal (first AE JD posted) is strong because it is specific and timed. Secondary signals (founder still active on LinkedIn, no existing sales hire on the team) confirm the company is genuinely in the right state.
ICP Scoring Breakdown
| Signal | Points | |--------|--------| | First AE JD posted less than 14 days ago | 45 | | First AE JD posted 14–30 days ago | 30 | | No current sales hire confirmed on LinkedIn | 20 | | Founder active on LinkedIn in last 30 days | 25 | | Company headcount 10–35 (sweet spot) | 15 | | Revenue signals $3M–$10M ARR | 10 |
Threshold: enroll at 55+. Every company in this play should be genuinely in the right window — do not stretch the signal thresholds to increase volume.
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], Saw [Company] is hiring its first Account Executive. One thing worth doing before they start: building the pipeline infrastructure so they arrive to a full list and a running sequence — not a blank CRM and a loose ICP definition. First AEs who build their own lists from scratch spend their first 60–90 days not selling. That is not what you hired them to do. We build the infrastructure in 4–6 weeks. The rep starts selling on day one. Worth a call? CJ SortedGTM
[First name], The math on a first AE without infrastructure: If they spend 40% of their time on list-building, email setup, and tooling questions — which is optimistic for a first rep at a company that has not done this before — you have hired a $130k/year researcher for the first quarter. The enrichment layer, ICP scoring, and sequence infrastructure is a 4–6 week build. After that, the rep's job is to close, not prospect. Happy to show you what that looks like for [Company]. CJ
[First name], Not going to keep following up. Either the rep is already hired and you are past this decision, or the timing is not right. If the infrastructure question is still open before the AE starts: sortedgtm.com. Stack assessment is free and usually takes 30 minutes. We will tell you honestly what to build before the hire and what can wait. Good luck with the search. 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
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 is the timing of the JD posting so important?
The window between posting the first AE JD and that person starting is the best possible moment to pitch infrastructure. Before the JD goes up, the founder is not thinking about systems yet. After the AE starts, the decision about how they will prospect has already been made by default. The JD-to-hire period is the window where the founder is thinking about what the rep will actually do on day one.
Why target the founder and not the incoming AE?
The founder controls the budget and makes the decision. The incoming AE has no authority to commission a build before they start, and may not even be hired yet. The founder is the right person to convince that the rep should arrive to infrastructure rather than build it themselves.
What if the company already has a sales tool in the stack?
If they have Apollo or ZoomInfo but no enrichment layer and no scoring model, the message is the same — they have the data spend but not the logic to use it. Adjust the opener to reference what they already have and show the missing layer, rather than starting from scratch.
How do you confirm the AE JD is genuinely their first sales hire?
Check the company's LinkedIn employee page for current employees with AE, SDR, BDR, Account Manager, or similar sales titles. If any exist, this is not a first-hire situation and the signal loses most of its weight. Only target companies where this hire would be the first person in the sales function.
What is the decision threshold after the first batch?
One booked meeting from 50 contacts is the threshold to expand. Zero replies after the full sequence means the message needs a rewrite before expanding — likely the timing is being addressed correctly but the value framing is not landing. Do not scale what has not proven it can generate replies.
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.