Treat the cycle as a diagnostic. If it is longer than the benchmark for your segment, something is wrong at a specific stage, and a CRM that measures cycle time by stage is how you find it.
A sales cycle is the total elapsed time from the first interaction with a prospect to a closed-won deal. In B2B, cycles run 30 to 60 days for SMB deals, 60 to 120 days for mid-market, and 120 to 365 or more for enterprise. The length is driven by deal size, number of stakeholders, procurement rules, and buyer behavior, not by sales effort alone.
The five things to know about sales cycles before you try to manage one, including the one benchmark that tells you whether your process is healthy or quietly broken.
A sales cycle measures elapsed calendar time, not working hours, from the moment a prospect enters pipeline to the moment the deal is marked won or lost. Lost deals have cycles too, and separating won-cycle from lost-cycle is where most teams discover their qualification problem.
SMB deals typically close in 30 to 60 days. Mid-market lands in the 60 to 120 day range. Enterprise deals routinely take 120 to 365 days or more, with large infrastructure and multi-year contracts pushing past a year. These are not laws, they are gravity, and they come from procurement complexity, not sales skill.
Deal size, number of stakeholders, procurement rigor, and buyer behavior. A ten-stakeholder deal with a security review and a legal redline is a different animal from a one-stakeholder credit-card deal, even if both are the same product. The cycle is the price of the complexity, not a failure of effort.
A sales pipeline is a snapshot of where every open deal sits right now. A sales cycle is a measurement of how long those deals take to move from end to end. Pipeline tells you what you are working. Cycle tells you how long it takes to work it. Both metrics live in the same CRM data.
Shaving ten days off the average cycle at the same win rate is more revenue earlier in the year, more capital to reinvest, and higher sales capacity per rep. For venture-backed teams, cycle compression is often the fastest path to a healthier burn-to-ARR ratio without hiring more reps.
A single average hides the problem. Measure time-in-stage for every stage so you can see whether deals rot in Qualification, Proposal, or Legal Review. The slowest stage is where your next process intervention lives, and a decent CRM gives you that view in a report.
Published benchmarks vary, but the shape is consistent across industry reports. Cycles track three variables most of the time: deal size, buyer size, and whether procurement is involved. The numbers below are the ranges most B2B teams can calibrate against. If your segment runs significantly longer than its range, treat that as a diagnosable problem, not the normal speed.
Deals under roughly fifteen thousand dollars annual contract value, usually one or two stakeholders, credit-card or light contract. The buyer is often the user, which collapses the decision loop. Fastest cycles live here. If your SMB deals are averaging over sixty days, you likely have an under-qualified top of funnel or a demo-to-trial gap.
Deals from fifteen thousand to one hundred thousand annual contract value, typically three to seven stakeholders, a real MSA, and a security questionnaire. Procurement starts to show up. Legal review becomes a stage of its own. Economic buyer is usually separate from the user, which adds internal-selling time on top of the external sales motion.
Deals above one hundred thousand annual contract value, often seven to fifteen stakeholders, formal RFP or committee review, SOC 2 or ISO review, custom contract terms, and a procurement team whose job is to slow you down. Multi-year commitments and multi-geography rollouts stretch past twelve months routinely.
Government, education, and healthcare procurement rules add their own quarters. Fiscal calendars, bid cycles, cooperative purchasing agreements, and compliance reviews make eighteen-month cycles routine. A deal entering this segment with a sixty-day forecast is almost always a close-date error, not a reality.
For PLG motions where users self-serve into paid tiers, the "cycle" collapses to the time from signup to card entry. Measurement shifts from stages to activation events. Sales enters only when the account hits enterprise criteria, at which point the enterprise benchmark applies to the expansion motion.
Multiple 2024 and 2025 reports from Gong, Pavilion, and others put B2B cycles 15 to 30 percent longer than pre-2022 baselines, driven by tighter budgets, more approval layers, and increased committee-based buying. If your cycle lengthened in the last two years, you are not alone, and the question is which of those drivers hit your motion hardest.
Cycle time is the sum of a small number of frictions, and each one has a known fix. Before trying to compress the cycle, measure where the time actually goes. The slow stage is rarely the stage sales reps complain about.
A fifty thousand dollar deal clears one or two approvers. A five hundred thousand dollar deal gets a procurement team, a legal review, a security review, and a finance sign-off. The approval graph is nonlinear with contract value. If deal size doubled this year, expect cycle time to grow with it, and plan for parallel-tracking the security and legal work instead of running them in series.
Gartner research puts the average B2B buying group at six to ten people. Each additional stakeholder adds roughly a week of coordination time, meeting scheduling, internal consensus-building, and the risk that one new voice reopens settled questions. Multi-threading early, instead of selling to one champion, is how teams prevent the late-stage surprise.
Procurement is not sales's counterparty, it is a different buyer with a different scorecard. Their job is price pressure and risk reduction, measured on savings against list price and vendor consolidation. Once procurement enters, the technical sale is over and the commercial sale begins. Teams that pre-build procurement packages (security docs, references, pricing schedules) cut this stage by weeks.
6sense, Gartner, and Forrester all converge on the same finding: buyers are 60 to 70 percent through their evaluation before they talk to sales. That shifts the cycle. The first touch happens later, after most comparison work is done, which compresses the usable sales window and makes initial-call quality more important than initial-call volume.
The champion's job is selling internally when sales is not in the room. Deals with a strong champion close roughly twice as fast as deals with a weak one, because the champion runs the internal consensus loop in parallel with the sales process. The question "who is actually going to push this inside the account" is a stage-gate, not a nice-to-have.
Even qualified deals stall without a reason to decide now. A compelling event (a system end-of-life, a budget use-it-or-lose-it, a competitor contract renewal, a compliance deadline) is what moves a deal from "we should" to "we must". Deals without one average 40 percent longer cycles and are the first to be deprioritized when budgets tighten.
Shortening a cycle is not about pushing harder. Teams that compress cycle time without hurting win rate do a short list of specific things, and most of them happen before the deal enters pipeline. The headline move is to stop treating the sales motion as a serial process.
Pull the last fifty closed-won deals, cluster by firmographic and technographic traits, and find the segment with the shortest average cycle at the highest win rate. That segment is your ideal customer profile. Reorient marketing targeting and sales prospecting against it. The cycle compresses because you stop spending time on buyers who were never going to move fast.
The fastest way to shorten the average cycle is to remove the slowest deals from pipeline. Deals without budget, authority, timeline, or a compelling event drag the average and tie up rep capacity. A disciplined qualification framework (MEDDPICC, SPICED, or your own) run honestly at Stage 2 is cheaper than closing the same deals six months later as closed-lost.
Most cycles are serial by habit: technical demo, then business case, then security review, then legal review, then procurement. Each handoff is a week of calendar time. The compressed version runs security and legal review in parallel with the final technical validation, and gets the procurement package to the buyer before they ask. The deal does not actually change, the clock does.
Security questionnaires are the most common invisible cycle-killer. Publish a trust center with the SOC 2 report, DPA, subprocessor list, pen test summary, and a pre-filled SIG or CAIQ questionnaire. Buyers who find it self-serve. Buyers who ask get it in a day instead of three weeks. One intervention routinely cuts two to four weeks off mid-market and enterprise cycles.
A mutual action plan (MAP) is a shared document with every step from today to signature, each with an owner and a date. It converts the buyer's internal process from invisible to visible, which lets both sides manage it. Deals with a MAP close 20 to 30 percent faster in most published studies because the slow steps get surfaced early instead of discovered late.
Every custom quote is a round-trip. If pricing can be published or configured to self-serve for the standard case, deals that would have taken a week to price now take an hour. Enterprise custom pricing still happens, but the 70 percent of deals that fit the standard shape skip a stage entirely.
Cycle data lives in the CRM. Deal records carry created-date, stage-change timestamps, and closed-date, and the quality of your cycle analysis is a function of whether those timestamps are accurate. The reports below are the ones every revenue leader should have on the Monday dashboard.
The headline chart. Cycle length for closed-won deals in the last four quarters, broken out by SMB, mid-market, and enterprise, or by industry if your segmentation is vertical. If one segment's cycle doubled this year, you have found the thing to investigate before the quarter closes on the wrong side of the plan.
For every stage in the pipeline, show the median time deals spend before advancing. The stage with the longest median is where your next process intervention lives. This is almost never the stage reps complain about. Qualification, Legal Review, and Procurement are the usual suspects, in that order.
Separate the cycle average for closed-won from closed-lost. Lost deals almost always have longer cycles, because they are the deals that stalled before they died. If won-cycle is 90 days and lost-cycle is 160 days, your rep capacity is being eaten by deals that were never going to close. That is a qualification lesson, not a closing lesson.
Group cycle length by lead source: inbound demo request, outbound SDR, partner referral, event, content download. The source with the shortest cycle at the highest win rate is where to send more marketing budget. The source with the longest cycle at the lowest win rate is where to send less, regardless of volume.
Rank reps on average won-cycle at the same deal size and segment. The fast reps are doing something repeatable: better qualification, better multi-threading, better MAP discipline. The slow reps are doing the opposite. The variance is a coaching plan, not a performance review.
Sales velocity equals (opportunities times average deal size times win rate) divided by cycle length. Compressing cycle time has a direct, measurable effect on velocity. The CRM should calculate velocity automatically against pipeline, segment, and rep so cycle-time improvements translate into forecast dollars, not just a dashboard chart.
Strkr ships pipeline, forecasting, and stage-level cycle reporting as one tool, so time-in-stage and sales velocity are a report you open, not a spreadsheet you rebuild every Monday. Published pricing. Start free.
Published studies converge on roughly 90 days as a cross-segment B2B average, but the average is misleading on its own. SMB deals run 30 to 60 days, mid-market deals 60 to 120 days, and enterprise deals 120 to 365 or more. The right benchmark is the one for your deal size, not the industry-wide number.
A sales pipeline is a snapshot of every open opportunity grouped by stage: how many deals you have, where they sit, and what they are worth. A sales cycle is a measurement of elapsed time: how long deals take to move from first touch to closed-won. Pipeline is state, cycle is duration, and both are reported from the same CRM data.
Take every closed-won deal in a given window (usually the last four quarters), subtract the created-date from the closed-date for each deal, and average the result. For a more useful view, calculate the median instead of the mean to avoid a few outlier year-long enterprise deals pulling the number up. Segment the result by deal size and lead source to find the real patterns.
Healthy is relative to segment. For SMB, under 45 days is strong. For mid-market, under 90 days is strong. For enterprise, under 180 days is strong. More important than hitting a number is whether the cycle is stable or stretching, and whether the won-cycle and lost-cycle are converging (good) or diverging (bad). A lost-cycle twice the won-cycle is a qualification signal.
The four interventions that compress cycle time without hurting conversion are: tighten the ICP so you sell to buyers who move fast, qualify harder so slow deals leave pipeline before they consume capacity, run security and legal review in parallel instead of serial, and use a mutual action plan to surface the buyer's internal steps. All four are process changes, not sales effort changes.
The three most common causes in 2024 and 2025 are tighter buyer budgets (more approval layers), larger buying groups (Gartner now cites six to ten people as typical), and more rigorous procurement review. External factors have added 15 to 30 percent to cross-industry cycle time. Internally, the usual suspects are drift in ICP targeting, weaker qualification, or more serial handoffs between discovery, security, and legal.
Not necessarily. A shorter cycle at the same win rate and deal size is pure improvement. A shorter cycle driven by discounting, by selling only to smaller customers, or by walking away from legitimate enterprise deals is just a different motion, not a better one. The right lens is sales velocity (opportunities times deal size times win rate divided by cycle), which balances all four variables at once.
A CRM is where stage-change timestamps live, which makes it the only honest source of cycle data. The right reports show cycle length by segment, time-in-stage, won versus lost cycle, source-attributed cycle, and rep-level variance. Without those reports, cycle discussions default to anecdote. With them, the slow stage becomes visible, and the fix becomes a process change instead of a motivational speech.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
