The Real Cost of CFO Scope Creep

CFO Scope Creep: When Everything Reports to the CFO

The org chart said they didn’t have a COO. The calendar said the CFO was running operations, HR, and IT while signing off on the quarterly close at midnight.

I see this pattern regularly in growth-stage and mid-market companies. Nobody decides to turn the CFO into the operating executive. Responsibilities migrate toward the person who reliably gets things done. IT first. Then HR. Then contracts, facilities, systems, procurement — whatever else lacks a natural owner.

Eventually the org chart still shows a CFO. The operating model shows something else.

The Ferrari Version

Mattia Binotto had been at Ferrari since 1995. He rose through the engineering ranks and became Chief Technical Officer in 2016. In January 2019, Ferrari promoted him to Team Principal.

When the team announced the move, they confirmed that all technical areas would continue to report directly to Binotto. The technical director role was distributed across several engineers, but Binotto himself acknowledged that the organization needed to restructure internally to support him on the technical side.

What interests me is not the internal politics of Maranello. It’s what happens when an organization promotes a deeply valuable functional leader without becoming equally clear about where the old responsibilities end and the new ones begin.

Ferrari returned to front-running competitiveness under Binotto. The 2022 car was fast enough to challenge for the championship — Charles Leclerc won two of the first three races. But the title campaign was undermined by reliability problems, strategy errors, and operational mistakes that cost the team position after position. Ferrari started on pole twelve times and converted only four wins.

The car was competitive enough to fight at the front. Too many things around it were not.

Binotto resigned at the end of 2022. Whatever combination of factors drove that outcome, the organizational question remains useful: when a company promotes its most capable functional leader into a broader role without genuinely redesigning what sits underneath, it risks weakening two functions instead of strengthening one.

That’s the CFO problem, translated into a pit lane.

How Responsibilities Accumulate

Nobody designs an organization where the CFO runs operations, HR, and IT. It accretes, one responsibility at a time, each individually reasonable.

IT often lands under finance because budgets and vendor contracts already sit there. HR may start in finance because payroll does. Facilities, procurement, and internal systems follow for the same reason: the CFO manages what touches money, and in a growing company, most things touch money.

Each decision is defensible in isolation.

The problem appears later. Functions that began as administrative responsibilities become strategic — or simply grow large enough to require genuine leadership. A system migration. A cybersecurity incident. A compensation structure that needs redesigning. An employee relations issue that consumes twenty hours of executive attention in a week.

The reporting line never changes because the CFO keeps making it work.

That’s the distinction this article is about. There is nothing inherently wrong with a CFO who oversees IT, or procurement, or even HR administration in a smaller company. Plenty of effective CFO organizations are designed that way deliberately.

The pattern I keep seeing is different. It’s scope that has accumulated because nobody else owns it — not because someone designed it to sit there.

What Breaks Quietly

The danger isn’t dramatic. It’s three things that degrade simultaneously, none of them loudly enough to trigger an alarm.

Finance loses strategic attention. The CFO’s core value is financial stewardship — cash management, forecasting, risk identification, board-level governance. That work requires focused analytical time. The CFO who spends Monday managing an IT vendor problem, Tuesday on an HR escalation, and Wednesday negotiating an office lease does not have the same quality of attention available for the financial work that justifies their seat at the table.

The symptoms are specific but easy to miss. Financial reporting takes longer. Forecasts become less precise. The board receives updates that are adequate but not insightful. Cash management becomes reactive. Nobody measures the decline because the numbers still get reported. The work gets done. It gets done less well.

The CFO becomes a cross-functional single point of failure. By the time the CFO raises the issue — or leaves — the organization discovers simultaneously that it has lost its financial leader, its de facto operating executive, its HR escalation point, and its IT decision-maker. One departure creates four vacancies.

That isn’t dedication. It’s concentration risk disguised as executive capability.

The organization delays building what it actually needs. This is the most consequential failure, and the hardest to see while it’s happening.

When the CFO manages operations, the operations get managed. Adequately. Personally. Reactively.

What doesn’t happen is the construction of systems, teams, and processes that would allow those functions to operate independently. The CFO doesn’t build an operations team because they’re managing operations themselves. They don’t invest in HR leadership because the current approach — the CFO handling escalations personally — works well enough. Their presence substitutes for infrastructure.

The CFO’s competence at carrying the extra scope is precisely what prevents the organization from investing in the infrastructure it needs. The arrangement can persist for years because the work keeps getting done.

Sometimes the clearest evidence that an operating model is underbuilt is the executive who keeps making it work anyway.

The Diagnostic: CFO Scope Creep

Five questions reveal whether executive capacity has been substituting for organizational design.

Which functions require the CFO personally to keep moving? Not formally. Actually. Which decisions stall, which vendors go unmanaged, which people issues queue up when the CFO is unavailable?

What work would stop or accumulate if the CFO disappeared for two weeks? If the answer involves IT decisions being deferred, HR issues piling up, and operational questions waiting, the CFO is carrying functions the organization has not built to sustain independently.

Which responsibilities reached finance by design, and which arrived by default? This is the question most companies have never asked. IT may report to finance because it was deliberately placed there. Or it may report to finance because nobody else claimed it in 2019 and the reporting line was never revisited. The organizational implications are very different.

What financial work is receiving less attention because of the accumulated scope? Not whether the CFO is busy. Whether the strategic financial work — the forecasting, the cash management, the board-level governance — is getting the quality of attention the organization needs from it. A CFO can be working eighty hours a week and still be underserving the financial function if forty of those hours go elsewhere.

Is the CFO building leaders underneath these functions, or personally substituting for them? If HR, IT, or operations have grown but still depend on the CFO’s personal involvement for every significant decision, the CFO is compensating for an absence of functional leadership. That works until it doesn’t.

Two Complications Worth Naming

Before reaching for the obvious prescription, two things are worth examining.

The CFO may want the broader mandate. Some CFOs are deliberately expanding their operating scope. They may be preparing for a CEO role. They may be acting as president in all but title. They may be leading a transformation, overseeing shared services, or running what some organizations call a CFO-plus mandate.

That isn’t necessarily dysfunction. The question is whether the broader scope is intentional, resourced, and reflected in what the organization expects from the financial function. A CFO who is explicitly chartered to run operations and finance — with appropriate support underneath — is a different situation from a CFO who has absorbed four functions because nobody else would.

The answer may not be a COO. The title implies a missing COO. Maybe. But the company may actually need a controller, a Head of People, a CIO, a VP of Operations, a chief administrative officer, or simply stronger functional leaders underneath the CFO.

The reflex to hire a COO because the CFO is overloaded can be its own calibration mistake. The better question is: what exactly has accumulated around the CFO, why did it accumulate there, and which parts of that accumulated scope require genuine executive leadership versus better functional management?

That question may lead to a COO. Or it may not.

When the Structure Needs to Change

If the diagnostic reveals that the CFO’s scope has grown beyond what the operating model can sustain, the response should not be a predetermined sequence. It should follow from what the company actually finds.

Separate the function whose dependence on the CFO creates the most risk, consumes the most executive judgment, or has grown furthest beyond the CFO’s expertise. In some companies that’s HR, because people decisions are unpredictable and time-intensive. In others it’s IT, because a system migration or security incident requires technical leadership the CFO cannot provide. In others it’s operations broadly — the accumulation of facilities, procurement, logistics, and vendor management that has quietly become a second job.

Different company. Different answer.

What matters is that the CFO’s mandate narrows back toward financial leadership — not because the CFO can’t handle operational work, but because the organization can’t afford to have its strategic financial capacity diluted by work that should be led elsewhere.

The CFO who returns to a focused financial mandate will produce better insight, more accurate forecasts, and stronger governance. The value gained by narrowing the focus will exceed whatever the CFO was providing by spreading across four functions adequately.

CFO Scope Creep: The Real Pattern / TLDR

The CFO may be handling the extra scope perfectly well. That’s what makes the problem difficult to see.

An organization where the work is visibly falling apart gets attention. An organization where one capable executive keeps preventing it from falling apart can go years without examining whether the structure underneath is sufficient.

The dangerous question is not whether the CFO can carry the load. Most of the time, they can. For a while.The question is what the organization is not building while the CFO compensates for its absence.

Charlie Solórzano is a Managing Partner at Alder Koten, a boutique executive search firm specializing in C-suite and board placements across the U.S. and Mexico markets. He advises founders, investors, and boards on leadership transitions using The Race Conditions Model™, a proprietary diagnostic framework built on the thesis that leadership success is determined by conditions, not credentials. He also leads the Sports Practice at both Alder Koten and IMD International Search Group, a globally coordinated executive search network operating across 26 countries.