Selected work
What we've built for SAP for Utilities
Project experience
Selected Project Experience
Client names stay confidential; references are available on request under NDA.
- 01
Tier 1 West Coast utility
Utilities. Name confidential.
SAP C4C, Sales and Service Cloud V2, Emarsys
Our founder's advisory role on an end-to-end SAP customer experience project: SAP C4C, Sales Cloud V2, Service Cloud V2 and Emarsys, working closely with SAP and the system integrator.
- 02
Northeast toll agency
Transportation & tolling. Name confidential.
SAP BRIM (CC, CI and CM)
Architecture and hands-on delivery on an ongoing SAP BRIM implementation: Convergent Charging, Convergent Invoicing and SAP Convergent Mediation, alongside the agency's internal team.
- 03
California county government
Public sector. Name confidential.
SAP SuccessFactors
End-to-end SAP SuccessFactors implementation and ongoing application support, through a delivery partner.
- 04
Northeast utility
Utilities. Name confidential.
SAP IS-U, Customer Management and FSM
End-to-end SAP IS-U implementation for a gas utility, then ongoing support, upgrades and merger-related changes, through a delivery partner.
Featured use cases
A few of the problems we solve
Prototypes run on sample data. Filter by area.
- IS-U / S/4HANA Utilities
BPEM billing exception agent
- Problem
- Billing exceptions pile up faster than specialists can clear them, and bills wait.
- Approach
- An AI agent prioritizes the exception worklist and recommends a resolution that a billing specialist approves.
- Outcome
- Smaller, younger exception backlog and fewer delayed bills
- IS-U / S/4HANA Utilities
Credit and collections agent
- Problem
- Collections treats very different accounts the same way, and protected customers need careful handling.
- Approach
- An AI agent suggests the next step for each account in collections, and a collector decides.
- Outcome
- Better-targeted collections effort with customer protections respected
- SAP BRIM
One customer invoice with SAP BRIM
- Problem
- Commodity and non-commodity charges end up on separate bills.
- Approach
- We design SAP BRIM so charges from different sources come together on one customer invoice.
- Outcome
- One clear bill for customers and simpler billing operations
- SAP BRIM
BRIM accounting that reconciles
- Problem
- Contract accounting is where BRIM programs overrun their budgets.
- Approach
- We plan the accounting side of BRIM in from the start, so finance can trust what billing posts.
- Outcome
- Fewer late surprises and books that reconcile
- AI & Data / Analytics
Utilities BI foundation
- Problem
- Leaders' questions cut across billing, metering, outage and asset systems that each report on their own.
- Approach
- A shared data model and KPI set across billing, metering, outage and asset data, adapted to your source systems.
- Outcome
- Shared, trusted KPIs and a faster start on analytics and AI
- AI & Data / Analytics
Consultant copilot
- Problem
- Answers about SAP for Utilities are scattered across documents, and unsourced answers are hard to trust.
- Approach
- An AI assistant answers consultants' questions with sources and drafts routine delivery documents.
- Outcome
- Faster, better-sourced answers for delivery teams
- SAP SuccessFactors
Onboarding and one workforce record
- Problem
- New-hire tasks are tracked in inboxes and spreadsheets, and people start without what they need.
- Approach
- We implement SuccessFactors so recruiting hands over cleanly to onboarding and every new hire has one record.
- Outcome
- A smoother first day and cleaner workforce data
- SAP SuccessFactors
Required training and HR-to-payroll
- Problem
- Required training and recertification dates are hard to track and report.
- Approach
- We set up required learning by role and connect HR to payroll, so the records agree.
- Outcome
- Compliance you can report on and HR changes that reach payroll
More use cases available on request. Tell us what you're working on and we'll walk you through the ones that fit. Contact us →
See a use case on sample data
We'll demo it on sample data and talk through what it would take on your SAP release.