So, are you ready for the AI bill? Because it’s coming, and it’s landing squarely on top of another, much older bill that’s been lurking in the shadows for years. Think API sprawl, application proliferation – all the lovely tech messes we’ve made that we never quite figured out how to govern or, more importantly, cost. Now, with AI sprinting onto the scene, that reckoning isn’t just a whisper; it’s a full-blown roar.
Kin Lane, a guy who’s been shouting about this stuff for ages, likens the current AI frenzy to the early days of cloud migration. Remember that? Companies with solid foundations, clear designs, and a culture that didn’t treat engineers like second-class citizens sailed through. The rest? Well, they stumbled. And this new wave of AI is doing the same thing, only faster and at a much, much grander scale. Without a real grip on what’s actually under the hood, we’re building the future on what amounts to digital quicksand.
The Chasm: Where Engineering Meets Wishful Thinking
Why is AI spending such a black hole? Lane nails it: the persistent, soul-crushing divide between the people who code and the people who sign the checks. It’s been like this for two decades. Business throws requirements over the fence. Engineers build it, often with zero clue about the actual customer. Agile? Sure, we’ve got that – or at least the watered-down, “faux-agile” version where nobody speaks the same language. Engineers can’t explain tech woes in business terms, and business leaders are blissfully ignorant of the chaos lurking in GitHub.
I go into a lot of business groups that don’t know what their engineers are saying or doing, or have any bridge to connect the dots. Engineers are resistant to anything business-aligned, and business people are resistant to opening up GitHub to see what’s going on.
Beyond Uptime: What’s the Business Actually Seeing?
And it’s not just communication breakdowns. Look at observability. Sure, your engineers can see uptime, error rates, and security threats. Great for them. But does it tell the business anything useful? What’s this system costing? What value is it spitting out? Who’s it serving? The answer, more often than not, is a resounding “nope.” The tools and the culture just aren’t built for it. This is how API costs – let alone AI costs – vanish into the ether, allowing AI to run wild because, hey, nobody’s actually tallying the tab.
This isn’t just about forgotten legacy systems sapping resources. It’s about a fundamental lack of business observability that’s now catching up to us with AI. Lane’s not about replacing what we have; he’s about expanding it. Instead of error rates, we need to see dollar signs, customer sectors, product lines. Think product view, not just Kubernetes ops.
The Real Talk: Business Observability for AI
Business observability, as Lane sees it, flips the script. It’s about outcomes, not just infrastructure. It’s about grouping spend and usage by product, customer, sales pipeline, whatever makes sense to the business folks. The point? Make engineering’s work visible. This isn’t just a dashboard tweak; it’s a cultural shift. Who owns the vocabulary? What gets tracked? What’s surfaced? AI, Lane hopes, can be the bridge – the translator between raw telemetry and actual business language.
He’s looking for AI to help us build this vocabulary for traceability, empowering business stakeholders to interact with and shape these systems. The engine for this, Lane suggests, is tagging. Embedding structured metadata into every API call, every model inference, every token. Think UTM parameters for your AI.
It’s a smart idea. For years, we’ve built systems that are opaque to the business, and now we’re surprised when they can’t be managed or costed effectively. The AI influx is forcing our hand. We either build systems with true business observability, or we continue to build on the sand, waiting for the inevitable tide. The question isn’t if the bill will come due, but how prepared you’ll be when it does. And honestly, most outfits aren’t.
Is AI Business Observability Just a Fancy New Buzzword?
Lane argues it’s far more than that. For 20 years, businesses have struggled with understanding the true cost and value of their IT investments due to a persistent disconnect between engineering and business stakeholders. Traditional IT observability focuses on technical metrics like uptime and error rates, which are meaningless to business leaders. Business observability, conversely, aims to translate that technical data into business-relevant terms, such as cost per customer segment, revenue generated by a specific feature, or impact on sales pipelines. It’s about making the invisible visible to the people who sign the budgets.
Why is API Sprawl a Precursor to AI Cost Issues?
API sprawl refers to the uncontrolled proliferation of APIs within an organization, often leading to a complex, unmanaged, and undocumented web of services. This lack of governance makes it incredibly difficult to track usage, manage security, and, crucially, understand the associated costs. Lane’s point is that this decades-old problem of opaque and unmanaged technical debt has left organizations ill-equipped to handle the even more complex and rapidly scaling costs and dependencies of AI systems. The foundational lack of visibility in API management directly translates to a greater lack of visibility when AI tools and services are layered on top.
🧬 Related Insights
- Read more: Venezuela Telemedicine: Forget Fancy Apps
- Read more: AI Agents Devour Tokens: 4 Hidden Costs Found
Frequently Asked Questions
What does ‘agentic influx’ mean in this context?
‘Agentic influx’ refers to the rapid and widespread adoption of AI systems, particularly those that involve autonomous “agents” capable of performing tasks and making decisions without constant human intervention. This surge in AI adoption is overwhelming existing IT management and observability capabilities.
Will business observability help me understand my AI model performance?
Yes, business observability aims to provide context for AI model performance by connecting technical metrics to business outcomes. Instead of just seeing inference latency, you’d see how that latency impacts customer experience or sales conversion rates, and what the associated costs are.
What is the core problem with AI spending right now?
The core problem is a lack of visibility and traceability. Organizations lack the tools and culture to understand what their AI systems are costing, what value they are delivering, and who or what they are impacting from a business perspective. This is largely due to a long-standing IT-business communication and tooling gap.
