The finance transformation bill is here. Can you explain it? 📊

In Partnership with

In order for AI efforts to pay off, you need department heads on board and embedded into your company's strategy. On 3/17, from 2-3pm ET, Section is giving away the formula for activating function leaders and translating company vision for priority teams.

Two separate CFO conversations this week revealed the same core issue: finance is being asked to support transformation before the financial benefits are expressed in a way the balance sheet can comprehend. In one case, controllership was still seen as just a reporting function when the business needed it to serve as an operational guide. In another, engineering was proudly reporting sprint velocity while finance still couldn't determine what was creating an asset and what was just increasing expenses.

This issue examines the representation gap within finance leadership, a practical approach to translating transformation into finance language before the budget discussion becomes confrontational, and three articles worth your time.

That figure is easy to categorize under culture, brand, or talent strategy. It also serves as a financial indicator. A narrow leadership pipeline limits the range of judgment available when companies decide how to allocate capital, govern AI, and design systems that will influence future growth. If you want a more resilient finance organization, don't only ask if you have strong operators at the top. Ask if your leadership bench is broad enough to challenge assumptions before they solidify into policy.

If the answer is no, you don't just have a representation issue; you also have a decision-quality issue.

At one SaaS company, the product team kept showcasing roadmap wins with clear sprint metrics and increasing release frequency. However, finance saw something very different. Engineering costs were climbing, capitalization was inconsistent, and no one could clearly explain which work extended the platform's life and which kept it running. The team believed the issue was messaging. It was not. The true problem was that the economic significance of the work had never been made explicit.

When your CFO asks whether transformation is creating enterprise value or just adding costs, you respond with a documented logic chain instead of a vague progress update. That is the difference between a budget discussion and a budget cut.

Controllership is transforming into a strategic value driver as CFOs depend on it for quicker insights, better forecasting, and more ready-to-use financial data.

My take: The real shift here is not just automation, but the expectation that controllership helps leadership act sooner, not only report later. If the underlying data and governance are weak, this expanded role creates speed without confidence, which is a risky trade for any CFO.

The core issue is that agile teams measure progress by delivery, while CFOs need that same work translated into capitalization, expense treatment, and economic impact. 

My view: Finance isn't resisting innovation; it’s resisting ambiguity that could distort how investment quality is understood. When product and engineering can't clearly explain the financial implications of their work, the CFO is left to shoulder the risk after spending has already been incurred.

The article argues that mentorship, sponsorship, and inclusive leadership development directly shape the quality of future finance decision-making, especially as AI and transformation reshape the function.

My take: This matters because the strength of the leadership pipeline determines whose judgment is present when strategy, controls, and systems are being designed. If the bench is too narrow, blind spots form early and are much harder to address later.

The main issue I see isn't that companies are rushing, but that transformation efforts in finance come mixed together: maintenance, refactoring, new features, and platform extension. When accounting is asked to interpret it, the original purpose is lost, and the discussion shifts from a clear process to a debate.

Can you show right now which current transformation initiatives are meant to create an asset, who approved that logic, and what evidence supports it? If not, this is the system to build before the next quarter closes.

The common failure this week isn't a lack of ambition; it's a lack of clear communication. Finance teams are being asked to support AI adoption, controllership modernization, and large-scale transformation without a shared economic language to define what the work truly entails.

That is why these three points connect. One emphasizes that controllership must evolve into a strategic value driver. Another explains why CFOs resist when transformation efforts lack clear financial purpose. The third highlights that the quality of future finance leadership relies on who is developed, sponsored, and heard before new systems are implemented.

If you want the CFO function to advance more quickly in 2026, don't begin with more dashboards. Instead, focus on clearer definitions, stronger governance, and a broader leadership team capable of asking better questions. That's how finance moves from merely reacting to change to actively shaping it.

Until next edition. — Marcus Reid, CPA.

P.S. If your finance team has already developed a clear way to distinguish transformational spend that builds a durable asset from spend that just keeps operations running, reply directly. I am gathering real examples of documentation and triggers that truly hold up under scrutiny.