Average Days to Close: What Duration Data Reveals About Real-World Deadlines

There's a particular kind of optimism that infects every project kickoff meeting. Someone writes "2 weeks" on a whiteboard, and the room nods. Two weeks feels reasonable. Two weeks feels professional. Two weeks almost never happens.

The gap between estimated duration and actual duration is one of the most documented — and most ignored — phenomena in business operations. We have decades of data on how long things actually take. We routinely set deadlines that contradict that data. Understanding why, and what the numbers really say, can change how you plan, negotiate, and build accountability into your workflows.

The Baseline Problem: What "Days to Close" Actually Measures

Before diving into the numbers, it's worth being precise about what duration data captures. "Days to close" in a business context refers to the elapsed calendar time between two defined events — a contract sent and a contract signed, a support ticket opened and resolved, a deal entered into a pipeline and marked won or lost.

This is distinct from effort hours. A contract might take 45 minutes of actual human work but sit in someone's inbox for 11 days. That 11-day figure is the duration that matters for planning. It's the number that determines whether your Q3 target closes before quarter-end, whether your client gets their deliverable before their own board meeting, whether you can start phase two before the budget resets.

Duration is what fills calendars. Effort is what fills timesheets. Most deadline failures are duration failures, not effort failures.

Sales Cycles: The Classic Duration Gap

Sales pipeline data offers some of the richest duration benchmarks available, largely because CRM systems have been collecting it for decades. The picture is consistently humbling for optimists.

Research from Salesforce's State of Sales reports and independent analyses from CSO Insights consistently shows that average B2B sales cycle lengths have been increasing, not decreasing, despite better tools and more process. For mid-market deals (roughly $25,000–$100,000 contract value), average close times routinely run 84 to 120 days. Enterprise deals frequently stretch past six months. Even transactional SMB sales, the category most likely to be characterized as "quick," average 30–40 days in practice.

Compare that to what most sales reps forecast. Studies on forecast accuracy — including work by Clari and Gartner — consistently find that reps underestimate their deal duration by 30 to 50 percent. A deal a rep calls "closing next week" has a statistically meaningful chance of closing in three weeks. A deal called "this quarter" has a real probability of slipping to next.

The mechanism isn't laziness or wishful thinking, though those play roles. It's that salespeople observe the deal from their own vantage point and undercount the steps that happen outside their visibility: legal review, procurement committee scheduling, budget approval chains, competing internal priorities on the buyer's side. Each of those invisible steps carries its own duration.

Contract Review: The Step Everyone Underestimates

Legal and contract review data is particularly striking because it involves a discrete, bounded task — read a document, mark up changes, return it — that nonetheless takes far longer than anyone budgets.

Data from contract lifecycle management platforms like Ironclad and Icertis, which process millions of contracts annually, shows that average contract review and negotiation cycles run 3.4 weeks for standard commercial agreements. For agreements requiring significant redlining — which is the majority of first-time vendor contracts — that stretches toward 5 to 7 weeks.

A 2022 World Commerce & Contracting survey found that organizations lose an estimated 9.2 percent of annual revenue to contract process inefficiencies, with cycle time being the primary culprit. The same research found that 65 percent of companies believe their contract process takes longer than it should — which is remarkable because that belief coexists with persistent underestimation at the individual deal level.

People know their process is slow in aggregate. They still assume their specific contract will be different.

IT Projects and the Hofstadter Effect

Software and IT projects have their own well-documented duration pathology. Douglas Hofstadter articulated it memorably in 1979: "It always takes longer than you expect, even when you take into account Hofstadter's Law." The data has been confirming this ever since.

McKinsey research on large IT projects found that they run on average 45 percent over budget and 7 percent over time — but that average is misleading because it's pulled down by smaller projects. Projects above a certain scale (roughly $15M+) run dramatically longer, with 17 percent of large IT projects running so far over schedule that they threaten the company's existence.

Even at the task level, the pattern holds. Research by Stefan Thomke at Harvard Business School and others on agile sprint completion rates shows that the average story point estimate is accurate about 35–40 percent of the time when measured against actual completion. Teams improve with experience, but they rarely eliminate the gap — they just narrow it.

What's particularly interesting is where the time goes. Post-mortem analyses of delayed IT projects consistently identify the same culprits: dependency wait time (waiting for another team, another system, another decision), scope clarification cycles (the requirements that weren't quite right), and integration testing that surfaced problems not anticipated in design. None of these are exotic failure modes. They're the ordinary texture of complex work, and they're systematically absent from initial estimates.

Business Days vs. Calendar Days: A Compounding Error

One underappreciated source of duration error is the business-days-versus-calendar-days confusion. Contracts often specify "net 30 days" or "5 business days." Project timelines are often set in working days. But human intuition about elapsed time operates in calendar days.

The difference compounds quickly. Five business days is seven calendar days if it crosses a weekend — but it becomes nine or ten if there's a holiday in the span, and it can balloon to twelve or fourteen during holiday-adjacent periods in December or around major national holidays. A "net 30 business days" payment term is actually 42 calendar days in a standard month, and can exceed 50 calendar days when holidays intervene.

This isn't a trivial arithmetic point. It affects when payments are due, when deliverables must be ready, when contracts expire, and when penalties kick in. Automated date calculation tools that properly account for business days and regional holidays exist precisely because the mental math is error-prone at scale. For a company processing hundreds of contracts, the accumulated drift between "assumed due date" and "actual due date" can create significant financial exposure.

The Estimation Asymmetry

The research literature on planning and estimation has identified a consistent cognitive asymmetry: people are better at identifying reasons a task might take longer, when explicitly asked, than they are at spontaneously incorporating those reasons into their estimates.

Psychologists call this the "planning fallacy," first named by Daniel Kahneman and Amos Tversky in 1979 and studied extensively since. The core finding is that people estimate task duration based on an idealized scenario of how the task could go — the inside view — rather than the base rate of how similar tasks actually go — the outside view. Lawyers who have handled dozens of contract negotiations will still estimate their next one based on the best-case scenario rather than their own historical average.

The practical implication for anyone managing deadlines is that reference class forecasting — looking at actual completion data for comparable tasks — consistently outperforms intuitive estimation. If your organization has data showing that RFP responses take an average of 14 business days from brief to submission, that number should anchor your next estimate, not your feeling about how smoothly this particular RFP will go.

What Good Duration Tracking Looks Like in Practice

The organizations that manage this best tend to share a few characteristics. They track duration systematically — not just completion, but the elapsed time at each stage of a workflow. They use that data to build reference ranges for common task types, capturing not just averages but distributions (because a task that averages 10 days with a standard deviation of 8 days requires different planning than one that averages 10 days with a standard deviation of 2).

They also build in buffer explicitly rather than hoping for best-case scenarios. Adding 20–30 percent to estimates based on historical data isn't pessimism; it's accuracy. And they use automated tools to handle the calendar complexity — because tracking business days, excluding holidays, and calculating accurate deadline dates manually at any significant volume is an invitation to error.

Perhaps most importantly, they treat slippage data as information rather than failure. When an actual duration exceeds an estimate, that's a calibration opportunity. The question isn't who missed the deadline but what the data now tells you about how long this type of work actually takes.

The Useful Discomfort of Accurate Data

Looking at duration data honestly is somewhat uncomfortable. It tends to reveal that things take roughly twice as long as we'd like them to, that the stages we consider "quick" aren't, and that our confidence in specific timelines is poorly calibrated against our historical track record.

That discomfort is the point. Accurate duration data doesn't just help you plan better — it changes the conversations you have. You stop committing to timelines that the data says are unreachable. You start negotiating deadlines based on what's realistic rather than what sounds impressive. You build workflows that account for the actual pace of human review, legal approval, procurement cycles, and the thousand small delays that occur between one step and the next.

The average days to close, properly measured, is a signal about reality. It's more useful than the number you wrote on the whiteboard at the kickoff meeting — even if it's a lot less satisfying to look at.