Pillar

Sales cycle length: where the time actually goes

Long cycles are usually a few long gaps, not uniform slowness. Finding the gaps is more useful than trying to go faster everywhere.

Updated October 31, 2026 · 1 article

A ninety day average cycle is rarely ninety days of steady progress. It is more often thirty days of work and sixty days of waiting, distributed unevenly across a handful of specific points.

Averages hide the problem

The average tells you almost nothing about where to intervene. Two teams with identical ninety day averages can have completely different problems: one is slow to reach the right person, the other is fast to reach them and then stuck in procurement for two months.

Measure the gaps between events, not the total. The longest gap is the one worth attacking.

The usual suspects

• Time to reach somebody who can actually decide
• Time between a demonstration and any internal discussion
• Time waiting on a budget cycle nobody asked about early
• Time in security or legal review that could have started in parallel
• Time lost re-explaining the case to a stakeholder who joined late

Reaching the right person first

The first gap is the one most under your control, and it is often the largest. Time spent working through somebody who cannot decide is not progress at a slower rate. It is a detour that ends where it started.

This is why prioritization and cycle length are the same subject. A shorter cycle usually comes from starting in a better place, not from pushing harder from a worse one.

What to measure next quarter

Record two timestamps per deal: first contact, and first conversation with somebody who has budget authority. The distance between those two is a number most teams have never looked at, and it is usually the largest single block of time in the cycle.