The real cost, security, and culture problems behind enterprise AI agents
Our take
The conversation around enterprise AI agents has been dominated by a sense of urgency – a fear of being left behind. VentureBeat’s recent AI Impact event, however, offered a more grounded perspective, courtesy of Red Hat’s Brian Gracely, who illuminated the practical hurdles facing organizations moving beyond pilot projects. It's a welcome counterpoint to the breathless hype, especially considering the ongoing challenges with AI moderation, as seen in Discord’s recent admission of a bug wrongfully banning users over harmless images Discord admits AI moderation bug wrongfully banned users over harmless images. Gracely’s observations suggest that while the learning curve for adopting agentic AI is proving less steep than initially anticipated, the subsequent complexities around cost, security, and organizational alignment represent significant, and often overlooked, barriers to widespread adoption. This pragmatic view is essential for organizations attempting to navigate the current AI landscape, which continues to evolve rapidly, as evidenced by Google’s upcoming Pixel event set for August 12 Google’s Pixel event is set for August 12.
The most striking takeaway is perhaps the widespread miscalculation of AI costs. Enterprises, often defaulting to the most powerful models irrespective of task complexity, are facing an escalating expense that’s quickly becoming a boardroom-level concern. Gracely’s analogy to FinOps practices, which matured over years of experience managing cloud compute spending, is particularly apt. The shift from engineering oversight to financial accountability mirrors the evolution of cloud adoption itself. Furthermore, the increasing reliance on a small number of dominant model providers introduces another layer of risk, prompting a search for alternative solutions that offer greater control over costs and infrastructure. Semantic routing and infrastructure-level optimizations, such as caching, offer immediate levers for cost reduction without sacrificing innovation. The message is clear: efficiency and innovation aren't mutually exclusive; smart resource allocation is the key.
Beyond cost, the rapid pace of AI development is fundamentally altering security protocols. The ability of AI to uncover vulnerabilities faster than traditional methods demands a drastically accelerated patch management cycle. What was once a manageable operational task is now a strategic imperative, requiring organizations to adapt to a far more dynamic threat landscape. The emergence of AI-driven security tools capable of identifying complex, chained vulnerabilities further underscores this shift. This necessitates not only faster patching but also a deeper understanding of potential attack vectors. Moreover, the human element remains critical. Gracely’s emphasis on securing buy-in from subject matter experts and incentivizing their participation is crucial; the successful integration of AI agents hinges on addressing potential anxieties and fostering a collaborative environment where knowledge is shared and valued.
Ultimately, the success of enterprise AI agent adoption hinges on a holistic approach that addresses cost management, security vulnerabilities, and organizational alignment. It's a journey that demands a pragmatic mindset, a willingness to experiment with different models and infrastructure techniques, and a commitment to fostering a culture of collaboration and continuous learning. As organizations navigate this evolving landscape, the question remains: will they prioritize strategic control and cost efficiency, or continue to chase the allure of ever-more-powerful, but potentially unsustainable, AI solutions? The answer will likely determine which enterprises truly unlock the transformative potential of agentic AI and which remain tethered to costly, inefficient pilot programs.
Presented by Red Hat
At VentureBeat's recent AI Impact event, where the discussion centered on what separates enterprises that scale agentic AI from those that stall in pilot mode, Brian Gracely, senior director of portfolio strategy at Red Hat, detailed what companies actually run into once agents reach production.
He dove into cost discipline, the security blind spots unique to autonomous systems, and the organizational friction that determines whether agent adoption spreads beyond early champions.
Enterprises are overestimating how far behind they are on AI agents
Many enterprise leaders, especially those following industry keynotes and AI announcements, worry that they’re already falling dangerously behind competitors deploying agents at scale. But according to Gracely, much of that anxiety reflects a misconception about how quickly organizations learn once they begin building. Teams often move up the learning curve far faster than they expect.
That rapid progress creates a different challenge, however. As agent usage expands, AI costs rise just as quickly, turning cost management from an engineering concern into a recurring boardroom discussion.
Agentic AI usage is orders of magnitude higher than during the chatbot era, making AI costs a growing concern for enterprises. At the same time, organizations are becoming increasingly aware of their dependence on a small number of model providers. According to Gracely, that combination is driving many enterprises to explore alternatives that give them greater control over costs and infrastructure.
"The two or three top providers are already telling the market that they're losing money, and they're trying to go public to make up those gaps," he explained. "At some point, the dependency on that means you're either going to buy at a very high-cost level, or you're going to figure out alternatives to control what you're doing."
Right-sizing AI models is the fastest lever for cutting agent costs
The biggest cost issue is that enterprises overspend by defaulting to the most capable model available regardless of task complexity.
"If I'm simply trying to resolve an insurance claim, I don't need to know about the history of Western civilization in my model, I don't need to know World Cup soccer scores," Gracely said.
Semantic routing is the mechanism many companies use to make that judgment automatically, classifying requests and sending each to a model sized for the task without requiring users to choose, while infrastructure techniques like caching repetitive queries cut how often a request needs to reach GPU compute at all. Together, he said, these tools remove the assumption that efficiency and innovation pull in opposite directions.
"There's a lot you can do at a GPU infrastructure level, and quite a bit you can do in terms of flexibility of models," he explained. "Those give excellent choices in terms of the levers you're trying to pull, whether you need efficiency or you need innovation. That shouldn't be a binary choice."
The financial discipline needed for token spend is similar to the FinOps practices that took years to mature in order to take control of cloud compute spending. Those underlying frameworks will transfer even as the vocabulary changes, Gracely said, especially as organizations push for internal education on model selection so teams stop defaulting to the most prominent option for tasks that don't need it.
"The same way we first had to teach the financial people what an EC2 instance is and what an S3 bucket is, you're going to have to start explaining tokens to them," he said. "We don't always need a Rolls-Royce. We don't always need caviar, because we're trying to do basic types of things."
Patch speed is now critical as AI tools find vulnerabilities faster
AI-powered vulnerability discovery is forcing enterprises to rethink how quickly they can identify, validate and deploy patches. Long-established patch management cycles may no longer be fast enough in an environment where AI can uncover — and attackers can exploit — new vulnerabilities much more quickly.
"Most companies are probably going to have a window of somewhere between seven and 14 days to stay ahead," he said. "There are groups, Red Hat included, that are going to build patches for these, but the embargo window is going to be short."
AI is also changing what defenders need to look for. Rather than simply uncovering isolated critical flaws, AI security tools can identify combinations of seemingly minor vulnerabilities that become dangerous only when chained together. As both software complexity and vulnerability discovery accelerate, Gracely argued that the ability to rapidly manage and update software is becoming a strategic capability rather than simply an operational one.
Subject matter experts and compliance teams decide whether agents scale
In the end, organizational adoption comes down to the need for deep, sustained involvement from the subject matter experts whose knowledge the agent is meant to encode, which makes earning their buy-in a prerequisite rather than an afterthought.
"You have to think about the incentives, what you do for people who participate in this work so they don't feel threatened that it's going to take away their job, and how you incentivize people in the long run to cooperate with that innovation," he said.
Sponsored articles are content produced by a company that is either paying for the post or has a business relationship with VentureBeat, and they’re always clearly marked. For more information, contact sales@venturebeat.com.
Read on the original site
Open the publisher's page for the full experience