First, find the stage where the time went
Compare closed deals from a recent period with closed deals from a comparable earlier one, matched as closely as you can on segment and deal size, and calculate the median days each spent in every pipeline stage. Medians matter because one enormous deal can drag an average for a year. Then do the same for open deals that are past their expected close date, since a cycle that is lengthening shows first in what has not yet closed. The result is a short table: stages down the side, earlier and recent medians across, and the difference in the last column.
Most of the increase usually sits in one or two stages, and that is the diagnosis. Time added before an opportunity is qualified suggests deals entered too early. Time added in evaluation suggests missing proof or more evaluators. Time added in approval and procurement suggests pricing and paperwork. Time added late in negotiation, especially in deals where a rival is recorded, suggests competition. Nielsen Norman Group's journey mapping primer describes laying out the phases a person goes through toward a goal, with what they do and think in each; drawing that map for the buyer's side of your slowest stage, role by role, usually shows who is waiting for what.
Diagnosis table
Diagnosis
| Symptom | Check | Likely cause | Fix |
|---|---|---|---|
| Evaluation takes longer; new names appear late in deals | Contacts engaged per opportunity, by role, against the roles in the decision | Buying group growing while marketing reaches one contact | Reach every role in the committee before and during evaluation |
| Long early stages; many deals stall soon after creation | Share of opportunities with a confirmed project, owner and timeframe at creation | Deals entered before real buying intent | Tighten opportunity entry criteria; keep early leads in nurture |
| Deals wait on security reviews, business cases or procurement | Which documents sales requests late, and how long each takes to produce | No proof for late questions | Publish answers and documents for finance, security and procurement |
| Approval stages lengthen; buyers ask for custom quotes or comparisons | Discount requests, custom quotes and pricing questions per deal | Pricing and packaging hard to compare or approve | Simplify tiers and publish pricing logic the approver can follow |
| Negotiation stretches in deals where a rival is recorded | Share of opportunities with a named competitor, and their stage times | Competitors present in more deals | Equip sales with current, honest competitive answers |
Fix, verify and prevent each cause
More people deciding, and marketing still talking to one
When a purchase gets more expensive or riskier, more roles join it: finance, security, procurement, the user team's manager. If marketing and sales have only ever engaged the original champion, each new role arrives late, starts its own evaluation from zero and adds weeks.
Fix: count, for open opportunities, which roles have engaged with anything you produced, and plan reach to the missing ones before evaluation rather than during it. The account-based marketing guide covers how to map and reach a committee; the diagnostic point here is to compare the roles engaged with the roles that sign.
Verify: the number of roles engaged per opportunity rises, and fewer deals show a new decision-maker appearing in the final stages.
Prevent: record the committee's roles at opportunity creation and review coverage in the weekly pipeline meeting, not only at forecast time. The weekly pipeline review tutorial sets that meeting up so each stuck deal leaves with one action and an owner.
Opportunities opened before a project exists
A cycle measured from opportunity creation lengthens if opportunities are opened earlier. When a salesperson creates a deal after a friendly first call, or marketing's qualification rule passes readers as buyers, the clock starts before the buyer has a budget, an owner or a date, and the early stages fill with deals that are really nurture.
Fix: tighten the entry criteria for an opportunity along the lines of the lead stages guide: a confirmed need, a named owner and a plausible timeframe recorded in fields, with anything short of that kept as a lead or returned to marketing.
Verify: time in the first opportunity stage falls, the share of opportunities closed as "no decision" falls, and the win rateShare of closed sales opportunities that were won. of what remains rises.
Prevent: make the entry fields required at the stage change, and read cycle length only on opportunities that met them.
Late questions nobody prepared answers for
Deals often stall in the last third, when security, legal, procurement and finance ask their questions. If the answers have to be written from scratch for each deal, the buyer waits, and some lose momentum altogether.
Fix: build the late-stage material the business-to-business content guide lists for those roles: security and architecture documentation, standard terms and data-processing pages, a business case template and reference customers by sector. Strategyzer's Value Proposition Canvas is a useful check here: each role has its own jobs, pains and gains, and proof that answers the champion's pains does nothing for procurement's.
Verify: the time between a security or procurement request and its answer shortens, and fewer deals record "waiting on documentation" as their reason for slipping.
Prevent: ask sales monthly which questions arrived late in deals, and add the answer to the library the same month. The late-stage deal content guide covers building that library: a business case kit, an owned security and data protection answer library, a procurement pack and a process for requests for proposal.
Prices that are hard to compare or approve
An approver who cannot see what is included, how the price will grow or how it compares with the alternatives will ask for a custom quote, a comparison or a meeting, and each request adds a cycle of waiting. Complicated tiers and unexplained add-ons also invite negotiation.
Fix: review the packaging against the pricing and packaging guide: tiers that follow segments, fences that follow value, and a pricing page or proposal that shows what each option costs and how the bill grows. Give sales packaging options that solve a budget problem without a discount.
Verify: custom quote requests and pricing questions per deal fall, and the approval stage shortens.
Prevent: record the pricing questions buyers ask in the opportunity, and review them with product marketing each quarter. The tutorial on running a pricing and packaging review shows where those recorded questions sit beside discounts, lost deals and tier mix when the packaging is reviewed.
A competitor in more of your deals
A rival that appears in more deals adds comparison work to each one: another demo, another reference, another round of objections. If sales has no current answer to that rival's claims, the buyer slows down to resolve the doubt themselves.
Fix: check the share of opportunities with a named competitor and the stage times in those deals, then build or refresh the card for that rival as the competitive battlecards guide describes, with honest reasons for losses and questions that bring real differences into the evaluation.
Verify: stage times in deals against that rival fall toward the rest, and the win rate against them holds or rises.
Prevent: make the competitor field required at opportunity creation, so the trend is visible before it shows in the cycle.
A prevention routine for deal velocity
Cycle length is a lagging measure, so the routine watches what precedes it. Monthly, read median days in each stage for opportunities created in recent months, alongside the number of roles engaged per opportunity and the share with a named competitor. Monthly too, collect from sales the questions that arrived late and the documents that were requested and missing, and treat each one as a content gap with an owner and a date. Quarterly, compare closed-deal stage times with the previous quarter and the same quarter last year, by segment, and read lost and no-decision reasons for the deals that took longest. Keep the opportunity entry criteria, the committee roles and the competitor field required in the CRM, because the routine is only as good as those fields. Review the pricing page and proposal template with product marketing at the same quarterly session, using the pricing questions buyers asked. When the cycle does lengthen, look first at the newest change: a new segment, a larger deal size, a new competitor, a pricing change or a looser opportunity rule explains most increases. Report cycle length beside win rate and deal size, since a cycle that lengthens while deals grow is a different story from one that lengthens while deals shrink, and read all three across the whole FunnelModel of the customer journey stages. rather than for the final stages alone.
A facilities software vendor finds its slow stage
A facilities management software vendor saw its median cycle rise from 94 to 131 days over a year. Stage medians showed that discovery had barely changed, while the security and procurement stage had grown from 12 to 41 days. In 23 of the 30 slowest deals, the buyer had sent a security questionnaire that the solutions team answered from scratch, taking about three weeks each, and 14 of those deals had added an IT security reviewer after evaluation began. The vendor published a security and architecture document set, a standard data-processing page and pre-answered questionnaires for the two most common formats, and began engaging IT roles during evaluation with a short technical briefing. Over the next two quarters the security and procurement stage fell to a median of 18 days and the overall cycle to 104 days.
Common mistakes
Reading an average cycle that one huge deal distorts. Blaming the economy before measuring stage times. Opening opportunities after a first friendly call. Writing security answers from scratch for every deal. Pulling deals forward with discounts that teach buyers to wait. Updating the battlecard once a year. Judging the cycle without win rate and deal size beside it.
