Most prospecting problems get blamed on copy, and most of them start earlier. The list was too broad, nobody knew why these accounts and why now, and the "sequence" was four emails spaced three days apart. Better wording won't rescue that.
A prospecting playbook fixes the parts that come before the words. It decides who you go after, what you need to know before the first touch, which channels to use in what order, and when to stop. The templates are the last layer, and they work far better on top of the first three.
This playbook covers all four. The 15 templates at the end span email, LinkedIn and phone, and each one tells you what data it depends on. If you run an SDR team and need qualification rules, handoff criteria and research automation, our sales development playbook covers that side.
Part 1: Targeting
Write the ICP as filters, not adjectives
"Mid-market SaaS companies that value data" can't be searched. An ICP is useful once every line of it maps to a field you can filter or enrich on:
Layer | Example criteria | Where the data comes from |
|---|---|---|
Firmographic | Software, 50 to 500 employees, HQ in US or UK | Company databases, enrichment by domain |
Technographic | Uses HubSpot or Salesforce, no dedicated enrichment tool | Tech-stack lookups |
Team shape | Has 3+ SDRs or a RevOps hire | People search by title at the account |
Trigger | Raised in the last 6 months, hiring sales roles, new sales leader | Funding data, job postings, job-change data |
Firmographics and technographics tell you whether an account could buy. Triggers tell you whether now is a reasonable moment to ask. You need both. A perfect-fit account with no trigger goes into a slower nurture track. An account with a strong trigger but poor fit is a distraction.
Tier your accounts
Not every account deserves the same effort. Three tiers is enough for most teams:
Tier 1 (top 20 to 50 accounts): perfect fit plus an active trigger. Manual research on each account, several contacts per account, email plus LinkedIn plus phone.
Tier 2 (a few hundred accounts): good fit, trigger present or likely. Research is semi-automated: enriched fields plus one AI-generated line you check before sending. Email and LinkedIn.
Tier 3 (everyone else who fits): good fit, no trigger yet. Light personalization based on segment, email only, and a watch for triggers that would move them up.
Accounts should move between tiers. A Tier 3 company that announces a funding round this week belongs in Tier 1 or 2 next week. That movement is the core of signal-based prospecting, and it only works if someone (or something) is checking for signals on a schedule.
Pick contacts by role in the deal
For each account, map two or three people rather than one:
The owner of the problem. Usually a director or head of the function your product serves.
The economic buyer. A VP or C-level who signs.
A user or champion. Someone who feels the pain daily and will tell you whether your pitch is real.
Multi-threading from the first touch means one ignored inbox doesn't end the account.
Part 2: Research
The "why you, why now" line
Before any template, every Tier 1 and Tier 2 contact needs one sentence that answers: why am I contacting this person, at this company, this month? If you can't write it, the contact isn't ready.
Good ones reference something specific and checkable:
"You opened four SDR roles in London in the last month."
"You moved from Head of Growth at a Series A company to VP Marketing here in June."
"Your pricing page now lists an enterprise plan, which suggests a move upmarket."
Weak ones restate the ICP: "As a fast-growing SaaS company..."
What to collect per tier
Field | Tier 1 | Tier 2 | Tier 3 |
|---|---|---|---|
Verified work email | Yes | Yes | Yes |
Mobile or direct dial | Yes | If available | No |
LinkedIn URL | Yes | Yes | Optional |
Trigger and date | Yes | Yes | No |
"Why now" line | Written by hand | AI draft, human checked | Segment-level |
Recent posts or talks | Yes | Optional | No |
Tech stack | Yes | Yes | Yes |
Contact data is where coverage breaks. Any single provider will miss part of your list, so run emails and phones through a waterfall of providers and verify emails before they reach a sequence.
Use AI for first drafts of research, not for facts you haven't checked
Language models are good at reading a company website and summarizing what a company sells and to whom. They're less reliable on dates, funding amounts and who holds which title. A prompt that works well for per-row research:
Asking for a source URL and allowing "none found" cuts down on invented triggers. Review the output for Tier 1 and 2 before it goes into a message.
Part 3: Sequence Design
A three-week, multi-channel sequence
This is a starting structure for Tier 1 and Tier 2 contacts. Adjust spacing to your market, but keep the logic: open with the strongest reason, change channels instead of repeating yourself, and end cleanly.
Day | Channel | Step | Template |
|---|---|---|---|
1 | View profile, send connection request | L1 | |
1 | Trigger-based opener | E1, E2 or E3 | |
3 | Phone | Call, leave voicemail if no answer (Tier 1) | P1, P2 |
5 | Reply in thread with a new angle | E4 | |
8 | Message after connection is accepted | L2 | |
10 | Right-person ask to a second contact | E5 | |
14 | Phone | Second call attempt (Tier 1) | P1 |
17 | Comment on a recent post, then message | L3 | |
21 | Breakup | E6 |
Rules that matter more than the exact days:
Stop every channel on any reply, including "not now." Route it to a human.
Don't call without a reason in the first ten seconds. If there's no trigger and no mobile number, drop phone steps for that contact.
One ask per message. A reply, a referral or a yes/no, never all three.
Keep threads. Follow-ups sent as replies to your first email keep context in front of the reader.
Tier 3 gets a shorter version: three or four emails over two to three weeks, no calls.
Part 4: The 15 Templates
Placeholders are in brackets. Each template lists the data it needs, because a template missing its data is where generic outreach comes from.
E1. Funding trigger
Needs: funding round and date, headcount, one hiring or growth detail.
Subject: after the [round type]
Hi [First Name], congrats on the [round type] in [month]. Companies around [headcount] people usually start hiring [function] right after a raise, and I can see [Company] already has [number] [role] roles open.
We help [function] teams at this stage [specific outcome]. Worth a short call to see if that applies to [Company]?
Skip the congratulations if the round is more than three months old. It reads as automated.
E2. New leader in the role
Needs: start date in the role, previous company, their team's current open roles or tools.
Subject: first quarter at [Company]
Hi [First Name], saw you joined [Company] from [Previous Company] in [month]. New [title]s tend to spend the first quarter deciding what to keep and what to replace, and [problem area] usually comes up early.
If it's on your list, I can show how [similar company] handled it in about 15 minutes. If not, no worries.
E3. Hiring signal
Needs: specific open roles, location, posting date.
Subject: your [role] openings
Hi [First Name], [Company] has [number] [role] openings posted in [location]. Growing a [team] that fast usually means [consequence, such as ramp time or tooling gaps] becomes the bottleneck.
We help teams in that spot [outcome]. Is that a problem you're dealing with right now?
E4. Follow-up with a new angle
Needs: one relevant proof point you can actually stand behind (a named customer who agreed to be referenced, a public case study, or a specific product capability).
Hi [First Name], one more thought on [topic from E1 to E3]. [Customer or type of company] had the same [problem] and [what they changed]. The piece they found most useful was [specific capability].
Happy to send the details if that's relevant.
Add information in follow-ups. "Just bumping this" gives the reader nothing new to respond to.
E5. Right-person ask (to a second contact)
Needs: second contact's name and role, a one-line summary of the problem.
Subject: who owns [problem area]?
Hi [First Name], I reached out to [Contact 1] about [problem area] but may have the wrong person. Is that something you or someone on your team looks after?
E6. Breakup
Needs: nothing beyond the thread.
Subject: closing the loop
Hi [First Name], I haven't heard back, so I'll assume [problem area] isn't a priority right now. If that changes, just reply to this thread. And if someone else at [Company] owns it, a name would be appreciated.
Keep connection notes short. Personalized note length and the number of notes you can send depend on your account type, so check LinkedIn's current limits before you build a sequence around them.
L1. Connection request
Needs: one shared context point.
Hi [First Name], I work with [function] teams at [industry] companies and saw your [post/talk/role change] on [topic]. Would be good to connect.
No pitch in the request. The goal is acceptance.
L2. Message after connecting
Needs: the trigger from your research.
Thanks for connecting, [First Name]. I noticed [Company] is [trigger]. When teams hit that point, [problem] tends to show up. Is that on your radar, or am I early?
L3. Comment then message
Needs: a recent post by the prospect.
Leave a genuine comment on their post first, one that adds a point or asks a real question. A day or two later:
Enjoyed your post on [topic], especially [specific point]. It connects to something we see a lot at [type of company]: [short observation]. Curious how you're handling [related problem] at [Company].
L4. Message to an existing connection you haven't spoken to
Needs: a trigger or a change in their role.
Hi [First Name], it's been a while since we connected. Congrats on [new role/launch/milestone]. I'm working on [problem area] with a few [industry] teams and thought of you. Open to comparing notes?
Phone
P1. Cold call opener
Needs: direct dial or mobile, the trigger.
Hi [First Name], it's [Your Name] from [Company]. I'm calling because [trigger]. That usually means [problem] shows up soon. Do you have 30 seconds for me to explain why I called, and then you can tell me if it's relevant?
Lead with the reason, then ask for a short slot. If they say no, ask when a better time is, or whether an email is easier.
P2. Voicemail
Needs: the same trigger, your email subject line.
Hi [First Name], [Your Name] from [Company]. I saw [trigger] and had an idea about [problem]. I'm sending you an email with the subject "[subject line]" so you don't need to call back. Thanks.
Keep it short and tie it to the email so the two touches reinforce each other.
P3. Gatekeeper or switchboard
Needs: the contact's name and role.
Hi, could you help me? I'm trying to reach [First Name] [Last Name], who I believe leads [function]. Is that right, or is there someone else who handles [problem area]?
Asking for help and confirming the role gets further than pretending you've spoken before.
Warm and inbound follow-up
W1. High-intent content engagement
Needs: what they downloaded or attended, company enrichment, a relevant next resource.
Subject: the [content title] you downloaded
Hi [First Name], thanks for grabbing [content title]. Teams at [company type] usually download it when they're working on [problem]. If that's the case at [Company], I can walk you through how [peer type] set theirs up. If you were just researching, here's [related resource] as a next step.
Reply fast. A lead that engaged this week is warmer than one you get back to next month.
W2. Event follow-up
Needs: the event name, what you talked about (or the session they attended), verified email.
Subject: following up from [Event]
Hi [First Name], good to meet you at [Event]. You mentioned [specific problem or comment]. I said I'd send over [resource or example], so here it is: [link].
If it's useful, I'm happy to go through how it would apply at [Company] next week.
Send it within a couple of days, and reference the actual conversation. If you only scanned a badge, say which session they attended instead of pretending you talked.
Part 5: Measuring and Improving
Track the funnel per template and per tier, not just in aggregate:
Reply rate and positive reply rate (replies that lead to a conversation). Positive replies are the number to optimize. Raw reply rate rises when you annoy people too.
Meetings booked per 100 contacts reached, split by tier. If Tier 1 doesn't clearly beat Tier 3, your research isn't adding enough to justify its cost.
Bounce rate. If it creeps up, fix list quality before changing copy.
Test one variable at a time (the opener, the trigger type, the channel order) and give each variant enough contacts to see a real difference. A few dozen sends won't tell you much. For writing-level fixes, our cold email copywriting rules go deeper on subject lines, length and calls to action.
Running the Playbook in Databar
The data work in Parts 1 and 2 is where most teams lose time, and it's what Databar is built for. In one table you can pull target accounts, enrich firmographics and tech stack from 160+ data providers, find and verify work emails and phone numbers with waterfalls, and run the AI Researcher on each row with a prompt like the one above to draft the "why now" line. Scheduled runs keep trigger fields fresh so accounts can move between tiers, and the finished list syncs to HubSpot or Salesforce for sequencing.
Paid plans start at $99/month, and you only pay for lookups that return data. You can start a 14-day trial or book a walkthrough with the founders to see it on your own ICP.
FAQ
What should a sales prospecting playbook include?
Four parts: an ICP written as searchable criteria and account tiers, a research standard for each tier, a multi-channel sequence with stop rules, and message templates tied to specific triggers. Add the metrics you'll review and how often.
How many touches should a prospecting sequence have?
For high-value accounts, eight or nine touches over about three weeks across email, LinkedIn and phone is a common starting point. Lower tiers get three or four emails. The number matters less than whether each touch adds something new.
Should I use the same template for every prospect?
No. Pick templates by trigger. A funding-round email sent to a company that hasn't raised reads as automated. If a contact has no trigger, use a segment-level message or move them to a slower track until one appears.
How do I personalize outreach at scale without it sounding generic?
Personalize the reason for reaching out, not the small talk. One accurate, specific trigger beats three lines about someone's alma mater. Automate the data gathering and first drafts, and keep a human check on Tier 1 and 2 messages.
Recent articles
See all








