This guide is written for bid managers, proposal leads and pre-sales teams selling into formal procurement, the ones who have had to explain why a deal everybody already agreed on is still not signed. If your deals close in two weeks on a credit card, the stages below will read as overkill, and that is fine.
A sales cycle is the repeatable sequence of stages a seller moves a deal through, from first contact to a signed contract. Most published models count seven stages, but credible sources range from four to seven, and the disagreement is not cosmetic: it turns on whether producing the proposal counts as a stage of its own. Shortening a cycle means attacking the parts you actually control, and in deals that go through procurement, the largest of those is the time spent building the documents the deal requires.
Key takeaways
- A sales cycle is the sequence of stages a deal moves through, and a sales process is the method your team uses to move it. The working test: a stage belongs in the cycle only if the buyer could confirm it happened.
- Seven stages is the consensus model, but none of the published models gives the document its own stage. If your deals go through procurement, add the three the models leave out: requirements received, response delivered, and evaluation or security review passed.
- Do not benchmark against the 84-day figure that circulates everywhere. Its citation chain leads to a compilation of other publications, not a measurement. Compute your own instead, and split it by deal size and by whether procurement ran the process.
- A blended average usually describes no deal you have ever sold. In the worked example, 105 days on average hides 60 days for direct deals and 210 for deals that went through central procurement.
- Sort the levers before pulling them. You do not control budget timing, procurement policy, legal queues or committee availability. You do control how fast you qualify out, whether you multi-thread early, how long your documents take to produce, and how complete your first response is.
- Document turnaround is the only part of the cycle that depends on nothing outside your walls. At Open, an IT services group, RFP response time fell by half. Measure the working days between a buyer asking for a document and receiving it: most teams have never counted it.
What is a sales cycle, and how is it different from a sales process?
A sales cycle is the sequence of stages a deal passes through. A sales process is the method your team uses to move it. Salesforce frames the distinction cleanly: the cycle is the what, the process is the how.
The two terms get used interchangeably, including by people who sell for a living. The confusion is common enough that Indeed maintains an entire page dedicated to separating them, and it comes up regularly in sales communities. The mix-up is harmless in conversation and expensive in reporting. If your CRM stages describe activities your reps perform rather than commitments the buyer makes, you are measuring your own process and calling it a cycle. Cycle length then moves whenever your team changes its habits, which makes the number useless for forecasting.
A working test: a stage belongs in your sales cycle if a buyer could confirm it happened. Discovery call booked, requirements received, proposal delivered, security review passed, contract signed. Anything your rep does alone belongs to your process.
Consider a fleet management vendor selling telematics to a logistics group. "Ran a discovery call with the operations director" is a cycle stage, because the operations director would confirm it. "Completed MEDDIC scoring in the CRM" is a process step, because nobody on the buyer's side knows it happened. Both matter. Only the first one should ever appear in a cycle length calculation. Teams that mix them end up reporting a sales cycle that shortens every time management simplifies the CRM, which tells you nothing about how fast deals actually close.
What are the 7 stages of the sales cycle?
The consensus model runs seven stages. Below is what the most widely read explainers actually publish, taken from their live pages in August 2026.
Read the table across rather than down and something stands out. In the three seven-stage models, no stage is dedicated to building the document. Presentation and objection handling sit side by side, and the proposal is assumed to appear between them. RAIN Group's third stage, solution crafting, is the only one in the whole set that names the act of constructing what you send.
Salesforce is the exception worth crediting. Its guide does describe the step in prose, noting that in a complex sale you still have to draft a formal proposal for stakeholders and finance, that procurement will negotiate, and that legal will scrutinize the terms. It describes the step accurately. It just never treats it as time.
Why some models count six stages, or four
RAIN Group merges closing and nurturing into a single winning stage and folds discovery into a broader need-driving stage, which lands them at six. Four-stage and five-stage models circulate alongside them, both of which are compressions used in training material.
None of these models is wrong. They are cuts of the same continuum at different resolutions, made by organizations selling different things: a CRM vendor slices by pipeline stage because that is what its software tracks, a sales training firm slices by skill because that is what it teaches. Pick the resolution that matches how your own deals actually progress, then keep it stable long enough to produce comparable data.
If your deals routinely involve a written response, a formal evaluation or a compliance review, the seven-stage model will not survive contact with your pipeline, and you should add stages rather than force your deals into someone else's diagram. A sales cycle that reflects reality usually adds three: requirements received, response delivered, and evaluation or security review passed. Those three are the ones a buyer can confirm, which makes them measurable, and they are precisely the ones the published models leave out.
How long is a sales cycle, and why the number you keep reading is unverifiable
Search for average sales cycle length and you will meet the same figure everywhere: 84 days for a B2B deal. It appears on vendor blogs, in glossary pages, and in AI-generated summaries.
Where the 84-day figure actually comes from
Following the citations is instructive. One widely cited page attributes the number to HubSpot without a link. Another cites two other blogs. Those blogs cite an aggregator, Optifai, which is the only link in the chain that publishes a methodology at all. That page reports a sample of 939 companies over four quarters, and then describes its data collection in its own words as "synthesized from publicly available industry research, benchmarking studies, and sales operations reports", aggregated from third-party sources.
In other words, the 939 companies were never surveyed. The figure is a compilation of other publications, and the publications it compiles are not named. The same page attributes a buying group size of 6.8 decision makers to Gartner, where Gartner's published research gives a range of six to ten and no mean at all.
This is not a scandal, and the people repeating the number are not acting in bad faith. It is simply what happens when a plausible statistic enters circulation and every subsequent article inherits it. The practical consequence for you is narrow and important: do not benchmark your cycle against 84 days, and do not put that number in a board deck. It is an estimate of unknown provenance.
What you can rely on is first-party research that names its method. Gartner's work on the B2B buying journey holds that a typical buying group for a complex solution involves six to ten decision makers, each arriving with information gathered independently. That finding is stable, sourced, and far more actionable than a median, because it tells you what to plan for rather than what to compare against.
How to measure your own sales cycle length
Your own number is the only one worth managing. The calculation is simple, and the discipline is in the definitions.
- Pick a closed-won population. All deals won in the last four quarters. Exclude renewals and expansions unless you plan to manage them separately, because they behave nothing like new business.
- Fix your start event. First qualified contact, not first touch. Marketing-sourced first touch will inflate every figure you produce.
- Fix your end event. Countersigned contract, not verbal commitment.
- Sum the elapsed days and divide by the number of deals. That is your average cycle length.
- Then compute the median as well. If your median sits far below your average, a handful of very long deals are dragging the mean, and the average is describing a deal type you rarely sell.
Segment the result by deal size and by whether procurement was involved. Two segments in the same company routinely differ by a factor of three, and a single blended number hides exactly the deals that hurt.
A worked example makes the point. Say you closed 40 deals last year for a total of 4,200 elapsed days. Your average sales cycle is 105 days. Now split them: 28 deals sold directly to a business unit accounted for 1,680 days, an average of 60 days each, while 12 deals that went through central procurement accounted for 2,520 days, an average of 210 days each. The blended 105-day figure describes no deal you have ever sold. It sits between two populations that need different forecasts, different resourcing and different qualification criteria. Run this split before you run anything else, because every other cycle metric you produce inherits the error if you skip it.
Where the time actually goes: the stage nobody counts
Here is what prompted this article. Read the standard explainers on this subject and the vocabulary of a document-heavy deal is missing entirely. No tender, no questionnaire, no statement of work, no technical memo, no security review, no redline, and almost no mention of turnaround. The proposal itself barely appears, and when it does it is a noun in a list rather than a body of work with a duration.
They are competent explainers. They answer the question a student or a new rep is asking. They simply do not describe the deal that a bid manager recognizes, where the gap between "send it over" and the document actually landing in the buyer's inbox is measured in working days.
Practitioners describe that gap constantly. A thread in r/revops asks the question directly: how much do RFPs slow down your sales cycle. In r/procurement, a poster describes drowning in RFPs that are slowing down their enterprise deals, each one generating multi-day coordination. In r/AskNetsec, security engineers are asked how often they get pulled into filling out customer RFPs and due diligence questionnaires. Cobl's CEO put the same observation in a January 2026 post: the common RFP workflow is still copy and paste, and a technical proposal that sounds like ten days of work rarely takes ten days.
What a document-heavy deal really contains
In a deal that goes through procurement, the seller is not producing one artifact. A single opportunity typically requires a written response to the requirements, a security or vendor risk questionnaire, a technical memo, a pricing sheet, references, sometimes a slide deck for the steering committee, and a statement of work once terms are agreed. Each one is assembled from material that exists somewhere in the company and has to be found, adapted, formatted, checked for consistency, and reviewed internally before it goes out.
The internal loop is where the days accumulate, and it is almost never modeled. A pre-sales engineer drafts the technical section, then waits for legal to clear a liability clause, then discovers that the pricing tab contradicts what the account executive quoted in the last meeting, then sends a corrected version to a manager who is travelling. Each handoff is short. The queue between handoffs is not. Multiply that by seven documents and a deal that everyone describes as moving fast has quietly consumed three weeks of calendar time that no stage in your CRM records.
There is a second cost, harder to see and more damaging. When documents are assembled ad hoc, they stop resembling each other. Daoud Chami, Data Science and AI Manager at CBTW, frames the problem as one of internal grammar: RFP responses, technical memos and HR templates all follow rules the organization knows implicitly and writes down nowhere. When that grammar lives only in the heads of two senior people, every document either waits for them or goes out inconsistent, and both outcomes lengthen the sales cycle.
None of that work appears in a seven-stage diagram. All of it appears in your cycle length.
That is the argument for treating deal documents as a managed workflow rather than an afterthought, whether through templates, a shared library, proposal automation, or a workspace that carries the deal context from one document to the next. Whatever the mechanism, the discipline is the same: stop treating the assembly of the deliverable as invisible time.
How to shorten the sales cycle: what you control and what you don't
Most advice on shortening a sales cycle fails for the same reason: it targets the buyer's calendar. Send more follow-ups, create urgency, add a discount deadline. Buyers in regulated or committee-driven purchases are not slow because they lack motivation. They are slow because an approval path exists and it has a fixed length.
Sort the levers before you pull any of them.
The parts you don't control
Accept them and plan around them. A thread in r/sysadmin describes six months to approve a two thousand dollar tool because procurement required three competitive bids for a product that met the security requirements on its own. No seller technique compresses that. What you can do is discover it early, because a mandatory three-bid policy discovered in week two changes your forecast, and discovered in month four destroys it.
Ask about the approval path during qualification. Who signs, in what order, and what has to exist in writing before each signature. The answer is your real cycle map, and it is usually more accurate than your CRM stages.
The parts you do control
Qualify out faster. A thread in r/sales puts a large RFP at over a hundred hours of work with no realistic chance of winning. Time spent on a deal you were never going to win is the most expensive slowdown in your pipeline, because it delays the deals you could have won. A formal go or no-go call before you commit the team is the cheapest cycle intervention available.
Multi-thread before you need to. With six to ten decision makers on a complex purchase, a single champion is a single point of failure, and re-educating a stakeholder who appears in month three costs weeks.
Cut document turnaround. This is the lever nobody publishes about and the only one that depends on nothing outside your walls. At Open, an IT services group responding to public sector tenders, RFP response time fell by half, and their engagement executive describes going from two to three hours of drafting a proposal from scratch to a framework version in about five minutes, leaving the remaining time for adapting it to the client. At Randstad, consultants moved from an average of 25 minutes per document to three.
Two caveats worth stating plainly. Those figures come from Cobl customers describing their own results, so read them as directional rather than as a benchmark. And no generative tool should send anything unreviewed. AI drafts documents well and gets details wrong, which is why human validation before delivery is not optional in a deal where a wrong number is contractual.
Make the first response complete. Every clarification round is a full lap of the buyer's internal calendar, not a quick email. A response missing an insurance certificate, a signed data processing agreement or a reference in the right vertical will sit in a procurement queue until the next review meeting, which may be two weeks out. Ask during qualification what the evaluation committee needs to see, assemble it once, and send it whole. The effort is identical. The elapsed time is not.
Notice what these four levers have in common. None of them requires the buyer to move faster. They compress the parts of the sales cycle that sit entirely on your side of the table, which is why they work on deals where the customer genuinely cannot accelerate.
Why your cycle can't be benchmarked, and what to compare against instead
Cycle length varies more within a single company than it does across an industry average. A deal sold to a department head on a corporate card and a deal sold to the same logo through central procurement share a product, a price list and a sales team, and behave like different businesses.
That is why an industry benchmark tells you almost nothing. What does tell you something is your own baseline, segmented on the variables that actually move the number:
- Deal size, because approval thresholds are the single most reliable predictor of how many signatures you need.
- Whether procurement runs the process, because a formal process adds mandatory steps regardless of enthusiasm.
- Whether a security or compliance review applies, because those queues belong to a team with no revenue target.
- Number of stakeholders engaged, using Gartner's six to ten as a planning assumption rather than an average to match.
Build those four segments, measure each one for two quarters, and you have something a competitor's blog post cannot give you: a baseline that describes your deals. Sector context helps at the margins, and the patterns differ genuinely between, say, IT and telecom vendors and professional services firms, but it never substitutes for your own numbers.
What to change before next quarter
Four things, in order. Redefine your sales cycle start and end events so the number means something. Segment by procurement involvement, because that single split will explain most of your variance. Add the three missing stages to your pipeline, requirements received, response delivered and evaluation passed, so the documentary phase becomes visible in the data rather than hiding inside a stage called negotiation. Then measure how many working days pass between the moment a buyer asks for a document and the moment they receive it, which is almost certainly a figure nobody in your organization currently holds.
That last measurement usually surprises people, and it is the one you can act on immediately. Everything else in a sales cycle depends on a buyer, a committee, a fiscal calendar or a legal queue. Document turnaround depends on you.
Cobl is a deal workspace built for teams who produce those documents under deadline. Try it for free.
