Two companies in the same sector, similar revenue, comparable headcount. Three years later one has doubled its margins and the other is still debating whether to replace the ERP. The most honest difference isn't in the product or the commercial team. It's in one box on the org chart: who the technology lead reports to.
A CIO under the CFO optimises for cost. A CIO under the CEO optimises for margin. Both will claim they "align technology with business". Only one does it, because the reporting line decides which question gets asked at every decision.
In 2026, with technology embedded in product, sales and customer relationships, keeping the CIO subordinate to finance is a decision that drains growth every quarter. And almost nobody on the board challenges it, because it's inherited structure that never shows up on an agenda.
The org chart decides the question
Picture a concrete decision: invest eight hundred thousand euros in a data platform that lets the commercial team see per-customer profitability in real time. Same project, two reporting lines.
CIO under CFO. The first question is: "what's the three-year licence cost? can we renegotiate?". The conversation pivots on amortisation, TCO, and benchmarks against what competitors paid. Approval takes four months. By the time it lands, the project is already poorly positioned in the committee's head: an expense that had to be justified.
CIO under CEO. The first question is: "what commercial decisions will it enable that we aren't making today? how much margin do we recover if we stop subsidising our least profitable customers?". The conversation pivots on P&L impact, execution speed and the opportunity window. Approval takes three weeks. The project enters the committee framed as a margin lever.
Same CIO, same project, same numbers. Entirely different outcomes, because the question on the table is different.
Call this the logical consequence of how questions get distributed across an organisation. The CFO has a fiduciary obligation to control cost and liquidity. Hand her the technology function and she'll apply the frame she knows best: controlled spend. It's role coherence at work.
The data exists and it isn't ambiguous
The Harvey Nash/KPMG CIO Survey has spent two decades tracking where technology leaders report. Numbers shift from edition to edition, but one pattern holds: CIOs reporting directly to the CEO are significantly over-represented in companies classified as high-performing, and their influence on strategic decisions tends to grow year over year compared with CIOs reporting to the CFO.
The Deloitte Global CIO Survey introduces a telling category: "Vanguards", CIOs whose agenda is oriented to growth and product rather than internal operations. The share of Vanguards reporting to the CEO is materially higher than for their "Trusted Operator" peers (the ones still focused on keeping the ship steady). It isn't coincidence. To be a growth agent you need to sit at the table where growth moves are decided.
The MIT Center for Information Systems Research (CISR) observed something similar throughout the digital transformation years: the more digital the business model, the closer the technology lead sat to the CEO. The exceptions were companies that, despite calling themselves "digital", ran an internal operation so mechanised that the CFO remained the natural owner.
"The CIO's reporting line is the most robust predictor we've found for whether a company will be aggressive or defensive with technology over the next five years."
— Synthesis of MIT CISR research
Why the CFO-CIO model worked, and why it doesn't anymore
CIO reporting to CFO has a solid historical rationale. Through the 1990s and 2000s, technology in a mid-sized European company amounted to three things: payroll, ERP and email. These were expensive, complex back-office systems with no direct impact on the customer offer. Grouping them with the rest of operational spend made sense.
The CFO owned the financial-discipline conversation around large SAP or Oracle projects. When the implementer drifted, the CFO had the tools to pull them back. The CIO of that era was often a senior project manager with an operational profile, not a business strategist.
That world is gone. Today technology is part of the product for almost any company billing more than twenty million euros. The customer portal, the service app, the recommendation engine, sales automation, AI in support, the data that drives which product ships in which channel: all of that is product, not back-office. All of it gets built with technology.
Keeping the owner of that stack inside the CFO's perimeter is like asking the head of product, in the 1980s, to report to the industrial cost controller. Coherent on paper. Devastating in practice.
Five questions that diagnose your reporting line
Before you move the org chart, run an honest diagnostic. These five questions, answered without filters in a thirty-minute conversation between CEO and board chair, reveal whether the current structure is a lever or a brake.
1. When did the CIO last present the board with a margin initiative rather than a savings initiative? If the answer is "never" or "I can't remember", the reporting line is pushing technology to justify itself on cost. In that model, the CIO spends the calendar defending budget, not discovering revenue levers.
2. Is the technology budget defended as a percentage of projected revenue or as a percentage of operational savings? The first framing puts the CIO on growth. The second traps her in containment. Changing the denominator of the conversation is the cheapest, most powerful mental change you can make this quarter.
3. Who signs strategic technology vendor contracts first, the CFO or the CEO? If the CFO always signs first, the vendor knows the conversation will be about cost. If the CEO signs first, the vendor knows it's about impact. Vendors tune their proposals to the counterpart. Your org chart conditions the kind of commercial relationship you'll have across your entire technology supply chain.
4. Is the CIO a full executive committee member or does she attend as a guest? "Guest" means you invite her when technology is on the agenda and send her out when strategy is. It's a signal to the rest of the committee that technology doesn't get to weigh in on the business. Few symptoms are more corrosive.
5. How many one-to-one conversations between CEO and CIO have happened in the last twelve months before a product or market decision? Fewer than five? Technology is arriving late to decisions. Arriving late means retrofitting something that was already promised to the outside world.
The European mid-market pattern
In European mid-sized companies there's a structural pattern that explains why the CIO ends up under the CFO even when nobody consciously chose it. The founder-CEO comes from a commercial or industrial background. The first executive hire is the CFO, because the company needs to close its books and deal with banks. Technology, at that moment, is an administrative function. When it's professionalised years later, it lands where the rest of the admin functions already sit: under the CFO.
Nobody pushes back because there was no decision to push back against. It's inheritance from when the company did fifteen million in revenue and ran a small ERP. Now it does one hundred and twenty million and operates a B2B portal, a data platform, customer integrations, sales automation and an AI pilot. The structure is still the 2008 structure.
The board rarely intervenes because the question feels minor. It does feel minor, until a big decision shows up (a platform swap, an AI bet, a cybersecurity investment) and the discussion gets stuck for months in the CFO's treasury while competitors execute.
A ninety-day sequence to move the reporting line
Changing a reporting line without setting off a political fire requires sequence and clear messaging. Good CFOs understand the shift as a redefinition of responsibilities. The bad ones take it personally. The CEO initiating the change needs to have done the homework before making any announcement.
Week 1–2. Honest diagnosis using the five questions above. Answer them yourself, on paper, without sharing with anyone. If three or more answers are uncomfortable, the decision is effectively made. If none are, leave the structure alone.
Week 3. Private conversation with the CFO before any announcement. The frame must be: "we're going to treat technology as a revenue lever. Your role in financial discipline doesn't change; what changes is the CIO's reporting line. I want you to remain the CIO's control partner, not his boss". If the CFO resists, the conversation becomes a leadership test for the CEO rather than a technical debate.
Week 4. Conversation with the CIO. The frame must be: "from now on your agenda stops being running the stack on time and on budget. It becomes margin impact and execution speed. Your KPIs change. I will ask you things you've never been asked, and stop asking for things that used to be the core of your evaluation". If the CIO isn't ready for that pivot, the reporting change gets paired with a coaching plan or, in some cases, a transition to a new profile.
Month 2. Reformulate KPIs and cadence of committees. The CIO becomes a full executive committee member. KPIs stop being uptime and cost-per-user. They become technology-assisted margin, decision-to-execution time, and two or three product or customer metrics the CIO agrees on with the CEO. The first version is almost always miscalibrated. Review it at ninety days.
Month 3. Internal and external announcement. Up to this point the change has been managed in a tight circle. Now you announce it to the organisation, to strategic vendors and, if relevant, to the formal board. Skip the "we've promoted the CIO" framing. Say instead that technology is a central strategic lever and the org chart now reflects it.
What happens if you don't
In the European mid-market, most companies that keep the CIO under the CFO between 2026 and 2028 will carry a compounding disadvantage. Not because the CIO is weaker. Because every technology investment cycle they decide will arrive late and out of context. And every late cycle widens the gap with the competitors who did reorganise in time.
You don't see it in one quarter. You see it after five years, when you look back and ask why a competitor who was smaller captured forty percent of the sector's growth while you defended margins.
If your current org chart was designed more than ten years ago and today technology touches product, channel or customer, it is probably out of date. The decision to change it belongs to the CEO. And it's free: no investment, no new hire, no vendor required. It just needs someone to say the conversation has changed.
Saying it out loud at the next executive committee is enough.
