Most follow-up programs get longer over time for the wrong reason. Someone looks at a sequence that booked a few meetings, notices that a handful of replies arrived on touch five or six, and concludes that the sequence should keep going. The next quarter, the same sequence has nine steps. The quarter after that, twelve. Opens still happen. Meetings do not. The team assumes the market got harder and adds another touch.
I have watched this pattern at two SaaS companies where I help design the follow-up systems. The longer drip almost always looks productive in the tool: more sends, more opens, more "engaged" contacts sitting in a stage that never turns into a call. The shorter sequence looks thin on paper. Then you compare meetings booked per contact entered, and the thin one wins.
What a long drip is actually doing
A long drip is often doing one of three jobs that nobody named out loud.
The first job is emotional cover. Reps feel better when the CRM shows that a prospect is still "in sequence." Silence is uncomfortable. A twelve-step drip turns silence into a managed state. That comfort belongs to the seller, not the buyer.
The second job is metric theater. Sequence tools reward activity. More steps produce more events. Dashboards fill up. Meetings booked per contacted account is harder to watch every week, so it gets less airtime.
The third job is delayed honesty. A long drip postpones the moment when you admit the contact is cold, the ICP fit was weak, or the first three messages failed. Ending a sequence feels like losing. Extending it feels like diligence.
None of those jobs help the buyer. Buyers notice cadence length before they notice clever subject lines. After the third or fourth near-identical check-in, they stop reading. After the sixth, some of them mark you as the kind of vendor who cannot tell when a conversation is over.
A concrete comparison from renewal and expansion work
Customer success teams hit this same pattern during expansion. Take a mid-market account where the champion went quiet after an initial "we might add seats next quarter" note. One playbook I inherited used eight touches over ten weeks: reminder, soft bump, case study, soft bump, webinar invite, soft bump, end-of-quarter nudge, breakup email. It looked thorough. The booked meeting rate on that path was under two percent of contacts entered.
We rebuilt it as a four-touch path stretched over three weeks, then a pause with a signal watch. Touch one restated the expansion idea in one short paragraph and asked for a timing answer, not a meeting. Touch two, four days later, offered a one-page usage summary the champion could forward internally. Touch three, a week after that, asked whether the timing had slipped or the idea was dead. Touch four, five days later, closed the loop and named the condition under which we would come back (usage crossing a threshold, a new hire in their ops role, or a renewal window).
Meetings booked per contact roughly tripled. Reply quality improved more than that. People who were not ready said so. People who were ready picked a time. The long drip had been training both sides to treat expansion as background noise.
Sales outbound shows the same shape. A seven-step cold sequence into product-led trial accounts that never activated often underperforms a three-step sequence that asks one clear question, offers one concrete observation from their trial behavior, then stops.
Why shorter wins more often than people expect
Attention is the scarce part. Every extra touch spends a little of the goodwill you have not earned yet. Early touches can create a reason to reply. Late touches usually repeat the ask with thinner novelty. By the time you reach "just circling back," the message has almost no new information. The buyer already knows what you want.
Shorter sequences also force better first messages. If you only get three or four shots, you cannot hide a vague opener behind a long drip. You write the useful observation first. You ask a question the recipient can answer in one sentence. You attach or link something that stands on its own. Length discipline improves content quality because there is nowhere to bury a weak start.
There is also a measurement advantage. A short sequence ends. Ending creates a clean cohort: of one hundred contacts who entered this path last month, eleven booked, twenty-three replied with timing, and the rest went to a signal waitlist. A twelve-step drip blurs those outcomes across ten weeks.
What "shorter" should mean in practice
Shorter does not mean abrupt or rude. It means every touch has a job, and the sequence stops when those jobs are done.
For cold or cold-ish outbound into a named account list, three touches over roughly two weeks is usually enough before you switch to signal-based watching. For post-demo silence, four touches over two to three weeks is plenty if the messages change job each time: confirm the decision path, answer the open objection, offer a lighter next step, then close the loop. For expansion inside an existing account, three to five touches over a few weeks beats a quarter-long drip that nobody can defend in a QBR.
The content matters more than the count, but count still matters. If touch three and touch seven say the same thing in different clothes, the later ones are not follow-up. They are repetition with a calendar.
A useful test before you add a step: write the new email, then ask what new fact, offer, or question it introduces that the previous emails did not. If the honest answer is "another reminder," delete the step. If the honest answer is "a different stakeholder angle" or "a specific artifact they can use internally," keep it and make that the whole point of the message.
The pause is part of the system
The part people skip when they shorten a sequence is the pause design. Stopping is not the same as abandoning the account. After the last touch, the contact should land in a state that waits for signal: pricing page visits, feature usage spikes, a new contact joining the thread, a support ticket that implies budget pain, a hiring post that matches your ICP trigger. That is when the next email earns the right to exist.
Teams that fear shorter sequences usually fear the empty calendar after the last send. Give that fear a job. Build the watch list. Decide which signals reopen a conversation. Decide who owns the reopen. Write the reopen email in advance so nobody panics into a "just checking in" note three months later.
I have seen CSMs keep ghosted expansion accounts "warm" with monthly newsletter-style notes that nobody asked for. The open rates look fine. The meeting rates do not. A clean close plus a signal watch produces more real conversations than those monthly drips, because the next message arrives with a reason attached.
How to run the experiment without a religious fight
If your org is attached to a long drip, do not argue philosophy in a Slack thread. Run a split on a real segment for four to six weeks. Pick one ICP slice. Send half the contacts through the existing long path. Send the other half through a short path with a defined pause. Hold the offer and the first-message quality as steady as you can. Compare meetings booked, positive replies, unsubscribe or spam complaints, and time-to-meeting. Ignore vanity opens unless they correlate with those outcomes.
In every case where I have seen this run honestly, the short path either wins on meetings or ties on meetings while cutting send volume enough that deliverability and rep attention both improve. The long path rarely wins once you stop counting "still in sequence" as progress.
There is one exception worth naming. Complex enterprise deals with many stakeholders sometimes need a longer communication plan. That plan is still not a drip of identical bumps. It is a set of distinct messages aimed at distinct people, with distinct artifacts, timed to their evaluation process. Length without distinct jobs is still waste.
A practical default
If you need a default while you redesign, use this: three to five touches, two to three weeks, each touch changes the job, then pause into signal watch. Write the close-the-loop email as carefully as the opener. Tell the person what would bring you back. Mean it.
Longer sequences are not evil. They are usually lazy design dressed up as persistence. Persistence is useful when the message keeps earning attention. Persistence without new information is just a longer way to be ignored. When the shorter sequence books more meetings, it is rarely because buyers love brevity as a lifestyle. It is because the short sequence made the team say the useful thing sooner, stop sooner, and come back only when something real changed.