# finops

FinOps is an operational framework and cultural practice for maximizing technology value, enabling data-driven decisions, and creating financial accountability through collaboration between engineering, finance, and business teams.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Keep skyrocketing AI costs in check

DevFeed: [Keep skyrocketing AI costs in check](<https://devfeed.tech/articles/keep-skyrocketing-ai-costs-in-check-141277.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4243812/keep-skyrocketing-ai-costs-in-check.html>)

Author: Snowflake and Google Cloud

Published: 2026-11-18T21:31:59Z

Content type: article

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [finops](<https://devfeed.tech/topics/finops.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>)

Tags: [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-costs](<https://devfeed.tech/tags/ai-costs.md>), [ai-economics](<https://devfeed.tech/tags/ai-economics.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-usage](<https://devfeed.tech/tags/ai-usage.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [budget](<https://devfeed.tech/tags/budget.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [coding](<https://devfeed.tech/tags/coding.md>), [controls](<https://devfeed.tech/tags/controls.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [finops](<https://devfeed.tech/tags/finops.md>), [google](<https://devfeed.tech/tags/google.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [limits](<https://devfeed.tech/tags/limits.md>), [llm](<https://devfeed.tech/tags/llm.md>), [storytype-brandpost](<https://devfeed.tech/tags/storytype-brandpost.md>)

### AI overview

AI costs can rise quickly as agentic systems consume more tokens and AI workloads depend on model choice and prompt iteration. The text describes three Snowflake approaches, developed with Google Cloud: granular spend views, quotas and group budgets with programmable enforcement; model flexibility, including routing tasks among approved open or proprietary models using cost and performance trade-offs; and an agent harness that loads tools on demand, bundles calls, compacts outputs and supplies context to reduce calls, turns and tokens. These controls aim to improve cost visibility and predictability while supporting AI adoption. The text does not quantify savings.

### Source excerpt

The rapid rise of AI has introduced another challenge for IT leaders: How to effectively manage surging compute and infrastructure costs with an eye towards optimizing spend and achieving demonstrable ROI. Expensive AI infrastructure, rising development costs, and token-based pricing models are helping to drive up the AI price tag, often to levels that are higher than expected. Agentic AI takes a greater toll on costs as models use between 5 and 30 times more tokens per task than standard chatbots. By 2028, Gartner predicts AI coding costs will overtake the average developer's salary due to surging LLM token consumption and the shift to consumption-based licensing models. A FinOps Foundation survey identified managing the cost and use of tokens in SaaS-model AI as the top challenge facing practitioners today. "Agents have blown out the cost of everything," says Rachel Roundy, principal product marketing manager for AI at Snowflake. "Companies are at a point where they are weighing the pros and cons of how much value they are getting out of the agentic toolset versus how much they are paying for it. They are looking for ways to find cost efficiencies." A trifecta for keeping costs in check Compared to cloud compute workloads, AI tasks stack up costs more quickly depending on the model and prompt iteration cycle, creating budgeting and forecasting challenges. Snowflake, in tandem with partner Google Cloud, delivers capabilities and services to help optimize AI economics and bring predictability to deployments. Among them Budget and cost controls. Snowflake establishes transparency and trust on the cost front in a variety of ways. Highly granular views of daily AI spend provide visibility into adoption patterns and AI usage across business units so quick adjustments can be made. User quotas and group budgeting capabilities allow organizations to set spending limits for defined groups of users and resources while triggering automated and programmable cost enforcement. "

## From Prompts to Management Reports: Snowflake HTML Reports with CoCo

DevFeed: [From Prompts to Management Reports: Snowflake HTML Reports with CoCo](<https://devfeed.tech/articles/from-prompts-to-management-reports-snowflake-html-reports-with-coco-140791.md>)

Original publisher: [Read original article](<https://medium.com/snowflake/from-prompts-to-management-reports-snowflake-html-reports-with-coco-2febecfc5e8c?source=rss----34b6daafc07---4>)

Author: Omid Karami

Published: 2026-11-18T15:01:04Z

Content type: article

Language: en

Sources: [Snowflake Builders](<https://devfeed.tech/sources/snowflake-builders.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [data analyst](<https://devfeed.tech/topics/data-analyst.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [attribution](<https://devfeed.tech/tags/attribution.md>), [coco](<https://devfeed.tech/tags/coco.md>), [cost](<https://devfeed.tech/tags/cost.md>), [data](<https://devfeed.tech/tags/data.md>), [data-engineer](<https://devfeed.tech/tags/data-engineer.md>), [data-engineering](<https://devfeed.tech/tags/data-engineering.md>), [data-platform](<https://devfeed.tech/tags/data-platform.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [experiment](<https://devfeed.tech/tags/experiment.md>), [explore](<https://devfeed.tech/tags/explore.md>), [exploring](<https://devfeed.tech/tags/exploring.md>), [finops](<https://devfeed.tech/tags/finops.md>), [html](<https://devfeed.tech/tags/html.md>), [management](<https://devfeed.tech/tags/management.md>), [prompts](<https://devfeed.tech/tags/prompts.md>), [reports](<https://devfeed.tech/tags/reports.md>), [snowflake](<https://devfeed.tech/tags/snowflake.md>), [snowflake-coco](<https://devfeed.tech/tags/snowflake-coco.md>)

### AI overview

Snowflake CoCo and HTML Reports can turn Account Usage queries into shareable cost reports, but the report's usefulness depends on validating its data and SQL. In this case study, the report covered service, warehouse, query, storage, and CoCo usage; observed consumption spanned only November 9-10 of the requested 30-day window, and database storage returned no rows. Service-level CoCo metering was 5.1573 credits versus 5.3893 at the model level; warehouse figures also differed, with causes unverified. The reviewed SQL aggregated CoCo credits and tokens separately by model before joining, addressing a potential join-fanout concern without proving full financial reconciliation. HTML Reports are published snapshots: refreshing workspace data does not update a published artifact, which must be republished. During Public Preview, scheduled refresh and delivery were unavailable. Because viewers may access embedded data without source-table privileges, authors should review results, sensitive identifiers, and audience permissions before publishing. The report supports investigation, not automatic cost optimization or verified savings.

### Source excerpt

Exploring Snowflake's new HTML Reports capability through a practical cost consumption report -- and how AI-assisted reporting can support FinOps, cost visibility, and better platform decisions. AI-generated image created using ChatGPT by OpenAI.TL;DR Snowflake HTML Reports, introduced in Public Preview in November 2026, let practitioners use Snowflake CoCo to turn query results into shareable reports. This case study demonstrates a Snowflake Cost Consumption Report generated using the bundled cost-intelligence skill. It includes the original prompt, executed SQL, report screenshots, and validation findings. The experiment illustrates how AI-assisted reporting can support management decisions and FinOps, while highlighting the importance of data completeness, SQL verification, and transparent limitations. 1. From Data to Decisions: The Management Reporting Challenge "Where are our Snowflake credits going?" Answering this question often requires examining several Account Usage views. Service metering, warehouse consumption, query attribution, storage, and AI-assisted development activity each provide different perspectives. For Data Platform Teams, the challenge extends beyond retrieving metrics. Technical results must be organized into reports that stakeholders can understand, question, and use to prioritize investigations. I chose to explore whether CoCo and HTML Reports could bridge the gap between technical data exploration and management reporting. As a data engineer working with Snowflake, I see value in making platform consumption understandable beyond engineering teams. Cost consumption was a practical starting point because Snowflake already provides detailed Account Usage data. This allowed me to evaluate two things together: the AI-assisted reporting experience and the accuracy of the generated results. The objective was not to demonstrate automatic cost optimization or claim financial savings. It was to investigate whether an AI-assisted workflow could pro

## Tokenomics Foundation: Making sense of what AI actually costs you

DevFeed: [Tokenomics Foundation: Making sense of what AI actually costs you](<https://devfeed.tech/articles/tokenomics-foundation-making-sense-of-what-ai-actually-costs-you-140727.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4249751/tokenomics-foundation-making-sense-of-what-ai-actually-costs-you.html>)

Author: Raul Leite

Published: 2026-11-18T09:00:00Z

Content type: article

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [finops](<https://devfeed.tech/topics/finops.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apis-artificial-intelligence-development-approaches-software-development](<https://devfeed.tech/tags/apis-artificial-intelligence-development-approaches-software-development.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [business-value](<https://devfeed.tech/tags/business-value.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [costs](<https://devfeed.tech/tags/costs.md>), [development-approaches](<https://devfeed.tech/tags/development-approaches.md>), [foundation](<https://devfeed.tech/tags/foundation.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [linux-foundation](<https://devfeed.tech/tags/linux-foundation.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [tokenomics](<https://devfeed.tech/tags/tokenomics.md>)

### AI overview

The Tokenomics Foundation aims to help organizations connect AI spending to business value through open, vendor-neutral definitions, frameworks, cost-data standards, benchmarks, training, and certification; it does not provide a cost-tracking product. The excerpt describes two frameworks: a seven-layer stack that maps cost drivers from electricity to user requests, pointing teams toward areas such as model choice, caching, and context size; and Big-T notation, which classifies how model-call volume grows per user request--from a cached response (T(1)) and one call (T(n)) to multiplied calls, agent spawning, or unbounded loops. The author's practical starting question is how many model calls each workflow triggers, since hidden call multipliers can drive costs even as token prices fall. The excerpt does not detail the stack's seven individual layers.

### Source excerpt

For the last two months, I have been reading and trying to understand more about tokenomics. In my conversations with peers in the industry, I hear the same question more and more: "We're spending on AI, but what are we getting for it?" Most teams can tell me their monthly bill. Very few can tell me which use drove it. If you've ever opened an AI bill and felt your stomach drop a little, you're not alone. Cost companies now spend real money on tokens, API calls and GPUs. Very few can connect that number to a business result. That's the gap of the problem the Tokenomics Foundation wants to close. And honestly, it's about time someone did. Here's what I found, what it is, what it does and two ideas from it worth knowing. What is AI tokenomics? What I like about this definition is that it doesn't stop at the token price. In my experience, the price per token is rarely the problem. The problem is how many tokens quietly consume. Every prompt you send and every response you get is split into tokens, and each one costs something. AI tokenomics means understanding that cost structure and connecting it to business outcomes. As a rough rule, one token is about 4 characters, or 0.75 words, in English. AI tokenomics is the practice of managing that economy. The Foundation's own tagline sums it up: don't just count tokens, get value from the total cost of AI. That means looking at the whole picture, from the power and hardware that produce tokens to the business value they create. One quick clarification: this has nothing to do with crypto. In crypto, "tokenomics" means the supply and incentives of a coin. Here, it means the cost and value of running AI. Who is behind it The Tokenomics Foundation is a Linux Foundation project that launched in August 2026. It works alongside the FinOps Foundation, which did the same job for cloud spending. Members include large AI buyers such as banks and retailers, plus cloud and model providers. It doesn't sell a product or ship a cost-trackin

## A Seven-Slide Framework for Funding AI Transformation Without New Headcount

DevFeed: [A Seven-Slide Framework for Funding AI Transformation Without New Headcount](<https://devfeed.tech/articles/a-seven-slide-framework-for-funding-ai-transformation-without-new-headcount-140465.md>)

Original publisher: [Read original article](<https://hackernoon.com/a-seven-slide-framework-for-funding-ai-transformation-without-new-headcount?source=rss>)

Author: marian kamenistak

Published: 2026-11-18T07:00:02Z

Content type: tutorial

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [roadmaps](<https://devfeed.tech/topics/roadmaps.md>), [finops](<https://devfeed.tech/topics/finops.md>), [ai-experiments](<https://devfeed.tech/topics/ai-experiments.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption-strategy](<https://devfeed.tech/tags/ai-adoption-strategy.md>), [ai-transformation](<https://devfeed.tech/tags/ai-transformation.md>), [ai-transformation-costs](<https://devfeed.tech/tags/ai-transformation-costs.md>), [ai-workforce-planning](<https://devfeed.tech/tags/ai-workforce-planning.md>), [business](<https://devfeed.tech/tags/business.md>), [business-strategy](<https://devfeed.tech/tags/business-strategy.md>), [capacity](<https://devfeed.tech/tags/capacity.md>), [case](<https://devfeed.tech/tags/case.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [engineering-capacity-planning](<https://devfeed.tech/tags/engineering-capacity-planning.md>), [engineering-management](<https://devfeed.tech/tags/engineering-management.md>), [funding](<https://devfeed.tech/tags/funding.md>), [product](<https://devfeed.tech/tags/product.md>), [rice-prioritization](<https://devfeed.tech/tags/rice-prioritization.md>), [roadmap](<https://devfeed.tech/tags/roadmap.md>)

### AI overview

The article argues that an AI transformation without new hires should be funded in roadmap capacity, making the central question what product and engineering will jointly defer or drop. It proposes seven slides: the decision, product's expected payoff, an honest capacity breakdown, shared product and platform cuts, options to reduce scope/stretch/drop work, cost of delay, and written commitments from both leaders. It recommends showing the product benefit before the cuts, presenting them as a shared choice, and circulating the proposal and capacity table as a pre-read after discussing it with decision makers individually. The throughput figures, including a modeled recovery to about 3x by year-end, are illustrative assumptions rather than measured results; the article says leaders should commit to the multiplier and treat AI-generated cut suggestions as proposals.

### Source excerpt

Learn how engineering leaders can fund AI transformation through roadmap capacity, negotiate product trade-offs, and build a seven-slide business case.

## Cloud overspend is an accountability problem not a tooling gap

DevFeed: [Cloud overspend is an accountability problem not a tooling gap](<https://devfeed.tech/articles/cloud-overspend-is-an-accountability-problem-not-a-tooling-gap-136138.md>)

Original publisher: [Read original article](<https://www.networkworld.com/article/4249100/cloud-overspend-is-an-accountability-problem-not-a-tooling-gap.html>)

Author: Sean Michael Kerner

Published: 2026-11-16T19:49:24Z

Content type: news

Language: en

Sources: [Network World](<https://devfeed.tech/sources/network-world.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>), [Software as a service](<https://devfeed.tech/topics/saas.md>), [Infrastructure as a Service (IaaS)](<https://devfeed.tech/topics/infrastructure-as-a-service-iaas.md>), [Platform as a Service (PaaS)](<https://devfeed.tech/topics/platform-as-a-service-paas.md>)

Tags: [17](<https://devfeed.tech/tags/17.md>), [2026](<https://devfeed.tech/tags/2026.md>), [accelerated](<https://devfeed.tech/tags/accelerated.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [automation](<https://devfeed.tech/tags/automation.md>), [availability](<https://devfeed.tech/tags/availability.md>), [change](<https://devfeed.tech/tags/change.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cloud-computing-network-management-software-networking](<https://devfeed.tech/tags/cloud-computing-network-management-software-networking.md>), [cloud-operations](<https://devfeed.tech/tags/cloud-operations.md>), [control](<https://devfeed.tech/tags/control.md>), [cost](<https://devfeed.tech/tags/cost.md>), [design](<https://devfeed.tech/tags/design.md>), [doing](<https://devfeed.tech/tags/doing.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [flexera](<https://devfeed.tech/tags/flexera.md>), [gap](<https://devfeed.tech/tags/gap.md>), [governance](<https://devfeed.tech/tags/governance.md>), [iaas](<https://devfeed.tech/tags/iaas.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [network-management-software](<https://devfeed.tech/tags/network-management-software.md>), [networking](<https://devfeed.tech/tags/networking.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [tooling](<https://devfeed.tech/tags/tooling.md>)

### AI overview

Cloud overspend is framed as an accountability and operating-model problem: teams remain responsible for availability, cost, and risk while having less control over cloud mechanisms. Sherif cites Flexera's estimate that 29% of IaaS and PaaS spend is wasted and public cloud budgets run 17% over on average. He argues that more tools, training, self-service, or automation do not resolve responsibility without leverage. His method is to classify work as consuming SaaS, hosting workloads, or building custom services; prioritize the area with the greatest risk or volume; define the work areas and suitable governance or delivery patterns; then map current teams to identify gaps. SaaS-heavy organizations need vendor management and integration skills, while development-heavy ones need CI/CD pipelines and developer support. Cost, reliability, and security should be considered at design time. The supplied text presents this as Sherif's approach, not a universal prescription.

### Source excerpt

After years of using the clouds, many organizations are coming to realize they didn't have a proper plan in place from the get-go. Cloud adoption has often been driven by urgency, not design, according to Nabeel Sherif, principal advisory director at Infotech. It accelerated over the past 15 years, especially during the pandemic. Most organizations moved workloads and adopted SaaS, but the operating models behind that work did not change at the same pace. Infrastructure and operations teams, network teams included, now run on-premises and cloud side by side, often without a unifying model. They remain accountable for availability, cost, and risk but with far less direct control than in the past. The cost shows up in the numbers. Flexera's 2026 State of the Cloud Report, which Sherif cited, estimates that 29% of IaaS and PaaS spend is wasted. Organizations also run 17% over their public cloud budgets on average. During a session at the Infotech LIVE 2026 conference in Toronto, Sherif outlined a method for redesigning cloud operations around the work that needs doing, then assigning that work to teams. "Cloud doesn't eliminate operations work; it just changes its nature," Sherif said. Why more tools and training miss the problem The common reaction that many organizations have to cloud problems is to buy more tools or add training. Those actions don't however always solve the underlying issues. In Sherif's view, the data points to governance, organizational structure, visibility, and accountability as the right path forward. Accountability is the sticking point because ownership and control no longer line up in the cloud. "In traditional operations, you assume ownership of the stack. Cloud breaks that assumption," Sherif said. "You still own the outcomes. You don't necessarily own all the underlying mechanisms." He added that neither self-service nor automation fixes the issues. "Without redesign, you get responsibility without leverage," he said. "So, governance, cos

## Your AI is smarter. Is your business still working the same way?

DevFeed: [Your AI is smarter. Is your business still working the same way?](<https://devfeed.tech/articles/your-ai-is-smarter-is-your-business-still-working-the-same-way-135533.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4248443/your-ai-is-smarter-is-your-business-still-working-the-same-way.html>)

Author: Hang Tan

Published: 2026-11-16T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [AI Trends](<https://devfeed.tech/topics/ai-trends.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [finops](<https://devfeed.tech/topics/finops.md>), [AI for data automation](<https://devfeed.tech/topics/ai-for-data-automation.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assistants](<https://devfeed.tech/tags/ai-assistants.md>), [ai-strategy](<https://devfeed.tech/tags/ai-strategy.md>), [ai-value](<https://devfeed.tech/tags/ai-value.md>), [also](<https://devfeed.tech/tags/also.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [analyze](<https://devfeed.tech/tags/analyze.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-business-operations-digital-transformation-it-leadership-it-operations](<https://devfeed.tech/tags/artificial-intelligence-business-operations-digital-transformation-it-leadership-it-operations.md>), [automate](<https://devfeed.tech/tags/automate.md>), [benefit](<https://devfeed.tech/tags/benefit.md>), [better](<https://devfeed.tech/tags/better.md>), [business](<https://devfeed.tech/tags/business.md>), [business-operations](<https://devfeed.tech/tags/business-operations.md>), [but](<https://devfeed.tech/tags/but.md>), [can](<https://devfeed.tech/tags/can.md>), [cases](<https://devfeed.tech/tags/cases.md>), [challenge](<https://devfeed.tech/tags/challenge.md>), [cio](<https://devfeed.tech/tags/cio.md>), [company](<https://devfeed.tech/tags/company.md>), [constraint](<https://devfeed.tech/tags/constraint.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [digital-transformation](<https://devfeed.tech/tags/digital-transformation.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [it-operations](<https://devfeed.tech/tags/it-operations.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

AI can speed individual tasks while leaving business performance unchanged when work still waits on the same queues, approvals and system handoffs. The article argues that value comes from redesigning workflows around business outcomes: remove steps that no longer add value, then assign remaining work to conventional automation, agents or people with judgment and accountability. It cautions that not every problem needs an agent; a simple rule may work better and cost less. Employees build AI fluency and identify opportunities, while business leaders choose priority workflows and own results. CIOs should provide an approved, usable enterprise foundation combining trusted data, application connections, security and governance, and visibility into performance, cost and value. If that foundation is late or hard to use, teams may adopt tools and connections outside IT's view, creating fragmentation and risk. Measure success by changed business outcomes, not deployment, usage or hours saved.

### Source excerpt

AI is getting smarter at remarkable speed. Employees can draft, analyze, search and automate routine work faster than they could a year ago. Recent research on the state of AI shows organizations continuing to expand adoption across functions and use cases. Yet in many organizations, the business still works the same way. The same work moves through the same systems, waits in the same queues and stops at the same approvals. AI speeds up a task, and the benefit disappears into a process designed for another era. I see this from two vantage points. CDW works across thousands of customer environments, so we have a broad view of where AI creates value and where companies get stuck. I also help lead CDW's own AI strategy and transformation. We have made AI assistants available to more than 14,000 coworkers, built more than 12,000 agents and started redesigning core workflows. That experience has convinced me the CIO's challenge has changed. It is no longer simply enabling access to AI. It is helping the business move quickly without creating fragmented technology, uncontrolled cost and risks that IT will ultimately have to manage. Where the productivity gains get lost Here is the pattern I keep seeing. A company gives employees AI. People use it to summarize documents, prepare analysis and draft recommendations. Employees report saving time. But business performance barely moves. The reason is simple. Every task sits inside a larger workflow. An employee may finish one step faster, but the output still lands in the same queue and waits for the same sign-off. Another team may still re-enter it in a different system. The task got faster. The constraint just moved. We saw the same thing inside CDW. Usage climbed quickly, but usage alone couldn't tell us whether the business was performing better. The task is not the real unit of business performance. The workflow is. In many organizations, the next phase of AI value creation will come from improving how work moves across th

## Cloud reports measure the wrong thing

DevFeed: [Cloud reports measure the wrong thing](<https://devfeed.tech/articles/cloud-reports-measure-the-wrong-thing-133214.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4248511/cloud-reports-measure-the-wrong-thing.html>)

Author: David Linthicum

Published: 2026-11-13T16:21:12Z

Content type: opinion

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [finops](<https://devfeed.tech/topics/finops.md>), [Cloud Architecture](<https://devfeed.tech/topics/cloud-architecture.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-usage](<https://devfeed.tech/tags/ai-usage.md>), [analysts](<https://devfeed.tech/tags/analysts.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-architecture](<https://devfeed.tech/tags/cloud-architecture.md>), [cloud-architecture-cloud-computing](<https://devfeed.tech/tags/cloud-architecture-cloud-computing.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [cloud-costs](<https://devfeed.tech/tags/cloud-costs.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [finops](<https://devfeed.tech/tags/finops.md>), [flexera](<https://devfeed.tech/tags/flexera.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [governance](<https://devfeed.tech/tags/governance.md>), [hybrid-cloud](<https://devfeed.tech/tags/hybrid-cloud.md>), [iaas](<https://devfeed.tech/tags/iaas.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [metric](<https://devfeed.tech/tags/metric.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [public-cloud](<https://devfeed.tech/tags/public-cloud.md>), [report](<https://devfeed.tech/tags/report.md>), [reports](<https://devfeed.tech/tags/reports.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [survey](<https://devfeed.tech/tags/survey.md>), [team](<https://devfeed.tech/tags/team.md>)

### AI overview

The article argues that cloud survey metrics can make management activity look like maturity while obscuring architectural debt and weak business cases. It cites Flexera's survey of 753 cloud decision-makers: 64% measure value delivered to business units, 81% still prioritize cost efficiency and savings, 29% estimate wasted IaaS/PaaS spend, and 58% report using generative AI public cloud services. The author cautions that hybrid cloud may reflect acquisitions or inherited infrastructure rather than deliberate strategy, and that FinOps, dashboards, policies, and discounts can expose or reduce costs but cannot repair poor system design or uneconomic workload placement. It also questions whether reported "value" and AI use demonstrate measurable outcomes, noting that usage may include experiments or pilots. Because respondents are cloud-involved and the report is vendor-funded, the author recommends treating its findings as inputs rather than market truth.

### Source excerpt

Flexera's 2026 State of the Cloud Report agrees with many other cloud reports these days: Cloud is more strategic, cloud is more complex, AI makes everything harder, and better governance is the answer. This report, based on a survey of 753 cloud decision-makers and users, argues that enterprise cloud has entered a "value era" in which organizations are measuring success less by cost savings alone and more by business outcomes. The headline findings are familiar. Flexera says 64% of organizations now use "value delivered to business units" as a metric for cloud progress, up 12 percentage points year over year. Use of unit economics rose from 40% to 49%. Generative AI usage as a public cloud service rose to 58%, making it one of the most widely used public cloud services in the survey. Hybrid cloud remains dominant at 73%. Estimated wasted IaaS and PaaS cloud spend ticked up to 29%, reversing a five-year decline. Meanwhile, 71% of respondents say their company has a cloud center of excellence or a similar team, and 63% say they have a finops team. These reports provide a decent temperature check of what cloud teams are thinking about. The problem is what happens next. A survey of cloud-involved people becomes a story about the market. A set of self-reported answers becomes evidence of maturity. A vendor-funded report becomes a road map. Then CIOs, analysts, vendors, and conference speakers all repeat the same narrative until it sounds like reality. It is not always reality. The findings are not the problem I agree with Flexera that cloud complexity is increasing. I agree that AI is making cloud costs harder to predict. I agree that many enterprises are adding finops teams, governance groups, and centralized cloud functions. The issue is interpretation. The report frames much of this as cloud maturing into a more value-driven discipline. That is partly true, but it is also the optimistic version of the story. The less flattering version is that enterprises are still p

## Saying no to AI spend is how we protect AI value

DevFeed: [Saying no to AI spend is how we protect AI value](<https://devfeed.tech/articles/saying-no-to-ai-spend-is-how-we-protect-ai-value-131449.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4248060/saying-no-to-ai-spend-is-how-we-protect-ai-value.html>)

Author: Jay Miller; Ashley Rice

Published: 2026-11-13T10:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [shadow AI](<https://devfeed.tech/topics/shadow-ai.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [ai-experiments](<https://devfeed.tech/topics/ai-experiments.md>), [Finance](<https://devfeed.tech/topics/finance.md>)

Tags: [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-value](<https://devfeed.tech/tags/ai-value.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-budgeting-it-leadership-it-management-roi-and-metrics](<https://devfeed.tech/tags/artificial-intelligence-budgeting-it-leadership-it-management-roi-and-metrics.md>), [automation](<https://devfeed.tech/tags/automation.md>), [budget](<https://devfeed.tech/tags/budget.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [claude](<https://devfeed.tech/tags/claude.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [cost](<https://devfeed.tech/tags/cost.md>), [course](<https://devfeed.tech/tags/course.md>), [cross](<https://devfeed.tech/tags/cross.md>), [dev](<https://devfeed.tech/tags/dev.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [experimentation](<https://devfeed.tech/tags/experimentation.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [investment](<https://devfeed.tech/tags/investment.md>), [it](<https://devfeed.tech/tags/it.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [it-management](<https://devfeed.tech/tags/it-management.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [leaks](<https://devfeed.tech/tags/leaks.md>), [limit](<https://devfeed.tech/tags/limit.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [monthly](<https://devfeed.tech/tags/monthly.md>), [roi-and-metrics](<https://devfeed.tech/tags/roi-and-metrics.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [value](<https://devfeed.tech/tags/value.md>)

### AI overview

Paessler argues that AI spending limits should make usage a deliberate business decision while preserving room for valuable work. After experimentation and agent use drove unexpectedly high bills, it recommends setting group or per-person spending and token limits at rollout, then increasing them when a clear need justifies it. A cross-functional AI Center of Excellence reviews tools, checks whether existing products can meet needs, tests security, and provides shared guidance and training. The article also describes teaching employees that Claude's higher-effort responses use more tokens, and consolidating an app when the main platform could do the same job. Caps can prompt either a justified increase for critical work or a pause on low-priority experimentation; the process includes ongoing checks of performance, business value, and cost.

### Source excerpt

It's the 17th of the month and one of our engineers wants more credits for Claude. They've already spent $4,000 and we can't believe it. Barely halfway through July and they've not only overshot their monthly budget but need an even larger allocation. Soon after, alerts start going out that we've reached 75% of our allocated monthly spend limit. This request, among many others, made us think twice about AI spend. The interest is there and often the innovation is, too. But what about the value? If anyone asked us to approve an IT product that costs a few thousand dollars per seat, per month, would we say yes? Especially when the cost fluctuates and the return on investment isn't guaranteed? At Paessler, like many companies, we're building the AI boat as we sail it. The trouble is that spend leaks are common in the wild waters of automation. We realized the need to correct course: value-vs-spend checks serve as a necessary compass and a cross-functional AI team keeps the ship structurally sound, preventing things like shadow AI or unchecked agents from sinking the budget. We've learned the hard way that protecting AI value means being willing to sometimes say no, putting the processes and the people in place to make that call before the bill arrives. Heading into the new year, let's explore why "tokenmaxxing" is out and "valuemaxxing" is in. AI got a longer leash than any other software Earlier this year, our first AI-focused dev day showed us just how quickly expenses can get out of hand. We offered a $5,000 prize for the best feature we could build into our network monitoring platform. The team loved it, resulting in a record 29 submissions, with some deliberately choosing more expensive approaches to build things that would otherwise have been impossible, ranging from context-aware assistants to root cause analysis helpers. We encouraged that experimentation and gave a very long leash on cost, precisely because we'd never done it before and wanted to see the outcom

## Your AI ROI problem is a culture problem

DevFeed: [Your AI ROI problem is a culture problem](<https://devfeed.tech/articles/your-ai-roi-problem-is-a-culture-problem-131448.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4248056/your-ai-roi-problem-is-a-culture-problem.html>)

Author: Caitlyn Brazill

Published: 2026-11-13T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [ai-experiments](<https://devfeed.tech/topics/ai-experiments.md>), [finops](<https://devfeed.tech/topics/finops.md>), [Tool](<https://devfeed.tech/topics/tool.md>), [User Experience](<https://devfeed.tech/topics/user-experience.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-costs](<https://devfeed.tech/tags/ai-costs.md>), [ai-implementation](<https://devfeed.tech/tags/ai-implementation.md>), [ai-roi](<https://devfeed.tech/tags/ai-roi.md>), [algorithms](<https://devfeed.tech/tags/algorithms.md>), [anxiety](<https://devfeed.tech/tags/anxiety.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-employee-experience-it-leadership-it-management-roi-and-metrics](<https://devfeed.tech/tags/artificial-intelligence-employee-experience-it-leadership-it-management-roi-and-metrics.md>), [boston-consulting-group](<https://devfeed.tech/tags/boston-consulting-group.md>), [ceo](<https://devfeed.tech/tags/ceo.md>), [challenges](<https://devfeed.tech/tags/challenges.md>), [cio](<https://devfeed.tech/tags/cio.md>), [cios](<https://devfeed.tech/tags/cios.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-per-token](<https://devfeed.tech/tags/cost-per-token.md>), [culture](<https://devfeed.tech/tags/culture.md>), [data](<https://devfeed.tech/tags/data.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [efficiency](<https://devfeed.tech/tags/efficiency.md>), [employee-experience](<https://devfeed.tech/tags/employee-experience.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [generative](<https://devfeed.tech/tags/generative.md>), [generative-ai](<https://devfeed.tech/tags/generative-ai.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [it-management](<https://devfeed.tech/tags/it-management.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [roi](<https://devfeed.tech/tags/roi.md>), [roi-and-metrics](<https://devfeed.tech/tags/roi-and-metrics.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

The article argues that AI returns depend heavily on people and processes: it cites a BCG survey attributing about 70% of implementation challenges to those factors, and says high-value companies direct 70% of investment there. It recommends setting a named owner, baseline and business metric before starting; giving teams room to run bounded experiments and pivot; and building tools with the people who use them. Examples include ResumeBoost, which cut staff resume support time by over a third before its functionality was folded into a broader coaching platform, and Sherlock, built with job sourcing staff to filter more than 125,000 postings daily. Three weeks after launch, staff at nearly three-quarters of campuses had logged in and users reported saving over 100 hours. The article presents this as early progress and says continued improvement depends on dialogue between builders and users.

### Source excerpt

These days, when I talk to CIOs about how their organizations are using AI, there's a lot less excitement about new tools and the potential for higher productivity, and a lot more anxiety about what the return on investment has been so far. Because for most companies, that return has been less than expected, especially as cost per token is increasing. Last year, IBM's 2025 CEO study found that only 25% of AI initiatives had delivered the expected ROI over the last few years, and only 16% had scaled enterprise-wide. MIT's NANDA initiative found that 95% of generative AI pilots delivered no measurable P&L (profit and loss) impact. More recently, SAP and Oxford Economics' Value of AI Report 2026 found that 69% of businesses worldwide are "satisfied" with the ROI of their AI costs - but more than two-thirds think there's still room for improvement. It's tempting to read those numbers as a verdict on AI's limitations. But the research points somewhere else. When Boston Consulting Group surveyed 1,000 senior executives, it found roughly 70% of AI implementation challenges stemmed from people and processes, 20% from technology and 10% from the algorithms themselves. The companies seeing the most value from AI? They were investing 10% in algorithms, 20% in technology and data, and 70% in people and processes. As CIO, you don't just own the tools. You lead the teams that determine whether the tools pay off. My own experience with AI - integrating it into Per Scholas's classrooms, systems and processes to achieve even stronger outcomes for our learners - has convinced me that there are three cultural traits separating teams that produce returns from teams that produce pilots: they are results-oriented, entrepreneurial and collegial. Start with the result, and measure progress Decide what you're trying to change before choosing what to invest in. McKinsey's 2025 State of AI survey found that while 80% of companies set efficiency as an objective for their AI initiatives, the co

## From AI Tools to AI-Native: How HelloFresh Is Redesigning How Work Gets Done

DevFeed: [From AI Tools to AI-Native: How HelloFresh Is Redesigning How Work Gets Done](<https://devfeed.tech/articles/from-ai-tools-to-ai-native-how-hellofresh-is-redesigning-how-work-gets-done-130971.md>)

Original publisher: [Read original article](<https://engineering.hellofresh.com/from-ai-tools-to-ai-native-how-hellofresh-is-redesigning-how-work-gets-done-c71eb2b601f2?source=rss----ac51da0a699a---4>)

Author: Ingmar Krusch

Published: 2026-11-12T16:36:43Z

Content type: news

Language: en

Sources: [HelloTech](<https://devfeed.tech/sources/hellotech.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [workflow automation](<https://devfeed.tech/topics/workflow-automation.md>), [Platform Engineering](<https://devfeed.tech/topics/platform-engineering.md>), [internal developer platform automation](<https://devfeed.tech/topics/internal-developer-platform-automation.md>), [finops](<https://devfeed.tech/topics/finops.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Developer experience](<https://devfeed.tech/topics/developer-experience.md>), [Frontier AI](<https://devfeed.tech/topics/frontier-ai.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Claude](<https://devfeed.tech/topics/claude.md>)

Tags: [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [ai-native-transformation](<https://devfeed.tech/tags/ai-native-transformation.md>), [ai-tools](<https://devfeed.tech/tags/ai-tools.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [applications](<https://devfeed.tech/tags/applications.md>), [automate](<https://devfeed.tech/tags/automate.md>), [claude](<https://devfeed.tech/tags/claude.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [claude-cowork](<https://devfeed.tech/tags/claude-cowork.md>), [empowering-non-tech](<https://devfeed.tech/tags/empowering-non-tech.md>), [hellofresh](<https://devfeed.tech/tags/hellofresh.md>), [model-tiers-and-costs](<https://devfeed.tech/tags/model-tiers-and-costs.md>), [work](<https://devfeed.tech/tags/work.md>)

### AI overview

HelloFresh describes becoming AI-native as redesigning work around smaller teams and agents, rather than merely adding automation. Its shared foundations include a vetted AI Marketplace, a budgeted Model Router, a curated Company Brain, App Kitchen for governed hosting, and a Software Factory direction in which agents handle more delivery work while teams remain accountable. A review agent is live; broader agent identity and access controls are still in progress. Non-engineering staff build workflow tools, with personal sandboxes separated from reviewed, centrally hosted production tools; workflows involving core infrastructure, finance, or regulated customer data require Tech Team review. Routing suitable traffic to open-weight models cut model costs 41% in the first weeks, and an open-weight model matched a frontier review baseline at about 97% lower cost per review. The company tracks team delivery outcomes rather than tokens or lines of code, and says its main adoption opportunity is growing the share of employees building automated workflows. Company-wide AI-native workflows remain an ambition for next year.

### Source excerpt

Ingmar Krusch speaking at the GenAI Demo Session for non-tech HelloFresh employees HelloFresh has long brought a tech-first approach to an industry still catching up. AI extends that advantage, but only if we rethink how we work. Becoming AI-native means more than adopting tools or automating tasks. It means redesigning work across the company: removing obsolete processes, empowering smaller teams to own broader scope, and enabling AI agents to plan, decide, and execute alongside knowledge workers. Automating a flawed process only scales dysfunction. The opportunity is to fundamentally change what a team can accomplish. We are not starting from scratch, there are already many examples for agentic ways of working at HelloFresh: Our Start-Up Squads, cross-functional teams owning end-to-end scope, already build software with an AI agent as standard practice. Marketing uses AI at scale for media generation, AI-moderated focus groups, localization, and analytics. Operations has begun rolling out AI tools to over 1,000 employees. Scaling this company-wide is our core objective. This blog post shares what we've learned on our journey, from the technical foundations to the cultural shift and the lessons along the way. Enable Everyone to Build: Shared Platforms Over Custom Applications HelloFresh committed to becoming AI-native in late 2025, forming our first GenAI enablement team. In 2026, engineering began moving to agentic workflows. By mid-2026, the initiative expanded company-wide, enabling non-technical teams to automate processes and build custom applications. Instead of teams building isolated AI tools, we provide shared foundations anchored on four core pillars: Our AI Marketplace centralizes vetted skills and plugins for internal reuse. It serves Claude Code and Claude Cowork today, with support for OpenCode under way. Engineers and non-technical colleagues alike use it. Our AI Model Router gives every team one endpoint to frontier and open-weight models, with budg

## Hatz AI raises $24M to help small businesses go AI-native through their MSPs

DevFeed: [Hatz AI raises $24M to help small businesses go AI-native through their MSPs](<https://devfeed.tech/articles/hatz-ai-raises-24m-to-help-small-businesses-go-ai-native-through-their-msps-130364.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/12/hatz-ai-raises-24m-to-help-small-businesses-go-ai-native-through-their-msps/>)

Author: Mike Wheatley

Published: 2026-11-12T13:00:47Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [Managed Services](<https://devfeed.tech/topics/managed-services.md>), [ai security](<https://devfeed.tech/topics/ai-security.md>), [finops](<https://devfeed.tech/topics/finops.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-automation](<https://devfeed.tech/tags/ai-automation.md>), [ai-control-plane](<https://devfeed.tech/tags/ai-control-plane.md>), [ai-native](<https://devfeed.tech/tags/ai-native.md>), [ai-research](<https://devfeed.tech/tags/ai-research.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [autonomous-agents](<https://devfeed.tech/tags/autonomous-agents.md>), [early-stage](<https://devfeed.tech/tags/early-stage.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [funding](<https://devfeed.tech/tags/funding.md>), [hatz-ai](<https://devfeed.tech/tags/hatz-ai.md>), [it](<https://devfeed.tech/tags/it.md>), [it-outsourcing](<https://devfeed.tech/tags/it-outsourcing.md>), [jimmy-hatzell](<https://devfeed.tech/tags/jimmy-hatzell.md>), [managed-services](<https://devfeed.tech/tags/managed-services.md>), [managed-services-providers](<https://devfeed.tech/tags/managed-services-providers.md>), [medium-sized-businesses](<https://devfeed.tech/tags/medium-sized-businesses.md>), [msps](<https://devfeed.tech/tags/msps.md>), [news](<https://devfeed.tech/tags/news.md>), [series-a](<https://devfeed.tech/tags/series-a.md>), [siliconangle](<https://devfeed.tech/tags/siliconangle.md>), [small-businesses](<https://devfeed.tech/tags/small-businesses.md>), [startup](<https://devfeed.tech/tags/startup.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>)

### AI overview

Hatz AI raised $24 million in a Series A led by Nadia Partners to expand an AI platform delivered through managed services providers (MSPs). Its multitenant control plane offers governance guardrails, spend tracking, automated routing to leading frontier models, and customizable agents and workflows that MSPs can package under their own labels. The described workflows include ticket triage, operations, marketing, sales and bookkeeping. The company says this approach helps smaller businesses adopt AI through MSPs they already trust, addressing barriers such as limited in-house expertise and budgets, tool complexity, unpredictable compute costs and security concerns. Hatz AI reports that its active MSP partner base tripled over the past year and says it will use the funding to develop model-routing engines and software-factory infrastructure and expand engineering and research teams. The source provides company claims and selected product examples, not independent performance comparisons.

### Source excerpt

Large enterprises have emerged as the foremost adopters of artificial intelligence technology, and it's giving them an unfair advantage over their smaller competitors. Looking to change that is a startup called Hatz AI Inc., which has just raised $24 million in early-stage funding to empower managed services providers with the tools they need to keep [...] The post Hatz AI raises $24M to help small businesses go AI-native through their MSPs appeared first on SiliconANGLE.

## AI is everywhere. At what cost? Tech-Baithak London | Spectro Cloud

DevFeed: [AI is everywhere. At what cost? Tech-Baithak London | Spectro Cloud](<https://devfeed.tech/articles/ai-is-everywhere-at-what-cost-tech-baithak-london-spectro-cloud-132558.md>)

Original publisher: [Read original article](<https://www.spectrocloud.com/blog/tech-baithak-london-ai-cost>)

Author: Ant Newman

Published: 2026-11-12T00:00:00Z

Content type: article

Language: en

Sources: [Spectro Cloud Feed](<https://devfeed.tech/sources/spectro-cloud-feed.md>)

Topics: [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [digital sovereignty](<https://devfeed.tech/topics/digital-sovereignty.md>), [Local AI](<https://devfeed.tech/topics/local-ai.md>), [finops](<https://devfeed.tech/topics/finops.md>), [Developer Events](<https://devfeed.tech/topics/developer-events.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-certification](<https://devfeed.tech/tags/ai-certification.md>), [ai-roi](<https://devfeed.tech/tags/ai-roi.md>), [ai-skills](<https://devfeed.tech/tags/ai-skills.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [amd](<https://devfeed.tech/tags/amd.md>), [community](<https://devfeed.tech/tags/community.md>), [community-events](<https://devfeed.tech/tags/community-events.md>), [cost](<https://devfeed.tech/tags/cost.md>), [events](<https://devfeed.tech/tags/events.md>), [london](<https://devfeed.tech/tags/london.md>), [skills](<https://devfeed.tech/tags/skills.md>), [sovereignty](<https://devfeed.tech/tags/sovereignty.md>), [tokenomics](<https://devfeed.tech/tags/tokenomics.md>)

### AI overview

At the first Tech-Baithak London, speakers highlighted a tension between employers prioritizing AI skills in hiring and production teams still needing experienced humans to catch AI errors. Spectro Cloud's Ed Owen argued that falling token prices have not reduced bills: enterprise generative AI spending rose from $11.5 billion to $37 billion, while hosted models can send prompts, context and source code outside an organization. He outlined three approaches: use metered frontier APIs, build and maintain a private stack, or run open models locally behind a policy gateway with permitted bursts to frontier models. The article presents the third approach as the basis of Spectro Cloud's PaletteAI Inference Launchpad. It also notes that regulated firms need trustworthy, auditable decisions and evidence when changing models.

### Source excerpt

Notes from the first Tech-Baithak London: AI's cost, skills and accountability, Ed Owen on tokenomics and sovereignty, and why we back community events.

## OpenAI Codex on Amazon Bedrock

DevFeed: [OpenAI Codex on Amazon Bedrock](<https://devfeed.tech/articles/openai-codex-on-amazon-bedrock-129759.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/machine-learning/openai-codex-on-amazon-bedrock/>)

Author: Shivi Bhatia

Published: 2026-11-11T23:35:47Z

Content type: tutorial

Language: en

Sources: [Artificial Intelligence](<https://devfeed.tech/sources/artificial-intelligence.md>)

Topics: [codex](<https://devfeed.tech/topics/codex.md>), [Amazon Bedrock](<https://devfeed.tech/topics/amazon-bedrock.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [Amazon Bedrock AgentCore](<https://devfeed.tech/topics/amazon-bedrock-agentcore.md>), [Amazon CloudWatch](<https://devfeed.tech/topics/amazon-cloudwatch.md>), [Security, Identity, & Compliance](<https://devfeed.tech/topics/security-identity-compliance.md>), [LLM security](<https://devfeed.tech/topics/llm-security.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [AWS CloudTrail](<https://devfeed.tech/topics/aws-cloudtrail.md>), [finops](<https://devfeed.tech/topics/finops.md>)

Tags: [access-management](<https://devfeed.tech/tags/access-management.md>), [advanced-300](<https://devfeed.tech/tags/advanced-300.md>), [agentcore](<https://devfeed.tech/tags/agentcore.md>), [amazon-bedrock](<https://devfeed.tech/tags/amazon-bedrock.md>), [amazon-bedrock-agentcore](<https://devfeed.tech/tags/amazon-bedrock-agentcore.md>), [amazon-bedrock-guardrails](<https://devfeed.tech/tags/amazon-bedrock-guardrails.md>), [aws](<https://devfeed.tech/tags/aws.md>), [bedrock](<https://devfeed.tech/tags/bedrock.md>), [codex](<https://devfeed.tech/tags/codex.md>), [cost](<https://devfeed.tech/tags/cost.md>), [developers](<https://devfeed.tech/tags/developers.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [finance](<https://devfeed.tech/tags/finance.md>), [governance](<https://devfeed.tech/tags/governance.md>), [guide](<https://devfeed.tech/tags/guide.md>), [model](<https://devfeed.tech/tags/model.md>), [openai](<https://devfeed.tech/tags/openai.md>), [openai-codex](<https://devfeed.tech/tags/openai-codex.md>), [platform](<https://devfeed.tech/tags/platform.md>), [platform-security](<https://devfeed.tech/tags/platform-security.md>), [security](<https://devfeed.tech/tags/security.md>), [technical-how-to](<https://devfeed.tech/tags/technical-how-to.md>)

### AI overview

The article recommends starting a Codex-on-Bedrock rollout with a small, least-privilege Native AWS Access pilot. Validate workforce sign-in and direct Bedrock Runtime access before configuring Codex, then run a safe task and confirm identity, invocation, audit, and telemetry evidence; use two users to check identity attribution. AgentCore Gateway suits teams seeking AWS-managed routing or Bedrock Guardrails, while an existing or purpose-built LLM Gateway can enforce controls in the request path. Custom integration is the most involved option and should address a specific unmet requirement. Codex OpenTelemetry describes client activity; Bedrock service records, AWS identity records, and billing data provide different evidence, so token volume is not a cost report. Keep provider and organization settings in managed or user-level configuration, control plugins and MCP servers, expand in phases, and verify rollback by confirming new invocations are denied.

### Source excerpt

A practical guide for enterprises rolling out OpenAI Codex to developers on AWS, with Amazon Bedrock as the model backend, covering the access, governance, and cost decisions that platform, security, and finance teams need to align on.

## FinOps starts before the bill: visibility and ownership in small, chaotic teams

DevFeed: [FinOps starts before the bill: visibility and ownership in small, chaotic teams](<https://devfeed.tech/articles/finops-starts-before-the-bill-visibility-and-ownership-in-small-chaotic-teams-122300.md>)

Original publisher: [Read original article](<https://blog.devops.dev/finops-starts-before-the-bill-visibility-and-ownership-in-small-chaotic-teams-5fa0a3ed17b7?source=rss----33f8b2d9a328---4>)

Author: Soufiane Chahid

Published: 2026-11-07T20:46:01Z

Content type: article

Language: en

Sources: [DevOps.dev](<https://devfeed.tech/sources/devops-dev.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [Finance](<https://devfeed.tech/topics/finance.md>), [Cloud Networking](<https://devfeed.tech/topics/cloud-networking.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [bill](<https://devfeed.tech/tags/bill.md>), [billing](<https://devfeed.tech/tags/billing.md>), [builds](<https://devfeed.tech/tags/builds.md>), [business](<https://devfeed.tech/tags/business.md>), [business-value](<https://devfeed.tech/tags/business-value.md>), [but](<https://devfeed.tech/tags/but.md>), [certificate](<https://devfeed.tech/tags/certificate.md>), [change](<https://devfeed.tech/tags/change.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-computing](<https://devfeed.tech/tags/cloud-computing.md>), [company](<https://devfeed.tech/tags/company.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [devops](<https://devfeed.tech/tags/devops.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [finops](<https://devfeed.tech/tags/finops.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [ownership](<https://devfeed.tech/tags/ownership.md>), [small](<https://devfeed.tech/tags/small.md>), [teams](<https://devfeed.tech/tags/teams.md>), [visibility](<https://devfeed.tech/tags/visibility.md>)

### AI overview

In small teams sharing infrastructure across projects, FinOps often stalls before optimization because the people managing resources cannot see the bill or identify who owns each resource. The article recommends starting with visibility and ownership: give infrastructure operators read-only billing access, map running resources to projects, and use showback to make project costs visible without charging teams. It also treats unmanaged changes as operational and financial risks, and says to make infrastructure changes visible through a shared channel. For sizing, measure usage, weigh extra capacity costs against the cost of failure, and account for how quickly a machine can be resized. Security monitoring can also reveal cost anomalies such as compromised workloads consuming compute. Its 30-day sequence is to see resources and costs, assign owner labels, alert on certificate expiry and sustained high CPU, then review project costs and sizing. The author argues this requires someone with authority over both infrastructure and budget.

### Source excerpt

A production site went down for four hours because a certificate expired. Nobody had touched the certificate. A firewall rule had been changed at the cloud provider's edge, outside the usual runbook process, and it quietly blocked the renewal. There was no business impact at the time. But there could have been, and nobody saw it coming, because nobody had the full picture. At first glance, this isn't a FinOps story; it isn't about money. But it has the same root as most cost problems in small teams: things change where no one is looking. I've spent the past year as the only infrastructure and DevSecOps engineer for several products in production, so I've seen this from the inside. Most FinOps writing assumes a big company: a finance team, an infrastructure bill split by tags and ownership for each team, even maybe a dedicated FinOps practitioner. Even the State of FinOps 2026 survey reflects this: 80% of respondents work at organizations with 1,000+ employees, and those managing $100M+ in annual cloud spend average 8 to 10 FinOps practitioners. A five-person startup where the CTO holds the cloud account usually sees its bill just fine. The trouble starts when one small team runs shared infrastructure for many projects, as in a venture studio, an incubator, an agency, or a research lab, and the money sits somewhere else. One person builds and runs the infrastructure. Someone else holds the billing accounts. Another one pays them. Resources appear without anyone telling the person in charge. In that world, FinOps does not fail at optimization; it fails before that, at seeing and informing. FinOps in one paragraph FinOps isn't about cutting costs. It's about getting the most business value from every dollar spent on technology. Sometimes the right answer is to spend more, because it's worth it. The FinOps Foundation describes it as a loop of three phases: Inform: see where the money goes and who uses it. Optimize: use less, and pay less for what you use. Operate: turn

## In the era of AI, we are all buying technology wrong

DevFeed: [In the era of AI, we are all buying technology wrong](<https://devfeed.tech/articles/in-the-era-of-ai-we-are-all-buying-technology-wrong-120989.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4245173/in-the-era-of-ai-we-are-all-buying-technology-wrong.html>)

Author: Enrique Camacho

Published: 2026-11-06T09:00:00Z

Content type: opinion

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [The Three Main Cloud Service Models](<https://devfeed.tech/topics/the-three-main-cloud-service-models.md>), [AI Trends](<https://devfeed.tech/topics/ai-trends.md>)

Tags: [acquisition](<https://devfeed.tech/tags/acquisition.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-services](<https://devfeed.tech/tags/ai-services.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [budgeting-it-leadership-it-management](<https://devfeed.tech/tags/budgeting-it-leadership-it-management.md>), [business](<https://devfeed.tech/tags/business.md>), [capabilities](<https://devfeed.tech/tags/capabilities.md>), [contributor](<https://devfeed.tech/tags/contributor.md>), [cost](<https://devfeed.tech/tags/cost.md>), [disruptive](<https://devfeed.tech/tags/disruptive.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [emerging-technologies](<https://devfeed.tech/tags/emerging-technologies.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [features](<https://devfeed.tech/tags/features.md>), [fixed](<https://devfeed.tech/tags/fixed.md>), [innovation](<https://devfeed.tech/tags/innovation.md>), [it](<https://devfeed.tech/tags/it.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [it-management](<https://devfeed.tech/tags/it-management.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [licensing](<https://devfeed.tech/tags/licensing.md>), [locking](<https://devfeed.tech/tags/locking.md>), [models](<https://devfeed.tech/tags/models.md>), [negotiation](<https://devfeed.tech/tags/negotiation.md>), [operational](<https://devfeed.tech/tags/operational.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>), [technology](<https://devfeed.tech/tags/technology.md>)

### AI overview

The source argues that enterprise buyers can save on unit prices yet lose business value by specifying products before defining the problem. Rigid RFPs may exclude new approaches, while bundling mature SaaS or IaaS with fast-changing AI can lock buyers into inflexible terms and expose budgets to unpredictable usage. It recommends separating contracts by technology maturity, using small proof-of-value sandboxes with clear success, budget, and security criteria for emerging tools, and judging procurement by adoption, cost management, and ROI rather than discounts alone. Its examples illustrate the tradeoff: a regional insurer's RFP secured a 15% seat-license discount but maintained a call-center workflow that cost $3 million over two years, while a separate customer's unmonitored AI script consumed 18% of an annual infrastructure commitment in one weekend.

### Source excerpt

Every year, thousands of enterprise organizations walk into technology negotiations trapped by the same fundamental mistake: they negotiate a product instead of solving a problem. Having advised over 2,000 enterprise customers annually on technology acquisition over two decades, I see this pattern play out daily. Purchasing committees meticulously list the specific features, software modules and server specs they think they need, converting their organizational requirements into a static shopping list. On paper, this strategy feels disciplined. It creates a standardized, predictable item that procurement can use to negotiate a line-item discount with providers. When you buy a fixed product, you get the immediate, gratifying perception of a lower price. But that upfront discount can come at a hidden cost: you risk cutting yourself off from the disruptive innovation of emerging technologies like artificial intelligence (AI). By prescribing the solution before the negotiation even begins, enterprises force vendors into the narrow role of commodity suppliers rather than strategic partners. You ask them, "How cheaply can you build what our internal committee specified six months ago?" instead of asking, "What is the most efficient way to achieve this outcome today using capabilities we might not even know exist?" In an era where AI can reshape entire operational workflows, anchoring your procurement strategy to fixed product specifications means you may pay less for yesterday's way of doing business while missing the value of new capabilities. When procurement treats technology as fixed products, it tries to bundle mature products, such as software-as-a-service (SaaS) licenses, with rapidly evolving capabilities, such as AI services billed by token consumption, into one grand contract. You end up applying three-year static product licensing to AI capabilities that change on a monthly basis, locking your company into rigid pricing models and outdated technology. A request

## "Move Fast and Break Things" Is Dead. What Counts in Enterprise AI Now?

DevFeed: ["Move Fast and Break Things" Is Dead. What Counts in Enterprise AI Now?](<https://devfeed.tech/articles/move-fast-and-break-things-is-dead-what-counts-in-enterprise-ai-now-121021.md>)

Original publisher: [Read original article](<https://hackernoon.com/move-fast-and-break-things-is-dead-what-counts-in-enterprise-ai-now?source=rss>)

Author: Victoria Loskutova

Published: 2026-11-06T08:45:42Z

Content type: article

Language: en

Sources: [HackerNoon](<https://devfeed.tech/sources/hackernoon.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [Finance](<https://devfeed.tech/topics/finance.md>)

Tags: [2014](<https://devfeed.tech/tags/2014.md>), [2023](<https://devfeed.tech/tags/2023.md>), [2025](<https://devfeed.tech/tags/2025.md>), [2026](<https://devfeed.tech/tags/2026.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-boom](<https://devfeed.tech/tags/ai-boom.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [ai-cost](<https://devfeed.tech/tags/ai-cost.md>), [ai-cost-optimization](<https://devfeed.tech/tags/ai-cost-optimization.md>), [ai-for-finance](<https://devfeed.tech/tags/ai-for-finance.md>), [ai-infrastructure](<https://devfeed.tech/tags/ai-infrastructure.md>), [ai-powered](<https://devfeed.tech/tags/ai-powered.md>), [ai-spending](<https://devfeed.tech/tags/ai-spending.md>), [alarm](<https://devfeed.tech/tags/alarm.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alphabet](<https://devfeed.tech/tags/alphabet.md>), [business](<https://devfeed.tech/tags/business.md>), [cfo](<https://devfeed.tech/tags/cfo.md>), [cost](<https://devfeed.tech/tags/cost.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [enterprise-ai](<https://devfeed.tech/tags/enterprise-ai.md>), [finance](<https://devfeed.tech/tags/finance.md>), [financial](<https://devfeed.tech/tags/financial.md>), [roi](<https://devfeed.tech/tags/roi.md>)

### AI overview

Enterprise AI is shifting from rapid experimentation toward cost control and measurable returns as token bills rise and reported financial benefits remain limited. The article cites a PwC survey in which 56% of CEOs saw no significant AI financial benefit, and a Harness study in which 72% of organizations reported unexpected cost spikes; it notes Harness sells cost-management software. Uber reportedly exhausted its 2026 AI budget in four months, then capped employee spending per coding tool. Proposed practices include routing routine classification, extraction, and summarization to cheaper models, caching repeated prompts, tagging calls by team and feature, and setting budgets and alerts for agents. Cost tracking is becoming an architecture concern, but ownership remains concentrated in technology: 78% of FinOps teams report to a CTO or CIO, versus 8% to a CFO. The article flags a tension between financial discipline and exploratory research, with no 2026 evidence presented that cost controls are reducing exploration. It also contrasts customer spending caps with hyperscalers' reported $700-725 billion in 2026 capital expenditure, leaving demand assumptions unresolved.

### Source excerpt

Discover why enterprise AI is shifting from "move fast and break things" to a focus on cost control, ROI, and financial accountability in today's landscape.

## The Two-Ledger Model: Transaction-Grain Cost Accounting for Multi-Agent AI Systems Across Clouds, Models, and Systems of Record

DevFeed: [The Two-Ledger Model: Transaction-Grain Cost Accounting for Multi-Agent AI Systems Across Clouds, Models, and Systems of Record](<https://devfeed.tech/articles/the-two-ledger-model-transaction-grain-cost-accounting-for-multi-agent-ai-systems-across-clouds-models-and-systems-of-record-120147.md>)

Original publisher: [Read original article](<https://arxiv.org/abs/2611.06989>)

Author: Vivek Acharya

Published: 2026-11-06T05:00:00Z

Content type: article

Language: en

Sources: [arXiv: Artificial Intelligence](<https://devfeed.tech/sources/arxiv-artificial-intelligence.md>), [arXiv: Distributed Computing](<https://devfeed.tech/sources/arxiv-distributed-computing.md>)

Topics: [Multi Agent Systems](<https://devfeed.tech/topics/multi-agent-systems.md>), [ai observability](<https://devfeed.tech/topics/ai-observability.md>), [finops](<https://devfeed.tech/topics/finops.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>)

Tags: [a2a](<https://devfeed.tech/tags/a2a.md>), [accounting](<https://devfeed.tech/tags/accounting.md>), [billing](<https://devfeed.tech/tags/billing.md>), [correlation](<https://devfeed.tech/tags/correlation.md>), [cs-ai](<https://devfeed.tech/tags/cs-ai.md>), [cs-dc](<https://devfeed.tech/tags/cs-dc.md>), [cs-ma](<https://devfeed.tech/tags/cs-ma.md>), [focus](<https://devfeed.tech/tags/focus.md>), [large-language-models-llms](<https://devfeed.tech/tags/large-language-models-llms.md>), [multi-agent](<https://devfeed.tech/tags/multi-agent.md>), [opentelemetry](<https://devfeed.tech/tags/opentelemetry.md>), [probabilistic](<https://devfeed.tech/tags/probabilistic.md>), [rate-card](<https://devfeed.tech/tags/rate-card.md>), [reconciliation](<https://devfeed.tech/tags/reconciliation.md>), [shadow-ai](<https://devfeed.tech/tags/shadow-ai.md>), [simulation](<https://devfeed.tech/tags/simulation.md>)

### AI overview

The Two-Ledger Model aims to attribute AI costs to individual business transactions, which settlement-grain billing cannot do because providers do not see enterprise transaction boundaries. It joins a FOCUS-conformant settlement ledger with an invocation-grain attribution ledger built on OpenTelemetry GenAI telemetry. A layered correlation spine uses trace context, A2A/MCP metadata, business keys, then probabilistic matching, recording its method and confidence; a versioned rate card prices usage, and invoice reconciliation uses unexplained residuals to identify shadow AI. In a simulation, cost coverage stayed above 99% as trace propagation fell to zero, residuals recovered planted unmetered spend within 0.24 percentage points while flagging billing errors, and mid-flight gating reduced p99 transaction cost by up to 61% with a 2-4% false-pause rate. The authors propose standardizing the attribution ledger as an invocation-grain FOCUS profile.

### Source excerpt

arXiv:2611.06989v1 Announce Type: new Abstract: Enterprises run business transactions through multi-agent AI systems spanning clouds, large language models (LLMs), orchestration harnesses, and systems of record. Finance receives AI cost only at settlement grain, aggregated by SKU and charge period. The business question (what did this order, claim, or case cost in AI?) cannot be answered from billing data, because providers never see enterprise transaction boundaries. The FinOps Open Cost and Usage Specification (FOCUS) gives billing data one schema across providers but remains settlement-grain even as it adds AI token and requester attribution. We formalize this grain mismatch, derive seven requirements, and propose the Two-Ledger Model: a settlement ledger of FOCUS-conformant billing data joined to an attribution ledger of invocation-grain usage records built on OpenTelemetry GenAI telemetry. A layered correlation spine (trace context, A2A/MCP metadata, business-key correlation, probabilistic matching) assigns each record to its business transaction with recorded method and confidence; a versioned rate card prices usage in near real time; period reconciliation ties both ledgers to the invoice, and the unexplained residual identifies shadow AI. Costs are reported per order, claim, or outcome with agentic cost metrics. A simulation with known ground truth shows the spine sustaining cost coverage above 99% as trace propagation falls to zero, the reconciliation residual recovering planted unmetered spend within 0.24 percentage points while flagging provider billing errors, and mid-flight gating cutting p99 transaction cost by up to 61% at a 2-4% false-pause rate. We propose the attribution ledger as an invocation-grain FOCUS profile for standardization.

## Why AI Cost Management Isn't Cloud FinOps 2.0

DevFeed: [Why AI Cost Management Isn't Cloud FinOps 2.0](<https://devfeed.tech/articles/why-ai-cost-management-isn-t-cloud-finops-2-0-132618.md>)

Original publisher: [Read original article](<https://www.harness.io/blog/same-curve-twice-the-speed-why-ai-cost-management-isnt-cloud-finops-2-0>)

Author: Kelsey Rosen

Published: 2026-11-06T00:00:00Z

Content type: article

Language: en

Sources: [Harness](<https://devfeed.tech/sources/harness-blog.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [about](<https://devfeed.tech/tags/about.md>), [adapting](<https://devfeed.tech/tags/adapting.md>), [adopting](<https://devfeed.tech/tags/adopting.md>), [adoption](<https://devfeed.tech/tags/adoption.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-and-machine-learning](<https://devfeed.tech/tags/ai-and-machine-learning.md>), [ai-cost](<https://devfeed.tech/tags/ai-cost.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-finops](<https://devfeed.tech/tags/cloud-finops.md>), [cost](<https://devfeed.tech/tags/cost.md>), [cost-management](<https://devfeed.tech/tags/cost-management.md>), [finops](<https://devfeed.tech/tags/finops.md>), [isn-t](<https://devfeed.tech/tags/isn-t.md>), [management](<https://devfeed.tech/tags/management.md>), [organizations](<https://devfeed.tech/tags/organizations.md>), [speed](<https://devfeed.tech/tags/speed.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

AI cost management requires different budgeting and accountability from traditional cloud FinOps because AI spend varies by model, prompt, and task, while leaders expect ROI early. Harness's survey of more than 700 practitioners and engineering leaders found that organizations estimate roughly a quarter of AI spend is wasted; 52% have no dedicated cost owner, and many engineers lack cost data. The excerpt recommends defining value measures upfront, naming one accountable owner, and improving attribution and anomaly response. It describes Harness views linking AI tool adoption, generated code, pull request outcomes, and cost, plus plain-language queries and transaction-level anomaly investigation where OpenTelemetry tracing is available. Budgets can span vendors such as Claude and Cursor, but hard limits depend on vendor support and may fall back to reporting or alerts. Richer billing exports and tracing can help attribute usage. These examples are presented in an excerpt, not a complete account of the report or product.

### Source excerpt

AI spend is following cloud's adoption curve at twice the speed, with a quarter of it wasted and most organizations still without a clear owner. | Blog

## Apple is reportedly cutting budgets for its internal AI usage

DevFeed: [Apple is reportedly cutting budgets for its internal AI usage](<https://devfeed.tech/articles/apple-is-reportedly-cutting-budgets-for-its-internal-ai-usage-117935.md>)

Original publisher: [Read original article](<https://techcrunch.com/2026/11/04/apple-is-reportedly-cutting-budgets-for-its-internal-ai-usage/>)

Author: Lucas Ropek

Published: 2026-11-05T01:26:22Z

Content type: news

Language: en

Sources: [TechCrunch | AI News & Artificial Intelligence](<https://devfeed.tech/sources/techcrunch-ai-news-artificial-intelligence.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-costs](<https://devfeed.tech/tags/ai-costs.md>), [ai-usage](<https://devfeed.tech/tags/ai-usage.md>), [apple](<https://devfeed.tech/tags/apple.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [in-brief](<https://devfeed.tech/tags/in-brief.md>), [limit](<https://devfeed.tech/tags/limit.md>), [spending](<https://devfeed.tech/tags/spending.md>), [tc](<https://devfeed.tech/tags/tc.md>), [tokenmaxxing](<https://devfeed.tech/tags/tokenmaxxing.md>)

### AI overview

Bloomberg reports that Apple lowered its engineering teams' daily AI spending cap from $300 to $200 in October, with some allowances potentially falling to $100. The company is also reportedly weighing a daily limit as low as $25 for employees outside engineering. The excerpt links these cuts to companies reconsidering broad AI use as token costs mount, amid uncertainty about whether productivity gains justify the expense. Apple had not commented to TechCrunch at the time of the excerpt.

### Source excerpt

The company is said to be significantly dropping the amount it's spending on AI for its engineering teams.

## Your AI Bill Is a Data Problem

DevFeed: [Your AI Bill Is a Data Problem](<https://devfeed.tech/articles/your-ai-bill-is-a-data-problem-118740.md>)

Original publisher: [Read original article](<https://sdtimes.com/ai-costs/your-ai-bill-is-a-data-problem/>)

Author: David Lyman

Published: 2026-11-04T20:20:35Z

Content type: article

Language: en

Sources: [SD Times](<https://devfeed.tech/sources/sd-times.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [AI Infrastructure](<https://devfeed.tech/topics/ai-infrastructure.md>), [data-engineering](<https://devfeed.tech/topics/data-engineering.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [data](<https://devfeed.tech/topics/data.md>), [Data pipelines](<https://devfeed.tech/topics/data-pipelines.md>), [semantic-layer](<https://devfeed.tech/topics/semantic-layer.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [agents-in-production](<https://devfeed.tech/tags/agents-in-production.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [ai-spending](<https://devfeed.tech/tags/ai-spending.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [analysts](<https://devfeed.tech/tags/analysts.md>), [api](<https://devfeed.tech/tags/api.md>), [api-key](<https://devfeed.tech/tags/api-key.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [benchmark](<https://devfeed.tech/tags/benchmark.md>), [bill](<https://devfeed.tech/tags/bill.md>), [billing](<https://devfeed.tech/tags/billing.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [cost-governance](<https://devfeed.tech/tags/cost-governance.md>), [data](<https://devfeed.tech/tags/data.md>), [economics](<https://devfeed.tech/tags/economics.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [featured](<https://devfeed.tech/tags/featured.md>), [latest-news](<https://devfeed.tech/tags/latest-news.md>), [tokenmaxxing](<https://devfeed.tech/tags/tokenmaxxing.md>), [tokenomics](<https://devfeed.tech/tags/tokenomics.md>), [tokens](<https://devfeed.tech/tags/tokens.md>), [tools](<https://devfeed.tech/tags/tools.md>), [turns](<https://devfeed.tech/tags/turns.md>)

### AI overview

Enterprises may see their AI bills but often cannot connect spending to business value: only 9% of respondents in the Tokenomics Foundation survey were confident they could show value. The article identifies fragmented provider reporting and missing links between costs and request activity as attribution barriers; FOCUS and OpenTelemetry are working on a schema to associate cost and telemetry data. CData's benchmark found that adding business context sharply improved results across models: without context, about 1 in 400 runs succeeded, while 12 models achieved 15 of 15; the cheapest cost under a cent per correct answer and the most expensive about $1.17. In preliminary runs, context reduced median turns from 29 to 7 and tool calls from roughly 40 to 8. Suggested ways to reduce waste include shaping or replicating data before requests, or supplying business definitions through an AI gateway. The article cautions that switching models can break token caches, and says standard provider budgets and alerts do not explain cost per business question or correct answer.

### Source excerpt

Enterprises are getting better at seeing what they spend on AI. Proving what they got for it is another matter. During a recent SD Times Live! Supercast on the economics of AI, J.R. Storment, executive director of the Tokenomics Foundation, described a "whiplash" this year. Early on, tokenmaxxing was all the rage. By spring, he... ... continue reading The post Your AI Bill Is a Data Problem appeared first on SD Times.

## AI on Kubernetes: Essential Concepts for Platform and ML Teams

DevFeed: [AI on Kubernetes: Essential Concepts for Platform and ML Teams](<https://devfeed.tech/articles/ai-on-kubernetes-essential-concepts-for-platform-and-ml-teams-118975.md>)

Original publisher: [Read original article](<https://www.fairwinds.com/blog/ai-on-kubernetes-essential-concepts-for-platform-and-ml-teams>)

Author: Andy Suderman

Published: 2026-11-04T13:39:15Z

Content type: article

Language: en

Sources: [Fairwinds](<https://devfeed.tech/sources/fairwinds-blog.md>)

Topics: [Kubernetes](<https://devfeed.tech/topics/kubernetes.md>), [AI Platform](<https://devfeed.tech/topics/ai-platform.md>), [LLM optimization](<https://devfeed.tech/topics/llm-optimization.md>), [finops](<https://devfeed.tech/topics/finops.md>), [baseten](<https://devfeed.tech/topics/baseten.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-workloads](<https://devfeed.tech/tags/ai-workloads.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [concepts](<https://devfeed.tech/tags/concepts.md>), [essential](<https://devfeed.tech/tags/essential.md>), [featured](<https://devfeed.tech/tags/featured.md>), [kubernetes](<https://devfeed.tech/tags/kubernetes.md>), [managed-kubernetes](<https://devfeed.tech/tags/managed-kubernetes.md>), [ml](<https://devfeed.tech/tags/ml.md>), [platform](<https://devfeed.tech/tags/platform.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

AI workloads on Kubernetes require teams to coordinate GPU allocation, scheduling, storage, and model serving. The text distinguishes training, which typically runs as queued Jobs needing gang scheduling, from inference, which runs as long-lived services that benefit from autoscaling and request-aware routing. GPUs are requested in whole units unless shared, so low utilization and oversized CPU or memory requests can waste capacity. Device plugins expose GPUs by count; Dynamic Resource Allocation can match device attributes and supports sharing through ResourceClaims, but requires driver and workload migration planning. Time-slicing is flexible without guaranteed memory or performance, while hardware partitioning offers isolation in supported fixed sizes. Quotas, queues, and node autoscaling help allocate scarce GPUs, though node startup takes minutes and savings depend on removing freed nodes. Storage speed affects training resumes and model startup. The text also recommends tracking utilization separately from allocation, since an assigned GPU may be idle. Inference tradeoffs include scale-to-zero savings versus slow first responses, and in-place CPU or memory resizing without a,

### Source excerpt

Learn essential Kubernetes concepts for AI workloads, bridging the gap between platform and ML teams for effective resource management and model serving.

## Taming Cloud Costs: A Guide to the FinOps Framework in Google Cloud

DevFeed: [Taming Cloud Costs: A Guide to the FinOps Framework in Google Cloud](<https://devfeed.tech/articles/taming-cloud-costs-a-guide-to-the-finops-framework-in-google-cloud-116037.md>)

Original publisher: [Read original article](<https://medium.com/google-developer-experts/taming-cloud-costs-a-guide-to-the-finops-framework-in-google-cloud-85fff9762107?source=rss----a67bd6fa7d58---4>)

Author: Fed Mestrone

Published: 2026-11-03T13:13:50Z

Content type: article

Language: en

Sources: [Google Developer Experts](<https://devfeed.tech/sources/google-developer-experts-medium.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>), [Google Cloud Platform (GCP)](<https://devfeed.tech/topics/google-cloud.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [Finance](<https://devfeed.tech/topics/finance.md>), [Cloud](<https://devfeed.tech/topics/cloud.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [engineering-leadership](<https://devfeed.tech/topics/engineering-leadership.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [performance-engineering](<https://devfeed.tech/topics/performance-engineering.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [Test automation](<https://devfeed.tech/topics/test-automation.md>)

Tags: [abstract](<https://devfeed.tech/tags/abstract.md>), [abstractions](<https://devfeed.tech/tags/abstractions.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [applications](<https://devfeed.tech/tags/applications.md>), [based](<https://devfeed.tech/tags/based.md>), [bloat](<https://devfeed.tech/tags/bloat.md>), [bottlenecks](<https://devfeed.tech/tags/bottlenecks.md>), [business](<https://devfeed.tech/tags/business.md>), [business-value](<https://devfeed.tech/tags/business-value.md>), [but](<https://devfeed.tech/tags/but.md>), [cause](<https://devfeed.tech/tags/cause.md>), [cloud](<https://devfeed.tech/tags/cloud.md>), [cloud-costs](<https://devfeed.tech/tags/cloud-costs.md>), [cloud-finops](<https://devfeed.tech/tags/cloud-finops.md>), [cloud-finops-tools](<https://devfeed.tech/tags/cloud-finops-tools.md>), [costs](<https://devfeed.tech/tags/costs.md>), [finops](<https://devfeed.tech/tags/finops.md>), [framework](<https://devfeed.tech/tags/framework.md>), [google](<https://devfeed.tech/tags/google.md>), [google-cloud](<https://devfeed.tech/tags/google-cloud.md>), [google-cloud-platform](<https://devfeed.tech/tags/google-cloud-platform.md>), [guide](<https://devfeed.tech/tags/guide.md>)

### AI overview

The article presents FinOps as a shared engineering, finance, and business practice for making cloud spending visible and accountable while preserving team agility. It recommends a central governance function with financially informed staff embedded in product teams, clear RACI decision rights, and continuous cost allocation, forecasting, and optimization within engineering workflows. Its three-phase cycle is Inform (attribute and analyze costs), Optimize (reduce waste and improve rates), and Operate (apply ongoing guardrails), supported by five pillars covering accountability, measurement, optimization, planning, and tools. Named Google Cloud capabilities include Billing Reports and BigQuery Billing Export for visibility; FinOps Hub, Active Assist/Recommender, committed use discounts, Spot VMs, and BigQuery autoscaling for optimization; and budgets, alerts, Pub/Sub, Functions, policies, quotas, and labeling enforcement for governance. The article stresses that useful reporting depends on accurate resource labels and cost allocation.

### Source excerpt

FinOpsWhy FinOps is the DevOps of the Cloud Era I remember the early days of software engineering [Yes, I was there! Well, maybe not for the very very early days, but early enough...] As languages became more high-level and abstract, we became more productive and could create more software more quickly. But then we started needing new disciplines to manage the inefficiencies that the abstractions introduced: manual testing could no longer keep up with the sheer volume of output, so Test-Driven Development (TDD) came to the rescue; Performance Engineering emerged to wrangle the memory bloat and garbage collection latency introduced by managed languages like Java and Python; similarly, Site Reliability Engineering (SRE) and DevOps were born to manage the dizzying operational complexity that occurred once we abstracted monolithic applications into sprawling, virtualised micro-services. Today, the paradigm has shifted again. The computing power and storage we need for our applications and data are now based on rapidly elastic, globally distributed cloud infrastructure. This has unlocked unprecedented agility, allowing teams to innovate faster and scale instantly to meet global demand, deploying without the friction of physical hardware limits. Yet with infinite scale comes infinite spending potential. Because resources are consumed dynamically, unoptimised code and unchecked architectural decisions no longer just cause performance bottlenecks, they translate directly into an exponential financial drain. This reality has created the need for a new operational framework and cultural shift: Cloud FinOps. Just like DevOps, FinOps helps us to address the exact same underlying "crisis": speed breaks traditional organisational silos. When infrastructure becomes software and spending becomes dynamic, engineering decisions become financial decisions. FinOps brings technology, finance and business together to drive financial accountability and accelerate business value realisation

## 7 sure-fire ways to blow your AI budget

DevFeed: [7 sure-fire ways to blow your AI budget](<https://devfeed.tech/articles/7-sure-fire-ways-to-blow-your-ai-budget-113716.md>)

Original publisher: [Read original article](<https://www.cio.com/article/4240639/7-sure-fire-ways-to-blow-your-ai-budget.html>)

Author: Isaac Sacolick

Published: 2026-11-03T10:01:00Z

Content type: article

Language: en

Sources: [CIO](<https://devfeed.tech/sources/cio.md>)

Topics: [finops](<https://devfeed.tech/topics/finops.md>), [cloud cost management](<https://devfeed.tech/topics/cloud-cost-management.md>), [LLM observability](<https://devfeed.tech/topics/llm-observability.md>), [cost-optimization](<https://devfeed.tech/topics/cost-optimization.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-finops](<https://devfeed.tech/tags/ai-finops.md>), [ai-pricing-models](<https://devfeed.tech/tags/ai-pricing-models.md>), [ai-strategy](<https://devfeed.tech/tags/ai-strategy.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-budgeting-it-leadership-it-management-it-operations-it-strategy](<https://devfeed.tech/tags/artificial-intelligence-budgeting-it-leadership-it-management-it-operations-it-strategy.md>), [budget](<https://devfeed.tech/tags/budget.md>), [budgeting](<https://devfeed.tech/tags/budgeting.md>), [edition-us](<https://devfeed.tech/tags/edition-us.md>), [governance](<https://devfeed.tech/tags/governance.md>), [it-leadership](<https://devfeed.tech/tags/it-leadership.md>), [it-management](<https://devfeed.tech/tags/it-management.md>), [it-operations](<https://devfeed.tech/tags/it-operations.md>), [it-strategy](<https://devfeed.tech/tags/it-strategy.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [production](<https://devfeed.tech/tags/production.md>), [storytype-opinion](<https://devfeed.tech/tags/storytype-opinion.md>)

### AI overview

AI budgets can grow as experimentation moves into production: more users and agents drive consumption, while retries, context retrieval, and tool calls can make costs variable. The article identifies seven pitfalls: strategies without measurable business outcomes; delayed governance; focusing on token prices rather than total business value; deploying AI code generators without quality and cost standards; using frontier models for every task; failing to monitor agent cost spikes; and deploying agents without change management. It recommends tying spend to business metrics, assigning owners and controls, tracking total costs and outcomes at employee, department, and workflow levels, benchmarking code tools, routing tasks to suitable lower-cost models, and monitoring agent logs and runtime. Governance, budgets, and human review should evolve as systems mature, with trusted low-risk workflows earning greater autonomy over time.

### Source excerpt

CIOs have always felt pressure to deploy emerging technologies rapidly. Implementation brings challenges, including calculating and measuring upfront investment costs. Deploy too quickly, and when the hype fades, many IT departments are left with a costly architecture to support, security gaps, and operational issues. The same trend is happening with AI. Many CIOs procured enterprise-wide AI model licenses and empowered employees to experiment with language models and develop AI agents. Others asked DevOps teams to accelerate AI code generation and vibe coding. The shift from rapid experimentation to deploying more AI capabilities to production can leave CIOs with mounting AI debt and AI FinOps gaps. CIOs' near-term concern is managing budgets amid consumption-based AI pricing models. Even as AI token costs decrease, more employees are using AI, and agents are given more challenging, expensive assignments. Here are seven common mistakes IT leaders make that result in blown AI budgets. Defining an AI strategy without measurable business outcomes Most CIOs and CAIOs recognize the need to establish AI strategies focused on areas where AI can provide lasting business value. But many fail to quantify targeted business outcomes, leaving employees to use adoption metrics as the primary objective. "Every token spent on a pilot that never proves its value is money leaders can't get back and lost opportunity cost, which is a governance failure more than a technology one," says Rob Scudiere, CTO at Verint. "Every agent and workflow should have to earn its budget by showing results that achieve the desired business outcome, or lose it." Kris Beevers, CEO and cofounder of Netbox Labs, says to use existing business metrics to see whether the areas adopting AI are improving them faster. "If adoption is climbing but the outcomes aren't moving with it, that's a pretty good signal to rethink where you're spending," Beevers says. Recommendation: Financial impacts may be hard to target

## VCs bet $30M on Larridin's ability to help enterprises demonstrate AI's value for money

DevFeed: [VCs bet $30M on Larridin's ability to help enterprises demonstrate AI's value for money](<https://devfeed.tech/articles/vcs-bet-30m-on-larridin-s-ability-to-help-enterprises-demonstrate-ai-s-value-for-money-112968.md>)

Original publisher: [Read original article](<https://siliconangle.com/2026/11/02/vcs-bet-30m-on-larridins-ability-to-help-enterprises-demonstrate-ais-value-for-money/>)

Author: Mike Wheatley

Published: 2026-11-03T02:12:41Z

Content type: news

Language: en

Sources: [SiliconANGLE](<https://devfeed.tech/sources/siliconangle.md>)

Topics: [ai evaluation](<https://devfeed.tech/topics/ai-evaluation.md>), [finops](<https://devfeed.tech/topics/finops.md>), [AI Strategy](<https://devfeed.tech/topics/ai-strategy.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>)

Tags: [adoption](<https://devfeed.tech/tags/adoption.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-adoption](<https://devfeed.tech/tags/ai-adoption.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-coding-tools](<https://devfeed.tech/tags/ai-coding-tools.md>), [ai-impact](<https://devfeed.tech/tags/ai-impact.md>), [ai-insights](<https://devfeed.tech/tags/ai-insights.md>), [ai-investments](<https://devfeed.tech/tags/ai-investments.md>), [ai-technology](<https://devfeed.tech/tags/ai-technology.md>), [ai-tool](<https://devfeed.tech/tags/ai-tool.md>), [ai-usage](<https://devfeed.tech/tags/ai-usage.md>), [ai-value](<https://devfeed.tech/tags/ai-value.md>), [ai-value-measurment](<https://devfeed.tech/tags/ai-value-measurment.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [enterprises](<https://devfeed.tech/tags/enterprises.md>), [funding](<https://devfeed.tech/tags/funding.md>), [larridin](<https://devfeed.tech/tags/larridin.md>), [measurement](<https://devfeed.tech/tags/measurement.md>), [news](<https://devfeed.tech/tags/news.md>), [pelion-ventures](<https://devfeed.tech/tags/pelion-ventures.md>), [return-on-investment](<https://devfeed.tech/tags/return-on-investment.md>), [russ-fradin](<https://devfeed.tech/tags/russ-fradin.md>), [series-a](<https://devfeed.tech/tags/series-a.md>), [series-a-funding](<https://devfeed.tech/tags/series-a-funding.md>), [the-latest](<https://devfeed.tech/tags/the-latest.md>), [value](<https://devfeed.tech/tags/value.md>), [vcs](<https://devfeed.tech/tags/vcs.md>)

### AI overview

Larridin raised $30 million in a Series A led by Pelion Ventures to expand its platform for measuring the business value and costs of enterprise AI use. It connects adoption data with productivity and spending, tracks end-to-end workflows, and assesses the cost and value of autonomous agents. The article argues that logins and seat counts can miss operational impact: one customer found a single engineer accounted for 65% of its AI budget despite surveys showing 92% of engineers were active users. Larridin's report also found AI-assisted pull requests rose from 35% to 62% between April and September while median code-review waits increased by more than 50%. In another case, it found a 66-fold difference in cost per shipped code change between two AI coding tools; the customer dropped the pricier tool without affecting productivity. The company says it will use the funding to grow its go-to-market and engineering teams.

### Source excerpt

As enterprises ramp up their spending on artificial intelligence tools, it's only right for senior executives to want to know exactly what they're getting in return for their costly investments. Larridin Inc., a startup focused on AI adoption measurement, has just raised $30 million in Series A funding to try and provide them with the [...] The post VCs bet $30M on Larridin's ability to help enterprises demonstrate AI's value for money appeared first on SiliconANGLE.

[Next page](<https://devfeed.tech/topics/finops.md?cursor=WyIyMDI2LTExLTAzVDAyOjEyOjQxKzAwOjAwIiwgImUzYjM3NjY1LTkyZmYtNGZiNS1hOTdlLWExM2NhYTk1YTg5ZiJd>)