Procurement and finance leaders running multi-site operations need a straightforward playbook for b2b energy procurement that cuts utility spend and makes budgets predictable. Readable, actionable steps cover contract structure and hedging, aggregation and supplier consolidation, and operational levers like demand response and targeted storage—backed by interval data and simple analytics. You will get an implementation roadmap, RFP checklist, and KPIs that procurement and finance can start using in 30 to 90 days.
1. Map the Current State: Bill Anatomy, Data Sources, and Baseline
Start with the bill, not the vendor pitch. For effective b2b energy procurement you must separate what you buy (commodity kWh) from what you are billed for (demand, transmission, capacity, riders, taxes). Buyers who treat all spend as a per kWh problem miss the largest levers for savings and predictability.
Bill anatomy at procurement-relevant granularity
Key point: Commodity often looks obvious, but noncommodity items frequently drive cost and volatility. Map each tariff line to a procurement lever: can it be hedged, deferred, avoided with operations, or negotiated away through aggregation?
| Bill Component | Typical contribution (range) | Procurement or operational lever |
|---|---|---|
| Commodity (energy kWh) | 20% – 60% | Fixed contracts, index deals, hedges |
| Demand / peak charges | 10% – 50% | Load control, storage, tariff reclassification |
| Transmission & capacity | 5% – 25% | Contract assignment, location aggregation, regulatory review |
| Riders, line items, taxes | 0% – 20% | Tariff review, contestability, supplier billing audits |
Data sources and practical collection
Collect these first: 12 months of monthly bills, interval meter CSVs or EDI feeds, tariff sheets for each utility account, historical outage logs, and meter-to-site mappings. Without interval data you are guessing at peak drivers and demand exposure.
- Quick pulls: download bills from utility portals and request EDI/CSV exports where available
- Interval tools: ingest into EnergyCAP or EnergyPrint for normalization and baseline analytics
- Regulatory artifacts: keep tariff and rider notices to capture upcoming rate changes
Tradeoff to plan for: interval data is necessary but not free. Expect 30 to 90 days of utility engagement and occasional vendor fees to normalize feeds. If procurement skips this step to save time, they will overpay on demand-driven sites and misjudge hedging needs.
Normalize, baseline, and KPIs
Normalization matters. Use ENERGY STAR Portfolio Manager and regional price indices from EIA to convert raw usage into comparable metrics like $ per kWh and $ per peak kW by site. That makes aggregation decisions defensible to finance.
Concrete Example: A midwest logistics portfolio pulled interval data and found one 300k sq ft distribution center had demand charges accounting for roughly 38 percent of its monthly bill. Targeted compressor scheduling and a short-duration battery pilot reduced its peak by 22 percent in three months, materially lowering the site level budget variance used in corporate forecasts.
- Gather 12 months of bills and request interval CSVs or EDI feeds for all accounts
- Collect tariff sheets and recent utility notices for each account
- Load interval data into an analytics tool or a clean
Power BI/Excel model - Produce the one-page baseline KPI dashboard and rank sites by budget risk
Takeaway: If procurement and finance start here, decisions on fixed contracts, hedges, aggregation, or onsite projects are evidence based. Skipping interval normalization is the single largest practical mistake I see; it turns supplier pitches into noise and loses leverage in negotiations. Next consideration: decide whether you have internal bandwidth to do the 90 day work or need a managed services partner to collect feeds and produce the baseline.
Frequently Asked Questions
Direct answers, not theory. Below are practical responses procurement and finance teams actually use when they take action on b2b energy procurement—each answer includes the operational trade-offs you need to decide on.
Hedging and volatility: how much will it help?
Short answer: hedging reduces invoice swings but introduces liquidity and governance demands. Hedging buys predictability at the cost of flexibility and potential margin if market prices drop. Implement only after defining allowed instruments, hedge ratios, and collateral triggers.
Practical insight: most mid-market programs are simpler and more effective when limited to a single instrument class (for example collars or swaps) and a fixed coverage band for a defined portion of load. That simplicity reduces accounting headaches and makes monthly variance reports meaningful for treasury.
When to pick a long term PPA vs a fixed retail contract
Guideline: choose a long-term PPA only when you need multi-year price visibility and can support the contract size or use a sleeved/virtual structure that matches your load profile. For many multi-site buyers, shorter fixed retail contracts combined with targeted renewables purchases give a better balance of liquidity and budget certainty.
Trade-off to consider: PPAs lock you into basis and shape risk; they can materially help sustainability targets but often require more complex accounting and credit arrangements than retail contracts.
Fastest way to cut bills where demand charges dominate
Tactical answer: targeted load shifting and short-duration battery dispatch typically give the fastest ROI for demand-sensitive sites. Focus on operational changes first—compressor and HVAC sequencing—then add storage where control limits are hit or where programs provide additional revenue.
Concrete Example: A regional manufacturer with about $1.2M annual electricity spend implemented a collar on 50 percent of its expected load and ran a three-month battery pilot at its largest plant. The collar reduced monthly budget swings significantly while the battery pilot dropped the site peak by enough to lower its demand charges in two billing cycles; the main operational hurdle was meeting the collateral call schedule during a market stress event.
Aggregating sites and running an enterprise RFP
Practical advice: aggregation works when you can standardize tariff classes, invoice timing, and credit treatment. If sites are heterogeneous, consider grouping by similarity rather than geography. Using a single enterprise RFP often yields better commercial terms and reduces administrative burden.
What usually goes wrong: procurement teams run RFPs without normalized interval profiles. That invites bids that look low on price per kWh but fail at addressing demand charges and settlement mechanics.
Demand response and production conflicts
Reality check: well-designed programs include advance notice, opt-out windows, and performance measurement that align with production cycles. Always pilot enrollment with operations and document acceptable curtailment thresholds before you sign.
Where should a procurement team start with limited energy expertise?
Start small and produce a deliverable. Run a 60 to 90 day audit to collect bills and interval data, produce a ranked site risk list, and execute one narrow pilot (commodity RFP for a subset or a demand response trial). If internal bandwidth is tight, bring in a specialist to collect EDI feeds and build the baseline in an analytics tool such as EnergyCAP.
