Business Models — EaaS, SaaS & Managed Services | EC.DATA

CFO reviewing financial models on dual monitors

The operations team loves your energy management solution. The sustainability director is championing it internally. But the CFO just asked the question that kills 60% of energy deals: 'Where does the capital come from?'

The best technical solution in the world fails if you can't solve the financial equation.

Tense negotiation with rejected CAPEX proposal

The standard proposal asked for $450K upfront. The CFO's response: 'We have three other capital projects competing for that budget — HVAC replacement, roof repair, and a new ERP system. Energy management ranks fourth.' Deal stalled.

70% of energy projects are delayed or cancelled due to capital budget constraints, not lack of interest.

Consultant presenting flexible contracting models to approving client

Matching the Model to the Client

The winning move: restructuring from CAPEX to a shared savings model. Zero upfront cost, payments funded entirely by verified energy savings, 70/30 split. The CFO went from 'we can't afford this' to 'we can't afford not to do this.'

7 contracting models exist: CAPEX, OPEX, CAPEX Light, SaaS, EMaaS, Shared Savings, and EaaS. Matching the right model to the client's financial reality is the unlock.

Signed contract with multi-year energy savings projection

The Lesson: Sell the Financing, Not Just the Solution

Understanding business models is as important as understanding the technology. The best energy sales professionals are part consultant, part financial architect — they match the contracting model to the client's balance sheet.

Craig Wortmann: 'You're not just selling a solution — you're selling a financial structure that makes the solution possible.'

Business model and contracting frameworks grounded in ESCO industry economics. The U.S. ESCO market reached $9.6B in 2021 with shared savings representing 60%+ of all performance contracts (LBNL/DOE, 2022). CAPEX vs. OPEX decision frameworks follow IAS 16/IFRS 16 lease classification standards. The Total Contract Value (TCV) calculation methodology is based on NAESCO guidelines for energy performance contracting. Latin American contracting preferences reflect EC.DATA partner network deployment data across 6 countries.

LBNL — U.S. ESCO Market Report, 2022 / NAESCO Contracting Guidelines / IAS 16 & IFRS 16 — Lease Classification / EC Academy 3.0

Master the financial structures behind energy management deals. From one-time purchases to performance-based contracts — learn when to use each model to maximize deal value and client satisfaction.

Contracting models landscape: from simple CAPEX purchase to full-service EMaaS

CONTRACTING MODEL SPECTRUM

↑ Zero risk to client

7 Contracting Models

Each model suits different client needs, risk appetites, and financial realities. Click any card to explore its pros, cons, and best-fit scenarios.

MODEL COMPARISON MATRIX

MODEL DECISION TREE

Which Model to Propose?

Follow this decision tree to identify the best contracting model for each client situation.

Does the client have capital budget available?

Want full ownership or managed SW?

Priority: flexibility or pay-by-results?

Multi-site operation needing full service?

Full ownership, one-time

Pay from savings only

Outcome-based contract

Total Contract Value by Industry

EMaaS and SaaS applicability varies by industry segment. Higher complexity and energy spend favor EMaaS; simpler operations favor SaaS.

Shared Savings & IPMVP

The shared savings model aligns provider and client incentives through verified energy performance. Based on the international IPMVP protocol adopted by 50+ countries.

The International Performance Measurement and Verification Protocol (IPMVP) is an international standard adopted by 50+ countries for quantifying and verifying energy savings. Developed by the Efficiency Valuation Organization (EVO), it provides clear, defined processes for measuring energy conservation results.

Efficiency Valuation Organization

IPMVP defines four measurement options (A, B, C, D) with increasing rigor. The core formula compares baseline energy consumption with reporting-period consumption, adjusted for independent variables (weather, production, occupancy).

In the ENSE shared savings model, verified energy savings are split between the service provider (70%) and the client (30%). The client receives immediate savings with zero investment.

Financial Requirements

Minimum monthly energy cost: $3,600 USD

Savings target range: 12–25% of energy consumption

Contract duration: typically 36–60 months

Typical energy savings achievable through monitoring, optimization, and ECM implementation

Shared Savings Engagement Process

Break-Even Benchmarks by Industry

Energy cost as a percentage of revenue that indicates project viability. Lower percentages mean higher potential for shared savings contracts.

Energy Cost / Revenue

Industry / Manufacturing

Market Segmentation Quadrant

Map client opportunities by complexity and contract value to identify the best contracting model for each segment.

HIGH VALUE / LOW COMPLEXITY

HIGH VALUE / HIGH COMPLEXITY

LOW VALUE / LOW COMPLEXITY

LOW VALUE / HIGH COMPLEXITY

EMaaS Engagement — Key Decision Makers

Maintenance / Facilities

Test Your Knowledge

Apply what you've learned about contracting models, shared savings, and market segmentation.

EC.DATA Powers Every Model

Whether you sell EMaaS, shared savings, or fixed-fee monitoring — EC.DATA is the engine that delivers the service behind each business model.

EC.DATA calculates verified savings, generates monthly billing reports, and tracks contract performance — automating the financial backbone of every EMaaS deal.

Track revenue, margins, and contract health across your entire portfolio from a single dashboard — whether you manage 5 sites or 500.

Build client proposals with real baseline data, projected savings, and payback timelines pulled directly from EC.DATA's analytics engine.

Negotiation Tips by Model

Shared Savings Mastery

Energy Business Models

Understanding the business model options for selling energy management solutions.

Model Comparison

• SaaS license — monthly/annual subscription per meter point or building
• Energy-as-a-Service (EaaS) — bundled hardware + software + services, pay per kWh saved
• Managed services — outsourced energy management with performance guarantees
• Performance contracting — savings-based compensation verified through M&V
• Channel partner model — white-label platform resale with recurring revenue share

Business Models in practice

EC.DATA partners run software-licence, EaaS (Energy-as-a-Service), and shared-savings models. EC.Bills and EC.GAIA together compute the model's economics so the partner picks the structure that matches the customer's cash-flow appetite.

How EC.DATA operationalises Business Models

Business Models is taught inside EC.Academy with concrete artefacts the partner uses in real sales motions — discovery scripts, deck templates, ROI worksheets — all backed by data EC.DATA can produce. EC.Bills generates the savings model; EC.GAIA generates the verification narrative.

Partners running structured sales motions on EC.DATA close roughly 2× faster than partners running ad-hoc demos, primarily because the EC.Solution Design Studio output and the EC.Bills baseline let prospects validate economics inside the first 30 days.

Common pitfalls when working with Business Models

Business Models sales motions stall when partners skip qualification or rush to demo.

• Selling features instead of dollars-saved is the most common reason a strong technical demo loses.
• Skipping the audit pass guarantees a vague proposal that loses to a competitor with concrete numbers.
• Failing to identify the financial sponsor early surfaces budget objections at the worst possible moment.
• Promising savings without an IPMVP-grade plan creates verification disputes after deployment.

Where Business Models connects across EC.DATA

Business Models touches every layer of the EC.DATA stack: telemetry capture in EC.Node; visualisation and alerting in EC.EMS with EC.Alerts; tariff translation in EC.Bills; savings verification in EC.GAIA; and field-device fleet governance in EC.IoT. Solution work originates in EC.Solution Design Studio; partner and customer training live in EC.Academy.

Frequently asked questions about Business Models

How does EC.DATA expose Business Models to partners?

Business Models is supported by ready-to-use templates in EC.Academy and proof artefacts EC.Bills and EC.GAIA generate from real customer data.

Do I need a separate license to access Business Models?

No. Business Models is part of the core EC.DATA platform; partners get it as part of their standard licence and white-label it under their own brand for their customers.

Where do I learn more about Business Models on EC.DATA?

Start with the EC.Academy track this page belongs to, then explore the related EC.DATA platform modules linked above. The EC.DATA changelog announces new capabilities and the EC.Academy session catalogue tracks every recorded session.

How EC.DATA applies this in production

The concepts in this lesson are not theoretical — they are operationalised every day inside the EC.DATA platform across deployments in 10+ countries on 3 continents. The module most directly tied to this track is the EC.DATA platform, working alongside our value proposition and partner programme to translate the underlying physics, protocols, and methodology into a working production system.

Every reading in EC.DATA flows through the same lifecycle: telemetry is captured at the meter or sensor, normalised by the EC.Node edge gateway (which speaks Modbus RTU/TCP, BACnet, OPC-UA, MQTT and pulse counting natively), buffered locally for offline resilience, then delivered to the cloud where EC.EMS stores it as 1-minute resolution time-series. From there, EC.Bills reconciles metered kWh against the utility invoice, EC.Billing allocates consumption to tenants or cost centres, EC.Alerts watches for anomalies, EC.PQ scrutinises waveform quality, and EC.GAIA applies machine learning for forecasting and root-cause analysis.

That integration is what differentiates EC.DATA from the patchwork of disconnected tools most facilities run today. Because every module shares the same data warehouse and the same role-based permission layer, a finding in one module is immediately actionable in another — a tariff change in EC.Bills can adjust demand-alert thresholds in EC.Alerts, a setpoint override in EC.BMS is automatically measured for energy impact in EC.EMS, and an IPMVP baseline is established once and reused across reports forever.

The team behind EC.DATA — described in more depth on the Who We Are page — combines former Fortune 500 energy consultants, field commissioning engineers, and software developers, with a deliberate hiring policy that requires every senior product role to have prior experience on the customer side of an energy programme. The platform is what we wish had existed when we ran those programmes ourselves; the academy is the public-domain version of the training material we built internally to bring new hires up to speed.

If you want to see the platform in action, the free assessment, the savings calculator, and the Solution Design Studio are open without an account; the partner programme is the route in for ESCOs, facility-management firms, commissioning agents, and utilities that want to deliver EC.DATA under their own brand.