When Technology Starts Behaving Like Capital

For most of the last twenty years, technology occupied a familiar place inside the organisation. It sat alongside rent, utilities and payroll: necessary, significant and worth managing carefully, but ultimately a cost.

The language reflected it. We spoke about technology budgets, technology spend and technology cost optimisation. Even as technology became strategically important, we continued to manage it through the vocabulary of expense.

The problem is that technology stopped behaving like an expense a long time ago.

Capital, in this context, is not an accounting classification. It is an economic behaviour. Capital is allocated with the expectation that it will create future value. Increasingly, technology investments are being approved on exactly those terms, not because they sit on a balance sheet, but because leadership expects them to improve productivity, accelerate growth, reduce risk or create competitive advantage.

That distinction mattered less when technology was primarily infrastructure. Servers, storage, networks and software licences largely behaved in predictable ways. Organisations bought capacity, teams consumed it and finance tracked the cost.

Today the relationship looks very different.

Cloud scales with usage. SaaS scales across teams. AI scales with behaviour.

A decision made by an engineer can influence gross margin. A workflow adopted by a sales team can alter operating leverage. An AI deployment can affect customer experience, productivity, revenue growth and cost simultaneously. Technology no longer sits neatly underneath the business. It increasingly sits inside it.

The economic profile of technology increasingly resembles an investment portfolio rather than a utility bill.

Yet many organisations continue to govern technology as though it were simply another cost centre.

Earlier this year, Uber revealed it had exhausted its 2026 AI coding budget by April after adoption of Claude Code spread faster than anticipated.

Most coverage framed it as a story about AI costs. I think it points to something more significant.

Nothing had failed. The technology was working. Teams were using it. Adoption was accelerating. The challenge was that consumption scaled faster than the economic model designed to govern it.

More telling was the discussion that followed. Uber's leadership openly questioned whether they could draw a clear line between AI usage and meaningful business outcomes. The debate was no longer whether AI mattered or whether engineers were using it. The harder question was whether the investment was producing enough value to justify the pace of spending.

That is a fundamentally different conversation.

Most organisations can tell you approximately what technology costs. The harder challenge is understanding what technology produces.

And that tension tends to surface at exactly the wrong moment.

The CFO arrives at the quarterly review with a straightforward question: what did the AI investment produce?

Not whether it was the right strategic direction or whether the team is capable. What did it return?

The CTO has numbers. Usage metrics. Deployment counts. A list of initiatives that are live and running. What they often cannot produce, with confidence and in real time, is a clear line from spend to business outcome.

The connection exists. Building the evidence to demonstrate it is a different problem altogether.

For the past two years, AI investment has often been justified through a simple lens: the risk of falling behind. Boards approved budgets. Executives accelerated experimentation. Leadership teams accepted uncertainty because the alternative felt more dangerous.

That period is beginning to end.

Renewals are arriving. Budgets are being scrutinised. Boards are asking harder questions. Organisations are increasingly being asked to explain not simply what they spent, but what they received in return.

This is where many discover a structural problem they did not know they had.

The people approving technology investments and the people deploying them have rarely operated with the same view of value. The CFO is trying to understand return. The CTO is trying to manage complexity. Product leaders are trying to determine which initiatives deserve investment next. Each perspective is rational. The connection between them is often incomplete.

That gap has existed for years.

AI did not create it. It exposed it.

As AI touches more functions across the organisation, the traditional distance between technology decisions and business outcomes becomes harder to ignore. Technology leaders are increasingly being asked questions that sound less like operational reviews and more like investment reviews.

And perhaps that is the real shift taking place.

Most organisations still manage technology as a budget to control. Increasingly, it behaves more like a portfolio to manage.

Cost management asks where to spend less, while portfolio management asks where to invest more. One optimises for efficiency; the other optimises for return.

The organisations that navigate this transition successfully will not necessarily be the ones spending the most. They will be the ones that develop a clearer understanding of which investments are creating value, which are not, and where capital should move next.

That is a capital allocation problem.

And capital allocation has always been one of leadership's most important responsibilities.

Yet few organisations have developed a discipline for managing technology investment on those terms.

The language has not yet caught up. The governance often has not either. The behaviour already has.

We call this Technology Capital Performance.

The discipline of treating technology investment as capital and managing it for the return it produces.

Technology has been managed as a cost for two decades. It has been behaving as capital for at least one.

The organisations that figure this out first won't just perform better. They'll be impossible to catch.