Udam Dewaraja - Founder & CEO of StitcherAI. Founded FOCUS, a finance standard adopted by thousands of enterprises.gettyWhich investments are actually working? Every leadership team is asking about technology spend. Rapid growth in AI spend has shifted the focus back to efficiency and business value. Budgets are tripling, new tools land every quarter, and no one wants to be the company that poured a fortune into AI and cannot show what it returned.Only a small group of organizations can answer that question. They know which initiatives earn their cost and which quietly drain it. That certainty is the advantage.What separates those teams from other teams is their AI strategy: They can model scattered cost data into a true picture of what each product, team and feature actually costs. That picture is trusted, and it's expressed in terms the business understands.The Prerequisite To know what an investment returns, you have to know what it costs, truly costs, across everything it touches.Most businesses know what they spent in aggregate. The financials say so. But ask what a single product costs across cloud, SaaS, on-prem and AI inference, or which customers are more profitable than others, and the answer means manually stitching together dozens of cost datasets. Below the top line, the picture is coarse, assembled on demand and trusted by few.That was survivable when costs were static and decisions happened at human speed. It isn't anymore. Technology decisions now happen within agentic workflows, hundreds of times a day and faster than any monthly review can keep up with. An unclear picture of cost, compounding at that speed, becomes an expensive one. The prerequisite to knowing business value is a cost model that is comprehensive, accurate and trusted. Most organizations don't have one.What A Cost Model Has To BeYou don't get there in one step, and you don't need to. Start with the cost data you already have. Start by putting it all into a common language, so cloud, SaaS, on-prem and AI inference stop being separate dialects and become a single dataset you can reason about. From there, assign that cost to the business constructs that drive clarity and accountability: products, teams, revenue streams, etc. Then, sharpen it with shared cost allocation. That step can turn a rough picture into a trustworthy one.Completeness is the direction, not the entry fee. What makes the path worth walking is that the numbers the business cares about get better at every step. Put your sources in a common language, and a margin once based on guesswork can become a figure. The model can then map costs to products and teams, and the figures can break costs down by feature, customer and segment. Allocate shared costs honestly, and those unit economics can stop being roughly right and become defensible. Each source you fold in, and each layer of modeling you apply, can tighten the same numbers. Because everything speaks one language, adding a provider never means rebuilding what came before.Two things sit outside that path because they aren't about coverage. The first is trust. When the logic lives in one spreadsheet and a few people's heads, the number gets taken on faith until the first time it's wrong. A methodology open to inspection is one that people can act on. The second is pace. Organizations don't hold still, so a model that takes a reengineering cycle to update is always describing the company as it was months ago.What It ChangesAs your cost model becomes more complete, transparent and trusted, change can run straight through your organization.Start with the conversations that used to be arguments. A disputed chargeback can stop being a negotiation because the team being billed can see how the number was reached. Reconciliation can stop being a forensic exercise across four systems. Forecasts can be presented as figures leadership can plan against, with all associated assumptions visible underneath them, rather than buried in caveats. The monthly friction that consumes IT finance teams can quietly drain away.Larger changes can then compound. As costs become more complete, modeled in business terms and open to inspection, they can stop being things a central team reports and become something every function can embed into its decision-making, by both humans and agents. An engineer can see what an architecture choice costs while making it. A product manager can see the margin per feature during planning, not three weeks after the feature ships. A business lead can see the cost to serve a segment before committing to it. The decisions that move spend were always distributed across these people. A cost model built right is what can finally give them the context to own those decisions.That is the real prize, and it is why the few organizations that have it can pull ahead. They can tell which investments earn their cost and which drain it, so they can double down on what works and stop what doesn't months before competitors notice. Your IT finance team can change alongside your cost model. Their work can stop being the assembly and defense of numbers and become the stewardship of the model itself: owning the methodology, setting the standard the organization trusts and shaping where the money goes. It can shift from explaining the past to directing the future.A cost model this complete and this trusted has historically been out of reach for most organizations I've seen in the industry. It's too slow and too costly to build by hand. But that is the part that has changed. The foundation that once took years to construct is now within reach.Forbes Technology Council is an invitation-only community for world-class CIOs, CTOs and technology executives. Do I qualify?
The Business Value Of AI: How Do You Get There?
As your cost model becomes more complete, transparent and trusted, change can run straight through your organization.
Organizations triple AI spend but lack unified cost models for cloud, SaaS, on-prem and inference. A complete cost model lets engineers and product teams own decisions, cutting underperforming investments months before competitors.






