By Jeff Gray, CEO & Co-Founder, Gluware
The most actionable insights in business rarely arrive as revelations. More often, they arrive as recognition — the moment someone gives a name to a pattern that’s been quietly inflating your costs, compressing your margins, and slipping your timelines for years. You didn’t lack the data. You lacked the vocabulary.
Here’s the pattern. You approve a growth initiative — an acquisition, a market expansion, a major product launch. The business case is rigorous. The timeline is aggressive but defensible. Then, somewhere between the boardroom and execution, the initiative slows. Not dramatically. Not all at once. It slips a quarter, then another. Costs accumulate past the model. The competitive window that justified the urgency starts to close. The post-mortem will list a dozen contributing factors. None of them will say: the network wasn’t ready, and we had no idea how long it would take to make it so.
That gap – between how fast your business strategy demands you move and how fast your infrastructure can actually support that movement – is the infrastructure velocity gap. It exists in the data of nearly every Global 2000 enterprise. It has simply never had a name.
Why It's Invisible Until It Isn't
Executive strategy is stress-tested against the variables that are visible and measurable: market timing, capital allocation, competitive dynamics, talent. Infrastructure readiness is treated as a precondition – something IT will handle – rather than a variable with its own timeline, its own cost curve, and its own compounding risk profile.
The mechanics behind that assumption are worth understanding. A major enterprise initiative – an acquisition integration, a new market entry, a significant compliance deployment – can require thousands of individual network configuration changes. In the overwhelming majority of Global 2000 enterprises, those changes are still executed largely by hand. Skilled engineers configure each device individually, validate changes across multi-vendor environments, and document what was done.
According to Gartner’s 2025 Market Guide for Network Automation Platforms, 67% of enterprise network activity is still executed manually. That number is not an IT operations footnote. It is the arithmetic behind every initiative that missed its window. The gap isn’t the result of underperforming IT teams. It’s the result of a manual operating model that was never designed to keep pace with the demands of a modern growth strategy.
The Gap Has Arithmetic
The infrastructure velocity gap isn’t a soft risk. It has a dollar value and a timeline cost that most business cases have never calculated.
Consider a global biopharmaceutical company whose network operations had become a direct constraint on its research velocity. Necessary network changes to support global research collaboration were taking weeks to complete — and each configuration change on their global backbone cost $220,000 to execute manually. The delay wasn’t an IT problem. It was pushing back go-to-market timelines on medicines in active development, with compounding cost implications at every stage of the pipeline.
Once they closed the infrastructure velocity gap – automating their network operations to the point where their team could execute changes in hours rather than weeks – the impact was immediate and measurable: a 98% reduction in configuration change time, complex global network updates completed in under two hours, and over $2 million in avoided change costs in year one alone.
That’s the arithmetic of the gap in one direction. The arithmetic in the other direction – what it costs to leave the gap open, quarter after quarter, initiative after initiative – rarely gets calculated at all.
The Diagnostic: Four Questions That Surface the Gap
The infrastructure velocity gap is measurable before it becomes a crisis. These four questions give you a reasonable proxy for where your organization stands:
What does your network team’s change backlog look like at the start of a major initiative? If the answer involves a queue measured in weeks, your initiative timeline is likely already optimistic.
When your last acquisition closed, how long before the acquired company’s systems were fully integrated into your network? The business case probably assumed six to eight weeks. Most enterprises take six to eight months. That delta is the gap — and it has a cost that almost never appears in the deal model.
What percentage of your IT operating budget goes to maintaining current network state versus enabling new capabilities? For most enterprises, the ratio tilts heavily toward maintenance — meaning the infrastructure budget is funding yesterday’s operations, not tomorrow’s strategy.
If your three most experienced network engineers left tomorrow, which strategic initiatives would be immediately at risk? If the answer is several, critical execution capacity lives in a small number of people — not in a scalable operating model.
None of these are IT questions. They’re business execution questions that happen to have a network answer.
The Compounding Advantage
The most important characteristic of the infrastructure velocity gap isn’t its cost in any single initiative. It’s that it compounds in both directions.
Leave it open, and every initiative pays the tax. Each major program runs longer than modeled, costs more than projected, and hits the market later than the competitive window demanded. The tax is invisible in any individual case, buried in project overruns and attributed to a dozen other causes. But cumulative across a portfolio of initiatives, it is enormous.
Close it, and the dynamic inverts. The enterprise that has automated its network operations doesn’t just execute one initiative faster. It executes every initiative faster, and the advantage accumulates. Acquisitions integrate in weeks. Security mandates deploy at scale. New capabilities reach market ahead of competitors who are still waiting on their infrastructure to catch up. The gap between companies that have addressed this and those that haven’t is widening — and it is doing so quietly, without fanfare, in the execution layer where strategy either succeeds or stalls.
The Answer is in the Operating Model, Not the Headcount
The instinctive response to an execution capacity problem is to add capacity — more engineers, more budget, more hours. It’s the wrong answer here, and most enterprises that have tried it already know that. You cannot hire your way out of a structural misalignment between manual operations and the velocity a modern growth strategy demands. This simply distributes the problem across more people without changing its fundamental nature.
The enterprises that have closed the infrastructure velocity gap didn’t do it by scaling their teams. They changed how their networks operate entirely. They moved from a model where every change required human intervention to one where human expertise is applied to defining intent. From there, the infrastructure executes it consistently, at scale, across thousands of devices simultaneously.
The business impact of that shift is not incremental. It is structural. When the infrastructure layer can match the velocity of the business layer above it, the entire execution model changes. Initiatives launch on the timeline the business case modeled. Acquisitions integrate in the window the deal assumed. Competitive advantages compound rather than erode in the gap between approval and deployment.
Clarity is underrated as a competitive weapon. Most executives will spend the next planning cycle working around a constraint they can’t articulate. You now know what it’s called — the infrastructure velocity gap — and in strategy, as in most things, seeing the problem clearly is already half the solution.
