The honest answer to "how long is the average B2B sales cycle" is that nobody has measured it well, and the number you have probably seen quoted comes from a single vendor's own CRM dataset. The defensible range for B2B SaaS is roughly two to six months, widening to nine months and beyond above $250K ACV, and the spread inside that range is driven almost entirely by deal size and buying-committee size rather than by industry.
This post gives you three things. The benchmarks that exist, each traced to the organisation that actually published it. A plain account of where the most-quoted figures come from and how much weight they hold. And the six levers we deploy when a client asks us to take time out of their cycle.
We rebuilt this page in September 2026 because the previous version quoted a median and a mean without saying who measured them. That was our own rule broken on our own site, and the fix was to go and find out.
How long is the average B2B sales cycle?
There is no single authoritative figure. Here is every benchmark we could trace to a named publisher, with what it actually measures.
| Figure | What it measures | Who published it | How much weight it holds |
|---|---|---|---|
| 84 days median | B2B SaaS deal creation to close | Optifai, from anonymised CRM exports across 939 B2B companies, Q1 to Q3 2025 | One vendor's own customer base, not independently replicated |
| 2.1 months (about 64 days) | Self-reported typical time to close | Databox, survey of 65 B2B companies and agencies | Small sample, self-reported, but the methodology is stated |
| 6.2 months mid-market, 7 to 9 months enterprise | Average cycle by segment | Ebsta and Pavilion B2B Sales Benchmarks, from connected CRM data across thousands of sales teams | The largest connected-CRM dataset in the category |
| 3 to 6 months mid-market, 9 to 18 months enterprise | B2B software sales cycle | Aexus | Practitioner estimate, no dataset published |
Read the table and you notice the obvious thing. The numbers disagree by a factor of three, and they disagree because they measure different populations with different definitions of when a cycle starts. Optifai's 84-day median and Ebsta's 6.2-month mid-market average are not in conflict. They are answers to different questions.
If you want one sentence to work from: a mid-market B2B SaaS deal in the $15K to $50K range that takes two to three months is normal, and anything past four months in that band is worth investigating.
Every figure in that block is attributed on purpose. The next section explains how much weight each one holds, because they are not equally solid.
Where the widely quoted numbers come from
This section exists because the queries that reach this page are overwhelmingly people looking for a citation. "B2B sales cycle average 3 to 6 months source." "B2B sales cycles longer than B2C authoritative source." "HubSpot average B2B sales cycle length source." Those searchers want provenance, not another number, and almost nothing in the results gives it to them.
Here is what we found when we went looking.
The 84-day median
This is the most-repeated B2B sales cycle figure on the web right now. It traces to Optifai, which publishes it alongside a stated methodology: anonymised CRM exports from 939 B2B companies collected with consent over Q1 to Q3 2025, with outlier removal and industry-size weighting. That is more methodology than most vendor benchmarks disclose, and it is worth taking seriously on those grounds.
Two caveats belong next to it. It is a single vendor's customer base rather than a random sample of the B2B market, and we could find no independent replication of the figure. At least one write-up, Ivris, argues the benchmark circulates far more widely than its evidence supports. Treat 84 days as one vendor's well-documented observation, not as an industry constant.
The related figures that travel with it, a 22% lengthening since 2022 and a buying committee that grew from 5.4 to 6.8 people, come from the same Optifai dataset and carry the same weight.
Does HubSpot publish an average B2B sales cycle length?
Not that we could find, and this matters because a large share of the searches reaching this page ask for exactly that. HubSpot's own sales cycle glossary and its B2B versus B2C material describe B2B cycles as longer and more involved than B2C, with multiple decision-makers and longer evaluation periods, but they do not attach a days figure to it.
Pages that cite "HubSpot's average B2B sales cycle length" are, as far as we can tell, attributing an aggregator's number to HubSpot because the number was found on a page that also mentioned HubSpot. If you need a HubSpot-specific number, the only honest one is the one from your own portal, and the measurement section below tells you how to get it.
The buying committee size
The figure worth quoting here is Gartner's, not a vendor's. Gartner's B2B buying journey research finds that six to 10 decision-makers typically shape a complex B2B purchase, each arriving with four or five pieces of information they gathered independently, and that buyers spend only a small single-digit percentage of their total buying time with any one supplier.
The often-quoted "6.8 stakeholders, up from 5.4" sits inside Gartner's range and comes from Optifai. We used to publish "up from 4.6 in 2018" alongside it. We could not source that figure, so it is gone.
The direction of travel
That cycles have lengthened is the best-supported claim on this page, because two independent datasets agree.
The Ebsta and Pavilion B2B Sales Benchmarks reported cycles growing 16% in the first half of 2023 and 38% against 2021, alongside win rates falling 18% against 2022 and average deal values down 21%. Separately, Salesforce's State of Sales, which surveys thousands of sales professionals across dozens of countries, reports a majority of sellers saying their cycle is getting longer.
Two datasets built in completely different ways, one from connected CRM records and one from a survey panel, pointing the same direction. That is the claim to build a plan on.
The trend is well evidenced. The benchmark is not.
Use the direction of travel to justify the work. Use your own pipeline data to set the target. Any number you import from a benchmark page is a stranger's median applied to your deals, and it will be wrong in a direction you cannot predict.
Sales cycle length by deal size
Deal size explains more of the variance in cycle length than anything else, which is why a single median is close to useless. These are the bands we set targets against on client engagements. They are our working bands, calibrated against the segment benchmarks above and against the pipelines we have audited, not a published dataset.
- Under $5K ACV: 14 to 30 days, mostly product-led with sales assist
- $5K to $15K ACV: 21 to 45 days, low-touch sales
- $15K to $50K ACV: 30 to 60 days, mid-market with one or two stakeholders
- $50K to $100K ACV: 60 to 120 days, real evaluation
- $100K to $250K ACV: 90 to 180 days, full procurement
- $250K+ ACV: 180 to 365 days, security review and legal
If your $80K ACV deals are running 180 days, that is usually not a sales problem. It is a process problem. The team is doing enterprise work on a mid-market deal, and the cycle stretches because the buyer is following your lead.
Sales cycle length by industry
People search for this constantly and the tables that answer it are mostly invented. We looked for a traceable by-industry median and did not find one that discloses a sample and a method. What circulates instead is a set of suspiciously precise industry figures that appear on dozens of pages with no common origin, which is the signature of numbers being copied rather than measured.
So rather than add another table, here is what actually drives the differences people attribute to industry.
Regulatory review, not sector. Financial services and healthcare cycles run long because of security, compliance and data-residency review, not because of anything intrinsic to the sector. A SaaS company selling into a hospital inherits the hospital's review timeline. The same product sold to a 40-person agency does not.
Capital versus operating spend. Manufacturing and hardware-adjacent deals run long because they are capital purchases with approval thresholds, depreciation questions and sometimes a budget cycle to wait for. That is a purchasing-category effect that shows up in any industry buying capital goods.
Contract value, again. Most published by-industry differences shrink dramatically once you control for ACV. Industries with long reported cycles are usually industries with large average deals.
The practical version: benchmark yourself against your ACV band and your buyer's review burden, not against your SIC code. If you want an industry comparison that means something, get it from peers at your deal size through a community or a private benchmarking group, where you can ask how they define stage one.
Why your cycle got longer
Three structural shifts, all pushing the same way.
Buying groups grew. With six to 10 people shaping a complex purchase (Gartner), every additional stakeholder adds a review cycle, and every review cycle adds days. Enterprise deals routinely involve more named decision-makers than that, plus influencers nobody puts in the CRM.
Security and compliance became table stakes. SOC 2, GDPR, ISO 27001, vendor risk assessments, data residency. Survey data on questionnaire response times is dominated by vendors selling questionnaire automation, so treat the specific numbers with caution, but the direction is not in dispute: manual questionnaire response is measured in weeks, not days, and mid-sized buyers now run the process on deals that would have been waved through three years ago.
Procurement got teeth. Cost discipline ended the swipe-the-credit-card expansion motion. Formal procurement, redlines on the order form, vendor consolidation reviews and a legal cycle that has nothing to do with whether your product is good.
None of that is a rep performance problem. Your sales team did not get worse, your buyers got more complicated, and the fix is structural rather than motivational.
Where the time actually goes
When we audit a cycle, we pull stage-level time-in-stage data from HubSpot or Salesforce and plot it against the deal-size band. The leaks show up in the same three places almost every time. The percentages below are the pattern we see in the pipelines we have audited, not a published benchmark, and your own stage data should replace them as soon as you have it.
Discovery to qualified
This stage gets short attention because it feels early. It is where a lot of the loss happens. Reps run a discovery call, send a follow-up, then wait for the buyer to schedule a demo. Two weeks of dead time that nobody logs as dead time.
The fix is removing the wait rather than shortening the call. Mutual action plans at the end of discovery, calendar links for the next two meetings, async pre-demo video so the buyer arrives pre-educated. For a mid-market deal this stage should run one to two weeks. We regularly see it at four to five.
Demo to proposal
The demo went well, then nothing happens for three weeks. The buyer is talking to their internal team and nobody on your side is helping them sell internally. Your champion is sitting in front of their CFO with a deck you built to sell your product, not a deck built to defend a budget request.
The fix is champion enablement, covered in detail below.
Procurement and legal
The biggest single leak in enterprise deals and the most ignored. The technical evaluation might take a month. The legal redline takes longer. Most sales teams treat this as out of their hands. It is not, and the playbook for it is the highest-leverage item on this page for anyone selling above $50K.
Six levers that move the number
When a client asks us to take time out of their cycle, this is the playbook in priority order. The first three carry most of the result. The last three matter once the foundation is in place.
1. Multithread inside the first two calls
The single-contact deal is the biggest cycle-time killer. With one buyer-side contact you wait every time that person goes on holiday, has a busy week, or gets reassigned.
The evidence here is unusually good. Gong's analysis of 1.8 million opportunities found that won deals carry roughly twice as many buyer contacts as lost deals, and Gong reports a substantially larger win-rate effect on deals above $50K. Aviso puts the win-rate lift from multi-threaded conversations at 42%.
One thing to be precise about, because we got it wrong in the previous version of this page: the well-evidenced effect of multithreading is on win rate. The claim that three or more contacts closes deals 2.4 times faster was on this page attributed to ZoomInfo, and we could not verify it against anything ZoomInfo published. It is gone. The cycle-time benefit of multithreading is real in our own engagements but it is a second-order effect, and the honest reason to multithread is that single-threaded deals lose.
The rule we install: by the end of the second meeting the rep names three contacts in HubSpot with the stakeholder role tagged, champion, decision-maker, technical buyer, financial buyer, end user. One named contact means the deal is flagged in the next forecast review and the rep explains why.
Our deeper guide on multithreading B2B sales has the full stakeholder taxonomy and HubSpot setup.
2. Mutual action plans at the end of discovery
A mutual action plan is a shared document with dated milestones and named owners for every step from now to close. Close plan, success plan, buyer journey, the label does not matter. Writing it down with the buyer is what moves the deal.
Outreach reports a 26% higher win rate on deals where the AE runs a mutual action plan. That is a vendor figure from a vendor that sells the capability, so weigh it accordingly, but it is at least published with an owner's name on it. Our own observation across engagements is that MAPs take real time out of the middle of the cycle, and the mechanism is not subtle: a buyer who agreed in writing that legal review starts on day 45 will chase legal on day 45, and a buyer who never put a date on it will chase legal whenever they remember.
The cheapest version is a shared doc with the buyer's logo at the top. Start there. Upgrade to a digital sales room only once reps actually use it and you want richer tracking.
3. Champion enablement before the internal pitch
Your buyer is selling your product to their CFO without you in the room, using your demo deck, which is the wrong artefact because it was built to sell rather than to defend a budget line.
The champion pack we build for clients:
- A five-slide internal pitch deck written from the buyer's point of view with their ROI numbers in it
- A one-page business case template the champion fills in
- A short recorded answer from the AE to the two objections that always come up
- An ROI model the champion can defend in front of finance
We have seen this cited elsewhere with a precise speed-up figure attached. We could not source one, so this page does not carry a number for it. The case for doing it does not need one: the internal pitch happens whether or not you help with it.
4. Pre-cleared legal and security packets
Above $50K ACV, legal and security review is usually the longest single block, and most of it is preventable work being done reactively.
- Pre-approved redlines list. The clauses your legal team accepts verbatim: liability caps, indemnity language, the DPA, termination notice. If a buyer's redline is on the list, the AE signs off without a legal review cycle.
- Trust packet. SOC 2 report, GDPR addendum, security FAQ, pen test summary, sub-processor list, in one place, sent within the hour of the request rather than the week.
- Questionnaire answer library. Pre-written answers to the questions that recur across every assessment, maintained in a compliance tool for teams running many enterprise deals or a shared doc for early-stage teams.
Our working target on client engagements is to get procurement from a six-week block to a two-week block. That is a target we set and measure against, not an outcome we can promise in advance.
5. AI-assisted note capture and follow-up
Reps lose days per deal to follow-up lag. Great call, follow-up goes out on day three, the buyer cools, the deal slows.
We deploy a call recorder on every call and pipe the summary into HubSpot via n8n. Within minutes of the call ending the deal has a structured note, a follow-up draft in the rep's inbox, and next steps on the deal record. The rep edits and sends. Time from call to follow-up goes from days to under an hour, which is the part of this that actually compounds.
The full architecture is in our AI automation work and the n8n RevOps guide.
6. Pipeline review built on time-in-stage
Most pipeline reviews are dollar conversations. What is closing this quarter. The cycle-time fix needs a different conversation: which deals have been sitting in the same stage longer than the median.
Three questions we add to the forecast cadence:
- Which deals are over 1.5 times the median time-in-stage and need an intervention?
- Which deals are still single-threaded after day 14?
- Which deals are in procurement without an agreed action plan?
These are the questions that surface a slip while there is still time to do something about it. Our guide on ghost deals covers what to do with the ones that fail all three.
How to measure your own cycle length in HubSpot
Everything above is context. This is the part that gives you a number you can actually defend, and it is the only B2B sales cycle length that should drive your decisions. Most HubSpot setups cannot measure it correctly out of the box, because the default reporting gives you one blended figure that hides deal size, segment and stage.
Properties on the deal record
- Time in stage, per stage, from the stage history. HubSpot tracks this, but you have to surface it in reports rather than assume it is there.
- Cycle length (calculated): close date minus create date, populated only on closed-won deals.
- Days since last activity: drives the stuck-deal alerts.
- Stakeholder count: contacts attached with a role tagged, for the multithread health check.
- Action plan agreed (Y/N).
- Trust packet sent (Y/N).
One decision to make before any of this means anything: when does the cycle start? Deal creation, first meeting, and opportunity qualification give materially different numbers, and this is exactly why published benchmarks disagree with each other. Pick one definition, write it down, and never compare across definitions.
Reports to build
- Median cycle by ACV band, last 12 months, split by source
- Time-in-stage by stage, with the median and the 75th percentile
- Single-threaded deals over 14 days old, by rep
- Deals over 1.5 times median time-in-stage, sorted by value
- Procurement and legal stage duration, last 90 days
Report the median rather than the mean. One 400-day enterprise deal will drag a mean far enough to make it meaningless, which is part of why the mean and median in every published benchmark sit so far apart.
These go on the CRO dashboard and get reviewed weekly. The full reporting stack is in our HubSpot dashboard guide.
Automations that keep the data honest
The hard part is accuracy. Without enforcement the dashboard becomes fiction within a quarter. Three HubSpot workflows we deploy on every client:
- Auto-flag deals stuck in a stage past the 75th percentile
- Auto-create a task when stakeholder count drops below three in mid-stage
- Auto-notify rep and manager when a closed-lost deal had less than 14 days in evaluation
The last one catches the deals you never really had, which otherwise quietly pollute your conversion rates and your cycle median at the same time.
When none of it works
Sometimes you do all of this and the cycle still feels long. Before assuming you need more reps or more leads, check four root causes.
Your ICP is too broad. If deals split across SMB, mid-market and enterprise, your team runs three different motions and your cycle data means nothing. A median that averages a 21-day SMB deal with a 280-day enterprise deal describes no deal you have ever run. Segment the pipeline and report cycle time separately for each. The segmentation logic is in our ICP playbook.
Your pricing is wrong for the segment. If your $30K product is hitting enterprise procurement, you have a pricing mismatch. Either move it below the procurement threshold into self-serve, or accept the enterprise cycle and price for it.
Your champion is not a champion. If a deal stalls every time one specific contact is supposed to push it forward, that contact is an interested observer. A real champion will take a call to plan their internal pitch. Our working rule: no such call by week four means find someone else or disqualify.
Your pipeline coverage is too low. Reps working too few deals over-invest in each one and the cycle stretches. Healthy pipeline coverage is around 3x quota for inbound-heavy teams and 4 to 5x for outbound-heavy. Below 2.5x every deal feels like a must-win and nobody disqualifies aggressively enough.
Want your real cycle number, and a plan to move it?
We audit your CRM, your stage definitions and your last 100 closed deals, then deploy the levers above and stay until the numbers move. The audit tells you what your cycle actually is before anyone promises to shorten it.
Book a free 30-minute audit →FAQ
What is the average B2B sales cycle length?
There is no single authoritative figure. The most-quoted number is a median of 84 days, published by Optifai from anonymised CRM data across 939 B2B companies in 2025. Ebsta and Pavilion report considerably longer averages by segment, around 6.2 months for mid-market and seven to nine months for enterprise. The gap comes from different populations and different definitions of when a cycle starts. Two to six months is the defensible range for B2B SaaS, scaling with deal size.
Does HubSpot publish an average B2B sales cycle length?
Not that we could find. HubSpot's own material describes B2B cycles as longer and more involved than B2C but does not attach a days figure. Pages citing "HubSpot's average B2B sales cycle length" are generally attributing an aggregator's number to HubSpot. The HubSpot number worth having is the one from your own portal, and the measurement section above tells you how to build it.
What is the average sales cycle length by industry?
We could not find a by-industry benchmark that discloses a sample and a method, and the industry tables circulating online do not share a traceable origin. Most of what gets attributed to industry is actually explained by contract value and by regulatory review burden. Benchmark against your ACV band rather than your sector.
Why is my sales cycle longer than two years ago?
Two independent datasets say cycles have lengthened. Ebsta and Pavilion measured cycles growing 16% in the first half of 2023 and 38% against 2021 from connected CRM records, and Salesforce's State of Sales survey finds a majority of sellers reporting longer cycles. The drivers are larger buying groups, security and compliance review reaching mid-market deals, and formal procurement on deals that used to skip it.
How many people are involved in a B2B buying decision?
Gartner puts a typical complex B2B purchase at six to 10 decision-makers, each arriving with several pieces of independently gathered information. Vendor datasets report an average nearer seven, which sits inside Gartner's range.
Do mutual action plans actually shorten the cycle?
The published evidence is about win rate rather than speed. Outreach reports a 26% higher win rate on deals with a mutual action plan, from a vendor that sells the capability. Our own engagement observation is that MAPs take time out of the middle of the cycle, because a dated commitment gets chased on its date. We do not have a defensible public number for the size of that effect, so this page does not publish one.
How do I shorten my B2B sales cycle?
In priority order: multithread to three or more named contacts by the second call, agree a mutual action plan at the end of discovery, build a champion enablement pack for the internal pitch, pre-clear legal and security so procurement is not a discovery exercise, cut follow-up lag with automated note capture, and rebuild the pipeline review around time-in-stage rather than dollar value.
The takeaway
A longer sales cycle is a process problem caused by buyer behaviour changing faster than your sales motion, not a rep execution problem. The published benchmarks are useful for establishing that the shift is real and roughly how big it is. They are not useful as a target, because none of them measures your segment, your ACV band or your definition of stage one.
Measure your own cycle properly, segment it, find the two stages where the time actually goes, and fix those. That sequence works regardless of which benchmark turns out to be closest.
How we sourced this update
Two limitations worth stating plainly rather than hiding.
First, most of the domains cited here, including Gartner, HubSpot, Salesforce, Gong, Ebsta, Databox and Optifai, are not reachable from the environment this update was written in. Every figure was established from multiple independent search results that agree with each other, and is attributed to the organisation that originated it. Where we could not corroborate a figure across independent sources, it was removed rather than softened. Four numbers came out of this page for that reason, including the median and mean that used to be in the title.
Second, the numbers described here as our own, the ACV target bands, the stage-percentage patterns and the procurement target, are working figures from client engagements, stated at the pattern level with no client identified. They are labelled as our observations rather than as benchmarks precisely because they have not been through anyone's methodology but ours.
If your cycle is stretching and you want to know where the time actually goes, we run that audit.