The energy manager at a plant knows monitoring is needed: meters, software, 15-minute visibility. They take it to the CFO and get the usual question: "What's the return?". They answer with technical arguments —"we'll have better control," "we'll be able to optimize"— and the proposal dies right there. Not because the CFO is against saving money, but because "better control" is not a figure you can put into a business case.
Energy monitoring almost always has an excellent ROI. The problem is rarely the real return: it's that whoever proposes it doesn't translate it into the CFO's language. This article gives you the structure to build a business case that gets approved on the first pass.
The CFO's question isn't "is it good?", it's "how much and when do I get it back?"
A CFO evaluates every investment with the same logic: how much it costs, how much it returns, in what time frame, and what risk it carries. Energy monitoring is no exception. If your proposal doesn't answer those four things in pesos, it competes at a disadvantage against any other investment that does.
The good news: monitoring is one of the few investments where the cost of not doing it is quantifiable and tends to be large.
The invisible cost: how much you lose today by not measuring
Without monitoring, the plant pays "blindness taxes" that are rarely accounted for:
- Unmanaged demand peaks that drive up the fixed charge for the entire month.
- A penalized power factor that no one corrects because no one sees it in time. See Power factor: why CFE penalizes you.
- Billing errors that slip through undetected. See CFE billing validation: 7 common errors.
- Off-hours consumption or idle equipment that no one notices.
You are already paying these costs. Monitoring is not a new expense: it's what stops an existing leak. That's the reframe that changes the conversation with the CFO.
How to quantify the recoverable savings
The business case is built with conservative, defensible figures, not with the "up to 30%" from the vendor's brochure:
- Take 12 months of real bills (via UDM).
- Identify the leaks measurable today: power factor penalty (it's on the bill), excess demand charge, tariff errors.
- Estimate what's recoverable with a prudent percentage of consumption (a well-run monitoring program typically frees up between 5% and 15%).
- Subtract the cost of monitoring (hardware + software + operation).
- Calculate the payback in months.
The structure of the business case: an example in MXN
| Item | Annual amount (MXN) |
|---|---|
| Current electricity spend | $12,000,000 |
| Power factor penalty (visible on the bill) | $480,000 |
| Unmanaged demand charge (estimated) | $360,000 |
| Recoverable billing errors (estimated) | $150,000 |
| Identified recoverable savings | $990,000 (~8%) |
| Investment: meters + software (year 1) | $320,000 |
| Operation / service (annual) | $180,000 |
| Net savings year 1 | $490,000 |
| Payback | ~6 months |
The figures are indicative; the real case comes from your bills. But the structure is what a CFO needs to see: conservative savings, total cost, short payback.
Presenting the risk of NOT investing
The second argument, after the payback, is the opportunity cost: every month without monitoring, the leaks continue. If the recoverable savings are ~$990k per year, postponing the decision six months costs ~$495k. Presenting inaction as a decision with a cost —not as the neutral state— is what creates legitimate urgency.
Mistakes that sink the proposal
- Selling the technology, not the result. The CFO doesn't care about the meters; they care about the pesos.
- Using the savings from the vendor's brochure. Inflated figures destroy credibility. Be conservative.
- Asking for the software without asking for the time of whoever will operate it. An EMS without an operator doesn't save. See Energy management software: criteria for the CFO.
- Not bringing the bill. A business case without real data is an opinion.
- Omitting the risk of inaction. Without it, the decision is postponed at no apparent cost.
The CFO's three objections and how to answer them
Anticipating the objections is half the approval. The three most common:
"We already have meters." Having measurement is not having management. The question is not whether you measure, but whether someone acts on the data in time. If the existing meters don't generate actionable alerts and aren't reviewed, they're as blind as having none. See Energy management software: criteria for the CFO.
"We don't have anyone to operate it." A legitimate objection, and that's why the business case must include the cost of operation —internal or as a managed service—. An EMS without an operator doesn't save. Better to present the full cost and a real payback than to hide the cost of operation and fail at execution.
"The savings are speculative." That's why you start from what's already visible on the bill (power factor penalty, demand charges) and use conservative percentages for what's estimated. A case built on verifiable figures withstands scrutiny; one built on the vendor's brochure doesn't.
The constant across all three: answer with pesos and with your own data, never with generic promises.
How it fits into energy management
Justifying monitoring is one step within the larger system of industrial energy management: first the data, then the measurement, then the informed decision. Monitoring is the investment that enables the entire cycle, and that's why it's usually the first one worth approving. To place it among the other return levers, see Top 10 energy efficiency measures with the best ROI.
Next step
If you need to take a monitoring proposal to your CFO and want it approved, the path is a business case with your real bills and conservative figures. At Enerlogix we build it with you within the 360 Management Plan, our energy management service: we identify the recoverable savings visible on your bill and put together the payback in financial language.
Request a free evaluation of the 360 Management Plan and we'll deliver the business case ready to present to your leadership.
Frequently asked questions
In plants with real leaks, such as a power factor penalty or unmanaged demand, paybacks of 6 to 18 months are common. If your business case yields more than 24 months, it's worth reviewing the assumptions. Monitoring is one of the few investments where the cost of not doing it is quantifiable and tends to be large.
You start from what's already visible on the bill: the power factor penalty, the excess demand charge, and tariff errors. For what's estimated you use a conservative percentage of consumption, since a well-run monitoring program typically frees up between 5 and 15 percent. The verifiable part sustains the credibility of the estimated part.
As an example: on an annual electricity spend of 12 million MXN, you identify 480,000 in power factor penalty, 360,000 in unmanaged demand, and 150,000 in recoverable errors, for savings of about 990,000 MXN, close to 8%. Subtracting 320,000 of investment and 180,000 of operation, the net savings in year 1 are 490,000 MXN and the payback is around 6 months.
Every month without monitoring, the leaks continue. If the recoverable savings are about 990,000 MXN per year, postponing the decision six months costs close to 495,000 MXN. Presenting inaction as a decision with a cost, and not as the neutral state, is what creates legitimate urgency before the CFO.
If you don't have anyone to operate the system and act on the alerts, the managed service usually delivers a better return, because savings come from action, not from the dashboard. An EMS without an operator doesn't save. That's why the business case must always include the cost of operation, internal or as a service, instead of hiding it and failing at execution.
