# A four-step follow-up sequence for deals in Pipedrive: drafts first, auto-send later

https://salesbond.app/blog/pipedrive-sequences-deal-follow-up/
Published: 2026-10-03 · Updated: 2026-10-20

Build one sequence in Pipedrive Sequences (Pulse > Sequences) for deals that just had a demo, and give it four steps: two emails saved as drafts and two activities. Turn on automatic sending for exactly one of the emails, the one whose text does not change from buyer to buyer. The other three steps show up as reminders, and a person does them. That is the whole setup.

We run it this way because a deal after a demo is the opposite of a cold list. The buyer has seen the product, asked specific questions and said specific things. A follow-up that ignores all of that is worse than no follow-up. So the sequence’s job is not to send emails for the rep. Its job is to make sure the rep is reminded, on the right day, with the draft half written.

## A week after the demo, and nothing on anyone’s screen

An example, not a client of ours. A small team sells barcode software for warehouses. On Friday, September 18, 2026, a rep demos it to the operations manager of a regional distributor. One question stays open at the end: can their old SKU list be imported as it is? The rep says they will check with their engineer and come back.

The engineer answers the next morning, in the team chat. The answer is good. It never turns into an email, because nobody’s list says it should: the deal sits in the “Demo done” stage with no next activity, and the rep’s week fills up with other things.

The following Friday, September 25, the manager does a last pass before the weekend, filtering the pipeline for open deals without a next activity. The distributor deal is on it. The buyer has not gone quiet in the sense we covered in [what to do when a prospect goes silent after the demo](https://salesbond.app/blog/prospect-went-silent-after-demo/). They are still waiting for an answer that has existed for six days.

Nobody forgot the buyer. Nothing told anyone it was their turn. A sequence fixes that second part. It does not make the follow-up good, and the rest of this piece is about both.

## What Pipedrive Sequences are, and what they aren’t

A sequence is a linear flow of email steps and activity steps that you attach to deals or to leads. You build it once under Pulse > Sequences, choose at creation whether it is for deals or for leads, and then enroll records into it. Each sequence holds up to 10 steps, and every email step can be a draft the rep sends by hand or an email Pipedrive sends automatically at the scheduled time ( [Pipedrive: Sequences feature](https://support.pipedrive.com/en/article/sequences)). Once the first deal or lead has been enrolled, the sequence is locked to that record type.

Two things it is not.

It is not an automation. Pipedrive’s own wording is that Automations handle tasks like updating fields or assigning deals, while Sequences focus on structured communication (same article). You can combine the two and have an automation enroll deals into a sequence when they reach a stage, and that is a reasonable second step once the the sequence itself has run for a few weeks by hand. If you do, the automation side has limits of its own, from wait steps to [the sending limits behind automatic emails](https://salesbond.app/blog/pipedrive-automation-limits-follow-up/). If your account already has a pile of automations nobody remembers building, read [the owner’s audit of Pipedrive automations](https://salesbond.app/blog/pipedrive-automations-owner-audit/) before adding one more.

And in our view it is not a tool for cold outreach, even though the help center allows it. The deal-type sequence enrolls deals, and a deal is a conversation that already exists. Everything below assumes that: the buyer knows your name, and the next message should sound like it.

## Four steps after a demo, in order

The steps below are what we enroll a deal into the day after a demo. The day numbers count from the demo. In the builder each step is either an activity (you set the due date, type, assignee, priority and notes) or an email (you set a reminder time for sending, the sender and recipient, the text, and can pull in any email template already in the account, with the sequence owner’s signature at the bottom). If the whole team pulls from that library, [keeping the shared template library clean](https://salesbond.app/blog/pipedrive-shared-email-templates-team/) matters more than it seems.

![Four-row plan of a Pipedrive sequence after a demo: draft email, call, automatic email, call or task for someone who missed the demo](https://salesbond.app/wp-content/uploads/2026/10/pipedrive-sequences-deal-follow-up-2.png)

1. **Day 1, email, draft.** The recap that answers the one question they actually asked. In the example above that is the SKU list: can it be imported as it is, and who does it. The rep writes two or three sentences into the draft the sequence has already opened for them. This cannot be automatic because the question is different every time.
2. **Day 4, activity, call.** Type: Call. Note in the activity: “ask what they would change about the demo.” Not “check in.” The purpose of this call is to hear the objection while it is still small. Do not [time the next step off an open icon](https://salesbond.app/blog/pipedrive-email-tracking-opens-clicks-what-it-proves/) on the day-one email.
3. **Day 8, email, automatic.** A plain description of what happens after a yes: who from your side gets involved, what the buyer’s team has to prepare, roughly how the first weeks go. This text is the same for every buyer at this stage, which is the only reason it is allowed to send itself. More on that in the next section.
4. **Day 12, activity, call or task.** Reach the person who was not on the demo. The rollout owner, the person who signs, the person who asked about the SKU list by proxy. The note in the activity names who, because the rep knows by day 12 and the sequence does not.

After step 4 the sequence is done. If the deal is still open and still quiet, that is no longer a follow-up problem. It is a qualification question, and it goes to the weekly deal review rather than to a fifth email.

A note on what is not in these four steps: a proposal. If the demo ends with “send us pricing,” the deal needs the [follow-up rhythm after a proposal](https://salesbond.app/blog/follow-up-after-proposal-pipedrive/) instead, and you complete this sequence by hand.

## Draft steps or automatic sending: where the toggle belongs

Here is how the two kinds of email step behave, from the help center ( [Pipedrive: Sequences feature](https://support.pipedrive.com/en/article/sequences)).

A draft step appears in the rep’s Pulse feed when its day comes. That is the reminder. The rep opens it, changes what needs changing, and sends. Nothing leaves without a person. Keep in mind that [the feed shows only deals assigned to that rep](https://salesbond.app/blog/pipedrive-pulse-feed-overlooked-deals/).

An automatic step is switched on per email step with the “Send automatically” toggle in the Details section. Pipedrive then sends it at the scheduled time without anyone touching it. The message is scheduled at that time and can’t be edited afterwards. The step still appears in the Pulse feed, but it runs on its own at the scheduled time.

That one sentence, “can’t be edited,” is our whole rule. If there is any chance the rep would want to change a word after the demo, the step stays a draft. The day-one recap fails this test on every deal. The day-eight “what happens after yes” email passes it, because the content depends on how you onboard customers, not on which customer. Before it goes into the sequence, the owner of the sequence reads it once as if they were a buyer who just asked for a discount, or just said they need another month. If it still reads fine, it is safe to automate. And if you are not sure whose name it goes out under or where the reply lands, [we covered the automated email sender in Pipedrive](https://salesbond.app/blog/pipedrive-automated-email-sender/) separately.

There is also a consent step, and it is per person. Before an automatic email can send, each user has to turn on the “Authorize automated and delegated sending” toggle in the sequence builder. The consent is given per user, not for the whole company, and per sequence, not for all sequences. The practical consequence for a manager: a new rep enrolled into the team’s sequence has not consented to anything yet. If consent is removed after an email has already been scheduled, the sequence fails at that step, the deal is categorized as failed, and no further steps run. Which is where the next section starts.

That toggle records consent from the sender, not from the recipient, and the recipient side is a separate record: the [marketing status belongs to the email address](https://salesbond.app/blog/pipedrive-marketing-status-unsubscribed-contacts/), not to the person.

## Reading the overview tab on Monday

Open the sequence under Pulse > Sequences and click the Overview tab. You get the list of deals in the sequence, a count of In Progress, Completed and Failed, and filters by status and by owner ( [Pipedrive: Sequences feature](https://support.pipedrive.com/en/article/sequences)). Once a week is enough. We do it Monday, before teh pipeline meeting.

Three things to look at, in this order:

- Failed above zero. Filter to Failed, open the deals, find the step they failed on. In our experience this is a consent toggle somebody switched off, or a rep who left and whose sequences nobody reassigned.
- Completed deals that have not moved stage. The sequence finished all four steps and the deal is still in “Demo done.” Those are the deals for Thursday’s review, and the question is not “did we follow up” but “is this a deal.”
- In Progress, by owner. One rep with twelve deals in progress and another with one is either a workload story or an enrollment story.

The limit of this tab is that it only shows deals somebody put in. The distributor deal from the example was never enrolled, so no overview would have listed it. A disclosure, since this is the gap we work on: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. Deal Health checks every deal in the connected CRM against more than 20 rules, Activity among them, shows the specific violations and explains what to do, so a demo-stage deal nobody enrolled still gets looked at. [Check your CRM with SalesBond](https://salesbond.app/) if that unenrolled deal is the one that worries you.

One more place to look, when a “sent” step produced no reply at all: the rep’s Outbox. An email that failed to leave Pipedrive looks exactly like a buyer who is thinking it over, and [we wrote up how to find failed emails in Pipedrive deals](https://salesbond.app/blog/pipedrive-failed-emails-follow-up-gaps/) separately.

## When to take a deal out of the sequence

The moment the buyer answers anything, the sequence has done it’s job and the conversation belongs to the rep. The help center gives the same examples we would: the contact replied through another channel, converted outside the flow, or asked to opt out. For those cases there is “Mark as completed” on the individual sequence, visible only while it is in progress; it asks for confirmation, it cannot be undone, and the timestamp of the completion then shows in the sequence builder ( [Pipedrive: Sequences feature](https://support.pipedrive.com/en/article/sequences)). From the Overview tab you can also select several deals with the checkboxes and remove them in one go.

We make this a habit rather than a judgement call: reply received, mark completed, book the next activity by hand. The reason is the day-eight automatic email. A buyer who wrote back on day six with “we need to talk to finance first” and then received a scheduled note about onboarding on day eight has learned that your emails are not written to them. That costs more than the follow-up was ever worth. The draft steps are forgiving here, because a rep who sees a stale draft in Pulse simply does not send it. The automatic step is not forgiving, which is one more reason there is only one of them.

Take the deal out, too, when it moves to a proposal (see above), when it is marked lost, and when the buyer names a date. “Call us after our board meeting on the 15th” beats any schedule you built in advance. One activity on the 16th, and the sequence is complete.

What stays in: the deals where you have heard nothing. Four steps, twelve days, then the deal review. The sequence exists so that the silence is at least a silence you measured.