Home » Updating Your ERP: How to Build the Business Case

CentralViews

Updating Your ERP: How to Build the Business Case

Utility finance director presenting a plan to modernize utility ERP systems to city council members

Most utility finance and IT staff already know when their enterprise resource planning (ERP) system is holding them back. They see it every billing cycle, every month-end close and every time someone asks for a report the system can’t produce. The cost of an aging ERP is real but spread across dozens of everyday tasks that don’t manifest themselves in a single line item.

Why ERP Modernization Can Be a Hard Sell

The problem is perception. A city council, utility board or city manager weighs ERP modernization against water main replacements, substation upgrades and a dozen other needs that are easier to visualize.  By contrast, software upgrades rarely look urgent from the outside. Bills still go out. Payroll still runs. The work gets done, even if it takes overtime, endless spreadsheets and a few employees who know how to coax the old system along. Things still get done, just very inefficiently.

Start With a Problem Statement

In making the case for a new ERP system, a common mistake is focusing on features rather than outcomes. Leadership does not approve software; it approves solutions to the problems it understands. Before you mention a single product, write down what is going wrong in clear terms that a council member or board member would recognize.

Good problem statements are specific and tied to outcomes leadership already cares about. For example:

  • Month-end close takes nine working days because data has to be reconciled by hand between billing and the general ledger.
  • Rate studies require two staff members to spend several weeks pulling and cleaning historical data.
  • Our current vendor has announced the end of support for the version we run.
  • Only one employee fully understands our antiquated payroll module, and she plans to retire soon.

Use your own numbers, not industry averages. A figure drawn from your utility’s own records carries far more weight in a council chamber than a statistic from somewhere else.

Document the Real Cost of Standing Still

Every business case needs a “do nothing” option, and it should be presented honestly. Doing nothing is not free. It simply moves the cost to places that are harder to see. Look for these categories:

  • Staff time on manual work. Duplicate data entry, spreadsheet reconciliations and report assembly. Estimate hours per month and multiply by loaded labor cost.
  • Overtime and seasonal strain. Budget season, year-end close and audit preparation often run on overtime that a modern system could reduce.
  • Audit findings and compliance risk. Repeat findings tied to weak controls, missing audit trails or manual adjustments are a cost, and they are something governing bodies take seriously.
  • Knowledge risk. When critical processes depend on one or two people, a retirement or resignation becomes an operational risk.
  • Security and support exposure. Older platforms that are at or nearing end-of-life mean the risk of waiting is implicitly risky.
  • Level of Service. Online payments, faster customer service answers and better data for rate decisions all depend on integrated systems.

Lack of systems integration is one of the most common sources of hidden labor at small and midsize utilities. Our guide to Utility ERP Software for Municipal Utilities and Electric Cooperatives: A Complete Guide to Choosing the Right Platform covers the core functions an integrated platform should handle.

Speak Your Audience’s Language

The same facts land differently depending on who is listening.

For municipal utilities, the audience is often a city manager, a finance director and an elected council or utility board. They think in terms of the general fund, the rate base, transparency and public accountability. Emphasize stewardship: better data for rate decisions, cleaner audits, faster answers to public records requests and lower long-term risk to ratepayers.

For electric cooperatives, the audience is usually the general manager and an elected board of directors. Members expect reliable service and responsible use of their money. Emphasize member service, operational efficiency and the cooperative’s ability to plan for growth without adding staff.

A quick test for your business case: Could a council member or board member explain the request to a constituent or member in two sentences? If not, simplify it until they can.

Just the Facts Please

Leadership will scrutinize the financial picture, so credibility matters. A few principles help:

  • Separate one-time and recurring costs. Implementation, data migration and training are one-time. Licensing, hosting and support are recurring. Compare recurring costs against what you pay today, including maintenance on the old system.
  • Count internal staff time. Your team will spend real hours on discovery, testing and training. Including that time shows leadership you understand the full commitment.
  • Use conservative savings estimates. If you believe a change will save 30 hours a month, present 20.
  • Show a range, not a single number. A low, expected and high estimate is more believable than one precise figure.
  • Tie it to the budget process you already use. If your utility builds an annual rate justification, the same data discipline applies here. See Rate Case and Budget Season: How Municipal Utilities Use Software to Build Their Annual Rate Justification for how that process works.

Address Risk Head On

Every experienced council member or board member has heard of a technology project that ran long or over budget: delineate those risks and explain how you will manage them.

The biggest concerns are usually timeline, staff capacity and data migration. Lay out a realistic schedule, identify who will be involved and when, and be candid about the condition of your current data. Our article on Utility ERP Implementation: What a Realistic Timeline Looks Like walks through each phase and the factors that tend to stretch it.

It also helps to describe how you will measure success after go-live. Shorter close cycles, fewer manual adjustments and faster report turnaround are simple, visible indicators.

Assemble the Case: A Simple Outline

Keep the written business case short. Most governing bodies prefer a few clear pages over a thick binder. A practical structure:

  1. Problem statement. What is not working, and why.
  2. Cost of standing still. Hidden labor, risk and missed opportunities of doing nothing.
  3. Options considered. Do nothing, upgrade, or move to a new platform.
  4. Recommended path. What do you recommend and why.
  5. Costs and funding. One-time and recurring costs.
  6. Timeline and staffing. When the work happens and who is involved.
  7. Risks and mitigation. What could go wrong and how you will manage it.
  8. Measures of success. How leadership will know the investment paid off.

Timing is Everything

Even a strong case can stall if it arrives at the wrong moment. Bring your request forward early in the budgeting process. Informal conversations with key decision makers before the formal presentation can help. Eliminate the possibility for a surprise in the middle of the budgeting process.

Where CentralView Fits

CentralView¹ is a utility ERP platform built by Central Service Association (CSA) for municipal utilities and electric cooperatives. It brings core financial, billing and operational functions together on a single platform, which addresses many of the hidden costs described above. Our team can help you identify where your biggest gains are likely to be.

Talk With Our Team About Your ERP Business Case

¹ CentralView is Central Service Association (CSA) Trademark.

The information presented in this article is intended for general educational purposes. Utility software environments vary significantly. We recommend consulting with a qualified technology advisor to evaluate solutions appropriate to your organization’s specific operational requirements.