How long does a B2B sales cycle actually take?

TL;DR

• Sales cycle scales with ACV. Under $10K ACV: 14-30 days. $10-50K: 30-90 days. $50-250K: 90-180 days. $250K+: 180-365 days. $1M+: 365-540 days.
• Cycle starts at first meeting, not at first cold-email send. The pre-meeting timeline (cold outreach → meeting booked) adds 2-4 weeks on top.
• Industry adds variance. Regulated industries (healthcare, finance, government) are 1.5-3× longer than the segment average. Dev tools are typically faster than the average.
• Procurement, security review, and legal redlines drive most of the variance, not sales execution.
• Your first 10-20 deals will be faster than your steady-state cycle. They’re founder-sold to warm relationships and skip stages.
• If you’re planning runway: assume cycle length 1.5× what the data says. The slip is always longer than the projection.

How sales cycle is measured

The standard definition of sales cycle length, in B2B SaaS, is the time from first meeting (the discovery call) to closed-won (signed contract). It does not include the prospecting time (cold outreach, meeting booking) or the post-close implementation time.

This matters for planning. The numbers below are post-first-meeting cycle length. To get the full lead-to-revenue cycle, add:

• Pre-meeting: 2-4 weeks from first cold touch to booked meeting (faster for warm, longer for fully-cold)
• Sales cycle: the numbers in this chapter
• Implementation/onboarding: typically 2-12 weeks depending on product complexity

Cash-collection cycles are separate and depend on payment terms (Net 30/60/90 dominant). For SaaS pricing math, bookings count at signing; cash arrives later.

Sales cycle by ACV

ACV is the single best predictor of cycle length. The relationship is roughly logarithmic — each 10× increase in ACV roughly doubles cycle length. The reason: higher ACV deals require more stakeholders, more security/procurement review, and more business-case justification.

By industry — where the averages don’t hold

The ACV table is a rough average across B2B SaaS. Specific industries deviate predictably:

• Dev tools, productivity SaaS, API tools: 30-50% faster than the ACV average. Technical buyers can self-evaluate, procurement is lighter, security review is more lightweight at typical buyer companies.
• Marketing/sales SaaS: roughly at the average. Familiar buying motion, predictable procurement.
• Healthcare / health-tech: 1.5-2.5× longer than the ACV average. HIPAA review, IT security review, often 2-3 month BAA negotiation, and slower internal procurement.
• Financial services: 1.5-2× longer. SOC 2, vendor risk management, often a security review board that meets monthly.
• Government and public sector: 2-4× longer. FedRAMP, FISMA, ATO processes, multi-year budget cycles. A typical fed deal is 12-24 months from first meeting.
• Manufacturing and industrial: 1.3-2× longer. Conservative buyers, longer evaluation cycles, often requires on-site demos.
• Education (K-12 and higher ed): 2-3× longer. Budget cycles aligned to academic year, multiple stakeholders, slow procurement.

If your ICP is in one of the slower industries, the comp plan math (see AE compensation) shifts — longer cycles mean longer ramp guarantees, higher base/variable splits, and more capital required to sustain the motion.

By company stage of the buyer

The buyer’s company stage matters as much as their ACV. The same $50K deal closes at different speeds depending on who’s buying it:

• Startup (Series A-B buyer): 30-60 days. Founders or early VPs as buyers, light procurement, fast decisions.
• Mid-stage (Series C-D buyer): 60-120 days. Established procurement function, basic security review, multiple stakeholders.
• Late-stage / public (Series E+ or public buyer): 120-240 days. Mature procurement, formal vendor risk, often 60+ day security questionnaire response.
• Enterprise (Fortune 1000): 180-365+ days. Multi-tier procurement, full security review, legal redlines, often master services agreement negotiation.

The implication for early-stage founders: if you’re selling $50K deals, your cycle math is very different selling to other startups than selling to enterprise buyers. Pick the segment, plan to the cycle, and don’t mix the two in the same forecasting model.

The stage-by-stage breakdown

The post-first-meeting sales cycle, for a typical mid-market deal ($50K ACV, ~90-day cycle), breaks down roughly as:

Three of those stages — security review, procurement, and the internal business case — are almost entirely outside the seller’s control. Together they account for 60-80% of the cycle’s length. Sellers who try to compress the sales cycle by “running a better demo” are optimizing the wrong stage.

Why your first deals are faster than your steady-state cycle

Founders consistently project cycle length based on their first 5-10 closed deals and end up wrong. The first deals are almost always faster than the steady state because:

• Warm relationships. The first 10-20 customers are almost always sold to people the founder knows or who came through warm intro. These bypass cold-to-meeting time and shortcut procurement.
• Smaller deals. Early customers are often at the lower end of ACV range, where cycle is faster.
• Stage-skipping. Founders selling to friends skip multi-thread, security review, and sometimes even procurement (champion pushes deal through informally).
• Pre-PMF urgency. Early adopters move faster than mainstream buyers because they have a specific problem and lower switching costs.

The honest planning move: take your closed-deal average cycle, multiply by 1.5-2×, and use that for forecasting. The first 20 deals are not representative of what your sales motion looks like at $5M ARR and beyond.

What drives cycle slippage

The deal you forecast for 60 days that takes 120 days didn’t fail at execution. It failed at one of four predictable points:

• Champion change: the buyer-side advocate left, switched roles, or lost political power. This kills more deals than every other reason combined. Multi-threading (see multi-thread strategy) is the prevention.
• Budget freeze or reallocation: the buyer’s budget got cut or redirected mid-cycle. Common in Q4 and during macro tightening.
• Security review extension: SOC 2 questionnaires that come back in 6 weeks instead of 2, or a follow-up review triggered by a finding.
• Legal redlines: an MSA negotiation that adds 3-8 weeks because the buyer’s legal team is slow or because the contract has problematic clauses.

The forecast discipline: every active deal should have a explicit cycle expectation. When a deal blows past 1.5× its expected cycle, that’s your signal to investigate, multi-thread harder, or down-grade the forecast probability.

What this means for pipeline planning

Cycle length determines how much pipeline you need to hold to forecast a given quarter’s revenue. The math:

• Pipeline coverage ratio (typical): 3-5× target revenue for the quarter.
• Pipeline build-ahead: pipeline for Q3 close has to be sourced by start of Q2 if your cycle is 90 days; by start of Q1 if your cycle is 180 days.
• Forecast horizon: AEs should have full pipeline visibility for the current quarter and rough sight for the next quarter at minimum.

The most common pipeline planning mistake at early-stage startups: building pipeline in Q2 to hit Q2 revenue. With anything but a sub-30-day cycle, that’s already too late. Pipeline for a 90-day cycle has to be built in the prior quarter; pipeline for an enterprise 180-day cycle has to be built two quarters out.

How to compress the cycle (and what won’t)

Things that actually compress cycle:

• Pre-existing SOC 2 Type II: removes 2-4 weeks of security review.
• Standard MSA available in advance: short-circuits 1-3 weeks of contract negotiation.
• Multi-thread early: getting to 3+ stakeholders by week 3 of the cycle reduces champion-change risk and parallelizes internal selling.
• Annual contracts only (no monthly): removes some procurement complexity at the cost of higher upfront commitment.
• Targeting smaller buyer companies: the buyer’s company stage drives cycle as much as ACV. A $50K deal at a Series A startup closes in 45 days; the same deal at a Fortune 500 takes 9+ months.

Things that don’t compress cycle (and that founders waste time on):

• “Better” demos: shaving demo time saves 1-2 weeks against a 90-day cycle. Marginal.
• Discount pressure: offering a discount for “close this week” rarely actually closes the deal this week. Procurement still takes its time; you’ve just left money on the table.
• Quarterly close pressure: rarely accelerates buyer-side timelines and often poisons the relationship.

Where this fits

Cycle length is the input to pipeline math, AE quota setting, and runway planning. It’s also the input to comp planning — see AE compensation for how cycle length determines ramp guarantees and base/variable splits. The downstream chapter is pipeline conversion math, which takes the meetings-booked-per-week math and converts it through the cycle into quarterly closed-won.

The single most useful diagnostic: track your own cycle length per closed deal, segment by ACV and buyer-company-stage, and update your forecasting model quarterly. The benchmarks in this chapter are starting points; your own data is the real signal.