AEP Bill Analyzer: A Better Answer to High-bill Questions
September 01, 2026
Business
Technology
On a high-bill call, the first job is often not answering the customer. It is opening systems. A representative moves from the CIS to billing history, usage data, meter intervals, weather, and rate changes, trying to reconstruct one answer while the customer waits.
That gap matters. A bill that cannot be explained clearly creates repeat calls and escalations. More importantly, it makes a customer question whether the utility understands its own bill.
American Electric Power saw this as an operating problem, not a script problem. The goal was not a more fluent response. It was a representative with the right context at the moment an answer is needed.
Discipline is the foundation
I have learned this the hard way: speed creates little value if no one can explain who made a decision, what data informed it, or where accountability sits. Most teams miss this because those questions arrive after a demo works.
AEP made a harder choice. Before chasing a quick answer, the team worked through the call itself: what information the representative needed, which systems supplied it, and who remained responsible. They did not get it right on the first try. Live conditions corrected assumptions, and the workflow was revised.
That work identified more than 170 customer intents representing the reasons customers contact the utility. AEP documented each one and audited the decision behind it. We built Bill Analyzer to operate. Not experiment.
Through Gigawatt’s Customer module, Bill Analyzer brings together CIS data with billing and usage history, weather, and interval meter data during the call. The representative can see the context behind the bill without moving between systems.
Once that context was in one place, the change was visible in the calls themselves. AEP achieved a 5x improvement in resolution time. That result matters because it reflects less searching, fewer handoffs, and a clearer answer for the customer.
This is what governed execution means in practice. The CIS stays authoritative. Every answer is traceable. The representative remains accountable for the conversation. The architecture makes those boundaries clear.
I did not understand this at first. I thought more data would solve the problem. It does not. The value comes from putting the right data into a workflow with clear responsibility.
The role of modern utility billing software is not to replace judgment. It is to give people the information they need to exercise judgment well. That is the difference between a useful tool and another source of risk.
Why architecture matters more than interface
Here is what I have seen fail: a vendor produces a compelling answer from data in a sandbox, then asks the utility to work out ownership, controls, and evidence after the fact. The interface looks finished. The operating model is not.
AEP started from the other direction. The work began with a real customer question and the representative responsible for answering it. From there, the team connected approved data, defined the workflow, kept human authority in place, and recorded what happened. A fluent answer alone is not enough.
The same principle applies across customer, billing, revenue, and operations workflows. Connected data creates the context. Controls determine how that context is used. The existing CIS remains the system of record. Start with one real workflow, prove the result, and expand only when the operating model can support it.
Poor governance looks different. It is the answer that cannot be reconstructed, the handoff no one owns, and the exception that lives outside the system. It may look fast until something goes wrong.
Modernization and control are not competing
For years, utilities tried to modernize despite control. Wrong. Modernization requires control.
Control is not a brake on progress when it is built into the architecture. It gives teams the confidence to move because the authority of the CIS, the role of the representative, and the record of each decision remain clear.
AEP’s deployment shows what that looks like in practice. Bill Analyzer improves one consequential interaction without asking the utility to replace the systems it already relies on. It is something a team can operate every day, measure, and extend.
Discipline without rigidity creates freedom. When standards are clear and carried by the architecture, decisions get simpler and trust has a place to stand.
That is the lesson I take from AEP’s launch. Discipline is not what slows modernization but what makes modernization real enough to last.
Read the full announcement: Gigawatt AI announces AEP go-live with Bill Analyzer.
Continue reading:
AEP Bill Analyzer: A Better Answer to High-bill Questions
September 01, 2026
Business
Technology
High-bill questions test a utility’s ability to connect billing, usage, weather, meter, and rate context into one accountable customer interaction. This article explains how AEP and Gigawatt built Bill Analyzer around real service workflows, reduced resolution time, preserved CIS authority, and established a practical model for governed AI in utility customer operations.
AI Is Not a Feature, It Is Infrastructure
July 08, 2026
Business
Technology
AI should not sit around the edges of utility modernization. For regulated utilities, it must operate as infrastructure, connecting governed data, workflow execution, controls, auditability, and measurable outcomes. This essay explains why AI needs operating architecture before it can scale responsibly across utility systems, teams, and enterprise decisions at scale.
GENERATION: RE – The Official Nomination
March 23, 2023
Business
Life
Every generation is given a name – some more accurate than others. Consider this my nomination for the official name of the emerging generation (those born in 2000 to today): Generation:RE “What’s in a name?” mused Shakespeare. Demographers create generational groupings to examine economic trends and social changes over time. These groupings take on names, some […]