For most of the twentieth century, a utility customer information system had one organizing principle: read the meter, rate the consumption, print the bill. The system sat at the center of a simple transaction. That simplicity was not a design flaw; it matched the business. A residential customer received one commodity, one bill, once a month.
That model is cracking under the weight of distributed energy resources, electric vehicles, demand-response programs, community solar subscriptions, and dynamic tariffs. The CIS that was built to handle a meter-read-and-bill loop was never designed to manage a prosumer who exports solar in the morning, charges a vehicle overnight, and participates in a grid-flexibility event on Tuesday afternoon.
What the Old Architecture Assumed
Legacy CIS platforms were designed around three assumptions: the utility owns the generation, the flow of energy is one direction, and the customer relationship is a monthly billing event. SAP IS-U, Oracle Customer Care and Billing, and most of the platforms built before 2015 share this DNA. The meter is the anchor. Everything upstream of it belongs to operations, and everything downstream is finance.
That design produced stable, auditable billing systems. It also produced systems with a very narrow surface area. New product types require new rate tables, new rate tables require development cycles, and development cycles slow down the business. When a utility wants to launch an EV charging incentive or a time-of-use pilot, the CIS is often the constraint.
What Changed and Why 2025 Is the Inflection Point
Two forces accelerated simultaneously. On the grid side, distributed energy resource penetration crossed the threshold where utilities could no longer treat it as an edge case. On the software side, cloud-native platforms and AI inference at scale became commercially available to companies outside the hyperscaler tier.
Gartner formalized the market response in its Market Guide for Utility Customer Information Systems, published July 14, 2025 (document G00827595, also summarized at openintl.com). The guide named 19 representative vendors and framed modern CIS as going “beyond billing,” with composable architecture, real-time event-driven capabilities, and DER and EV integration as the defining characteristics of competitive platforms. Gartner also maintains a Utilities Customer Systems Peer Insights market where utility practitioners rate platforms on these dimensions directly.
The “composable” framing matters because it describes a shift in how vendors structure their products. Rather than a monolithic billing engine that owns every adjacent function, a composable CIS exposes APIs that allow utilities to add, replace, or extend components without touching the core. That is architecturally significant because it allows the billing foundation to remain stable while the product and engagement layer changes at the pace the business demands.
The Service-to-Cash Framing
The term “service-to-cash” has gained traction among practitioners and vendors as a way of naming what the new architecture must cover. Methodia, which publishes extensively on CIS modernization, uses the term explicitly to contrast the older meter-to-cash model with a broader flow: from service enrollment through usage tracking, pricing, billing, collections, and customer engagement across every product type the utility offers, not just consumption billing.
The distinction is not just semantic. A service-to-cash architecture has to support subscriptions, demand-response agreements, EV session fees, and DER compensation in the same system that handles a traditional residential bill. That requires a product catalog that is not hardcoded to commodity rate schedules, and it requires an event-driven processing model that can respond to grid signals in near real time rather than in a nightly batch window.
Cloud-Native Entrants and the AI Layer
The most watched new entrant in the CIS space is Kraken Technologies, which was spun out of Octopus Energy in December 2025 at an approximately $8.65 billion valuation and manages more than 70 million accounts globally. Kraken was designed from the start as a cloud-native, AI-native platform, which means the AI layer is not a bolt-on module sitting above a legacy core; it is woven into routing, scheduling, tariff recommendation, and customer interaction throughout the system.
Kraken’s emergence matters not because every utility should move to it, but because it demonstrates that the architectural assumptions of legacy CIS are not laws of physics. A platform can be built differently, and buyers now have a concrete example of what that looks like at scale.
The market estimates for CIS software vary meaningfully depending on scope. SNS Insider estimates the CIS market at roughly $1.26 billion in 2023 growing to approximately $3.54 billion by 2032 at a 12.23% CAGR. MarketsandMarkets puts the figure at approximately $1.79 billion in 2024 reaching $3.26 billion by 2030 at 12.8%. If you use a broader “utility billing software” scope, Mordor Intelligence arrives at roughly $6.23 billion in 2025, with cloud deployments at approximately 58% of installations. These estimates are not directly comparable; they reflect different definitions of the market boundary. The consistent signal across all three is sustained double-digit growth driven by modernization investment.
What It Means for Buyers
The architecture question for a utility in 2026 is not simply “which CIS vendor,” but “what capabilities do we need the CIS to own natively versus source through integration.” A composable, event-driven platform allows a utility to adopt best-of-breed DER management or EV charging settlement without replacing the billing core. A monolithic platform forces a tradeoff between stability and agility that compounds over time.
Evaluating CIS platforms against the service-to-cash model, rather than the meter-centric model, surfaces the right questions early: can the product catalog handle non-commodity products, can the system process sub-hourly interval data natively, and can the customer engagement layer respond to real-time grid events without a batch delay.
For a grounded starting point, the comprehensive guide to choosing utilities software lays out an evaluation framework applicable to this generation of platforms. If you are assessing SAP’s forward path specifically, the SAP Utilities overview and the Oracle vs SAP comparative analysis provide vendor-specific context. And for a broader view of what modern platforms are doing across the industry, modern software solutions transforming the utilities industry covers the wider landscape.
The meter-centric CIS served utilities well for decades. The service-to-cash architecture is not a replacement for the billing function; billing still has to be accurate, auditable, and on time. It is a broader frame that treats billing as one output of a system that manages the full customer and asset relationship across every product the utility offers. Buyers who frame their evaluations that way will ask better questions and make better decisions.