A prospecting sequence is the plan that turns a cold list of named accounts into booked meetings on the calendar. This guide walks the eight moves that separate a program from a batch-and-blast: pin the goal to meetings held, pick a touch count and spacing, map the channels, draft channel-specific copy, write a hook for every touch, set exit criteria the sequence actually honors, launch a 25-account pilot, and iterate on one lever per week until the reply rate holds.
Time: 3-4 hours per sequence
Prospecting sequences get judged on the wrong number more often than any other sales motion. Reply rate feels great in a dashboard but means almost nothing on its own; a sequence that generates lots of "not interested" replies is working, in the sense that it is being read, and failing, in the sense that the pipeline stays empty. Write the goal into the sequence spec as meetings held, not replies, not opens, not sends. State the target explicitly: for a 25-account pilot, two to four held meetings is a working outcome, one or zero means the ICP, the hooks, or the list quality needs work before the sequence does.
A prospecting sequence is a structure, not a stack of emails. Decide the shape first. For most cold B2B outbound, six to eight touches across roughly fifteen days is the working range: enough coverage to catch busy prospects across two work weeks, short enough to keep the thread warm and compliance windows clean. Space the first three touches two to three days apart, stretch the back half to three or four days, and anchor every send to a workday morning in the prospect's time zone. Lock the shape in a shared doc so every rep runs the same sequence and the reply-rate numbers compare across cohorts instead of across one-off rep habits.
A multi-channel sequence outperforms a single-channel one, but only when each channel has a defined job. Treat email as the backbone that carries the written record of the thread. Layer calls in to interrupt the inbox pattern, and use social (LinkedIn and short video) to raise familiarity between email touches. A working mix for seven touches: email on touches 1, 3, 5, and 7; a call on touch 2 and 4; a social touch (profile view and thoughtful comment, then a connection request with context) on touch 6. Record a 30 to 60 second personalized video for one high-value touch per account. Never stack a cold call and a cold connection request on the same day.
Each channel has its own physics and reusing one message across three of them is the fastest way to look automated. Email rewards short, scannable paragraphs, a single qualifier, and a soft CTA on its own line. Voicemails reward 25 to 35 seconds with the reason for the call stated in sentence one and no stacked claims. LinkedIn rewards brevity and a reference to something public the prospect posted or shipped. Personal video rewards a first frame that shows the prospect's name or company on screen and a clear ask inside sixty seconds. Address the reader as <FirstName> at <Company>, read every draft out loud before you ship it, and cut any sentence that makes you breathe wrong.
Every touch needs a reason to exist that the reader can feel in the first two seconds, and "just following up" is not one of them. Write the hook before you write the body. Touch 1 opens on a trigger event or a role-level outcome. Touch 2 reframes the problem from a new angle. Touch 3 adds a verifiable proof point and a specific question. Touch 4 pivots to a resource worth the open on its own (teardown, benchmark, checklist). Touch 5 drops a short peer-named insight. Touch 6 is a social touch that references something public. Touch 7 is a clean break-up that leaves the door open. If a hook will not fit in a one-sentence promise to the reader, the touch is not ready to send and should be cut from the sequence.
A prospecting sequence that cannot exit is a sequence that burns the list and earns spam complaints from prospects who were actually interested. Write exit rules into the spec before anyone presses send. Any reply pauses the sequence immediately and routes to a human within one business hour. Out-of-office responses pause until the return date plus one day, then resume at the next touch. Opt-outs exit permanently and write back to the suppression list across every channel and sender in the workspace. Hard bounces exit and flag the record for list hygiene. Meeting-booked exits and triggers the discovery playbook. Name the owner for each exit so a positive reply does not sit for three days while touch 4 keeps firing on autopilot.
A new prospecting sequence is a hypothesis, not a program. Run the first version against 25 named accounts drawn from a single ICP segment, with one rep sending every touch, before the sequence ships to the full team. Twenty-five is enough to catch broken merge fields, bad hooks, wrong send times, and compliance misses, and small enough that a flat pilot does not scorch the segment or the sending domain. Hold the pilot for the full window (fifteen days plus the exit tail) so late touches get a chance to land. At the end of the pilot, compare the number of held meetings against the goal written in step one, and decide: ship, revise one lever, or kill.
Prospecting is a weekly discipline, not a quarterly project. Hold a fixed-day weekly review that looks at per-touch open rate (as a deliverability signal, not a success metric), per-touch and per-channel reply rate, reply quality classified into positive, neutral, referral, and negative, cohort meeting rate from first touch to meeting held, and any deliverability or compliance signals from the week. Change one variable for the next 25-account cohort (a hook, a send window, a channel order, a CTA) and leave everything else alone so the delta is readable. Keep a changelog with cohort size, the change made, and the reply and meeting delta, so small-sample noise is visible and the running record decides which levers deserve more weight.
Six to eight touches across roughly fifteen days is the working range for most cold B2B outbound. Fewer touches and you leave meetings on the table from prospects who were busy on touch 1; more touches and reply rates fall off while unsubscribe and complaint rates climb. Build a clean break-up touch at the end and honor it instead of restarting the sequence silently two weeks later.
Email as the backbone, one or two cold calls spaced between email touches, and a light social touch (profile view, thoughtful comment, then a connection request with context) to raise familiarity. Add one 30 to 60 second personal video on a high-value touch per account. The mix only works when each channel has a defined job; never stack a cold call and a cold connection request on the same day.
Open on a trigger event or a role-level outcome specific to <FirstName> at <Company>, keep touch 1 under 125 words, and finish with one soft CTA on its own line. Cite one proof point rather than listing three. Read the draft out loud, cut any sentence that makes you breathe wrong, and let the hook (not the pitch) carry the open. Reuse the hook pattern across accounts; do not reuse the hook text verbatim.
Immediately on any reply, opt-out, hard bounce, or meeting booked. Pause on out-of-office until the return date plus one day, then resume at the next touch. Write exit rules into the sequence spec before touch 1 ships, and route positive replies to a human within one business hour. A sequence that cannot exit is a sequence that burns the list and earns complaints from prospects who were actually interested.
Track held meetings per 25-account cohort as the primary goal, with per-touch and per-channel reply rate, reply quality classified into positive, neutral, referral, and negative, and open rate as a deliverability signal (not a success metric). Review on a fixed day each week with the same owners. If reply classification lives only in a rep's head, the top-line reply rate hides a quality problem and the weekly review has no signal to work with.
Change one variable per weekly cohort (a hook, a send window, a channel order, a CTA) and keep the rest stable so the delta is attributable, not confounded. A full rewrite every two weeks produces no trend line, only noise. Keep a changelog with cohort size, the change made, and the reply and meeting delta in one place, and let the running record decide which levers deserve more weight next week.
Strkr brings cold emails, calls, LinkedIn touches, video sends, replies, and exit rules into one timeline so reps can run the shape, read the signal, and iterate on the lever that matters this week.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
