When a RevOps team asks "what's a normal sales cycle for our type of deal?" and the answer is "depends on a lot of factors," that's technically correct and practically useless. The actual variables deal velocity depends on are specific and measurable. The problem isn't that there are too many of them to track — it's that most teams don't track them, so they can't set meaningful benchmarks for their own business.
Published industry benchmarks for deal velocity — "B2B SaaS average sales cycle is 84 days" — are averages across extremely heterogeneous deal populations. An 84-day average includes a $12K/year SMB deal closed by an inside rep in three weeks and a $400K enterprise contract that took six months and two CFO approvals. Averaging those is mathematically valid and operationally meaningless for your specific pipeline.
The Variables That Determine Your Deal Velocity
Deal velocity varies primarily along five dimensions. Getting your internal benchmarks right requires segmenting along all five, which sounds onerous but is usually manageable with two or three cuts:
- ACV band: This is the most significant driver of cycle length. In a typical B2B SaaS environment, deals under $25K annual contract value close in roughly a third of the time it takes deals over $100K to close. The underlying reason is stakeholder count: sub-$25K deals often fall within a single budget holder's discretionary authority; $100K+ deals typically require VP-level sign-off plus procurement involvement plus (often) a legal review of the contract.
- Market segment: SMB, mid-market, and enterprise have structurally different buying processes. Enterprise deals have more stakeholders, formal procurement cycles, security reviews, and vendor approval processes. These add time regardless of deal quality. A mid-market deal of the same ACV will typically close faster than an enterprise deal, all else equal.
- Sales motion: Inbound-led deals close faster than outbound-led deals of the same size, on average, because the buyer self-identified an active need. A prospect who came to your website, requested a demo, and has a specific implementation deadline is in a different velocity category than a prospect your rep cold-outreached in the same ACV range.
- Buying trigger: Deals with an explicit, time-bound buying trigger (a compliance deadline, a contract renewal with an existing vendor, a board-driven initiative with a stated launch date) close faster than deals where the prospect is evaluating opportunistically. The trigger creates urgency that is exogenous to your sales process.
- Competitive landscape: Deals with no competitive evaluation are faster than deals in a four-way bake-off. When a prospect is evaluating three vendors simultaneously, your cycle length is constrained by their evaluation timeline, not yours.
What Your Internal Benchmarks Should Look Like
Rather than a single "average days to close" number, a useful internal velocity benchmark has three layers:
Layer 1: Total cycle time by ACV segment. The median and 75th percentile of days from opportunity creation to close, for each ACV band you sell into. Three bands is usually sufficient: sub-$30K, $30K–$100K, $100K+. The 75th percentile matters because it's your "if this deal takes this long, it's a genuine outlier" threshold.
Layer 2: Time-in-stage by stage and ACV segment. Where are deals actually spending time? A deal that takes 120 days might spend 10 days in Discovery, 15 in Technical Review, and 90 days in Legal/Procurement — meaning 75% of the cycle is outside your team's direct control. Knowing this changes how you forecast. You need to build legal and procurement time into your close date estimates, not add it on as a surprise at the end.
Layer 3: Velocity deviation as a risk signal. Once you have a baseline, stage duration at 1.5x historical average is an early warning. At 2x, it's a deal health issue. At 3x, the deal is probably lost or fundamentally paused and shouldn't be in forecast.
A Concrete Example: Segmenting Velocity at a Mid-Size Vendor
A 75-person B2B SaaS company in the data governance space ran a 24-month historical analysis of their closed-won and closed-lost deals. Before the analysis, their RevOps team estimated an "average cycle" of around 60 days. The segmented reality:
- Sub-$20K deals: median 28 days, 75th percentile 45 days
- $20K–$80K deals: median 67 days, 75th percentile 105 days
- $80K+ deals: median 134 days, 75th percentile 210 days
The 60-day average was almost exactly wrong for every segment. Their pipeline review had been using 60 days as the baseline for all forecast calls, which caused them to persistently overestimate which large deals would close in a given quarter. Once they switched to segment-specific benchmarks, their quarterly forecast accuracy improved substantially — not because the deals changed, but because they stopped expecting $100K deals to behave like $20K deals.
Red Flags Specific to Deal Velocity
A few velocity-related patterns that reliably correlate with deal risk in B2B SaaS sales cycles:
- Close date extensions without stage change: When a close date gets pushed but the deal doesn't move backward in stage, it often means the rep is updating the calendar but not acknowledging a substantive change in deal status. Three consecutive close date extensions of the same deal are a strong signal that the stated close date is aspirational, not informed.
- Discovery stage stalling: Deals that spend more than 2x the historical average in discovery are often stuck on qualification — the rep hasn't confirmed a real economic buyer or a compelling event. That's not a velocity problem, it's a qualification problem, but it shows up in velocity data first.
- Post-proposal silence: The period after a proposal is sent is one of the highest-churn moments in B2B SaaS deals. Deals where the prospect goes more than 10 business days without responding post-proposal have meaningfully lower close rates than deals with continued engagement. This is not unique to any particular deal size.
The Limitations of External Benchmarks
This is not to say that external benchmarks have no value. They're useful as sanity checks — if your sub-$25K deal average close time is 150 days, something structural is wrong with your sales process relative to peers. That's worth investigating. But external benchmarks should only trigger the question, not answer it. Your specific product complexity, your buyers' procurement maturity, and your team's sales motion all shape what "normal" looks like for you.
The most useful benchmark is always an internal one: your own historical closed-won deals, segmented by deal characteristics, analyzed to find what the actual distribution of velocity looks like across your customer base. That data is sitting in your CRM. The question is whether you've looked at it carefully enough to use it.
Once you have internal benchmarks in place, deal velocity becomes a real-time forecast input — a way of knowing, six weeks before quarter end, which deals are on a trajectory consistent with closing in time and which are already showing the velocity signature of a push.