Automate Deal Velocity Tracker — Weekly Pipeline Speed Benchmark in n8n — Step by Step
Your sales pipeline has a number hiding inside it that almost nobody tracks: how many days it actually takes a deal to go from created to closed-won. Not the number your CRM guesses. The real one, mea
Your sales pipeline has a number hiding inside it that almost nobody tracks: how many days it actually takes a deal to go from created to closed-won. Not the number your CRM guesses. The real one, measured from your own history. Without that benchmark, "this deal is stalling" is a gut feeling — and gut feelings don't get flagged, escalated, or rescued. They just quietly rot in stage three until the quarter ends. This article walks through building a Deal Velocity Tracker in n8n that computes your average days-to-close from actual won deals, then automatically flags every open deal that has aged past 1.5x that baseline. It runs weekly, posts to Slack, and costs nothing but the fifteen minutes it takes to wire up.
The Problem: Velocity Is Invisible Until It's Too Late
Every CRM shows you deal age. Almost none show you deal age relative to what normal looks like for you. A 40-day-old deal is fine if your average sales cycle is 60 days. It's an emergency if your average is 22 days. The same raw number means opposite things, and reps have no way to tell which situation they're in without doing math nobody does.
The result is predictable. Deals stall silently. A prospect goes quiet, the rep gets busy, and the opportunity sits in "Proposal Sent" for six weeks past your typical close window. By the time someone notices during a pipeline review, the momentum is dead and the deal is unrecoverable. Manual pipeline audits catch some of these, but they're slow, subjective, and happen too late. You need a system that computes your real baseline and screams the moment a deal drifts 50% beyond it — every week, automatically, with zero human effort.
The math itself is trivial. The hard part is doing it consistently, pulling clean data from your CRM, and delivering the alert somewhere people actually look. That's exactly what n8n is built for.
The Solution: A Self-Calibrating Benchmark That Runs Itself
The Deal Velocity Tracker works in two passes over your pipeline data. First, it looks at deals already closed-won and calculates the average number of days each took from creation to close — that's your velocity baseline, derived from your own performance rather than an industry guess. Second, it walks every open deal, computes its current age, and compares it to the baseline. Any open deal older than baseline × 1.5 gets flagged as stalled.
Because the baseline is recalculated on every run, the system self-calibrates. If your team gets faster, the threshold tightens automatically. If a seasonal slowdown lengthens cycles, the benchmark absorbs it. You never hand-tune a "deals older than X days" rule that goes stale the moment your sales motion changes. The workflow then formats the flagged deals into a clean digest and pushes it to Slack or email every Monday morning, so pipeline hygiene becomes a standing ritual instead of a heroic quarterly cleanup.
Step-by-Step: Building It in n8n
Here's the full node chain. It assumes a HubSpot or Pipedrive CRM, but the logic is identical for any source that returns deal records with a created date, a close date, and a status.
1. Schedule Trigger. Add a Schedule Trigger node set to a weekly cron — 0 8 * * 1 fires every Monday at 8:00 AM. This is your recurring heartbeat; everything downstream runs on this cadence.
2. Fetch won deals. Add your CRM node (HubSpot → Get All Deals or Pipedrive → Get All Deals). Filter by dealstage = closedwon and set a lookback window — the last 90 days of won deals gives a stable, recent baseline. Enable Return All or paginate so you capture the full set, not just the first page.
3. Compute the baseline. Add a Code node (JavaScript). Iterate the won deals, and for each one calculate days-to-close as (closedate - createdate) / 86400000. Average the results:
const days = items.map(i => (new Date(i.json.closedate) - new Date(i.json.createdate)) / 86400000); const baseline = days.reduce((a,b)=>a+b,0) / days.length; return [{ json: { baseline: Math.round(baseline), threshold: baseline * 1.5 } }];
This node outputs a single item carrying your baseline and the 1.5x stall threshold, which the rest of the workflow references.
4. Fetch open deals. Add a second CRM Get All Deals node, this time filtering for open stages (anything that isn't closed-won or closed-lost). These are the deals you'll test against the threshold.
5. Flag the stalled ones. Add a Code node (or a Filter node if you prefer no-code). For each open deal, compute its current age as (now - createdate) / 86400000 and keep only those where age exceeds the threshold from step 3. Reference the baseline with an expression like $('Compute Baseline').first().json.threshold. Attach the deal name, owner, current age, and how many days it's overdue so the alert is actionable, not just a count.
6. Format and deliver. Add a Set or Code node to build a readable digest — one line per stalled deal: name, owner, age vs. baseline. Then add a Slack → Send Message node (or Send Email / Gmail) pointed at your sales channel. Use an IF node before delivery so the workflow only pings the channel when at least one deal is flagged — nobody wants a "0 stalled deals" ping every week, but a silent all-clear is fine.
Save, run once manually to sanity-check the numbers against a deal you know is stuck, then activate. From that point it runs untouched every Monday.
The Benefits: What Changes When Velocity Becomes Visible
The obvious win is early rescue. Deals get flagged while there's still time to act — a re-engagement call, a discount nudge, a decision-maker escalation — instead of being discovered dead. But the second-order effects matter more. Managers get a weekly, objective read on pipeline health that isn't filtered through rep optimism. Forecasting sharpens, because a deal that's 1.5x past baseline is statistically far less likely to close on time, and you can weight your projections accordingly.
It also creates accountability without micromanagement. Nobody has to nag reps about aging deals; the system surfaces them, and the rep owns the follow-up. Because the benchmark is computed from real data, it's hard to argue with — it's not a manager's arbitrary rule, it's the team's own historical average. And since the whole thing runs on n8n rather than a paid analytics add-on, it works with whatever CRM you already have and costs nothing to operate month over month.
Common Pitfalls and How to Avoid Them
Dirty date fields. The single biggest failure mode is bad timestamps. Deals created via import sometimes carry a bulk-load date instead of the real origination date, which corrupts your baseline. Add a sanity filter in the baseline node to drop deals with a days-to-close under 1 or absurdly over 365 — these are almost always data artifacts, and one outlier can drag your average badly.
Too small a sample. If you've only closed three deals in your lookback window, the baseline is noise. Guard against it: if the won-deal count is below a floor (say 8–10), have the Code node fall back to a wider lookback or skip the run and post a "not enough data" note rather than flagging deals against a meaningless benchmark.
Mixing deal types. Enterprise and SMB deals often have wildly different cycles. Averaging them together produces a threshold that's too loose for fast deals and too tight for slow ones. If you sell across segments, split the workflow by deal type or pipeline and compute a separate baseline for each — n8n handles this cleanly with a Switch node routing to parallel baseline calculations.
Pagination silently truncating data. CRM nodes often return only the first 100 records by default. If you forget Return All, your baseline is built from a partial, non-representative slice. Always verify the count your fetch nodes return matches what your CRM reports.
Alert fatigue. If everything gets flagged, nothing gets acted on. Start at 1.5x, watch the volume for two weeks, and tune. A healthy digest surfaces a handful of genuinely stuck deals — not half your pipeline. If the list is huge, your baseline is probably too short or your pipeline genuinely needs a cleanup before the weekly cadence can keep it healthy.
Ja construimos isso pra voce
Nao comece do zero. O Deal Velocity Tracker — Weekly Pipeline Speed Benchmark e um workflow n8n pronto para instalar — conecta suas ferramentas em minutos, sem codigo.
Instalar por $79 →
