Skip to main content

Your Board Is Funding Ghosts

Anurag Gurtu
Airrived

Run a simple thought experiment with your next board deck. Take every enterprise software renewal over $250,000 and ask one question that almost never makes it into a vendor review: not "is this still being paid for," but "is this still where the work actually happens." Most finance teams can answer the first question instantly. Almost none can answer the second — and that gap is quietly costing companies more than any single line-item overrun ever will.

The Audit Nobody Runs

Procurement tracks renewal dates, license counts, and contract terms with real discipline. What it doesn't track well is workflow migration — the slow, undocumented drift of where employees actually go to get work done, which increasingly isn't the system of record the company is still paying full price for. A platform can show "active users" in its own usage dashboard while the actual decision-making and execution have quietly moved to a chat interface, an agent layer, or a workaround spreadsheet nobody approved. The system still gets logged into. It just isn't where the value lives anymore.

Call it ghost software: fully licensed, technically active, financially renewed — and functionally hollowed out. It survives because nobody owns the job of declaring it dead. Killing a vendor relationship requires a champion willing to disrupt a workflow; doing nothing requires no one to do anything at all. Renewal is the path of least resistance, which is exactly why ghosts accumulate in enterprise IT budgets and almost never get exorcised.

Why This Is a Board-Level Blind Spot, Not an IT Problem

This isn't a story about wasteful middle managers. It's a structural blind spot in how boards govern technology spend. Board-level vendor reviews are built around cost and renewal risk — are we getting a good rate, is the contract favorable — almost never around whether the workflow the tool was bought for still lives inside it. A board can approve a clean, on-budget renewal for a system that three teams have already functionally abandoned, and nobody in the room would be lying. They'd just be asking the wrong question.

Agentic AI is about to make this blind spot more expensive, not less, because it accelerates exactly the kind of quiet workflow migration that makes ghost software invisible. When an orchestration layer sits above five legacy systems and routes work between them automatically, the legacy systems can look perfectly healthy by every metric procurement tracks, while contributing almost nothing to where decisions actually get made.

The Fix Is a Question, Not a Process

Boards don't need a new audit framework to catch this. They need one new question added to every major renewal: who, specifically, still does their primary work inside this system — not who's provisioned, who's actually there. If the honest answer is "fewer people than last year, doing less of the actual decision-making," that's not a renewal. That's a ghost asking for one more year of rent.

The companies that get ahead of this won't necessarily spend less on software. They'll spend on the right things, instead of paying full price to keep haunting a building nobody works in anymore.

Anurag Gurtu is Co-Founder and CEO of Airrived

The Latest

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...

Your Board Is Funding Ghosts

Anurag Gurtu
Airrived

Run a simple thought experiment with your next board deck. Take every enterprise software renewal over $250,000 and ask one question that almost never makes it into a vendor review: not "is this still being paid for," but "is this still where the work actually happens." Most finance teams can answer the first question instantly. Almost none can answer the second — and that gap is quietly costing companies more than any single line-item overrun ever will.

The Audit Nobody Runs

Procurement tracks renewal dates, license counts, and contract terms with real discipline. What it doesn't track well is workflow migration — the slow, undocumented drift of where employees actually go to get work done, which increasingly isn't the system of record the company is still paying full price for. A platform can show "active users" in its own usage dashboard while the actual decision-making and execution have quietly moved to a chat interface, an agent layer, or a workaround spreadsheet nobody approved. The system still gets logged into. It just isn't where the value lives anymore.

Call it ghost software: fully licensed, technically active, financially renewed — and functionally hollowed out. It survives because nobody owns the job of declaring it dead. Killing a vendor relationship requires a champion willing to disrupt a workflow; doing nothing requires no one to do anything at all. Renewal is the path of least resistance, which is exactly why ghosts accumulate in enterprise IT budgets and almost never get exorcised.

Why This Is a Board-Level Blind Spot, Not an IT Problem

This isn't a story about wasteful middle managers. It's a structural blind spot in how boards govern technology spend. Board-level vendor reviews are built around cost and renewal risk — are we getting a good rate, is the contract favorable — almost never around whether the workflow the tool was bought for still lives inside it. A board can approve a clean, on-budget renewal for a system that three teams have already functionally abandoned, and nobody in the room would be lying. They'd just be asking the wrong question.

Agentic AI is about to make this blind spot more expensive, not less, because it accelerates exactly the kind of quiet workflow migration that makes ghost software invisible. When an orchestration layer sits above five legacy systems and routes work between them automatically, the legacy systems can look perfectly healthy by every metric procurement tracks, while contributing almost nothing to where decisions actually get made.

The Fix Is a Question, Not a Process

Boards don't need a new audit framework to catch this. They need one new question added to every major renewal: who, specifically, still does their primary work inside this system — not who's provisioned, who's actually there. If the honest answer is "fewer people than last year, doing less of the actual decision-making," that's not a renewal. That's a ghost asking for one more year of rent.

The companies that get ahead of this won't necessarily spend less on software. They'll spend on the right things, instead of paying full price to keep haunting a building nobody works in anymore.

Anurag Gurtu is Co-Founder and CEO of Airrived

The Latest

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Top-performing businesses prioritize data-driven decision making, enabling leaders to move from intuition and gut feel towards evidence-based judgment. But that judgment is only sound when the data underpinning decisions is accurate. With incident management, data accuracy is particularly important. Long-term revenue, customer trust, and operational stability depend on high-quality data that enables teams to quickly identify and address the root cause of major incidents. Against this backdrop, governance becomes a critical endeavor to ensure the right data drives the right action ...

In MEAN TIME TO INSIGHT Episode 26, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network compliance ... 

Most production autonomous agents do not run in a vacuum. They run inside cloud infrastructure: virtual machines, containers, pods, managed clusters or private servers. That is where most operations teams start monitoring. Is the VM alive? Is the container running? Did the pod restart? Is memory stable? Is CPU too high? Did the health check pass? Those signals are useful. They tell you whether the shell around the agent is alive. They do not tell you whether the agent inside is actually operational ...