A sales sequence is the plan that turns a cold list into a predictable meeting rate. This guide walks through the eight moves that separate a working outbound program from a batch-and-blast list burn: pick a touch count and spacing, map each touch to a channel, draft a hook pattern per touch, write channel-appropriate copy, set clear exit criteria, instrument reply tracking, pilot with a small cohort, and iterate on the signal you collect each week.
Time: 2-3 hours
A sequence is a structure, not a stack of emails. Decide the shape first. For most B2B outbound, five to seven touches over ten to fourteen days is the working range: enough coverage to catch busy prospects, short enough that the thread stays warm and compliance windows stay clean. Space early touches two to three days apart, stretch later touches to four or five days, and anchor the first touch to a workday morning in the recipient's time zone. Lock the shape in a shared doc so every rep running the sequence runs the same shape, and so your reply-rate numbers compare across cohorts instead of across one-off experiments.
A multi-channel sequence outperforms a single-channel one, but only when each channel has a defined job. Treat email as the backbone and layer calls and social in to reinforce the thread. A common working mix: email on touches 1, 3, and 5; a call on touch 2 or 4; a light social touch (profile view, thoughtful comment, connection request with context) between email touches. Do not stack a call and a cold connection request on the same day; the goal is to raise familiarity across days, not to crowd a single afternoon. Honor local call-time rules and respect any do-not-contact flags on the account.
Each touch needs a reason to exist that the prospect can feel in the first two seconds. Write the hook before you write the body. Touch 1 opens on a trigger or a role-level insight. Touch 2 reframes the problem from a new angle, never "just following up." Touch 3 adds a verifiable proof point and a specific question. Touch 4 offers a resource with no ask attached. Touch 5 is a short break-up that leaves the door open. Document each hook as a one-sentence promise to the reader; if you cannot write that sentence, the touch is not ready to send and should be cut from the sequence.
Each channel has its own physics. Email rewards short, scannable paragraphs, a one-line qualification, and a soft CTA. Voicemail rewards 25 to 35 seconds with the reason for the call stated in the first sentence. Social messages reward brevity, a reference to something public the prospect posted or shipped, and no pitch at all. Do not reuse the same paragraph across channels; the reader will notice, and the second impression gets worse, not better. Keep every message under the length a phone screen can hold without scrolling, and read every draft out loud before you ship it.
A sequence that cannot exit is a sequence that burns the list. Write the exit rules into the spec before anyone presses send. Replies exit the sequence immediately and route to a human. Out-of-office responses pause the sequence until the return date plus one day. 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 the sequence and triggers the next-stage playbook. Document who owns each exit so a reply does not sit for three days while the sequence keeps firing.
You cannot improve what you do not measure, and you cannot measure what the CRM is not capturing. Instrument the sequence so every open, reply, bounce, opt-out, call connect, voicemail, and social touch writes back to the account and contact timeline. Classify replies into positive, neutral, referral, and negative so the top-line reply rate does not hide a quality problem. Track per-touch reply rate, per-channel reply rate, time-to-reply, and cohort-level meeting rate from first touch to meeting booked. Review the numbers weekly on a fixed day; a dashboard that no one looks at is not instrumentation, it is decoration.
A new sequence is a hypothesis, not a program. Run the first version against ten named accounts from the ICP cohort, with one rep sending, before you hand it to the full team. Ten accounts is enough to catch broken merge fields, wrong send times, bad hooks, and compliance misses, and small enough that a bad pilot does not scorch the segment. Hold the pilot for a full cycle (ten to fourteen days) so late touches get a chance to land. At the end of the pilot, review the numbers against the exit criteria and decide: ship, revise, or kill. Do not scale a sequence whose pilot came in flat.
Outbound is a weekly discipline, not a quarterly project. Hold a standing review each week to look at reply rate per touch, reply quality, meeting rate, and any compliance or deliverability signals from the week. Pick one variable to change for the next cohort (a hook, a send window, a channel order, a CTA) and leave everything else the same so the delta is readable. Keep a running log of what changed and what the number did, with the cohort size next to each entry so small-sample noise is visible. Over a quarter, this is how a sequence goes from average to repeatable.
Five to seven touches over ten to fourteen days is the working range for most B2B outbound. Fewer and you leave meetings on the table from prospects who were busy on touch 1; more and reply rates fall off while unsubscribe and complaint rates climb. Build in a clean break-up touch and honor it instead of restarting the sequence two weeks later.
Space early touches two to three days apart and later touches four to five days apart. The first touch should land in a workday morning in the recipient's time zone. Avoid Friday afternoon and pre-9am Monday sends. The goal is a thread the prospect can follow without feeling crowded, and a shape your reply-rate numbers can compare against cleanly from one cohort to the next.
Email as the backbone, one or two calls spaced between email touches, and a light social touch (profile view, thoughtful comment, connection request with context) to raise familiarity. The mix only works when each channel has a defined job. Do not stack a call and a cold connection request on the same day; raise familiarity across days instead of crowding a single afternoon.
Immediately on any reply, opt-out, hard bounce, or meeting booked. Pause on out-of-office until the return date plus one day. Write exit rules into the sequence spec before the first send, and route replies to a human within one business hour. A sequence that cannot exit is a sequence that burns the list and earns spam complaints from prospects who were actually interested.
Track per-touch reply rate, per-channel reply rate, reply quality (positive, neutral, referral, negative), time to reply, and cohort meeting rate from first touch to meeting held. Review on a fixed day each week with the same owners. If reply classification lives only in a rep's head, the top-line number hides a quality problem; put the four buckets on the record so the weekly review has 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. A full rewrite every two weeks produces no trend line, only noise. Keep a changelog with cohort size, the change made, and the reply-rate delta in one place, and let the running record decide which levers deserve more weight.
Strkr brings sequences, calls, social touches, 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.
