Founding SDR Playbook
The founding SDR outbound playbook for the first 30 days.
A founding SDR should not begin with a blank CRM, a vague ICP, or a giant cold list. The first 30 days should be built around a narrow market, a ranked account queue, clear trigger reasons, verified contacts, and a handoff system the founder can inspect.
01
The first SDR needs operating context, not just leads
Most early SDR hires fail because the company gives them a quota before giving them an operating system. A founding SDR needs to know exactly which companies matter, why those companies matter now, who to contact, what evidence supports the outreach, and what happens after someone replies.
- Define the buyer role, company stage, geography, team size, and exclusion rules.
- Write the pain hypothesis in plain language so the SDR can explain it.
- Separate must-have accounts from experimental accounts.
- Create a daily review habit for positive replies, weak replies, bounces, and bad-fit accounts.
02
Build the first 500 accounts from signals
The first lead list should be smaller and sharper than a database export. Good signals include hiring for sales or RevOps roles, launching a new product, opening a region, raising funding, changing tools, publishing a pain-heavy post, or showing category activity that connects to the offer.
- Capture the source URL so the SDR can trust the reason-to-reach-out.
- Score each account for fit, trigger strength, recency, and buyer clarity.
- Keep backup accounts separate from high-confidence launch accounts.
- Review a small sample before sourcing hundreds of similar records.
03
Turn research into a rep-ready workflow
The workflow matters as much as the data. A useful SDR system has columns for status, owner, trigger, source, contact confidence, sequence angle, last touch, reply label, and next action. This makes the work inspectable instead of hidden inside random tabs.
- Use clear statuses such as research, verify, ready, sequenced, replied, bounced, and not now.
- Write three sequence angles before loading contacts into a sender.
- Route interested replies to the founder or AE with context attached.
- Archive bad-fit accounts so the team learns which assumptions were wrong.
Checklist
Use this before a launch batch goes live.
- 01ICP is narrow enough that weak accounts are easy to reject.
- 02Every launch account has a trigger note and source.
- 03Every contact has a role match and verification status.
- 04The first sequence has a reason-to-reach-out in the opening line.
- 05Replies, bounces, and not-now accounts have routing rules.
- 06The founder can review the dashboard without asking the SDR for context.
FAQ
Direct answers for search and buyers.
What should a founding SDR do in the first week?
The first week should focus on learning the ICP, reviewing the account queue, testing a small batch of trigger-based outreach, and reporting what replies reveal about buyer fit.
How many leads should a first SDR receive?
A focused first queue of 100 to 500 high-quality accounts is usually better than thousands of weak records, especially when the sales motion is still being proven.
What does ClickChain build for this?
ClickChain builds the ICP logic, first lead queue, trigger research, verification workflow, sequence angles, reply routing, and dashboard for the founding SDR launch.
Next step
Turn this into a 10-lead proof sample.
Send the market, buyer, and offer. ClickChain can return a small proof sample before a larger founding SDR launch kit.