Double-Counted Savings, Disappointed CFOs: Untangling the Overlapping ROI Claims of Energy and Communications Vendors

The pitch arrives in two separate meetings, usually weeks apart. First, the energy consultant presents a detailed analysis showing that infrastructure modernization and load optimization will reduce the facility's power costs by 18 percent annually. Then the communications vendor arrives with a competing deck, demonstrating that migrating to their platform will cut operational overhead—including energy-related infrastructure costs—by 15 percent. Both projections look credible. Both are supported by case studies and reference customers. Both are, in important respects, describing the same pool of money.

This is the handoff problem: a structural accountability gap in which two vendor categories each claim ownership of efficiency gains that overlap in practice, producing ROI projections that are individually plausible but collectively impossible. When the CFO reviews the actual results twelve months later, the combined savings fall well short of the combined promises—and neither vendor accepts responsibility for the shortfall.

How the Overlap Gets Built In

To understand why this happens, it helps to trace where the efficiency claims originate. Energy consultants typically identify savings opportunities by auditing total facility consumption and modeling the impact of specific interventions: equipment upgrades, load scheduling changes, demand response enrollment, or HVAC optimization. When communications infrastructure represents a significant portion of facility load—which it increasingly does—the energy audit will include projections for reducing that load through infrastructure changes.

Communications vendors, simultaneously, build their ROI models around the costs their platform displaces. Legacy on-premises PBX systems, distributed server infrastructure, and proprietary network hardware all carry energy costs that vendors correctly identify as eliminable through migration to cloud-hosted or software-defined alternatives. The energy savings from decommissioning that hardware are real. They are also the same savings the energy consultant is counting.

Neither vendor is fabricating numbers. Both are applying legitimate analytical frameworks to a shared operational reality. The problem is that no one is coordinating between them, and no one has ownership of the total picture.

The Incentive Structure That Sustains the Problem

Vendors do not resolve this overlap because they have no incentive to do so. An energy consultant's engagement is typically scoped to energy outcomes. If the communications vendor's platform migration eliminates some of the infrastructure the energy audit targeted, the consultant's projected savings still appear on paper—the consultant simply did not deliver them, because the work was done by someone else. From the consultant's perspective, the savings were real; the client just chose a different implementation path.

The communications vendor faces the mirror-image situation. If the energy consultant's infrastructure changes reduce facility load before the platform migration is complete, the vendor's ROI model still projects savings from the migration—but some of those savings have already been realized through other means. The vendor's contribution looks smaller than projected, not because the platform underperformed, but because the baseline shifted.

In both cases, the vendor's incentive is to present savings projections based on a static baseline that does not account for the other party's concurrent interventions. The CFO, who approved both engagements based on non-overlapping savings projections, is the only party with a clear view of the total commitment—and typically lacks the technical framework to identify the duplication before it is too late.

A Framework for Identifying Claimed-Twice Savings

The first step in preventing double-counted ROI is establishing a shared savings taxonomy before any vendor engagement begins. This means categorizing projected savings by their source mechanism—not by which vendor is claiming them.

Useful categories include: hardware decommissioning savings (energy and maintenance costs eliminated by removing physical infrastructure), load reduction savings (reduced consumption from more efficient operation of retained infrastructure), and behavioral or scheduling savings (reductions achieved through changed operational patterns rather than equipment changes).

When an energy consultant and a communications vendor both submit proposals, their savings projections should be mapped against this taxonomy. Any category that appears in both proposals should trigger a direct conversation with both parties about which engagement will actually deliver that savings category and how attribution will be measured.

This is not a complex analytical exercise. It requires approximately one structured meeting with both vendors present—something most enterprises avoid because it creates uncomfortable conversations about overlapping claims. That discomfort is precisely the point.

Structuring Contracts Around Actual Outcomes

The deeper solution is contractual. Most vendor agreements in both the energy and communications categories are structured around activity delivery—the consultant completes the audit and submits recommendations; the vendor migrates the platform and achieves uptime targets. Neither contract is typically structured around verified savings outcomes.

Performance-based contracting, in which a portion of vendor compensation is tied to independently verified savings against a defined baseline, forces vendors to take a position on exactly which savings they are responsible for delivering. It also creates a natural mechanism for identifying overlap: if two vendors are both claiming performance fees against the same savings category, the baseline conflict becomes visible and must be resolved.

For enterprises that lack the internal capacity to negotiate and administer performance-based contracts, a simpler alternative is the shared baseline agreement: a document, signed by both vendors before either engagement begins, that defines the starting consumption and cost figures against which all savings claims will be measured. This does not prevent overlap, but it prevents vendors from selecting favorable baselines that inflate their apparent contribution.

What Finance Leaders Should Demand Before Signing

CFOs and finance directors reviewing vendor proposals that include energy or communications efficiency savings should require three things before approval.

First, a savings source map: a line-by-line breakdown of projected savings that identifies the specific operational change responsible for each savings category. Second, a baseline certification: a written statement from the vendor specifying the exact baseline figures their projections assume, including any assumptions about concurrent changes to the operating environment. Third, a measurement protocol: a defined methodology for calculating actual savings post-implementation, using data sources that both the vendor and the enterprise agree are authoritative.

Vendors that resist these requirements are, implicitly, protecting their ability to claim credit for savings they did not uniquely deliver. That resistance is informative.

The handoff problem is not a vendor ethics failure. It is a procurement design failure—one that enterprises perpetuate by evaluating energy and communications vendors in separate processes, against separate baselines, with separate accountability frameworks. Closing that gap requires coordination that most organizations have not yet built. The CFOs who demand it will be the ones whose efficiency investments actually show up on the balance sheet.