Utilities · Customer information and billing systems
The CIS RFP was scoped before you heard of it.
You sell CIS, billing or customer portal software to utilities. At public utilities the need is often aired in a study session, and a consultant may write the specification long before the RFP. Arrive at the RFP and you answer a scope built around another product, then wait for a council or board vote.
- Typical deal (non-IOU)
- €30–450k a year Illustrative
- Sales cycle (non-IOU)
- 9–12 months typical Illustrative
- Buying group
- 6–12 people Illustrative
Updated 5 October 2026 · Based on Panelhop research, October 2026
At a US public power or municipal water utility replacing its CIS6–12 people Illustrative
The short answer
How do CIS and billing vendors sell to utilities?
Customer information system (CIS) and billing vendors sell to utilities through formal replacement projects. A legacy system reaches end of life, a budget or rate case funds the work, a consultant often writes the RFP and a council or board votes. Vendors should reach billing, IT and finance before the RFP, with references from same-type, same-size utilities.
Customer information and billing systems · How a deal really moves
Scoped in a study session you never saw. Then the spec favours a rival and the vote slips a meeting. The same deal, from the study session on. Study sessions flagged weekly, every seat mapped before scoring.
One utility replacing its CIS and 6–12 people, including the council or board. An estimated 12–24 months from need to award.
What opens a deal
- Legacy CIS end of life: Technology · US, UK
- AMI programme approval: Technology · US
- CIS funding in a rate case: Regulation · US
- Municipal budget season: Budget · US
- Merger or shared billing: Consolidation · US, DE
- ERP billing end of maintenance: Technology · DACH
Signal Desk · weekly: In-market accounts, scored and mapped
Your buyer and who decides
A utility replacing its CIS
Public power, co-op, water, IOU or Stadtwerk
Panel Check · coverage baselined
- Executive sponsor, can Veto: Being the utility whose migration fails in public.
- Governing body, can Veto: Approving a billing contract that becomes a headline.
- Finance, can Veto: Escalators over a long term that nobody priced.
- IT leadership, can Veto: Lock-in to a platform the team can’t support.
- Billing supervisor: Bills going out wrong after cutover.
- Selection consultant: Recommending a vendor that fails mid-migration.
How the deal moves
Need recognition Typical time: 2–6 months
- Where it stalls
- The study session happened without you
- With Panelhop: Signal Desk
- CIS study sessions and budget requests scored weekly, each with a brief
Budget approval Typical time: 3–12 months
Consultant scan Typical time: 1–3 months
- Where it stalls
- The spec was written around your rival
- With Panelhop: Signal Desk
- Consultant procurements flagged while requirements are still in draft
RFP response Typical time: 1–3 months
Demos and references Typical time: 1–3 months
- Where it stalls
- Won the demo, lost on references
- With Panelhop: Leak Fix
- References matched by type and size, every seat mapped before scoring
Negotiation and vote Typical time: 1–2 mo + vote
- Where it stalls
- The vote slips one meeting at a time
- With Panelhop: Panel Ops
- Close dates tied to board packet deadlines, slippage reported monthly
Migration
Add-ons and renewal
Panel Ops · monthly: Scores and plays tuned against the baseline
Illustrative Source: Stages, seats, triggers and stalls from Panelhop research, October 2026; the services as described on the Services page. Note: Durations, panel sizes and cycle lengths are Panelhop estimates from our research, not measurements.
At a glance
| Typical deal (non-IOU) | €30–450k a year Illustrative |
|---|---|
| Sales cycle (non-IOU) | 9–12 months typical Illustrative |
| Buying group | 6–12 people Illustrative |
| Motion | Replacement RFP, often run by a selection consultant |
Source: Panelhop research, October 2026. Note: Values marked Illustrative are Panelhop estimates from our research, not measurements.
Many CIS deals are decided before the RFP is public.
Where do CIS and billing deals get lost?
CIS and billing deals are often lost before the RFP is released, when the scope, budget and shortlist are set without the vendor. Others leak at the vote, in DACH tenders and in closed-lost records nobody revisits.
Where the pipeline leaks: 5 points across 8 stages.
CIS RFPs come from utilities you never spoke to
- What you see
- CIS RFPs arrive from utilities your team has never spoken to.
- Why it happens
- Nobody tracks study sessions, budget requests or consultant procurements at target utilities.
Stage Need recognition
Stadtwerke tenders ask for references you don’t have
- What you see
- Stadtwerke billing tenders arrive with reference criteria you can’t meet, or after the integrator slots are taken.
- Why it happens
- Stadtwerke aren’t tracked by migration status, and no German energy references or integrator partners are lined up.
Stage RFP response
You win the demo and lose on references
- What you see
- Bids lose on references from utilities of similar size, despite strong demos.
- Why it happens
- Reference customers aren’t matched to look-alike prospects by ownership type, size and region.
Stage Demos and references
The CIS close date slips one meeting at a time
- What you see
- CIS close dates slip by exactly one meeting, again and again.
- Why it happens
- Opportunities carry no packet deadline or meeting date.
Stage Negotiation and vote
Lost utilities re-tender, and you hear too late
- What you see
- A re-tender is found after publication at a utility you lost years ago.
- Why it happens
- Closed-lost accounts carry no competitor contract end date or extension decision.
Stage Add-ons and renewal
End of life and approvals open the CIS window.
What triggers a utility to replace its CIS?
A utility replaces its CIS when the old system reaches end of life, a metering rollout needs new billing or a regulator funds the work. Mergers and Stadtwerke migrations off legacy ERP billing open the same window, and each event is public months before the RFP.
The 6 events that open or close the window for a deal.
Technology
Legacy CIS end of life
- What happens
- A utility’s CIS stops being enhanced, and staff build the case for replacement.
- Where to spot it
- Council study sessions, budget requests and staff reports that mention end of life.
- Window
- A CIS replacement typically takes 12–24 months from need to contract award, by Panelhop’s estimate, so watch budgets one cycle ahead.
Technology
AMI programme approval
- What happens
- A council, co-op board or commission approves a smart metering rollout that the CIS must bill from.
- Where to spot it
- Council agendas and minutes, and commission orders.
- Window
- Billing changes and CIS integration are bought during the pilot and rollout, which starts 6–12 months after approval by Panelhop’s estimate.
Regulation
CIS funding request in a rate case
- What happens
- An IOU asks its state commission for incremental funding to replace its CIS.
- Where to spot it
- State commission dockets and administrative law judge rulings.
- Window
- Buying follows the commission’s decision, and requests for more detail can add months.
Budget cycle
US municipal budget season
- What happens
- A city utility’s departments prepare budget requests months before the new fiscal year.
- Where to spot it
- City budget calendars, budget documents and council agendas.
- Window
- A CIS project left out of the request usually waits for the next fiscal year.
Consolidation
Merger or shared billing across entities
- What happens
- A merger, or a group of legally separate companies, moves onto one billing platform.
- Where to spot it
- Commission merger dockets and tender notices for multi-entity billing.
- Window
- Platform decisions follow the close, and spending can freeze until then.
Technology
Legacy ERP billing end of maintenance (DACH)
- What happens
- Many German Stadtwerke bill on a legacy ERP release that is losing mainstream maintenance, so they must migrate, move to a hosted platform or replace the CIS.
- Where to spot it
- SektVO notices on TED, German e-Vergabe portals and IT tender aggregators.
- Window
- Selections cluster in 2026 and 2027, because migrations take 18–36 months by Panelhop’s estimate and integrators are scarce.
A consultant can shape the deal without a vote.
Who decides on a new CIS or billing system at a utility?
A new CIS is decided by the executive sponsor, IT, finance and procurement, with the billing manager as the daily voice and a governing body voting last. The selection consultant has no vote but often writes the specification.
At a US public power or municipal water utility replacing its CIS, 6–12 people sit on the panel and 5 seats can stop the deal.
At a US public power or municipal water utility replacing its CIS: 6–12 people
Executive sponsor
Can Veto
Utility Director · General Manager · Director of Utilities
- Cares about
- A go-live that keeps billing errors out of the local news.
- Worries about
- Being the utility whose migration fails in public.
Billing and customer service manager
Billing Supervisor · Customer Service Manager · Credit and Collections Manager
- Cares about
- Every rate class, tier and special charge billed correctly.
- Worries about
- Bills going out wrong after cutover.
IT leadership
Can Veto
IT Director · Applications Manager · Director of Information Services
- Cares about
- Clean integration with AMI, GIS, ERP and payment systems.
- Worries about
- Lock-in to a platform the internal team can’t support.
Finance
Can Veto
Finance Director · Budget Officer · Controller
- Cares about
- A funding route, such as reserves or refinancing savings, that needs no rate rise.
- Worries about
- Escalators over a long contract term that nobody priced.
Procurement and legal
Can Veto
Purchasing Agent · City Attorney · Procurement and Contract Management Director
- Cares about
- A compliant process, bids that score side by side and fixed pricing over the term.
- Worries about
- A bid protest or a challenge to the award.
Selection consultant
CIS selection consultant · Owner’s adviser
- Cares about
- A defensible selection with bids that score cleanly.
- Worries about
- Recommending a vendor that fails mid-migration.
Governing body
Can Veto
City council · Utility board · Utility commission
- Cares about
- Rate impact and value for money over the contract.
- Worries about
- Approving a billing contract that becomes a headline.
Billing, IT and finance agree the must-haves before any RFP.
Who buys CIS and billing software at a utility?
CIS and billing systems are bought by a utility’s customer operations and billing managers, with IT and finance setting requirements before the RFP is released. Outside IOUs, a replacement runs about €150k a year by Panelhop’s estimate, often packaged with portal, mobile workforce or ERP work. Buyers trust proof from utilities like their own, yet only 4 of 20 utility vendors Panelhop analysed publish quantified customer outcomes.
What vendors of this type sell
- Customer information and billing systems (CIS)
- Customer portals, payments and self-service
- Rate engines for complex tariffs and special charges
- Billing for multi-service municipal utilities: electric, water, wastewater and stormwater
- Data migration and implementation services
Which utilities buy it
- US public power, municipal water and joint water and sewer commissions
- US electric co-operatives
- US IOUs and gas distribution companies
- UK water companies and water retailers
- German Stadtwerke replacing legacy ERP billing and market communication
CIS deals start at the study session, not the RFP.
How does a CIS replacement deal move at a utility?
A CIS replacement moves from a public study session through budget, consultant scan, RFP, scripted demos and a council or board vote, then a long migration. Many vendors join at the RFP, after the scope is set.
Stage by stage: what you do, what the utility does, and what changes at the 4 stages where deals stall.
| Stage | What you do | What the utility does | Today | With Panelhop |
|---|---|---|---|---|
| Need recognition Typical time: 2–6 months | Rarely present; many CIS vendors first hear of the project at the RFP. | Staff document the need and present it to the council or board in a study session. | Study sessions and staff reports go unread. Stalls: Absent when the need is framed. The scope and budget of a CIS replacement are framed in a public session that many vendors never track. | Weekly scored accounts when a CIS study session or budget request fires, each with a brief for your rep. Signal Desk In-market accounts, weekly |
| Budget approval Typical time: 3–12 months | Has no field for the utility’s fiscal year or request deadline. | Puts the project in the annual budget, capital plan or rate case. | No record of each utility’s fiscal year. | Fiscal year, request deadline and rate-case status on every account, with close dates tied to them. Leak Fix We build the fixes |
| Consultant scan Typical time: 1–3 months | Tries to get onto the selection consultant’s long list. | Hires a consultant to run the needs analysis and draft the specification. | Consultant procurements found after the RFP. Stalls: Specification written for a rival. The consultant and the incumbent system’s users shape the requirements, so a late vendor answers an RFP built around another product. | Consultant procurements tracked as a signal, so your rep can reach the utility while requirements are still being drafted. Signal Desk In-market accounts, weekly |
| RFP response Typical time: 1–3 months | Makes a go/no-go call, then assembles a response matrix and a cost proposal. | Holds a pre-proposal meeting, answers questions and takes bids. | Bid notices sit in a shared inbox. | CIS and billing bid notices matched to the account and routed to the account owner as a CRM task. Signal Desk In-market accounts, weekly |
| Demos and references Typical time: 1–3 months | Demos on the utility’s own rate tables and lines up reference calls. | Scores scripted demos and calls utilities of the same type and size. | References picked ad hoc; IT and finance join at scoring. Stalls: No size-matched reference. A buyer that calls peers of its own ownership type and size marks down a vendor whose references are larger, foreign or in another segment. | Reference customers matched to each shortlisted utility by ownership type and size, with billing, IT, finance and the consultant mapped before scoring starts. Leak Fix We build the fixes |
| Negotiation and vote Typical time: 1–2 months, then 2–8 weeks for the vote | Agrees SLAs, liability and data terms, then waits for the vote. | Files the staff report in the council or board packet and authorises signature. | Close dates set without the meeting calendar. Stalls: Packet deadline missed. A staff report filed after the packet deadline moves the CIS vote to the next meeting. | Board packet deadlines on each CIS deal, with slipped close dates tracked against the baseline. Panel Ops We run it monthly |
| Migration | Migrates data and runs the cutover with an integrator. | Accepts go-live once the first bills from the new system are right. | Promises made in scripted demos stay with the sales team. | A handoff document from the CIS deal, so the migration team inherits every promise made in scripted demos. Leak Fix We build the fixes |
| Add-ons and renewal | Offers portal, analytics or new modules at the user conference. | Adds modules by contract amendment or a new tender. | Lost bids and renewal dates forgotten for years. | Contract end dates and add-on triggers on customers and closed-lost utilities, checked in the weekly signal review. Panel Ops We run it monthly |
Move your first contact back to the study session.
How does Panelhop change a CIS and billing pipeline?
Panelhop moves your CIS pipeline earlier: study sessions, budgets and consultant procurements become dated signals on the account, and every seat is mapped before scoring. A Panel Check (GTM audit) first baselines your pipeline stage by stage from your own CRM data, including the time from signal to first touch.
What we baseline and report
- CIS opportunities engaged before the RFP was published, against the baseline
- Buying-group coverage on shortlisted utilities: billing, IT, finance and the consultant
- Close-date slippage against council and board meeting dates
Other vendor types in utilities.
What other vendors sell to utilities?
The same utilities buy from these vendor types too, through different panels and pipelines.
- Vendor type
AMI, meter data management and analytics
Smart meter networks, head-end systems, MDM and analytics for municipal, co-op and investor-owned utilities and German meter operators.
Read the pipeline - Vendor type
Grid operations and DER management software
ADMS, OMS, SCADA, DERMS and flexibility platforms for US IOUs, co-ops and public power, British DNOs and European DSOs.
Read the pipeline - Vendor type
Asset, GIS and field workforce platforms
Network GIS, asset management, joint use, vegetation and mobile workforce software for electric, gas and water utilities.
Read the pipeline - Vendor type
OT security and cyber compliance
OT monitoring, vulnerability management, ISMS and NERC CIP compliance tools for utilities, Stadtwerke and DSOs.
Read the pipeline
The words your buyers use, defined.
What do terms like “CIS (customer information system)” and “Study session” mean?
Plain definitions of the terms that come up when you sell customer information and billing systems to utilities.
- CIS (customer information system)
- The utility’s core system for customer accounts, meter-to-cash billing, payments and service orders. Replacing it touches billing, IT, finance and every customer.
- Study session
- A public council or board meeting where staff present a need, such as a CIS replacement, before any budget vote or RFP. It is often the first public sign of a project.
- Selection consultant
- A firm a utility hires to run a CIS needs analysis, write the specification and score bids. It has no vote but often decides which vendors make the long list.
- Fiscal year and budget request
- A utility’s budget year and the deadline for department requests. A CIS project missing from the request usually waits for the next fiscal year.
- Rate class
- A group of customers billed under one tariff, such as residential or commercial. A CIS must bill every rate class, tier and special charge correctly, and buyers test it in scripted demos.
- Consent agenda
- A list of routine items a council or board approves in one vote without debate. Smaller utility software contracts are sometimes approved this way.
Answers before your next utility deal.
What do vendors of customer information and billing systems ask about selling to utilities?
How long does it take to sell a CIS to a utility?
Selling a CIS to a utility typically takes 9–12 months by Panelhop’s estimate, and longer at US investor-owned utilities, where deals are far larger. The utility often spends 2–6 months framing the need and 3–12 months securing funding, by the same estimate, before many vendors hear of the project. Core billing systems last 1–2 decades by Panelhop’s estimate, so a lost bid closes that account for years.
Who decides on a new billing system at a municipal utility?
A municipal utility’s billing system is chosen by an evaluation committee led by the utility director, with the billing supervisor, IT, finance and procurement scoring bids. A selection consultant often writes the specification. The city council or utility board then votes in open session on the staff report and authorises the contract.
How do CIS vendors find utility RFPs before they are published?
CIS vendors find utility RFPs early by tracking public records for each target utility. The signals are council study sessions on billing replacement, budget requests, capital plans, consultant procurements and rate case filings that ask for CIS funding. A vendor that meets billing, IT and finance at that point can still shape the requirements.
How do CIS vendors sell to electric co-operatives?
CIS vendors sell to electric co-operatives through a nearby reference co-op of similar size and a route through the G&T or statewide association. Many distribution co-ops already run a long-standing integrated suite. Co-ops choose after long peer-led evaluations and site visits to other co-ops, and the board approves.
Why do utilities ask CIS vendors for references of the same size?
Utilities ask CIS vendors for references of the same ownership type and size because a billing failure is public and peers are the evidence they trust. A co-op calls co-ops; a city utility calls a nearby city utility. CIS vendors should match each reference customer to look-alike prospects by ownership, size and region before the shortlist.
How do you get a meeting with a public power general manager?
Software vendors reach public power general managers through peers more than through outreach. A reference from a utility of the same type and size, an executive track at a practitioner conference or a place on the selection consultant’s long list opens the door. Council packets and staff reports name the sponsoring director, and a new general manager or CIO is a good moment to approach.
Where the numbers come from.
Sources
Sourced figures link to their source below. Figures marked Illustrative, and figures given as estimates, are inferred from Panelhop research. Vendors appear only as types, never by name.
- Panelhop research, October 2026: our analysis of the vendors, buying panels, pipelines and triggers for customer information and billing systems in utilities, from public sources. Vendor names are not published.
