FRACTIONAL CRO · MARYLAND-BASED, NATIONWIDE · $0→$200M

Kory White

RevOps & Revenue Leadership

Get a free 30-minute revenue checkup — Kory reviews your pipeline and forecast, then names the 1–2 fixes that move revenue fastest. 25 yrs scaling teams $0→$200M.

Free 30-min revenue checkup →
Hire a Fractional CROHow We Help?LinkedInRésuméCRO Syndicate
← Library
Knowledge Library · pulse-reviews
13/13 Gate✓ IQ Certified10/10?

Pipeline Aging Heatmap

GraphicsPipeline Aging Heatmap
📖 2,401 words🗓️ Published Jun 21, 2026 · Updated Jun 3, 2026
Direct Answer

A pipeline aging heatmap is a sales-management visualization that color-codes every open deal by how long it has been sitting in its current pipeline stage. Deals are arranged in a grid — typically stages across one axis and days-in-stage buckets along the other — and each cell is shaded on a gradient from green (moving on schedule) to red (stalled and at risk). The point is to surface stuck deals at a glance: instead of scrolling a CRM list, a manager can see which stages are clogged, which reps are carrying dead weight, and which opportunities need intervention before they quietly slip out of the forecast. Thresholds are not universal — a healthy "discovery" stage might allow 7 days while "procurement" allows 30 — so the bands should be set from your own historical cycle data rather than copied from a template.

Pipeline Aging Heatmap

Heatmap showing deals by stage and days-in-stage, with red flagging stale deals over 60 days.

Format: SVG (scalable vector) · Size: 1584×396 px · Category: Chart · License: Free to use — no attribution required.

[⬇ Download this graphic](/graphics/assets/gb0509.svg)

flowchart TD A[CRM Deal Records] --> B[Calculate Days in Current Stage] B --> C[Compare to Stage Benchmark] C --> D[Assign Color Band] D --> E[Render Stage by Age Grid] E --> F[Trigger Stale Deal Alerts] F --> G[Manager Review and Next Step]
flowchart TD A[Days in Current Stage] --> B{How long} B -->|0 to 14 days| C[Green - Maintain Momentum] B -->|15 to 30 days| D[Yellow - Re-engage and Re-qualify] B -->|31 to 45 days| E[Orange - Escalate and Create Urgency] B -->|46 plus days| F[Red - Salvage or Close Lost]

Recolor it to your brand

Use the color picker above to recolor this graphic to your team or company colors, switch the background (including transparent), then download it as an SVG or PNG. No sign-up, no watermark.

How to use it

The SVG scales to any size with no quality loss — drop it straight into PowerPoint, Google Slides, Canva, Figma, or a LinkedIn banner slot. The PNG export is ready to upload anywhere that wants a raster image.

More free graphics

Browse the full [Pulse Graphics library](/graphics) — banners, slides, printables, quote cards, and clip art you can borrow for your own decks and posts.

Related on PULSE

How to Read a Pipeline Aging Heatmap: Spotting the Signals Before They Become Problems

A pipeline aging heatmap is more than a colorful grid — it's a diagnostic tool that reveals the health of your sales process at a glance. The color coding (green, yellow, orange, red) maps to the number of days a deal has lingered in a given stage. The key is learning to interpret the patterns, not just the colors.

Green (0–14 days in stage) indicates healthy velocity — deals moving as expected with active engagement on both sides. Yellow (15–30 days) is a caution signal: still alive, but momentum may be slipping. Orange (31–45 days) suggests a deal that's stalling, often due to procurement delays, budget freezes, or a champion who's gone quiet. Red (46+ days) is a critical warning: high risk of churn or being overtaken by a competitor. Treat these bands as illustrative defaults; calibrate the exact cutoffs to your own stage-level cycle times.

The most valuable insight comes from comparing stages. If your demo stage is consistently yellow or orange but your negotiation stage is green, that points to a qualification or discovery problem — reps are pushing unqualified leads into demos, then struggling to advance them. Conversely, if demos are green but negotiation is red, the issue is likely pricing, contract complexity, or a mismatch between your solution and the buyer's budget.

A common blind spot is the "dead zone" — deals that sit in a stage for 60+ days but are still marked "open." These often represent opportunities that should be closed-lost but are kept alive for pipeline optics. A good rule of thumb: any deal beyond 45 days in a stage should trigger an automatic review by the sales manager or deal desk. Some teams set a hard cutoff at 60 days, after which the deal moves to a "stalled" category unless the rep provides a written justification with a specific next step and date.

Another pattern to watch for is "stage hopping" — deals that bounce back and forth between stages (e.g., from negotiation back to discovery). This often indicates scope creep, a lost champion, or a buyer restarting their evaluation. A heatmap showing multiple red cells for the same deal across different stages is a strong signal the deal is unlikely to close.

To make the heatmap actionable, pair it with a velocity metric: average days per stage for won deals versus lost deals. If your won deals average 10 days in demo but your current heatmap shows 25 days in demo for active deals, you have a leading indicator of lower win rates ahead. That lets you intervene before deals turn red — for example, by scheduling a call with the economic buyer or sending a case study that addresses a specific objection.

Common Pipeline Aging Heatmap Pitfalls and How to Avoid Them

Even experienced sales leaders misread a pipeline aging heatmap. Here are the most frequent mistakes and how to correct them.

Pitfall 1: Treating all red as equal. A deal that's been red for 10 days is very different from one red for 60 days. Instead of a single "red" threshold, use graduated alerts: orange at 31 days, red at 46 days, and "critical" at 60+ days. This prevents overreacting to deals that are merely slow versus those that are truly stuck.

Pitfall 2: Ignoring stage-specific benchmarks. A 30-day stay in "proposal" may be normal for enterprise deals with complex procurement, but the same duration in "discovery" is a red flag. Set different aging thresholds per stage based on your historical data. For example:

Review these benchmarks quarterly and adjust them to your average deal-cycle length.

Pitfall 3: Focusing only on the oldest deals. It's tempting to fixate on the reddest cells, but the most impactful saves often come from catching deals in the yellow zone. A deal that's been in demo for 20 days can frequently be rescued with a simple follow-up or value-add asset. Once it's red, the buyer may already have gone dark or chosen another vendor. Set automated alerts for any deal crossing the 20-day mark in any stage, not just the 45-day threshold.

Pitfall 4: Using the heatmap in isolation. It tells you *where* deals are stuck, not *why*. Always cross-reference deal notes, activity logs, and call recordings. A deal red in negotiation might be waiting on external legal review (often unavoidable), while a deal red in discovery is likely a qualification failure. Without context, you risk misdiagnosing the problem.

Pitfall 5: Not segmenting by deal size or buyer persona. A $50k deal in proposal for 30 days is very different from a $500k deal in the same stage — larger deals naturally take longer. Create separate heatmaps (or filters) for deal tiers: SMB (under $50k), mid-market ($50k–$250k), and enterprise ($250k+), each with its own aging thresholds. Likewise, segment by persona — a CFO-led deal moves differently than a department-head-led one.

Pitfall 6: Over-reliance on manual updates. If reps must manually update stages, the heatmap will always lag reality. Integrate your CRM with calendar and email to detect stage changes from meeting types, document sends, or signatures. If a rep sends a proposal via your CPQ tool, the deal should auto-advance to "proposal." That keeps the heatmap accurate without adding admin burden.

Pitfall 7: Ignoring the "ghost deals." These appear on the heatmap but have no recent activity — no calls, emails, or meetings in the last 14 days. They're effectively dead but never closed out. Run a weekly report flagging any deal in a stage more than 21 days with zero logged activity in the last 14, and require reps to either schedule a next step or move it to closed-lost.

Actionable Playbooks for Each Pipeline Aging Heatmap Zone

Once you know where deals are aging, you need a playbook for each zone. These aren't one-size-fits-all — tune them to your sales cycle — but they give you a starting framework.

Green Zone Playbook (0–14 days): Maintain momentum

Yellow Zone Playbook (15–30 days): Re-engage and re-qualify

Orange Zone Playbook (31–45 days): Escalate and create urgency

Red Zone Playbook (46+ days): Salvage or close-lost

Sources

FAQ

What is a Pipeline Aging Heatmap? A pipeline aging heatmap is a color-coded grid that shows how long each open deal has sat in its current sales-pipeline stage. By shading cells from green to red based on days-in-stage, it lets teams spot stalled opportunities instantly and prioritize action by deal age and stage.

How do I interpret the colors on the heatmap? Green means a deal is progressing within the expected window, yellow warns it's starting to age, orange signals real stalling, and red flags a deal that's stuck and at risk. A common four-band default is 0–14 days (green), 15–30 (yellow), 31–45 (orange), and 46+ (red) — but you should calibrate those cutoffs to your own stage-level cycle times rather than treat them as fixed.

What data do I need to create this heatmap? At minimum, CRM records with each deal's current stage, the date it entered that stage, and its last activity date. To set meaningful color bands you also need stage-specific aging thresholds derived from your historical close rates and average days per stage.

How often should I update the heatmap? Most teams refresh it weekly or bi-weekly — frequent enough to catch trends without flooding managers with noise. Fast-moving, high-volume pipelines may justify daily updates, but weekly is the common sweet spot. Wherever possible, automate stage updates so the heatmap reflects reality instead of lagging behind manual data entry.

Can this heatmap predict which deals will close? It isn't a predictive model, but it's a strong early-warning system. Deals that age past your typical stage duration are statistically less likely to close, so the heatmap highlights which opportunities need intervention now — pair it with a win/loss velocity metric for sharper signal.

What's the best way to act on a red deal in the heatmap? Run a focused review with the rep to diagnose the stall — common causes are no access to the decision-maker, unresolved objections, or budget delays. Set one clear next step with a deadline and an owner, and if there's no progress within about two weeks, either move the deal to a nurture track or close it lost with a reason code so your data stays clean.

Download:
Was this helpful?  
⌬ Apply this in PULSE
How-To · SaaS ChurnSilent revenue killer playbook