Drip Campaign: When a Fixed Sequence Is the Right Tool

A drip is a conversation with someone whose situation is changing while your sequence is not.

That one sentence explains most drip failures. The copy was fine. The sequence simply kept talking after the reader had bought, hired someone else, or stopped caring.

So this is not a template dump. It is the judgement call. For platforms, trigger types and stack choices, start with our guide to email marketing automation — a drip is one artefact you build with those tools, not the whole capability.

What a drip campaign actually is

A drip campaign is a set of emails written in advance, ordered deliberately, and released on a clock rather than on behaviour. Everyone who enters walks the same path with the same waits.

Four things have to be true before it is a drip:

• Fixed order. Email three always follows email two.
• Time-based gaps. "Three days later", not "after they visit the pricing page".
• Written before anyone enters. Nobody is drafting email four this week.
• One entry point. A single thing puts people in — a form, a tag, a list import.

Drop any one and you have built a worse version of a behavioural programme. The discipline of a drip is its constraint: you script it because the situation is stable enough to script.

Drip vs triggered: the distinction nobody explains cleanly

A drip runs on elapsed time from one entry event. A triggered email runs on the event itself, every time it happens. People conflate the two because both live in the same builder.

The honest rule: use a drip when the next useful thing to say depends on how long ago someone arrived, and a triggered email when it depends on what they just did. If you cannot name the event and where its data comes from, you do not have a behavioural option yet.

The less comfortable half: a drip is also right when your team is small. A fixed sequence reviewed every quarter beats a branching programme nobody has opened since launch.

The five drips worth building for most Indian SMBs

Described by the job they do, not the name a platform gives them. Most businesses need two or three of these, not five.

Three absences are deliberate. A true welcome sequence behaves differently enough to deserve its own treatment, which we are publishing separately. Nurture strategy — what you say across months rather than days — is a strategy problem. And cold outreach to people who never asked to hear from you is a separate discipline with its own consent and deliverability constraints.

All five assume you know who you are writing to. If the segments feel vague, fix that first: buyer persona work and a mapped customer journey sit upstream of any sequence.

How to write one: exit condition, then arc, then emails

Write the exit condition before you write a subject line. This is the step almost everyone omits, and it is why people get a "still thinking about it?" email the day after they buy.

1. Define the exit condition. Finish this sentence: "A person should stop receiving this the moment they ___." Usually it is the thing the drip asks for — booked, bought, replied, registered. Build it as a removal step, not a note in a spreadsheet.
2. Add the second exit. They did the thing elsewhere — walked in, called the office, bought on a marketplace. If that path is invisible to your email tool, your exit has a hole and you should know where.
3. Decide the arc. Write the reader's state at entry and the state you want at the end. The number of emails falls out of the distance between them, usually three to six.
4. Give every email one job. One idea, one ask, one link that matters. If you cannot name the job in four words, it is two emails or none.
5. Write the last email first. It works hardest and everyone writes it tired. Working backwards also exposes middle emails that exist only to fill a gap.
6. Read the whole thing in one sitting. Out loud, in order. Repetition is invisible when you write steps on separate days and glaring when you read them together.

The arc matters more than any single email, and a drip covers only one stage of the marketing funnel — write it for that stage and stop.

Timing and spacing: the gaps carry more weight than the copy

The gap is the only part of a drip the reader feels without reading anything. Short gaps read as pressure. Long gaps read as indifference.

• Front-load, then widen. Day 0, 2, 5, 11, 20 is a sane shape — attention decays fast early, and later you have less that justifies crowding.
• Make the gap longer than the decision. If a ₹2 lakh purchase needs two people and a meeting, a two-day gap asks for an answer that cannot exist yet.
• Respect the Indian working week. Saturday afternoons and festival weeks behave differently; check your own data rather than a send time from a US blog.
• Never let two sequences overlap. A contact in two drips gets two unrelated emails in the same hour, and neither survives it.
• Cap the total span. Past six or eight weeks it has become a newsletter without the editorial discipline of one, which is a different job with different rules.

A drip also does not need to be fast. The least pressured sequences we write have the widest gaps, because the entry event was a download rather than a quote request.

The one technical thing that breaks drips: a trigger that fires twice

Most broken drips are not badly written. They are entered twice, and the reader gets the whole sequence again from the top — a form submitted again, a tag applied by two automations, a CSV re-imported after a cleanup.

• HubSpot enrols records only the first time they meet the triggers by default; re-enrolment is an explicit setting. Its documentation adds that a record will not re-enrol while still enrolled, and that a re-enrolled record "will start the workflow again from the beginning and complete all workflow actions again" — a repeat, not a top-up. (HubSpot Knowledge Base, "Add re-enrollment triggers to a workflow", last updated 3 August 2026.)
• Klaviyo offers re-entry criteria: enter once, re-enter whenever they requalify, or re-enter after a minimum period. Its documentation also notes that failing a flow filter at one step skips that action rather than removing the person, with profile filters checked "before each action takes place". (Klaviyo Help Center, "Understand flow triggers and filters", updated 17 March 2026.)

That second detail is the one people misread. Skipped is not removed — a filter is not an exit, and a sequence relying on filters alone can still wake up and mail someone weeks later.

Three checks before launch: enter the sequence yourself with a real address, submit the entry form twice, and fire the exit condition halfway through to confirm the rest stops.

A five-email drip, laid out

Illustrative example, not a client: a Mumbai industrial-equipment supplier running a free 45-minute online demo on a fixed date. People enter when they join the invite list.

Exit condition: the moment someone registers they leave this sequence for the attendance reminders. Second exit: an unsubscribe or a reply asking not to be contacted. Third exit, the one teams forget: the date passes and the sequence is switched off rather than left running into next year.

Note what is absent from that table — open rates. Judge these five on registrations, replies and clicks, reported against the few marketing KPIs that connect to revenue. Open rate deserves suspicion: Apple's Mail Privacy Protection "downloads remote content in the background by default — regardless of whether you engage with the email" (Apple, "Mail Privacy Protection & Privacy", page dated 12 December 2025), so a share of recorded opens is machine behaviour, not interest.

How to tell a drip is failing before the unsubscribes arrive

Unsubscribes are a lagging signal. By the time they cluster, the sequence has been annoying people for weeks. Four earlier signals, in the order they appear:

• Reply content changes. Replies stop being questions and become corrections — "I already bought", "we went with someone else", "please take me off". Read your replies; it is the cheapest diagnostic you own.
• Click decay with a cliff. Gentle decline down the steps is normal. A cliff between two steps is a broken promise at that point in the arc.
• Complaints concentrated on one email. That is a copy or expectation problem at that step, not a list problem.
• Entries dry up while the drip stays live. Almost always a sequence written for a situation that has changed.

The quarterly audit, in this order

• Enter it yourself. Fresh address, full sequence, read in real time. Most problems show by email two.
• Test every exit. Exits break silently after changes to forms, CRM fields or payment flows.
• List the overlaps. Every sequence one contact could be in at once, then fix the collisions.
• Check links and offers. Dead pages, expired offers, last year's event date.
• Reread step one against today. If the opening premise no longer describes the person entering, editing downstream will not save it.

The sunset rule

Decide in advance what happens to someone who receives the whole sequence and does nothing. Leaving them on the main list for everything else is how an email programme quietly degrades.

A workable rule: complete the drip with no click and no reply, and you stop receiving campaign email, sitting in a dormant segment until you do something deliberate. That costs reach on paper and protects deliverability in practice — the wider version of that hygiene belongs to email marketing generally.

When to delete rather than rewrite

Rewriting is the default because the copy already exists. It is often the wrong call.

Delete when the entry premise has changed. A sequence written for people downloading a pricing calculator cannot be edited into one for people who attended a webinar — the state at entry is different, so every email is wrong in a way word changes cannot fix. Same if the offer no longer exists, or you cannot say in one sentence what the sequence is for.

The test we use: if you had never written it, would you build this sequence today? If not, you are maintaining it out of sunk cost. Switch it off, keep the list, write the one you would actually build. If you would rather someone else pulled apart what is running now, that is where our services start — the audit, not the rewrite.

Where to take this next

Pick one job from the five above, the one with a clear exit condition and a real entry point. Write the exit first, then the arc, then the emails. Launch it, enter it yourself, and put a quarterly review in the calendar with your name on it.

Then resist building the second one until the first has run a full cycle.