A sales sequence is a planned series of contacts with one person over a set period. Most are built as a series of emails that say the same thing in slightly different words, which is why most get ignored.
The structural problem is easy to describe. A sequence that repeats a pitch gives the reader nothing new to react to, so each message is strictly less interesting than the last. A sequence that carries something different each time keeps earning the next open. The difference is not tone or subject lines. It is whether the content changes.
How long, and how many
The honest answer is that it depends on deal size and how long your buyers take to decide, but some shapes hold up.
For a considered B2B purchase, somewhere around five to eight touches over three to four weeks is a reasonable starting point. Fewer than four and you are stopping before most replies arrive. More than about eight in a month and you are a nuisance regardless of how good each message is.
The spacing should widen as it goes. Two or three days between the first touches, then five, then a week or more. Tight spacing at the start matches the window where the trigger that prompted you is still relevant. Wide spacing later reflects that you are now waiting for their circumstances to change rather than for them to read more carefully.
Mix the channels. A sequence that is only email is easier to ignore than one that includes a call attempt and, where appropriate, a message on another platform. Each channel has a different attention cost and a different inbox.
What each touch should carry
This is the part that separates sequences that work from sequences that annoy. Each touch needs its own reason to exist.
One: the trigger. Why you are contacting this person now. A specific observation about their business beats any general claim about yours. If you cannot name a reason, you are not ready to start the sequence.
Two: one concrete thing. A number, a specific outcome, something you have seen in businesses like theirs. Not a feature list and not a case study link. One fact, short.
Three: something useful regardless. A benchmark, a short piece of analysis, a relevant change in their industry. This touch should be worth reading even if they never buy. It is also the one most teams skip, and it is where a decent share of replies come from.
Four: a different angle. If the first three were about one problem, this one addresses a different one. People ignore messages because the problem you named is not their problem, not necessarily because they do not have problems.
Five: the close. Short, direct, and it removes pressure rather than adding it. "I will stop here. If this is not the right time, say so and I will come back in six months." This message reliably outperforms its position in the sequence, because it is the only one that does not ask for anything.
The rules that keep it out of the junk folder
Deliverability is a technical subject and most of it is outside the scope of a sequence design, but a few things are directly in your control.
Volume per sender matters more than total volume. A large number of messages from one address behaves differently from the same number spread across a team.
Replies are the strongest positive signal you can generate. A sequence that provokes replies, even negative ones, does better over time than one that generates silence. This is another argument for touches that are worth reading.
Make unsubscribing easy and honor it immediately. Beyond the legal position, which varies by jurisdiction and is worth checking for the markets you send to, a person who cannot get off your list will mark you as spam, and that signal is far more damaging than losing the contact.
Stop the sequence on any reply. Obvious, routinely broken, and the most common way a sequence does real damage. Someone replies "yes, interested, call me Thursday" and receives touch four on Wednesday. It happens constantly, and the cause is that the reply handling is manual.
Personalization that is worth the time
There is a real trade-off here. Fully personalized messages convert better per send and take far longer to write. Fully templated ones scale and convert poorly.
The practical middle is to personalize the first line and the trigger, and template the rest. The opening needs to prove this message was written for them. The explanation of what you do can be the same for everyone, because it is the same for everyone.
What does not work is inserting their company name into a generic sentence. Readers have been trained to spot merge fields, and a visible one actively signals that nothing else was personalized either.
Where sequences break operationally
The design is usually not what fails. Four operational problems account for most of it.
Replies do not stop the sequence. As above. If reply detection is manual, it will be missed.
The same person is in two sequences. They get touches from two reps about two things in the same week, which reads as a company that does not know what it is doing.
The trigger is stale. A sequence written around an event that happened four months ago is no longer relevant, and the first touch gives that away immediately.
Nobody retires the sequence. It keeps running against a list that no longer matches the market it was written for, and performance drifts down slowly enough that nobody notices.
All four are plumbing. They are solved by connecting the sequence to your CRM properly: reply detection that updates the record, a check that prevents double enrollment, and an expiry on triggers.
Building it in what you already run
Sequence tools are a crowded market and most of them do the scheduling well. What they often do not do well is the connection to your own data, which is where the four failures above live.
If your triggers come from your CRM, your reply handling needs to update your CRM, and your exclusion rules depend on what your CRM knows, then the sequence logic is better built close to that data than rented above it. That means your existing stack doing the work, rather than another subscription with another integration to maintain.
That is the kind of build Regna Operations does: in your own accounts, on the tools you already pay for, documented, twelve month warranty, nothing to rent. The Revenue Roadmap is the way to find out whether this is the piece worth building first, or whether something duller and more valuable is sitting further up your funnel.
Common questions
How many touches should a sales sequence have?
Around five to eight over three to four weeks for a considered B2B purchase, with spacing that widens as it goes. Most replies arrive after the point where the average sequence has already stopped.
What makes a sales sequence feel like spam?
Repeating the same pitch in different words. If each touch carries something new, a trigger, a concrete fact, something useful regardless of whether they buy, a different angle, it reads as persistence. If they all say the same thing, it reads as volume.
Should sequences be automated or sent manually?
Automate the scheduling and the exclusion rules, and write the opening line yourself. The failures that do real damage, such as a sequence continuing after someone replies, are almost always caused by manual handling of something that should be automatic.
How do you know if a sequence is working?
Reply rate, including negative replies, is more useful than open rate. Silence is the failure mode to worry about: it usually means the trigger was not relevant to the reader rather than that the writing was poor.
