Sales Plays — Scenario-Based Energy Solution Selling | EC.DATA

Sales Plays — Scenario-Based Selling

Pre-built sales approaches for common energy management scenarios.

Sales Play Scenarios

• New construction — design-phase integration, specify EC.DATA in MEP scope
• Retrofit — bolt-on monitoring to existing electrical infrastructure
• Multi-site rollout — phased deployment across a portfolio, pilot-then-scale
• Compliance-driven — F-Gas, ISO 50001, or ESG disclosure as the buying trigger
• Cost reduction — utility bill reduction as primary ROI driver
• Equipment protection — power quality and predictive maintenance as risk reduction

Sales Plays in practice

A sales play is a packaged motion: target list, discovery questions, proof points, pricing, and the EC.DATA modules to demo. The EC.Academy plays cover refrigeration leak detection, HVAC right-sizing, demand-response readiness, and Scope 2 reporting.

How EC.DATA operationalises Sales Plays

Sales Plays 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 Sales Plays

Sales Plays 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 Sales Plays connects across EC.DATA

Sales Plays 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 Sales Plays

How does EC.DATA expose Sales Plays to partners?

Sales Plays 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 Sales Plays?

No. Sales Plays 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 Sales Plays 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.