The CIO as Commercial Leader: How Technology Decisions Move the P&L

There is a version of the CIO role that is essentially a senior operational manager — keeping systems running, managing vendors, delivering projects on time and within budget. That version of the role is not without value. But it is the version that gets restructured away when budgets tighten, and it is the version that sits outside the room when strategic decisions are made.

The CIO role that has a seat at the table — the one that influences M&A decisions, that the CFO calls before a major investment committee, that the board genuinely listens to — is one that speaks commercial language as fluently as it speaks technology language. This is not about learning to present better. It is about genuinely thinking about technology decisions in terms of their commercial consequences, and building the measurement infrastructure to demonstrate those consequences in terms the business already uses.

The measurement problem

Most technology functions are measured on inputs and activities: uptime, project delivery rates, cost versus budget, ticket volumes. These metrics matter operationally. They do not tell the board whether the technology function is creating or destroying value.

The shift from activity metrics to outcome metrics is the most important change a CIO can make to their relationship with the business. It is also one of the harder changes to make, because it requires the technology function to take accountability for outcomes it does not fully control.

Consider the difference between these two ways of reporting on a platform modernisation programme:

The first: "We migrated 40% of our workloads to cloud infrastructure, delivered on time and 3% under budget, achieving 99.95% uptime throughout the migration period."

The second: "The cloud migration reduced our infrastructure cost base by $4.2M annually, improved our release cycle from quarterly to fortnightly, and contributed to the 12-point improvement in customer satisfaction scores we saw in Q3 — because our teams could respond to the product feedback we were getting faster than before."

Both descriptions are accurate. Only one of them gives a board member a reason to defend the technology function's budget in a difficult year.

FinOps as a strategic conversation, not a cost programme

FinOps — the discipline of managing cloud and technology costs with financial accountability — tends to be framed as a cost reduction exercise. In most organisations it is implemented by the finance team or a dedicated FinOps practice, with the CIO's team in a supporting role.

The CIOs who use FinOps most effectively treat it differently. They treat it as a mechanism for making technology investment decisions visible, defensible, and aligned to business priorities — not just a way to find savings.

The distinction matters because cost reduction and investment optimisation are different objectives with different organisational dynamics. A FinOps programme focused on cost reduction produces a technology team that is defensive about spending, slow to approve new investment, and constantly justifying existing infrastructure. A FinOps programme focused on investment optimisation produces a technology team that can demonstrate, in real time, which technology investments are generating returns and which are not — and that can redirect resources from the latter to the former with speed and confidence.

That second version of FinOps requires a level of financial visibility that most technology organisations do not have — not because the data does not exist, but because the management systems were not built to surface it in the form that drives investment decisions. Building that visibility is not a finance project. It is a technology leadership project, and it is one of the most commercially valuable things a CIO can do.

The CFO relationship

In the organisations where technology has the most strategic influence, the CIO and CFO have a genuine working relationship — not just a governance relationship. They talk before the budget cycle, not just during it. The CFO understands what the technology function is trying to achieve and why; the CIO understands the commercial pressures and capital allocation constraints the CFO is managing.

Building this relationship requires the CIO to do something that many technology leaders find uncomfortable: to be genuinely transparent about uncertainty. Technology projects are inherently uncertain — timelines slip, costs change, benefits emerge later or differently than projected. CIOs who present technology investments with false precision — a single point cost estimate, a specific benefit number, a firm delivery date — undermine their own credibility when reality diverges from projection, as it almost always does.

CFOs are accustomed to managing uncertainty. They work with ranges, scenarios, and probability-weighted outcomes. A CIO who presents technology investments in the same framework — here is the range of likely costs, here is the range of likely benefits, here are the key assumptions and the risks that would change the picture — is communicating in a language the CFO trusts. That trust is the foundation of the relationship that gives technology a genuine voice in strategic decisions.

Technical debt as a board conversation

Technical debt — the accumulated cost of decisions to defer maintenance, modernisation, or architectural improvement — is one of the largest hidden liabilities on most organisations' balance sheets. It is also one of the most difficult things to communicate to a board.

The challenge is that technical debt is invisible until it manifests as an incident, a failed project, or a competitive disadvantage. By that point, the conversation is reactive and the options are expensive. The CIO's job is to make technical debt visible before it becomes a crisis — and to frame it in terms that motivate action rather than producing paralysis.

The framing that works best is not technical. It is a business risk conversation: here is the capability we cannot build, or the speed we cannot achieve, or the cost we cannot reduce, because of the decisions that were made five years ago. Here is what it would cost to address it over three years. Here is what it will cost if we do not — measured in slower time to market, higher operational risk, and increasing maintenance burden that crowds out investment in new capability.

Boards make decisions about technical debt the same way they make decisions about any deferred maintenance: by weighing the cost of addressing it against the cost of not addressing it. The CIO's job is to give them the information to make that decision — not to advocate for a particular outcome, but to ensure the decision is made with clear eyes rather than in ignorance of the consequences.

What commercial leadership actually looks like

The technology leaders I have seen operate most effectively at the commercial level share a few consistent characteristics. They understand the unit economics of the business they are supporting — not at a high level, but specifically enough to understand how technology decisions affect cost per transaction, revenue per customer, or margin per product line. They have built the measurement infrastructure to demonstrate technology's contribution to those metrics. And they have the discipline to translate every significant technology decision — investment, deferral, or retirement — into its commercial consequence before presenting it to the business.

None of this requires the CIO to become a commercial operator. It requires the CIO to understand that technology decisions are commercial decisions, and to hold themselves accountable to commercial outcomes — not just to the delivery of technology projects.

That accountability is what distinguishes the CIO who has a genuine seat at the strategic table from the one who is invited to present and then asked to leave the room.

← All Articles