Marketing Operations, MarTech Stack & Lead RoutingPlaybook3 min readUpdated September 2026

A Worksheet for Finding Where Your Pipeline Actually Slows Down

Every team has a theory about why deals move slowly. Usually the theory is wrong, because it is based on the last deal someone remembers rather than the pattern across all of them.

Build this worksheet in a spreadsheet pulling from your CRM, and let the stage-by-stage numbers tell you where the actual bottleneck is before you change your process to fix a problem you have not confirmed exists.

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.

How long do deals spend in each pipeline stage?

Pull the average number of days deals spend in each stage of your pipeline: lead to meeting booked, meeting to proposal, proposal to close. Most teams only track total sales cycle length, which hides where inside that cycle the time is actually going.

Put all the stage averages in one row of your worksheet, updated monthly. The stage with the longest average time relative to how much should logically happen there is your real bottleneck, not whichever stage feels slow because it is the one someone complained about last week.

Compare stalled deals against deals that moved fast

Add a column for deals that closed quickly and a column for deals that stalled for an unusually long time in the same stage. Look at what is different between them: deal size, who the buyer was, whether a specific stakeholder was involved, or which channel the lead originally came from.

A pattern here is worth more than any average, since it tells you which segment of your pipeline needs a different process rather than a faster version of the same one.

Which deals have no next scheduled action?

Add a formula column that flags any deal with no activity or scheduled next step logged in the CRM for more than a set number of days. A stalled deal usually is not stuck because the buyer is thinking it over; it is stuck because nobody scheduled the next conversation.

This single column often surfaces more recoverable pipeline than any messaging change, since it is pointing directly at deals that just need someone to follow up rather than deals that are genuinely cold.

Separate marketing-sourced deals from sales-sourced ones

Split your worksheet by lead source. Marketing-sourced deals and sales-sourced deals often move through the pipeline at different speeds, and averaging them together hides which one is actually dragging your overall cycle length down.

If marketing-sourced deals stall longer, look at whether those leads are being handed off with enough context for a rep to move quickly, or whether they arrive as a name and email address with nothing else to work from.

Review the worksheet monthly, not just when someone complains

The value of this worksheet comes from watching the numbers change over time, not from a single snapshot. Set a recurring monthly review where you update the stage averages and re-check the stalled-deal flag, even in months when the pipeline feels fine.

A bottleneck usually builds gradually over a few months before anyone notices it in a quarterly review. Monthly checks catch it while the fix is still a small process change instead of a quarter of missed targets.

Set up these columns in the worksheet:

  • Average days in each stage, from lead to meeting booked, meeting to proposal, and proposal to close, updated monthly.
  • A comparison of fast-closing and stalled deals alongside deal size, buyer, stakeholders involved, and original lead channel.
  • A formula that flags any deal with no logged activity or scheduled next step beyond a threshold based on your sales cycle.
  • Lead source, so marketing-sourced and sales-sourced deals can be compared instead of averaged together.
  • A distribution of deal cycle lengths, not just the mean, to reveal deals that close fast and deals that stall.

A common mistake: chasing average deal velocity, not the distribution

An average sales cycle length can look stable even while your pipeline is actually splitting into two very different populations: deals that close fast and deals that stall for a long time, canceling each other out in the average. Reporting only the average hides this split completely.

Plot the distribution of deal cycle lengths instead of just the mean, and look for a second cluster of unusually slow deals. If that cluster is growing as a share of your pipeline even while the average looks flat, you have a real, worsening bottleneck that an average-only report would let you miss for months before it shows up as a quarter you did not see coming.

Add this distribution view to the worksheet as its own tab, updated on the same monthly cadence as everything else. A widening slow cluster is worth flagging even in a month where the headline average still looks perfectly fine on its own.

Executive Capability Standard

What Good Looks Like

Solid pipeline management means tracking time spent in each stage separately, flagging deals with no next action, and reviewing the pattern monthly instead of reacting only when a quarter comes up short.

Building The Capability (5-Stage Skill Ladder)

1. Learn:Learn to pull stage-by-stage duration and a no-activity flag from your CRM's raw data rather than relying only on its default pipeline view.
2. Do Manually:Build and update the bottleneck worksheet by hand each month until the pattern of where deals stall becomes predictable.
3. Delegate:Hand the monthly worksheet update to a RevOps or marketing operations hire once the columns and thresholds are settled.
4. Automate:Automate the stage-duration and stalled-deal reporting directly inside a CRM like Pipedrive or Close so it updates without a manual pull each month.
5. Buy:Bring in a RevOps consultant when the bottleneck keeps moving between stages and your team cannot pin down a consistent root cause.

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.

Frequently Asked Questions

How many days of no activity should count as a stalled deal on the worksheet?

Set the threshold based on your typical sales cycle length rather than copying a generic number: something like two weeks for a short cycle, or a month for a longer enterprise motion. The specific number matters less than reviewing it consistently once it is set.

Should this worksheet replace our CRM's built-in pipeline reports?

No, it works alongside them. Most CRM pipeline reports show current state well but do not make stage-by-stage duration and the stalled-versus-fast comparison easy to see at a glance. The worksheet is for spotting patterns your standard reports were not built to surface.

What if marketing and sales disagree about which stage is really the bottleneck?

Let the worksheet settle it rather than opinions from either side. Pull the actual stage-by-stage averages and the stalled-deal flag for the last quarter and review them together. Data from the CRM tends to end that argument faster than another round of anecdotes.

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