(Image credit: IIR/Gemini.)
Most insurance CIOs understand why modernization matters. Translating that conviction into terms that resonate with the CFO and board is often the harder part.
Technology leaders tend to describe modernization in operational terms: faster product launches, easier integrations, more resilient systems and less dependence on manual work. Finance leaders, however, must evaluate the investment through its expected return, accounting treatment and effect on future budgets.
That difference in perspective can make essential modernization spending appear discretionary—particularly when its greatest benefits will emerge over several years rather than on the current year’s income statement.
The solution is not simply for CIOs to speak more persuasively about technology. They must structure and manage technology investment in a way that finance already understands.
The Modernization Value Gap
Finance looks for measurable returns and a high degree of confidence in when those returns will materialize. Insurance modernization, by contrast, often creates capacity whose value becomes visible only over time.
A modern policy administration system may support faster product launches. A new integration layer may make it easier to connect distributors, data providers and InsurTech partners. A cloud migration may reduce infrastructure constraints and improve resilience. A claims-platform investment may shorten cycle times or reduce the need for manual intervention.
Some of those benefits can be quantified immediately. Others emerge through launches that reach the market sooner, integrations that no longer require extraordinary effort and outages that never occur.
When the payoff does not appear clearly on the current year’s P&L, the investment can look optional. Optional spending is usually where budget reductions begin.
Capitalization Does Not Eliminate Cost
Insurance technology programs involve real accounting treatment, capitalization decisions and multiyear consequences. Technology leaders should understand those consequences as well as their counterparts in finance do.
When eligible project costs are expensed, the full amount is recognized on the income statement as incurred. When qualifying costs are capitalized, the expense is recognized over the asset’s useful life through depreciation or amortization.
That treatment can reduce the immediate P&L impact of a major modernization program. It does not make the cost disappear.
Every capitalized project creates a future obligation that subsequent budgets must absorb, whether or not the technology continues to deliver the value that justified the original investment.
Over time, insurers can accumulate what might be called a capitalization ladder. As new programs are added year after year, depreciation and amortization from earlier investments consume an increasing share of the technology budget.
Total IT spending may continue to grow while the amount available for new investment shrinks. From the boardroom, it can look as though technology is becoming more expensive while producing less incremental value.
The underlying problem may not simply be the amount being spent. It may be the structure of the portfolio and the effect of decisions made several budget cycles earlier.
Before approving another major program, CIOs and CFOs should examine how its future costs will combine with obligations already in place.
The Cloud Complication
Cloud adoption makes this conversation more important.
The transition from owned infrastructure and licensed software to SaaS and consumption-based services has shifted much technology spending from CapEx toward OpEx. Subscription and consumption costs that recur annually can raise operating expense even when the migration improves flexibility, resilience or speed.
A CFO may see technology OpEx increasing and conclude that IT has lost cost discipline. In reality, part of the increase may reflect a change in delivery and accounting models rather than uncontrolled spending.
Technology leaders should explain that shift before it becomes a point of contention. They should also acknowledge that cloud economics require active management. Moving spending to OpEx does not guarantee savings, and consumption-based services can become costly when ownership, usage and accountability are unclear.
The CIO who can describe both the benefits and the financial consequences of the cloud model is in a much stronger position than one who presents the migration as a purely technical decision.
Separate the Run and Build Portfolios
The CFO already knows how to evaluate an investment portfolio. Technology leaders should provide one.
Rather than presenting IT as a single aggregate budget, insurers can distinguish between two portfolios:
- A run portfolio, managed for operational reliability, security and efficiency.
- A build portfolio, managed for business return, strategic capacity and long-term value.
The run portfolio includes the cost of maintaining the current technology estate: infrastructure, software subscriptions, support, cybersecurity, regulatory requirements and the applications needed to keep the business operating.
The build portfolio includes investments intended to create new capabilities, improve customer or agent experiences, reduce operating costs, support growth or replace systems that constrain the business.
The distinction changes the budget conversation. Instead of asking only why technology costs so much, leadership can ask how much the company should invest to maintain current operations and how much it should invest to create future value.
One aggregate budget invites across-the-board cutting. Two portfolios invite a more productive discussion about priorities, returns and trade-offs.
Maintain a Visible Sunset List
An insurance technology estate cannot remain in add-only mode indefinitely.
Every new platform should be accompanied by a basic question: What will this investment allow the company to retire?
The answer may include a legacy application, redundant infrastructure, an expensive license, a manual process or one of several systems inherited through acquisition. In insurance, retirement may take time because of product runoff, regulatory requirements, historical data and dependencies among policy, billing and claims platforms. That makes an explicit retirement plan even more important.
A visible sunset list demonstrates that IT is managing the technology estate as a portfolio rather than an ever-expanding collection of systems.
Decommissioned applications, terminated licenses and retired infrastructure provide tangible evidence of financial discipline. They convert the modernization narrative from “IT wants more” to “IT is making room.”
Sunsetting also should be treated as part of the investment case rather than as an activity to be addressed after implementation. If a new platform is expected to replace existing technology, the costs, timing, dependencies and savings associated with that retirement should be identified at approval.
Model Future Budget Capacity
The most valuable chart a CIO can bring to a budget discussion may not be a project roadmap. It may be a view of committed future-year costs compared with the company’s projected capacity for new investment.
Before approving another capitalized program or multiyear cloud commitment, technology and finance leaders should model how it will stack against depreciation, amortization, subscriptions and contractual obligations already in place.
That analysis can reveal how much of the future IT budget is effectively committed before the next planning cycle begins.
It also turns an abstract risk into a shared management challenge. The CIO is no longer simply requesting funding for a project. The CIO and CFO are jointly deciding how much future flexibility the company is prepared to exchange for the expected return.
Quantify the Benefit—and Measure It
Technology leaders also need to be more confident and precise about the benefits their programs are expected to deliver.
A business case should quantify why the organization is undertaking the work. That may include changes in operating costs, implementation speed, claims handling, product-development time, system availability, distribution capacity or workforce productivity.
The financial case should be ambitious enough to explain why the program deserves priority, but it also must be measurable.
Every material benefit should have an owner, a baseline and a method for evaluating results after go-live. Without that accountability, a projection is merely a wish.
Confidence in the expected return, combined with discipline in measuring the result, is what turns a technology proposal into an investment case.
Plan in Finance’s Language
Underinvestment in insurance platforms rarely creates an immediate crisis. More often, it quietly accumulates future cost through slow product launches, brittle integrations, manual processes and an increasingly complex technology estate.
Those consequences may not appear on this quarter’s P&L, but they eventually surface—often with interest.
Insurers cannot cut their way to a modern technology environment. They also cannot capitalize their way around cost. The obligation remains, regardless of when it reaches the income statement.
The strongest technology leaders do more than translate IT terminology for the CFO. They separate the run and build portfolios, show what the company can retire, model future financial commitments and take responsibility for the benefits they promise.
They do not merely speak finance’s language—they plan in it.