# Consolidating utility vendors 2026: $1.20/sq ft savings for 5+ sites

Lars Bergstrom · November 6, 2026

> Separate utility vendor roles, normalize invoices to dollars per square foot, and find $1.20/sq ft savings when consolidating 5+ sites in 2026.

Separate the vendor role before comparing proposals. Commodity supplier, billing or utility-management processor, and waste or facilities contractor are different contracts, and consolidating one does not consolidate the others. Match each invoice line to the contract that owns it, because a single vendor name can hide separate scopes and separate exit terms.

Normalize every invoice to a common unit, dollars per square foot per year, by dividing 12 months of invoice totals by the site area used for normalization. Use the same 12-month window and the same area basis for every site, and keep transition, exit, and service-risk costs in the same numerator only when they are supported by invoices or signed change orders.

Record service-response coverage by site alongside the normalized cost. A lower cost that removes a response path, changes a payment owner, or leaves a meter unmapped is not a saving inside the perimeter; it is an uncovered risk that must be resolved before any consolidation decision.

![Separate the vendor role before comparing proposals. Commodity — Consolidating utility vendors 2026](https://static.mm-ais.com/article-images-ai/consolidating-utility-vendors-2026-1-20-ai-1d808881.jpg)

## Evidence: build the $1.20/sq ft test

The $1.20 per square foot figure is a test threshold set for this decision, not a benchmark from published market data. No vendor quote, tariff, or invoice in the available record validates $1.20 as a market price; it is a hurdle the consolidation case must clear with its own invoice-verified evidence.

To make the test invoice-verified, build a convergence file from documents rather than from one source. Each candidate source must show the same site, the same utility class, and the same normalized cost basis. The required comparison is gross savings before transition and exit costs, then net savings after those costs and after any service-risk adjustment. A source that only reports an incident workflow or safety outcome cannot carry a utility cost claim. Net savings also fail if any site loses service-response coverage, because a cheaper invoice alone does not satisfy the threshold.

| Source class | Site count | Utility class | Gross $/sq ft | Transition/exit cost | Net $/sq ft |
| --- | --- | --- | --- | --- | --- |
| Annual utility invoice set | All five or more sites | One class per row | From invoices | From contract terms | Calculated |
| Signed vendor rate card | All five or more sites | One class per row | From quoted rates | From contract terms | Calculated |
| Submeter or interval export | All five or more sites | One class per row | From measured use | From contract terms | Calculated |

No row may be populated from an estimate or from a safety-guide source. Require at least three source classes and all five or more sites before acting. A single invoice set, one vendor quote, or one submeter export is not enough, because each can hide a tariff, a fee, or a service gap. Convergence means the three classes agree on site count, utility class, and net result; if one class disagrees, treat the disagreement as a failed test rather than an average.

The decision gate is simple: consolidate only when the convergence file shows net savings at or above the threshold and no site loses service-response coverage; otherwise keep the incumbent. This keeps the $1.20 figure in its proper role as a test, not as a fetched benchmark.

![Evidence: build the .20/sq ft test — Consolidating utility vendors 2026](https://static.mm-ais.com/article-images-ai/consolidating-utility-vendors-2026-1-20-ai-6ff57c32.jpg)

## Options compared: win by net $/sq ft

Utility-type specialists are the default winner in this options table: they preserve utility-specific dispatch while allowing one reporting layer, and they should be treated as the baseline unless another option clears both the net and coverage tests.

| Option | Verified gross $/sq ft | Transition cost | Exit/termination exposure | Service-response coverage | Decision |
| --- | --- | --- | --- | --- | --- |
| A: single national utility vendor | Must be invoice-verified by site and utility type | Includes meter/invoice mapping labor | Includes early-termination fees and duplicate billing during cutover | Must preserve site dispatch | Choose only if net beats B after all costs and coverage holds |
| B: utility-type specialists | Invoice-verified by utility type | Limited to reporting alignment | Lower because contracts stay utility-specific | Retains specialist dispatch | Default winner |
| C: keep incumbents with shared reporting | Current invoice-verified baseline | None for vendor change | None for vendor change | Unchanged | Keep if the threshold is not met or coverage is at risk |

Load three cost buckets as separate lines before comparing net results: transition labor for meter/invoice mapping, early-termination fees, and duplicate billing during cutover. If any bucket is folded into gross savings, the comparison can make a weaker option look cheaper than it is.

The winner is B unless A's net per square foot beats B after all costs and preserves site dispatch. If A cannot demonstrate both, the specialist structure or the incumbent structure remains the safer choice.

Before declaring a winner, require the same cost basis, the same site set, and the same service-response definition across all three options. If one option changes the denominator or the dispatch assumption, reject that comparison and rebuild it.

## Worked 5-site test and usable worksheet

Use this worked example only to test the arithmetic behind the $1.20 per square foot threshold; it is arithmetic from the headline threshold, not an observed saving. At 100,000 square feet per site, the target equals $120,000 per site per year (100,000 × $1.20 = $120,000). For five identical sites, the annual target equals $600,000 ($120,000 × 5 = $600,000). Replace 100,000 with each site’s actual measured area before you run the test, because the same dollar result can pass at one site and fail at another when floor area differs.

Build the worksheet from invoice-verified records for all five or more sites over the same 12-month period. Enter each site’s baseline invoice total, the consolidated quote total for the same scope, and every transition or exit cost that would be incurred to move or unwind the arrangement. Calculate net savings as baseline minus quote minus transition or exit cost, then divide by the site’s square footage to produce net dollars per square foot. Keep the service-response check separate from the math so a dollar gain does not hide an operational gap.

Worked example at the 100,000 sq ft site size used above: a site with a $1,000,000 12-month baseline invoice total, a $900,000 consolidated quote for the same scope, and $20,000 of transition and exit costs shows $80,000 of net savings, or $0.80 per square foot — below the threshold, so the incumbent stays. The same baseline with an $860,000 quote and $20,000 of costs shows $120,000 of net savings, or $1.20 per square foot, which passes only if service-response coverage also holds at that site. Replace these illustrative totals with invoice-verified figures for each site before running the test.

Read the completed worksheet in two passes. First, confirm that each row uses the same 12-month window and that the quote covers the same utility scope as the baseline invoices. Second, compare each site’s net dollars per square foot to the $1.20 test threshold and record whether service-response coverage is maintained at that site. A portfolio total can look attractive while one or more sites miss the threshold or fail the service-response check, so the site-level row is the decision unit.

Before acting on the result, recompute every row with the actual square footage and invoice-verified totals, not estimates or blended averages. If any baseline, quote, or transition cost is missing, leave the row incomplete and resolve the document gap rather than filling it with an assumed number. In 2026, the worksheet is usable only when the inputs are traceable to site-level records and the arithmetic is reproducible.

## Limits, edge cases, and decision rules

In 2026, a multi-site utility-vendor consolidation decision should be treated as a controlled test, not a default efficiency move. The available record does not establish any actual savings per square foot, vendor rate, termination fee, or service-level credit; every figure used in the decision must come from site-level invoices, contracts, and service logs. Before applying any rule, confirm that the analysis covers the same sites, the same cost categories, and the same service obligations that will exist after a vendor change.

| Edge case | How the rule changes | Required check before deciding |
| --- | --- | --- |
| Regulated tariff areas | The commodity-switch part of the rule breaks if supply cannot be switched; consolidation can still win for bill processing or waste handling. | Separate commodity costs from administrative costs and test only the functions the vendor can legally control. |
| Landlord-metered sites | Exclude the site from the portfolio test until landlord data is obtained. | Request meter-level or pass-through invoice detail from the landlord and document any allocation method. |
| 1–4 sites | The 5+ site rule does not apply. | Evaluate each site or utility arrangement on its own transition burden, contract terms, and service needs. |
| Sites with more than 15% year-to-year usage swing | Annual invoices are not a reliable basis for the test. | Use interval data to distinguish operational change from vendor-driven savings before including the site. |

**Rule 1 — Scope gate:** If the portfolio contains fewer than 5 sites, do not apply the portfolio consolidation test. Use a site-specific review because transition effort and service risk can outweigh administrative gains at small scale.

**Rule 2 — Net-savings gate:** If a 12-month, site-level invoice sample for all in-scope sites does not show post-transition net savings at or above $1.20 per square foot after transition, exit, and service-risk costs, keep the incumbent arrangement. A projected saving that is not verified against invoices and contract costs fails the test.

**Rule 3 — Service gate:** If any site loses service-response coverage under the proposed consolidation, reject the consolidation or carve that site out before signing. Cost improvement does not justify a gap in outage, billing, or field-response support.

**Rule 4 — Data-quality gate:** If landlord data is missing, or if interval data is not used for a site with more than 15% year-to-year usage swing, pause the decision for that site. Consolidate only after the missing data is obtained and the savings estimate is recalculated on a comparable basis.

## Frequently Asked Questions

**Can one consolidated vendor contract be assumed to cover commodity supply, billing processing, and waste services?**

Commodity supplier, billing or utility-management processor, and waste or facilities contractor are different contracts, and consolidating one does not consolidate the others.

**Why must invoice lines be matched to contracts rather than vendor names?**

Each invoice line should be matched to the contract that owns it because a single vendor name can hide separate scopes and separate exit terms.

**How should invoices be normalized and compared across sites?**

Every invoice should be normalized to dollars per square foot per year by dividing a full year of invoice totals by the site area used for normalization, using the same time window and area basis for every site.

**When can transition, exit, or service-risk costs be included in the normalized comparison?**

Transition, exit, and service-risk costs belong in the numerator only when they are supported by invoices or signed change orders.

**Is the per-square-foot hurdle a validated market price?**

It is a test threshold set for this decision, not a benchmark from published market data, and no vendor quote, tariff, or invoice validates it as a market price.

**Does a lower normalized cost automatically count as a saving?**

Service-response coverage should be recorded by site alongside normalized cost, and a lower cost that removes a response path, changes a payment owner, or leaves a meter unmapped is not a saving inside the perimeter.

## Quick answers

| Why should vendor roles be separated before comparing consolidation proposals? | Commodity supplier, billing or utility-management processor, and waste or facilities contractor are different contracts, and consolidating one does not consolidate the others. |
| --- | --- |
| How should invoices be normalized when evaluating utility vendor consolidation? | Every invoice should be normalized to dollars per square foot per year by dividing the invoice totals over the specified period by the site area used for normalization, using the same time window and area basis for every site. |
| When can transition, exit, and service-risk costs be included in the cost calculation? | These costs should be kept in the same numerator only when they are supported by invoices or signed change orders. |
| Why might a lower normalized cost not represent a true saving? | A lower cost that removes a response path, changes a payment owner, or leaves a meter unmapped is not a saving inside the perimeter but an uncovered risk that must be resolved before any consolidation decision. |
| Is the stated per-square-foot savings figure a market benchmark? | No, it is a test threshold set for this decision, not a benchmark from published market data, and the consolidation case must clear it with its own invoice-verified evidence. |

### Related reading

- [Office Toilet Water Savings: 37% Cut Swap vs Sensor Retrofit](https://vuti.app/blog/office-toilet-water-savings-37-cut-swap-vs-sensor-retrofit.php)
- [Utility Reconciliation Drift: Why 2–4% Overcharges Persist](https://vuti.app/blog/utility-reconciliation-drift-why-24-overcharges-persist.php)
- [IFM Consolidation: Real Savings via Rate-Card Engine](https://vuti.app/blog/ifm-consolidation-real-savings-via-rate-card-engine.php)
- [Incident routing across sites in 2026: 12-minute auto-escalation vs vendor tiering](https://vuti.app/blog/incident-routing-across-sites-in-2026-12-minute-auto-escalation-vs-vendor-tiering.php)
- [2026 workplace EV retrofit: Level 2 load-sharing planning target vs DC expansion](https://vuti.app/blog/2026-workplace-ev-retrofit-level-2-load-sharing-planning-target-vs-dc-expansion.php)
- [2026 OpenAI security bug bounty: 4x critical rewards vs Cathedral tests](https://vuti.app/blog/2026-openai-security-bug-bounty-4x-critical-rewards-vs-cathedral-tests.php)

### Latest

- [Incident routing across sites in 2026: 12-minute auto-escalation vs vendor...](https://vuti.app/blog/incident-routing-across-sites-in-2026-12-minute-auto-escalation-vs-vendor-tiering.php)
- [2026 workplace EV retrofit: Level 2 load-sharing planning target vs DC expansion](https://vuti.app/blog/2026-workplace-ev-retrofit-level-2-load-sharing-planning-target-vs-dc-expansion.php)
- [2026 OpenAI security bug bounty: 4x critical rewards vs Cathedral tests](https://vuti.app/blog/2026-openai-security-bug-bounty-4x-critical-rewards-vs-cathedral-tests.php)

Canonical: https://vuti.app/blog/consolidating-utility-vendors-2026-120sq-ft-savings-for-5-sites.php
Markdown: https://vuti.app/blog/consolidating-utility-vendors-2026-120sq-ft-savings-for-5-sites.php/index.md