How do you get a five-figure backup power upgrade approved by someone who will never ask about dry contact alarms or amp-hours? Evoltix sees this bottleneck constantly, and it is never a technology problem. The engineer walks into the budget meeting already convinced the current system is overdue. The person signing off, usually a CFO, budget director, or finance officer, wants something else: not a runtime number, but a payback date.
That gap between technical justification and financial approval is where most backup power upgrades stall, not because the case is weak, but because it has never been translated into finance’s language. The Evoltix Zero-Glitch Power Module (ZPM) is the power intelligence system network operators install once a UPS can no longer make the runtime and reliability numbers work, and the financial case for it uses the same categories any capital request needs: what it costs, what it eliminates, and when it pays back.
This is that framework, the same categorization Evoltix uses when it builds a site-specific TCO model with customers, laid out so you can draft the first version yourself before the conversation with finance ever happens.
Why a Technical Case and a Financial Case Are Different Documents
Most engineers writing a capital request write the technical case well. The current system is aging. The runtime is inadequate. The battery chemistry fails without warning. That case answers “why does this need to change.” It does not answer the question a CFO or finance director is actually asking, which is “why this specific expenditure, at this cost, now.” Those are different documents, built from different evidence, and conflating them is the most common reason a solid technical case stalls in a budget cycle.
The Four Sections a Finance-Ready Business Case Needs
A business case a CFO will actually approve has four parts. Each answers one question, and each pulls its numbers from a different place.
| Section | What It Answers | Where the Numbers Come From |
|---|---|---|
| The Baseline | What the current system costs to keep running today | Your own dispatch logs, battery replacement history, and generator runtime records |
| The Proposed State | What changes, and over what time horizon | A site-specific model built against your load profile |
| The Capital Ask | What this costs, as a single number tied to a quote | A configuration-specific quote, not a published price list |
| The Payback | When the expenditure pays for itself | Confirmed across deployed customer networks at approximately 3 years |
The Baseline
This is the part most business cases shortchange. “Our UPS is old” is not a baseline. “We’ve replaced batteries at 14 of our 20 sites twice in the last eight years, and we dispatch a truck to a site 4 to 6 times a year on average” is a baseline. A reactive site typically runs 3 to 8 truck rolls a year, at roughly $400 for the base dispatch plus another $170 in materials. That is real money sitting in a maintenance budget line instead of a capital request, and it is exactly the kind of number a CFO respects, because you pulled it from your own logs, not a vendor’s average.
For a state DOT network, a county emergency management agency, or a Statewide Interoperability Coordinator (SWIC, the state official who manages public safety radio interoperability), the baseline carries a line most private-sector CFOs never see. Federal backup power certification requirements and grant funding tied to communications infrastructure both carry compliance exposure that a private-sector CFO doesn’t have to think about.
Source: fema.gov, BRIC and HMGP program guidance.
The two categories everyone reaches for first, generator fuel and maintenance costs, and the operational cost of a backup power failure, are covered in depth elsewhere: see Telecom Tower Generator Runtime for the fuel and maintenance math, and What Does a Backup Power Failure Cost a Public Safety Network? for the risk and dispatch-cost breakdown by segment.
The Proposed State
Model this against a 10-year horizon. That is not an arbitrary number. It is long enough to span two to three avoided lead-acid battery replacement cycles, which is where most of the operating cost difference between a legacy system and a ZPM actually shows up.
The Capital Ask
This should be a single number, not a range. A range invites a finance reviewer to negotiate toward the low end before the conversation even starts. Evoltix prices the ZPM by configuration rather than off a published list, which means your number should come from an actual quote, not an estimate.
The Payback
This is the line a CFO will actually remember after the meeting ends. Across deployed customer networks, ZPM payback runs approximately 3 years. Everything above it in the document is supporting evidence. This is the sentence the rest of the case exists to support.
“A CFO doesn’t approve a battery. A CFO approves a number and a date.”
Where the Numbers Should Come From
Most vendor TCO calculators run on assumptions: an average truck roll, an average fuel price, an average failure rate. Evoltix builds its models on a forecasting model validated against years of real deployment data, not just industry averages. A case built on documented deployment data survives a finance review in a way a vendor’s marketing average does not.
The same logic applies to your own baseline. Your dispatch logs and battery records make a stronger case than any industry figure, including the ones linked above. Use outside figures to sanity-check your records, not replace them.
Ready to Build the Numbers for Your Sites?
If you want help applying this framework to your own sites, that’s what a TCO Studio session is for.
Request a TCO Studio session: evoltixenergy.com/contact/
Call: +1 (855) 964-9274
Want the fuller product comparison first? See ZPM vs. UPS vs. DC Power System.
Related Reading
Telecom Tower Generator Runtime: How to Cut Fuel and Maintenance Costs
What Does a Backup Power Failure Cost a Public Safety Network?
How to Evaluate Backup Power Vendors: What UPS Spec Sheets Don’t Tell You
ZPM vs. UPS Battery Backup vs. DC Power System