.png)
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Procurement Guide How Are Utilities Customer Information & Billing Systems Cis Priced for Enterprises
A customer information and billing system sits unusually close to a utility’s financial core. It determines who receives a bill, how tariffs are applied, when revenue is recognised, which arrears enter collections, and whether regulators and customers can trust the figures. Replacing one can improve service and lower operating cost, but a weak procurement can lock the utility into years of change orders, disputed invoices, manual workarounds, and public scrutiny.
The commercial problem has become harder as vendors move from perpetual licences to cloud subscriptions. Buyers now face customer-account charges, meter-point rates, platform commitments, named-user licences, cloud infrastructure, integration fees, managed services, and separately priced digital modules. The software proposal may look predictable while the full programme remains exposed to data conversion, testing, regulatory changes, and implementation delays.
Monetizely’s position is that an enterprise CIS should be priced primarily through a committed annual platform fee tied to bands of active service points. Professional services should be separately capped, and a meaningful share of implementation fees should remain at risk until the utility proves bill accuracy, revenue reconciliation, and operational readiness. Per-user pricing is too far removed from value, while uncapped charges for bills, meter reads, transactions, or API calls transfer too much operating risk to the buyer.
Active service points provide the cleanest link between scale, value, and cost
Monetizely’s 5-Step Pricing Framework connects commercial design to the operating reality of a product. Goals and segmentation define the customers and business outcomes the price must serve. Packaging decides which capabilities belong in the core product and which should remain optional. Pricing metric identifies the unit that allows spend to rise with value. Rate setting determines the amount charged at each level. Operationalisation covers quoting, contracting, metering, invoicing, renewal, reporting, and dispute handling. The sequence, also developed in Monetizing Agentic AI, matters well beyond AI because a sensible metric still fails when packaging is unclear or the billing process cannot apply it consistently.
For a utility CIS, the commercial goal is not to maximise the price of each bill generated. It is to give the vendor fair growth as the utility’s service estate expands while keeping annual spend forecastable. An active service point, or its close equivalent such as a point of delivery, meets that test better than employee seats or raw transactions.
A service point represents the location at which a utility service is delivered and metered. One household may have separate electricity, gas, and water service points, while a large commercial customer may operate hundreds. Oracle’s application model treats service points as core operating records, and SAP defines a point of delivery as the location at which market participants exchange data and deliver utility services.
The distinction matters commercially. Customer accounts can merge, split, change occupants, or remain inactive. Service points usually persist with the physical network. Tying the primary fee to active service points therefore rewards the vendor when the utility expands its operating footprint without charging extra merely because the utility improves collections, increases digital interactions, or sends more frequent meter data.
Public price transparency remains rare. SAP and Gentrack provide the clearest meter-based signals, while most other vendors require a custom proposal.
| Vendor and enterprise offer | Dominant pricing approach visible in public sources | Main exposure for buyers | Public evidence as at 4 August 2026 |
|---|---|---|---|
| Oracle Utilities Customer Cloud Service / CC&B Cloud Service | Custom annual cloud subscription, normally scoped by product footprint, operating estate, environments, and service volume; no public CIS rate card | Separate modules, environments, implementation partners, integrations, and live-operation services | Oracle documents an integrated cloud CIS covering customer care, billing, metering, service orders, analytics, and supporting cloud services, but publishes no unit price. |
| SAP S/4HANA Utilities and related cloud services | Enterprise platform commitment combined with user, infrastructure, and utility-specific units; SAP’s utilities self-service offer is priced per point of delivery | Several contracts may sit behind one programme, including S/4HANA, cloud infrastructure, digital channels, implementation, and support | SAP’s official page prices its Self-Service Accelerator in blocks of one point of delivery, with terms from 3 to 60 months and automatic renewal, while keeping the rate quote-based. |
| Gentrack g2.0 | Usage-based SaaS dimension tied to meter points, usually negotiated through a private enterprise offer | Salesforce scope, AWS costs, implementation, managed services, and uncertainty over how the public usage dimension converts into the final commitment | AWS Marketplace displays a $25 cost unit described as the price per number of meter points in the system. The listing also states that infrastructure can cost extra and directs buyers to Gentrack for more detail. |
| Itineris UMAX | Custom cloud or managed-service agreement, generally anchored in platform scope and utility estate rather than a published seat rate | Microsoft Dynamics licences, payments, portals, mobile work, data conversion, and long-term support | Itineris identifies UMAX as a cloud-based CIS built on Microsoft Dynamics 365. A 2018 renewal for De Watergroep covered private-cloud CIS, ERP support, and managed services for an estate with 1.3 million customer contracts and more than 900 users, but disclosed no rate card. |
| Hansen CIS | Quote-based modular SaaS, PaaS, or on-premise pricing; utility and account scale are negotiated rather than publicly priced | Charges can spread across CIS, portal, meter data, inventory, support, hosting, and professional services | Hansen’s 2026 materials package configurable billing, collections, bill design, and integrations while offering SaaS, PaaS, and on-premise deployment. No public enterprise rate is displayed. |
| VertexOne utility platforms | Multi-year SaaS platform subscription, with account or transaction volumes normally addressed in the enterprise proposal | Digital engagement, payments, EDI, customer communications, and implementation can sit in separate workstreams | VertexOne describes its utility portfolio as SaaS and has deployed billing, CIS, and EDI together for competitive energy suppliers, but does not publish a CIS rate card. |
| Open Intelligence Smartflex | Quote-based platform fee shaped by customer scale, modules, and SaaS, PaaS, or on-premise deployment | Broad functional scope can make it difficult to separate core CIS cost from meter data, customer experience, and workforce management | Smartflex combines CIS, billing, customer experience, metering, and workforce capabilities and supports SaaS, PaaS, and on-premise deployment. Public prices are not disclosed. |
The market is converging on recurring subscriptions, but not on disclosure. Only a minority of vendors tell buyers what the scaling unit is before an RFP, and fewer still publish enough detail to calculate a credible three-year cost.
Cloud delivery changes when utilities pay, not merely how much they pay. Older CIS contracts often combined a perpetual licence, annual maintenance, infrastructure, and periodic upgrade projects. SaaS replaces much of that pattern with a recurring fee, regular releases, hosted environments, support, and continuously delivered product changes.
Oracle argues that its Utilities SaaS model removes the need for large, disruptive upgrades and places infrastructure maintenance, backups, patching, and security within the cloud service. Its April 2025 update policy moved relevant utilities cloud products from three major releases each year to two, which reduces release frequency but still requires testing and operational preparation from the customer.
Gentrack reported in January 2020 that it was moving from upfront licence revenue to contracted recurring SaaS payments. By May 2026, the company expected FY26 recurring revenue of about NZ$174 million and said that g2.0 was designed to produce higher recurring revenue while lowering customer onboarding costs.
Recurring pricing can improve budget planning, but buyers often underestimate the number of recurring lines. A proposal labelled “CIS SaaS” may omit the CRM layer, payment gateway, bill composition, identity management, disaster recovery environment, data warehouse, API platform, non-production environments, premium support, or cloud consumption.
The following cost structure should replace the single “software licence” line in a procurement model.
| Cost layer | Typical commercial treatment | Buyer question that exposes hidden spend |
|---|---|---|
| Core CIS platform | Annual commitment based on service-point bands, accounts, or a negotiated enterprise tier | Which billing, collections, rate, cashiering, and customer-care capabilities are included without another module? |
| Digital customer service | Separate portal, mobile, chatbot, notifications, or CRM subscription | Are external customers, authenticated accounts, messages, and payment journeys included? |
| Meter and usage processing | Separate meter-data module or volume charge | Does the price rise with meters, interval reads, retained history, or calculation runs? |
| Cloud environments | Production included; development, testing, training, and disaster recovery may cost extra | How many environments are included, and how long can parallel environments remain active during releases? |
| Professional services | Fixed-price phases, time and materials, or a blend | Which deliverables are fixed, and which events allow the vendor or integrator to issue a change request? |
| Data conversion and testing | Volume assumptions, conversion cycles, and defect thresholds | How many mock conversions and full bill comparisons are included before another fee applies? |
| Integration | Priced per interface, sprint, or service team | Are APIs included in the subscription, and who pays when an upstream system changes? |
| Managed operations | Monthly retainer, service tier, or consumption fee | Which batch failures, reruns, reconciliations, and release tasks are standard support rather than chargeable work? |
| Regulatory change | Included product updates or paid configuration work | Which tariff and statutory changes are covered by the roadmap, and which require professional services? |
| Renewal and growth | Indexation plus service-point or account true-ups | Can quantities fall, are discounts preserved, and does growth trigger retroactive repricing? |
The practical implication is clear: cloud removes some capital events but does not remove implementation or operating work. Without a complete recurring-cost schedule, the apparent predictability of SaaS can conceal a larger and more durable commitment.
Packaging, metric design, and operationalisation determine whether two proposals can be compared. A vendor may have strong software while presenting a weak commercial offer. Our scorecard therefore assesses the public buying model, not overall product quality.
Gentrack gets the metric closest to right because meter points correspond to the scale of the utility operation. SAP reaches a similar design for its self-service product through points of delivery. Neither public signal removes the need to define active, inactive, seasonal, disconnected, test, and duplicate records in the contract.
Oracle gets cloud operations right. The product set brings customer information, billing, metering, service orders, analytics, testing tools, and cloud operations into a managed environment. Yet commercial clarity lags technical completeness because buyers cannot move from Oracle’s public material to a budget without a detailed proposal.
Itineris demonstrates the value of a more bounded operating model. De Watergroep reported in 2018 that UMAX had cut CIS management costs in half over the prior decade, while Sarasota County said its UMAX deployment went live on time and on budget in January 2026. Both statements come from the vendor’s customer announcements, so buyers should verify the underlying baselines and acceptance measures during reference calls.
Monetizely’s view is that every finalist should produce a standard commercial workbook. It should show the price at current service-point volume, the price at three growth levels, the cost of every environment and module, all renewal adjustments, and the unit economics of professional services. A vendor that cannot do so during procurement is unlikely to make invoicing easier after signature.
Public failures show that implementation control matters more than the licence discount
CIS programmes rarely fail because the rate per account was five per cent too high. Failures usually begin when the organisation underestimates data defects, custom processes, integration effort, testing, training, or cutover risk. Weak reporting then allows the programme to continue until the remaining choices are all expensive.
Government audits provide harder evidence than vendor case studies. Four named cases show how quickly the cost can move beyond the original software decision.
These cases span different products, decades, and utility types, yet their pattern is consistent. The largest financial damage appeared outside the original licence line - through remediation, delayed revenue, bad debt, internal labour, customer support, and abandoned work.
A strong contract cannot replace programme leadership, but it can make bad news visible sooner. Monthly invoices should reconcile to accepted deliverables. Schedule movement should update the cost forecast. Defect trends should affect milestone payment. No steering committee should learn about a nine-figure exposure from a post-launch audit.
Three-year TCO is set by conversion, integration, and readiness
Price comparison often begins with the annual subscription because it is the easiest number to obtain. That practice reverses the real risk. For a new enterprise CIS, implementation and internal change commonly exceed the software commitment during the first three years.
Public projects illustrate the range. Baltimore agreed an $8.4 million Itineris contract in 2014 covering implementation and ten years of support for a 410,000-customer water and wastewater estate. LADWP’s far larger and more complex programme moved towards $200 million. The difference was not explained by account count alone; scope, integration, customisation, governance, testing, and remediation shaped the final cost.
A buyer should therefore model the programme by service-point estate and operating complexity, not by licence quote alone.
| Enterprise scenario | Three-year software and cloud | Implementation and integration | Data, testing, training, and internal backfill | Risk reserve | Three-year TCO range |
|---|---|---|---|---|---|
| Municipal water utility with 100,000 active service points | $3m-$6m | $8m-$15m | $4m-$8m | $3m-$6m | $18m-$35m |
| Regional multi-service utility with 500,000 active service points | $12m-$25m | $25m-$50m | $10m-$20m | $8m-$18m | $55m-$113m |
| Large regulated utility with 2 million active service points, interval metering, complex tariffs, and several legacy systems | $45m-$90m | $80m-$160m | $30m-$60m | $25m-$60m | $180m-$370m |
The model shows why a large software discount may have little effect on the board-level decision. Cutting a $20 million subscription by ten per cent saves $2 million. One failed conversion cycle, a six-month delay, or a disputed integration programme can consume that saving several times over.
Sensitivity should focus on five variables:
Procurement teams should model each variable before asking vendors for a “best and final” price. Otherwise, commercial negotiations optimise the visible ten to twenty per cent of TCO while leaving the rest largely uncontrolled.
The best time to control CIS pricing is before vendors convert requirements into proprietary packages. Once each bidder defines different modules, volumes, environments, and exclusions, comparison becomes a negotiation over language rather than price.
A buyer-side negotiation checklist should require:
- One contractual definition of an active service point. Exclude test records, duplicates, inactive locations, disconnected premises after an agreed period, and records retained only for history.
- Volume bands rather than retroactive tiers. Growth should move only the incremental service points into the next band, not reprice the entire estate at a higher rate.
- Annual true-ups with downward movement. Allow the commitment to fall when service points close, territories are divested, or commodities leave the platform.
- A complete entitlement schedule. List every included module, API, batch process, environment, storage allowance, data-retention period, report, and support tier.
- Separate software and services pricing. Prevent implementation overruns from being hidden through higher subscription commitments or vaguely defined managed services.
- Fixed conversion cycles and acceptance tests. State the number of extracts, mock conversions, parallel bill runs, reconciliations, and defect-remediation rounds included.
- A capped services rate card. Lock roles, locations, travel treatment, overtime, annual increases, subcontractor mark-ups, and approval thresholds for change orders.
- Payment holdbacks tied to business performance. Retain fees until bill accuracy, financial reconciliation, response times, batch completion, and production stability meet agreed thresholds.
- Included regulatory maintenance. Distinguish product changes delivered to all customers from utility-specific configuration and require estimates before work begins.
- Renewal limits. Cap indexation, preserve volume discounts, prohibit forced module bundling, and require at least twelve months’ notice of material packaging changes.
The preferred commercial architecture is not a mixture of unrelated meters. Active service points should remain the primary meter. An annual platform commitment can sit underneath it, and optional modules can carry their own fixed fees, but bills, payments, API calls, meter reads, messages, and employee seats should not become uncapped secondary charges.
Meter-data processing is the main exception. Interval data can expand much faster than the number of physical meters. A utility moving from monthly readings to half-hourly data creates roughly 1,440 readings per meter each month rather than one. A separate data band may therefore be justified, but it should use large committed blocks with predictable overage rates, not charge for every reading. AWS noted in November 2024 that Australian market changes can move settlement data from 48 to 288 points per meter per day, showing why raw transaction pricing can become volatile.
For buyers in 2026, Monetizely recommends five higher-level actions:
Fund the CIS as a revenue and customer-operations transformation. The accountable executive should own billing accuracy, collections, customer service, and regulatory outcomes rather than treating the programme as an IT replacement.
Choose the future operating model before selecting the platform. Decide which legacy processes will be retired, which functions will remain in-house, and where the utility will accept standard software. Commercial bids become comparable only after those decisions are fixed.
Create one lifetime commercial owner. A dedicated leader should govern the business case from RFP through implementation, operation, renewal, and exit, preventing responsibility from fragmenting across procurement, finance, IT, and the system integrator.
Make readiness an independent decision. Production launch should require documented approval from business operations, finance, customer service, security, and independent quality assurance. A programme sponsor should not be able to waive unresolved billing or reconciliation defects alone.
Judge the investment on five-year operating cost, not the initial contract value. Board approval should compare the cost of software, implementation, internal labour, parallel systems, regulatory change, managed operations, and likely renewal pricing in one model.
A CIS supplier deserves recurring revenue because the platform remains essential every day. The buyer deserves a price that grows with the utility’s real operating estate, not with every digital interaction the system happens to process. Active-service-point bands, capped implementation exposure, and outcome-based acceptance create that balance.
Assumptions
TCO figures are modelled in 2026 US dollars for replacement programmes rather than routine upgrades. Ranges include core software, standard cloud environments, implementation, integration, data conversion, testing, training, internal backfill, and a risk reserve, but exclude financing costs, taxes, major AMI hardware programmes, payment-processing interchange, and customer compensation. Public contract and audit figures are not inflation-adjusted and are used as reference points rather than vendor quotations.
Footnotes
https://www.amazon.com/Monetizing-Agentic-AI-Handbook-Transformation/dp/B0H7Z13VKJ/
https://docs.oracle.com/en/industries/utilities/customer-care-billing/
https://docs.oracle.com/en/industries/utilities/customer-cloud-service/
https://www.oracle.com/customer-hub/utilities/customer-care-billing-cloud-service/
https://www.oracle.com/jp/utilities/products/customer-information-system/
https://www.sap.com/india/products/crm/self-service-accelerator.html
https://help.sap.com/docs/SAPS4HANAON-PREMISE/47dffa81f77c4677b99540097c8db0f1/16586b205aeb11dc2b8d000f20fcb6a9.html
https://aws.amazon.com/marketplace/pp/prodview-qbgf4w72yjswi
https://gentrack.com/fy20-outlook-update/
https://gentrack.com/market-announcements/market-update-and-intent-to-launch-share-buyback/
https://www.itineris.net/de-watergroep-extends-partnership/
https://www.itineris.net/sarasota-county-launches-umax-us/
https://www.itineris.net/city-of-baltimore-selects-itineris-umax-cis-solution-for-water-billing-and-customer-care-us/
https://pages.hansencx.com/SE-2026-02-03-EU-NA-AWWASouthernWaterUtilityRoundtableUnified-Ecosystem-eBook.html
https://www.businesswire.com/news/home/20211102005041/en/VertexOne-Acquires-EC-Infosystems-Fulfilling-Energy-Market-Need-for-End-to-End-Technology-Solutions
https://www.openintl.com/platform/customer-information-system/
https://information.auditor.ca.gov/reports/summary/2014-105
https://controller.phila.gov/philadelphia-reports/city-spends-additional-9-2-million-on-another-failed-water-billing-system/
https://www.seattle.gov/city-auditor/reports
https://council.seattle.gov/2020/04/03/city-council-audit-completed-to-resolve-billing-problems-at-seattle-city-light/
https://aws.amazon.com/blogs/industries/gentrack-helps-utilities-cut-meter-data-processing-time-by-25-on-aws/