All case studiesThe droid that runs pipeline hygiene

A pipeline that keeps itself honest.

A droid that works the middle of the funnel every morning: it sweeps the CRM for deals drifting without a next step, drafts the follow-up each one needs, nudges the rep who owns it, and flags only the deals that are genuinely slipping — so the forecast reflects reality instead of wishful thinking.

Every morning
the pipeline swept before standup — no deal left without a next step
0 stale deals
nothing drifts silently past its follow-up date
~15 min
of rep busywork per deal handed off — drafted, not typed
Does
Sweeps the pipeline, drafts the nudges
Where
B2B SaaS, ~20-person sales team
Reaches people on
Slack, email
Works inside
HubSpot, Gmail
Runs
Every morning + on stage changes
The situation

Deals don't die — they drift, quietly, until the forecast lies.

Deals didn’t die loudly — they drifted. A demo went well, a next step never got set, and three weeks later the deal was cold and nobody had noticed. Reps meant to follow up, but the ones who slipped were exactly the ones that fell through the cracks of a busy week.

The manager found out at forecast time, when “commit” deals turned out to have no activity in a month. Keeping the CRM honest — a next step on every deal, a nudge when one goes quiet — was the discipline everyone agreed mattered and nobody had time to maintain.

Isometric sales-pipeline scene: a kanban board of deal cards with a funnel and a nudge arrow lifting a stale card
How it works

How the droid took it on.

Rather than nag reps to keep the CRM tidy, the team handed the discipline over. Every morning the droid sweeps the pipeline, drafts the nudge each drifting deal needs, and flags only the deals genuinely stalling.

TASK#188Pipeline hygienestanding
trigger
Every weekday at 8:00am — a full pipeline sweep
also
Any deal stage change, plus reps' chase requests
scope
Every open deal in the CRM
runs as
A contained droid action per sweep, change, or request
memory
Per-deal history and each rep's follow-up style

Set up once, in plain language — “every morning, find the deals drifting without a next step, draft the nudge each one needs, and only pull me in when a deal's actually stalling.” The droid turned that into a standing job — the CRM discipline a busy team never keeps up by hand.

Every morning trips the same loop:

Ongoing handling

How it ran, deal after deal.

Here’s a morning sweep as it actually unfolded — deal by deal, down to how it reached for each app. Only the one stalling deal made it to the manager.

  1. 8:00amsweep
    • HubSpot
    • Gmail

    Swept 47 open deals and found 9 drifting without a next step — drafted a tailored nudge for each.

  2. 8:20amstage change · Globex
    • HubSpot

    A deal moved to “proposal sent” — queued the 3-day follow-up and set the next step.

  3. 8:25amhousekeeping
    • HubSpot

    Closed out 3 long-dead deals as lost so they stopped inflating the forecast.

  4. 8:35amrequest · Acme
    • HubSpot
    • Gmail

    On a rep's ask, drafted a re-engage that answered the open pricing question and offered times.

  5. 8:48amslipping · Big Coescalated
    • HubSpot
    • Slack

    A $120k deal past its close date with no activity — escalated to the manager with the history.

  6. 8:55ampipeline digest

    The sweep reconciled — 9 nudged, 1 re-engaged, 3 closed out, 1 escalated. Every open deal has a next step.

See it in action

One morning, deal by deal.

The sweep, the stage changes, and a rep's request land on the left. Watch the droid pick up each one and work it across the CRM, inbox and calendar — pulling in a human only for the deal that's actually slipping.

We didn't add another dashboard nobody looks at — we put someone on it. Every morning the drifting deals already have a drafted nudge waiting, and the only deals that reach me are the ones actually stalling. The forecast finally means something.
Marcus D.VP Sales, B2B SaaS

An illustrative workflow based on real product mechanics. Tool names and behaviour reflect how a droid actually runs on a schedule and calls connected apps; figures are directional.

Try it with your droid

Run this workflow yourself.

Copy the brief below and paste it to your droid. It’ll walk you through the prerequisites, connect what it needs, and stand the workflow up with you.

Workflow brief
I run sales at a B2B SaaS company, and deals don't die loudly — they drift. A demo goes well, no next step gets set, and three weeks later it's cold and nobody noticed. Reps mean to follow up, but the ones that slip are the ones that fall through a busy week, and I only find out at forecast time when 'commit' deals turn out to have no activity in a month.

Own pipeline hygiene. Apps/channels: HubSpot (deals, stages, next steps, activity), Gmail (drafting follow-ups), Google Calendar (last-meeting context), Slack #sales (the morning digest and manager escalations).

Run a full sweep every weekday morning, react to deal stage changes, and handle reps' chase requests. On each sweep:
1. Pull every open deal and check for a real next step and recent activity.
2. For the ones drifting — no next step, or a follow-up date that's passed — read the last email and meeting to see where they stand.
3. Draft a follow-up tailored to where each stalled, and set a clear next step and date on the deal.
4. Post a pipeline digest to #sales.

Apply stage playbooks (e.g. follow up three days after a proposal is sent), and when a rep asks, re-engage a specific deal with a tailored note. Use judgment on escalation: nudge the rep for normal drift, but when a sizeable deal is past its close date with no activity and ignored nudges, flag the manager with the full history. Remember each deal's history and how each rep likes to follow up.

What would a droid take off your desk?

Tell us the job that never gets done before close. We'll wire up a droid on a call and you can watch it work.

Try now — freeBook a walkthrough