RevOps
Project close timelines from stakeholders and compliance steps.
- Category
- RevOps
- Signup
- None
- Your data
- Stays in your browser
- Also in
- Claude, via MCP
How do you forecast the length of a sales cycle?
Start from how long a simple, single-buyer deal takes, then add time for each extra decision-maker and for the review gates the deal must pass. Projected cycle = base days + (decision-makers − 1) × days per extra stakeholder + compliance days. Four decision-makers and a security plus legal review turn a 30-day base into about 78 days.
Expect roughly 78 days (2.6 months) to close. Every extra stakeholder and gate compounds, a mutual action plan is the single best tool for holding late-stage deals to schedule.
Forecast for capacity and quarter timing, not as a promise, a champion who drives internal consensus can beat this materially.
About this calculator
A "30-day sales cycle" only ever describes the simplest possible deal, one buyer, no procurement gates. The moment a deal picks up a second decision-maker or a security review, that base number stops meaning anything. This forecaster layers stakeholder count and compliance requirements onto a base cycle so the projected timeline reflects what enterprise deals actually look like.
How to use it
- Enter your base cycle, the time a single-buyer deal with no extra gates takes to close.
- Enter the number of decision-makers involved and the added days each extra stakeholder typically contributes.
- Select the compliance/procurement level the deal will pass through: none, security review, security + legal, or the full security + legal + procurement gate.
- Read the projected total cycle in days and months, plus the separate day contributions from stakeholders and from compliance.
Methodology
Stakeholder days added is (decision-makers − 1) × days per extra stakeholder, the first stakeholder is already priced into the base cycle, so only additional buyers extend it further.
Compliance days added is a fixed lookup based on the selected level: 0 days for none, 15 for security review alone, 30 for security + legal, 50 for the full security + legal + procurement gate.
Projected cycle is base cycle + stakeholder days + compliance days. Total added versus base is projected cycle minus base cycle, isolating how much enterprise complexity is stretching the deal beyond the simple case.
This is a forecasting tool for capacity and quarter-timing planning, not a guarantee, a strong internal champion who drives consensus among stakeholders and pushes procurement along can beat this projection meaningfully, just as a passive or conflicted buying committee can blow past it.
Projected sales cycle from base time, stakeholders and review gates
Stakeholder days = (Decision-makers − 1) × Days per extra stakeholder Compliance days = 0 (none) | 15 (security) | 30 (security + legal) | 50 (security + legal + procurement) Projected cycle = Base cycle + Stakeholder days + Compliance days Added vs base = Projected cycle − Base cycle
- Base cycle
- Days from first meeting to signature for a deal with one buyer and no formal reviews, taken from your CRM.
- Decision-makers
- People whose approval the deal needs, including finance, IT and the end user's manager.
- Days per extra stakeholder
- Average extra days each additional approver adds, from meetings, internal alignment and waiting.
- Compliance days
- Fixed allowances in this tool for security questionnaires, contract redlines and vendor onboarding.
The compliance allowances (15, 30 and 50 days) are planning assumptions built into the tool, not measured averages. If your deals regularly spend longer in legal or procurement, add the difference to the base cycle. The model adds stages one after another; running security and legal reviews in parallel with commercial talks is the main way real deals beat it.
Worked example: a mid-market software deal with four approvers
A SaaS company's simplest deals, a founder buying for a small team, close in about 30 days. A new opportunity involves four decision-makers (the champion, their head, IT and finance), and the buyer has said it will need a security questionnaire and a contract review. The team estimates each extra approver adds about 6 days.
- Stakeholder days = (4 − 1) × 6 = 18 days.
- Compliance days for security + legal = 30 days.
- Projected cycle = 30 + 18 + 30 = 78 days, about 2.6 months.
- Added versus base = 48 days, more than the base cycle itself.
- If procurement also has to onboard the vendor, compliance rises to 50 days and the projection to 98 days, about 3.3 months.
A deal opened in the first week of a quarter is unlikely to close in that quarter, and one opened mid-quarter certainly will not. Forecast it into next quarter, and ask the buyer in discovery who signs and which reviews apply, because those two answers change the date more than anything else. To see how a longer cycle affects revenue per day, use the pipeline velocity calculator; to estimate contract review time specifically, use the contract redline duration predictor.
Published reference point for cycle length
| Deal size | Average time to close | Source |
|---|---|---|
| $100,000 | About 70 days | Gong, The State of Revenue 2025, as reported by SaaStr |
What is a good sales cycle length?
A good cycle is a predictable one. A 90-day cycle you can forecast is worth more to planning than a 45-day average that swings between 15 and 120 days.
Three checks tell you whether yours is healthy:
- Spread: compare the median with the 75th percentile for deals of similar size. A wide gap means some deals stall, usually at legal or procurement.
- Stage time: find the stage where deals spend the most days. That is where to act first.
- Size relationship: larger deals should take longer. If small deals take as long as large ones, the process, not the buyer, is the bottleneck.
These are working checks rather than published benchmarks.
Sales cycles in India vs the US
Indian enterprise and mid-market buyers often add a commercial negotiation round late in the deal and a purchase order step after signature, so the deal is not "closed" for revenue until the PO and the vendor code exist. Count the PO step in the base cycle if your CRM marks deals won at signature. GST registration details, TDS treatment and vendor onboarding forms are routine paperwork that procurement teams handle; send them early so they do not hold up a signed deal.
US mid-market and enterprise buyers commonly run formal security reviews (questionnaires and requests for reports such as SOC 2) and send contracts through legal, which is what the security and legal allowances model. Having a standard security pack and a pre-negotiated contract position ready before the deal reaches that stage is the most reliable way to shorten US cycles. For ramp planning tied to cycle length, see the sales rep ramp calculator.
Common sales cycle forecasting mistakes
- Using the average cycle across all deals for a deal that is much larger or has more approvers than usual.
- Counting from opportunity creation in some deals and from first meeting in others, so the base cycle is inconsistent.
- Assuming security and legal reviews start only after commercial agreement, when they can run in parallel.
- Leaving out the purchase order or vendor onboarding step and calling deals late when they are actually waiting on paperwork.
- Forecasting the close date the buyer hopes for rather than the one the process allows.
Sources
- Gong: $100k deals take about 70 days to close, SaaStr. Accessed 2026-10-19.
Go deeper
FAQ
Because the base cycle already assumes a single buyer is involved, that first stakeholder's time is baked into the base days figure. Only the second, third, and further stakeholders represent genuinely additional coordination time, so the formula counts extra days only for stakeholders beyond the first.
Ask directly, early, rather than guessing, most enterprise buyers will tell you what gates a purchase this size triggers if you ask during discovery. If you genuinely don't know yet, security + legal is a reasonably common default for mid-market and enterprise B2B deals above a modest contract value.
The two levers in this model are stakeholder count and compliance gate, so multi-threading early to get all decision-makers engaged simultaneously rather than sequentially, and starting security/legal review in parallel with commercial negotiation rather than after it, are the two moves that compress the projection.
The sales cycle is the time from the first meaningful sales conversation with a prospect to a signed contract. Some teams measure from lead creation instead; pick one starting point and use it everywhere.
In your CRM, filter closed-won deals with a single decision-maker and no formal review, then take the median days from opportunity creation (or first meeting) to close. Use at least 20 deals if you have them.
Often, because deals that drift lose momentum and champions change roles. But some long cycles are normal for large deals. Compare win rates for deals that ran past your typical cycle with those that did not.
A shared document, agreed with the buyer, listing each step to a decision, who owns it and the target date. It surfaces approvers and reviews early, which is exactly what this forecast needs.
Numbers looking off?
If the model says one thing and the pipeline says another, that gap is usually where the revenue is. A 30-minute call finds it.
It starts with a 30-minute call. Pick a time below.