B2B Enterprise ABM & Demand Generation EnginePlaybook3 min readUpdated September 2026

A Fast Way to Find What's Slowing Down Your Pipeline

To find what's slowing down your pipeline, trace five recent deals from first touch to close, or to wherever they currently sit, and time each stage. Spend about thirty minutes on it before adding any spend, content or outbound. The stage that's clearly longer than the others is where to focus, and it's rarely the one people would have guessed.

Vendors Covered in this Article

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Pick Five Deals, Not Fifty

Pull five recent opportunities: two that closed won recently, two that closed lost, and one still open and stalled. Five is enough to see a pattern without turning this into a data project. For each one, note the date of first touch, the date it became a qualified opportunity, and every stage change after that. You're building a timeline, not a dashboard, so a shared spreadsheet with dates in columns is all the tooling this needs. Resist pulling in a fuller cohort until this quick pass tells you what's worth measuring at scale.

The exercise in short:

  1. Pull five recent deals: two closed won, two closed lost and one still open and stalled.
  2. For each deal, record the date of first touch, the date it became a qualified opportunity and every stage change after that.
  3. Time the gap between first touch and first real conversation, since that gap is often invisible in pipeline reports.
  4. Check whether stalled deals share a stage, and compare how fast the won and lost deals moved early on.
  5. Fix the slowest stage, then trace a fresh set of five deals a month later to confirm it sped up.

How long is the gap between first touch and first real conversation?

This gap is where B2B pipeline most often loses weeks without anyone noticing, because it happens before a deal is officially in the CRM as an opportunity and so it's invisible to most pipeline reports. A lead that downloaded something in January and didn't have a real conversation until March lost two months that no report will show you, since the clock in most systems only starts once the opportunity is created. If this gap is wide across your five deals, the fix is usually about follow-up speed and routing, not about generating more leads at the top.

Check Whether Stalled Deals Share a Common Stage

Look at your one open, stalled deal and any others you know are sitting quietly. If several deals independently stall at the same stage, for example right after a demo and before a proposal, that's a process gap, not five unrelated slow prospects. A common stall point usually means something is missing at that stage: a piece of content the rep doesn't have, a pricing conversation nobody wants to have first, or a stakeholder who hasn't been looped in yet. Fixing the shared gap moves every deal sitting behind it, which is a better use of time than pushing on any single deal.

Do your won deals move faster than your lost ones?

Look at how fast the two won deals moved compared to the two lost ones. Deals that eventually close often move noticeably faster in their early stages than deals that eventually stall out and die, even before anyone could tell which outcome was coming. If your won deals share a fast early pace and your lost ones share a slow one, that speed itself is a signal worth tracking going forward, not just a symptom, and it gives reps something concrete to watch for rather than guessing at a prospect's intent.

Use a Tool Like Apollo to Speed Up the Slowest Stage You Found

Once you know which stage is actually slow, the fix is usually narrow: faster initial routing, better contact data so the first outreach reaches the right person the first time, or a tighter follow-up cadence. A prospecting and outreach platform like Apollo helps specifically with the routing and contact-accuracy piece, which is a common culprit in the first-touch-to-conversation gap. It won't fix a stall that happens after a demo, so match the fix to the stage you actually found slow, not the stage that's easiest to buy a solution for.

Re-Trace the Same Five Deals a Month After You Fix Something

Once you've made a change aimed at the stage you found slow, don't wait for the next quarterly review to see if it worked. Pull a fresh set of five recent deals a month later and time the same stages again. If the stage you targeted sped up, you have real evidence the fix worked, worth mentioning in your next update to leadership. If it didn't move, you've learned that quickly too, which is far more useful than assuming the fix worked and discovering three months later, in the next full review, that pipeline is still just as slow as it was before you started.

Executive Capability Standard

What Good Looks Like

A team with real visibility into pipeline speed can name the specific stage where deals currently lose the most time, rather than describing pipeline as generally slow.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Learn to read stage-by-stage timestamps in your CRM well enough to trace a single deal's timeline without help.
2. Do Manually:Trace five deals by hand using the method above before investing in any tooling meant to speed up pipeline.
3. Delegate:Assign a RevOps or sales ops partner to trace a fresh cohort of deals each quarter and report back the current bottleneck.
4. Automate:Build a standing report that flags deals sitting in any stage longer than your historical median for that stage.
5. Buy:Bring in a platform such as Apollo when the bottleneck you find is specifically about contact accuracy or first-touch routing speed.

How to Get Started

Disclosure: We may earn a commission if you buy through some links on this page. It doesn't change what we recommend.

Apollo

Apollo helps when the bottleneck you trace is in the first-touch-to-conversation gap, where contact accuracy and routing speed matter most.

Visit Apollo→

Frequently Asked Questions

How many deals should we trace to trust the pattern we find?

Five is enough to spot an obvious problem worth investigating further, since a genuinely slow stage tends to show up consistently rather than in just one deal. If the pattern is subtle or the five deals disagree with each other, pull a larger sample of ten to fifteen before making any process change based on it.

What if the slow stage is on the sales side, not marketing's?

That's a common and useful finding. Marketing-sourced pipeline can stall in a stage marketing has no direct control over, like a proposal review or a legal step. The point of tracing deals isn't to prove fault, it's to find where speed is actually lost so the right team can address it, whichever team that turns out to be.

Should we run this exercise regularly or just once?

Run it once to find the current bottleneck, fix it, then re-run the same exercise a quarter later on a fresh set of deals. Bottlenecks move once you fix one, so a stage that looked fine the first time can become the new slow point after you've sped up the one before it.

About the numbers

This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.

Related Guides