Mercury for flexibility providers

Grow your device fleet without growing your integration backlog.

‍

Your platform sits between the device fleet and the grid services market, and every OEM you add is bespoke work. The cost scales linearly with brand count, so for a platform aggregating fifteen or more device categories, integration becomes the dominant engineering activity. The business needs OEMs added faster than engineering can integrate them, and the gap widens each quarter.

Mercury converts per-OEM integration to per-standard. A certified device comes with predictable integration, so onboarding a new OEM partnership moves from weeks or months to days or weeks, and adding the eleventh certified brand costs roughly what the first did.

Design programmes for the class, not the manufacturer

Integration is only half the pain. Devices that are technically integrated still behave inconsistently: response latency varies, fail-safe behaviour differs, telemetry granularity differs, and every difference becomes a special case in your flex programme. Mercury's class structure defines what consistent behaviour means. Class A is 1 second response with 1 second telemetry. Class B is 15 seconds with 2 second telemetry. Class C is 120 seconds with 30 second telemetry. A certified Class B device behaves like every other certified Class B device, whoever made it, so programmes are designed once per class rather than once per OEM.

The classes also map directly to the markets you sell into: Class A to the fastest frequency products, Class B to triggered reserves, Class C to distribution-level flexibility. That is a market-coverage story you can put in front of a utility customer.

Your product stays yours

The standard is the integration layer. Your differentiation lives in programme design, control algorithms, user experience and utility relationships, none of which Mercury touches. What membership does add is the procurement answer: utilities increasingly filter flex providers by standards support, and Mercury membership is a credible response before the RFP conversation even starts.

The maths is short

A provider under $100 million in revenue pays $10,000 as a Full Member or $5,000 as an Observer. If you integrate two or three new OEMs a year at meaningful engineering cost each, breakeven typically lands in year one. Certification can be sequenced over your normal release cadence, and the Class Alpha bridge gives existing implementations a 12 month window.

Join Mercury. Certify your platform. Build the resilient energy future.

‍