# The warm pipeline

> No-shows (a missed demo or sales meeting), event attendees and closed-lost deals become one ranked follow-up list in the CRM, kept current by two labels on each person.

- Canonical page: https://warmup.ai/library/warm-pipeline
- By Mike Hurley, founder of WarmUp. We taught this in a webinar on November 18, 2026 and are setting it up in our own CRM now. It is new, so there are no results to report yet.
- Version 1.0. Last updated 2026-11-18. About 9 minutes.
- Board: https://warmup.ai/library/warm-pipeline.webp
- Motion: Outbound
- Channel: CRM
- Tools: HubSpot

**The people who already raised a hand. One list, ranked by how fresh the reason is.**

## The warm pipeline: the route

In order: the five readiness checks, the two labels every person carries, then the four moves. Gather the three groups, clean out anyone you should not contact, rank by the three clocks, follow up. An orange arrow is a yes; every no ends at Not on the list and every unknown waits for a person. Each part is drawn in full beside its step under "How to build it".

### 1. What must exist first

Five readiness checks, each with a named writer:

**1. Meeting outcomes**
Does every past meeting have an outcome?
- Who writes it: The rep who was on the meeting. The CRM does not infer it.
- Pass: Every past sales meeting is marked Completed, No show, Rescheduled or Canceled.
- Fail: Outcomes are blank. The no-show group waits until the rep fills them in.

**2. Event lists**
Does every event have a registered list and an attended list in the CRM?
- Who writes it: The event owner, within 24 hours if the event tool does not sync.
- Pass: Two lists per event: who registered, and who attended.
- Fail: One list, or none. The attendee group waits until both are imported.

**3. Loss reasons**
Does every closed-lost deal have a reason from a short pick-list and a close date?
- Who writes it: The deal owner. The CRM requires both when the deal is marked lost.
- Pass: A reason and a close date on every closed-lost deal.
- Fail: Reasons are blank or free text. The closed-lost group waits; fix it going forward.

**4. A person on every deal**
Does every deal have a person with a working email attached?
- Who writes it: The deal owner, when the deal is created.
- Pass: A contact with a working email on every deal.
- Fail: Deals with only a company on them. Nobody to write to, so those deals wait.

**5. Who to leave alone**
Can you tell, from the record, who must not be contacted?
- Who writes it: The CRM owner, who also keeps the do-not-contact list.
- Pass: Customers, open deals, unsubscribes, bounces, do-not-contact, cooldowns and competitors can all be read.
- Fail: You cannot tell. No group starts until you can.

In: The CRM as it is today: past meetings, events and closed-lost deals.

### 2. The two labels

**Group and warm date**
Each person carries two labels: which group they came from, and the date of the thing that made them warm. The list reads those two labels, so people move on and drop off without anyone rebuilding it.

### 3. 1. Gather

**No-show**
Is a demo or sales meeting marked No show, with no later meeting booked?
Source: The meeting outcome, set by the rep
- Pass: Marked No show, and nothing booked since.
- Fail: A later meeting is booked, or the meeting happened.
- Unknown: The meeting has no outcome. The rep sets it; nobody guesses.
See note A below.

**Event attendee**
Did they attend one of our events?
Source: The event's attended list
- Pass: On the attended list.
- Fail: Registered but missed it: a separate, lower group, not this one.

**Closed-lost deal**
Lost 3 to 18 months ago, for a reason that can reopen, and is it time?
Source: The deal's close date and loss reason; replies, site visits and meetings after the loss
- Pass: The revisit date has arrived, or a first-party signal came after the loss: a reply, a site visit, a meeting booked.
- Fail: Poor fit, lost less than 3 or more than 18 months ago, or still inside the wait for its reason.
- Unknown: The reason is Other, or a lost champion with no new contact known. A person re-reads it.
See note B below.

The decision: In a group? Yes: On to Clean. Unknown: Waits for a person. No: Not on the list.

Tools we used: HubSpot, as the example CRM. The rules carry to any CRM.

### 4. 2. Clean

**Who stays out**
Is there any reason to leave this person alone?
Source: The record: deals, subscription status, the do-not-contact list, the cooldown date
- Pass: None of the six. Clear to contact.
- Fail: A customer, anyone with an open deal, unsubscribed or bounced, do-not-contact, a cooldown date still ahead, or a competitor.

The decision: Clear to contact? Yes: On to Rank. No: Not on the list.

### 5. 3. Rank

**The three clocks**
How recently did they engage? Warmth fades.
Score them by how recently they engaged. For a closed-lost deal the clock starts from the newest reason to write, not from the loss.
Source: The warm date on the person
- No-show: Hot for 7 days. On the list for 30 days.
- Event attendee: Hot for 14 days. On the list for 30 days.
- Closed-lost deal: Hot for 14 days. On the list for 30 days.
- Pass: Inside the hot window: top of the list, newest date first. After it, still on the list, below the hot people.
- Fail: Past 30 days. Off the list until a new date puts them back.
See note D below.

The decision: Still inside its 30 days? Yes: Follow up, hot people first. No: Not on the list.

### 6. 4. Follow up

**Hot: follow up now**
Inside the hot window and clear to contact. The rep works these first, with the group and the date beside each name.

**Waits for a person**
A loss reason of Other, a lost champion with no new contact, or a meeting with no outcome. Kept, and decided by a person, never by a guess.

**Not on the list**
Never in a group, cleaned out, or past 30 days. The two labels stay on the record, so a new date puts the person back with a fresh clock.

A different message per group:

**To a no-show**
No guilt. Two specific times to rebook.

**To an event attendee**
The resource that was shown, plus one question about their setup.

**To a closed-lost deal**
Name the original blocker and what has changed. One small ask.

Out: One short list in the CRM, hot people first, with the group and the warm date beside each name.

Key: The order of the moves; Yes: on to the next move; No: not on the list; Unknown: waits for a person.

A group that fails its readiness check waits. The groups that pass still start.

One person: Booked a demo and did not show, then no later meeting booked, clear to contact, then hot for 7 days, then a message with no guilt and two specific times to rebook. Illustrative.

### Four things HubSpot does that will catch you

We build this in HubSpot. The rules carry to any CRM; these four behaviours are HubSpot's own, checked on November 18, 2026.

- **A. A no-show filter matches any past meeting** (HubSpot). Someone who missed one meeting and showed up for the next still matches "No show". Exclude anyone with a later meeting booked.
- **B. A closed-lost filter means at least one closed-lost deal** (HubSpot). By default it matches anyone with at least one associated deal that is lost, including people who also have an open or won deal. Exclude anyone with an open or won deal.
- **C. How fast the list refreshes** (HubSpot). A list that filters plain contact properties refreshes almost at once. A list that filters on membership of another list can take up to two hours. Put the two labels on the contact and filter on those.
- **D. Why dates and not a decaying score** (HubSpot). Lead-score decay steps down no faster than once a month, which is too slow for a 7-day window. Date windows on the warm date rank better here.

## Why it helps

When a team needs pipeline, it usually goes looking for strangers. Meanwhile the CRM is full of people who already raised a hand and then went quiet. Someone who booked a demo or a sales meeting and did not show. Someone who came to one of your events. Someone you had a real sales conversation with and lost, which the CRM calls a closed-lost deal. They know who you are, and each of them once had a reason to talk to you.

Nobody works them because nobody can see them. They sit in three different places, mixed in with customers, open deals and people who asked not to be contacted, and there is no order to them. This guide turns them into one short list with the freshest reason at the top, and a different message for each group, because a no-show and a closed-lost deal should not get the same email.

The part that makes it last is small. Each person carries two labels: which group they came from, and the date of the thing that made them warm. The list reads those two labels and nothing else. People move up, move down and drop off as the dates pass, and nobody rebuilds the list by hand.

I am not going to quote a rebook rate or a win-back rate, because I have not found an independent number I trust. What I can say is that this is the list where the first message does not have to explain who you are.

## What must exist first: five readiness checks

The list is only as good as five things in the CRM, and each one needs a named person who writes it. Run these checks before you build anything. A team that fails a check still starts: it starts with the groups that pass, and fixes the rest going forward.

| The check | What it means and who writes it |
|---|---|
| 1. Every past meeting has an outcome | Completed, No show, Rescheduled or Canceled, set by the rep who was on the meeting. The CRM does not infer it. Without it there is no no-show group. |
| 2. Every event has two lists in the CRM | Who registered and who attended, as two separate lists. If the event tool does not sync, the event owner imports both within 24 hours. Without them there is no attendee group. |
| 3. Every closed-lost deal has a reason and a close date | The reason comes from a short pick-list, and the CRM requires it when the deal owner marks the deal lost. Without them you cannot tell a deal worth reopening from one that never fit. |
| 4. Every deal has a person attached | A contact with a working email, attached by the deal owner when the deal is created. A closed-lost deal with only a company on it gives you nobody to write to. |
| 5. You can tell who to leave alone | Customers, open deals, unsubscribes, bounces, a do-not-contact list, cooldown dates and competitors can all be read from the record, and the CRM owner keeps the do-not-contact list. |

## The three groups

| Group | Goes in when, and for how long |
|---|---|
| No-show | A demo or sales meeting is marked No show and no later meeting is booked. Hot for 7 days. On the list for 30. |
| Event attendee | They attended one of your events. Someone who registered and missed it is a separate, lower group, not this one. Hot for 14 days. On the list for 30. |
| Closed-lost deal | The deal was lost 3 to 18 months ago, the reason is one that can reopen, and either the revisit date has arrived or a first-party signal came after the loss: a reply, a site visit, a meeting booked. The clock starts from that newest reason to write, not from the loss. Hot for 14 days. On the list for 30. |

## How long to wait after each loss reason

The loss reason sets the revisit date: the close date plus the wait below. Keep the pick-list this short. A long one gets filled in at random.

| Loss reason | Default wait before looking again |
|---|---|
| Timing or no decision | 90 days. |
| Price or budget | 90 days. |
| No response, ghosted | 60 days. |
| Chose to do it in-house | 180 days. |
| Went with a competitor | 270 days. |
| Lost champion | No fixed wait. It reopens when a new contact is known. |
| Poor fit | Never. It does not come back. |
| Other | A person re-reads it and decides. |

## Four things HubSpot does that will catch you

We build this in HubSpot, and the rules carry to any CRM. These four are specific to HubSpot, checked on November 18, 2026.

1. A filter on meeting outcome matches any past meeting. Someone who missed a meeting in the spring and showed up for the next one still matches "No show". Exclude anyone with a later meeting booked.
2. A filter on closed-lost deals means "at least one associated deal is lost" by default. Someone with one lost deal and one open or won deal still matches. Exclude anyone with an open or won deal.
3. A list that filters plain contact properties refreshes almost at once. A list that filters on membership of another list can take up to two hours. Put the two labels on the contact and filter on those.
4. Lead-score decay steps down no faster than once a month, which is too slow for a 7-day window. Rank with date windows on the warm date instead of a decaying score.

## Why we built it this way

- **Readiness comes before the list.** A list built on blank meeting outcomes and missing loss reasons looks finished and is wrong. The five checks say which groups you can trust today, and each check has a named writer so it stays true next month.
- **A group that fails its check waits. The others start.** Most teams fail at least one check. That is not a reason to wait on all three groups. If meeting outcomes are clean and loss reasons are not, run the no-shows this week and fix closed-lost deals going forward.
- **Two labels on the person, and the list reads only those.** Which group, and the date of the thing that made them warm. Because the list is a filter on two fields, people move on and drop off by themselves as dates pass. Nobody exports, sorts or rebuilds anything.
- **Cleaning runs on every group, however warm.** A no-show who became a customer last month is not a follow-up. Customers, open deals, unsubscribes, bounces, do-not-contact, cooldowns and competitors come out before anyone is ranked. Warmth sets the order, not the rules.
- **Score them by how recently they engaged, with dates.** Warmth fades, and it fades at a different speed for each group. A missed meeting is stale in a week. An event or a reopened deal holds for two. A date window says that exactly. A lead score that decays monthly cannot.
- **The loss reason decides when a closed-lost deal comes back.** A deal lost on timing is worth a look in 90 days. One lost to a competitor is locked in for most of a year. One that never fit should not come back at all. One wait for every closed-lost deal would be wrong for most of them.
- **One message per group.** The reason to write is different, so the message is. A no-show gets two times and no guilt. An attendee gets the resource and a question. A closed-lost deal gets the original blocker and what changed. One template for all three reads like a blast.
- **Thirty days, then off the list.** A list that only grows stops being worked. After 30 days the person drops off. The labels stay on the record, so a new event, a new signal or a new revisit date puts them back with a fresh clock.

## How to build it

1. **Run the five readiness checks.** For each check, open a sample of recent records and ask whether the field is filled in and who fills it. Write the name of the writer next to each one. Note which of the three groups each check unlocks, and start with the groups that pass.
2. **Add the two labels to the contact.** One field for the group (no-show, event attendee, closed-lost deal) and one date field for the thing that made them warm: the meeting date, the event date, or for a closed-lost deal the revisit date or the date of the signal that came after the loss. Stamp both with a workflow when the trigger happens.
3. **Gather the three groups.** Write one entry rule per group, exactly as in the spec below. Registered-but-missed goes in its own lower group. A closed-lost deal with the reason Other, or a lost champion with no new contact, waits for a person to read it.
4. **Clean out anyone you should not contact.** One exclusion step, applied to every group: customers, anyone with an open deal, unsubscribed or bounced, do-not-contact, a cooldown date still ahead, and competitors.
5. **Rank by the three clocks.** Score them by how recently they engaged. For a no-show that is the meeting date, and for an attendee the event date. For a closed-lost deal the clock starts from the newest reason to write (the revisit date arriving, or a reply, a site visit or a meeting booked), not from the day the deal was lost. Hot is a date window on that date: 7 days for a no-show, 14 for an attendee, 14 for a closed-lost deal. Hot people sort to the top, newest date first. Everyone stays on the list for 30 days and then drops off.
6. **Follow up with the hot group, one message per group.** The rep works the hot people first. No-show: no guilt, two specific times to rebook. Attendee: send the resource that was shown and ask one question about their setup. Closed-lost deal: name the original blocker and what has changed, with one small ask.
7. **Write the outcome back.** Every follow-up ends in something the CRM can read: a meeting booked, a reply, a new deal, or a cooldown date. A booked meeting gets its own outcome when it happens. That is what keeps the five checks true without a cleanup project.
8. **Review the list once a week.** One person looks at who is hot, who is waiting for a person to decide, and which readiness check is slipping. If a group's list is empty for a month, the check behind it has usually stopped being filled in.

## Copy this: The warm pipeline rules

The entry rule, the clocks and the exclusions for each group, and the wait after each loss reason. The field names are examples. The rules and the numbers are the part to copy.

```yaml
# warm-pipeline.yaml: the only rules the list reads
labels:                               # every person on the list carries these two
  warm_group: [meeting_no_show, event_attendee, closed_lost_deal]
  warm_date:  the date of the thing that made them warm
ready_first:                          # a group that fails its check waits; the others start
  - meeting_outcome: set by the rep on every past meeting, never inferred
  - event_lists:     registered and attended, in the CRM within 24 hours
  - loss_reason:     from the pick-list, with a close date, required when a deal is marked lost
  - deal_contact:    every deal has a person with a working email
  - leave_alone:     you can tell who must not be contacted
groups:
  meeting_no_show:
    enters_when:
      - demo or sales meeting outcome is No show
      - no later meeting is booked
    clock_starts: the meeting date
    hot_days: 7
    on_list_days: 30
  event_attendee:
    enters_when: attended one of our events
    separate_lower_group: registered but missed
    clock_starts: the event date
    hot_days: 14
    on_list_days: 30
  closed_lost_deal:
    enters_when:
      lost: 3 to 18 months ago
      reason: one that can reopen     # see loss_reasons
      and_one_of:
        - the revisit date has arrived
        - "a first-party signal after the loss: a reply, a site visit, a meeting booked"
    clock_starts: the newest reason to write, not the loss date
    hot_days: 14
    on_list_days: 30
stays_out:                            # checked for every group, before ranking
  - customer
  - open deal
  - unsubscribed or bounced
  - do not contact
  - cooldown date still ahead
  - competitor
loss_reasons:                         # days after the close date before looking again
  timing_or_no_decision: 90
  price_or_budget: 90
  no_response_or_ghosted: 60
  chose_in_house: 180
  went_with_competitor: 270
  lost_champion: when a new contact is known
  poor_fit: never
  other: a person re-reads it
rank: by how recently they engaged; hot first, newest warm_date first, then the rest of the 30 days
follow_up:
  meeting_no_show:  no guilt, two specific times to rebook
  event_attendee:   the resource shown, plus one question about their setup
  closed_lost_deal: name the original blocker and what changed, one small ask
```

## Words we use

- **Warm pipeline:** The people who already raised a hand and went quiet: no-shows, event attendees and closed-lost deals, kept as one ranked follow-up list.
- **Readiness check:** One thing that must already be true in the CRM before a list built on it can be trusted, with a named person who keeps it true.
- **Warm date:** The date of the thing that made a person warm: the meeting they missed, the event they attended, or the day a lost deal became worth reopening. The list ranks by it.
- **Hot window:** The number of days after the warm date in which a person sits at the top of the list. It is shorter for a missed meeting than for an event or a lost deal.
- **Loss reason:** Why a deal was lost, chosen from a short pick-list when the deal is closed. It decides how long to wait before looking at the deal again.
- **Revisit date:** The day a lost deal is worth another look: its close date plus the wait for its loss reason.
- **No-show:** A booked demo or sales meeting the buyer did not attend. The rep marks it. The CRM does not work it out.
- **Cooldown:** A date on a person before which nobody reaches out again, set after a no, a recent touch or a request to wait.
- **Signal:** Something a company or a person did that gives a reason to reach out now: a job posting, a funding round, a visit to your site, a click on an ad, a contract award, a compliance date, an expansion, a comment on a post, a form, a reply.
- **Blocklist:** The companies and people we must never contact. One tool writes it, and every sender reads the same copy.

## Talk to a person

Want a free Warm Pipeline Scan of how you track these three groups today? WarmUp builds these systems for companies: https://warmup.ai/gtm-engineering. WarmUp's prices are published at https://warmup.ai/pricing.
