The market reality

Energy communities are growing fast. Most suppliers can't serve them.

Energy communities (cooperatives, housing-association collectives, VvE schemes, industrial-park clusters) are a structurally growing segment, accelerated by the end of the netting rule in January 2027. Each one needs a licensed supplier as its market interface.

The gap is operational capability. Standard retail ERP systems are built for one-to-one relationships, not the hierarchical, allocation-based, collectively-billed B2B2C model communities require. The result is a structural revenue leak.

The challenge

What's standing between suppliers and community revenue

For most suppliers, the demand is already arriving; the platform is what turns it away.

Willing suppliers, incapable platforms

Inbound requests from cooperatives and housing associations get turned down because the operational engine can't handle B2B2C billing, allocation, and member-level invoicing.

Communities can't find a capable supplier

Cooperatives and housing associations spend months looking for an energy partner. The first willing supplier wins the relationship and tends to keep it, because switching costs are high once live.

Rooftop solar sits underused

Housing associations with large rooftop portfolios can't share generation across tenants, because there's no operational partner to run the B2B2C engine. The asset is there; the back-office isn't.

Who this is for

BUILT FOR MODERN SUPPLIERS, AND COMMUNITIES THEY SERVE

Licensed energy suppliers

Small-to-mid players in the scale stage, already declining inbound requests from communities in the Netherlands and EU.

Housing associations

with a solar rooftop. Large portfolios looking for a B2B2C operational partner, or considering their own supply licence.

Cooperatives

of 200 to 500 members, on a reluctant mainstream supplier, looking for an actively enabling partner instead.

Heads of compliance, and operations

responsible for ACM obligations and SCE structuring, and for the billing complexity and back-office scalability that come with it.

CCOs and commercial directors

of the community business being declined, quarter after quarter; and carrying the revenue impact.

CTOs and heads of platform on

accountable for ERP extension scope, technical feasibility and whether the build is workable.

The solution

THE PLATFORM LAYER

A parent B2B contract with the community entity and individual B2C contracts with each member, linked but separately billed. The data model handles the relationship structure standard retail ERPs can't.

Pro-rata or rule-based distribution of community-generated energy across member connections, with rebate calculation built in. Handles both physical (behind-the-meter) and virtual (postcoderoos) community structures from day one.

Split billing between the community and the grid, with correct VAT treatment per actor type. Members see their personal statement; the community administrator sees the collective view.

Netting, feed-in, and virtual net metering per member, designed for the moment a member becomes a producer as well as a consumer.

Self-service for the community administrator, not just your back office. It reduces the load on your team while empowering the community to manage member-level changes.

ACM, CertiQ, E-MAID, and EAN management for community assets, built so the reporting layer is solved rather than bolted on.

Why this beats the alternative

01

ROI you can defend

Module fees are a fraction of the annual margin a supplier gains per community served
Straightforward to model and defend internally

02

An extension, not a rebuild

Sits on your existing ERP data model, so you don't replace your stack, you extend it
That same foundation carries cross-market depth across NL, BE, DE, FR, and ES, so the solution scales across jurisdictions as your footprint grows

03

Integral and built to last

Addresses the technical and commercial layers at once, unlike platform-only vendors who leave the structuring to you or consultancies who never ship the platform
Once live communities are on the platform, switching cost is high and churn is low, so the relationship deepens with every member added

How it works

Supplier readiness assessment

A four to six week diagnostic of your platform, operations, and regulatory status, ending with a clear gap analysis and a recommendation on what needs to ship in parallel with activation.

Market entry programme

A twelve to sixteen week go-to-market and operational setup, covering platform activation, proposition design, regulatory structuring, and commercial model. Ends with your first communities live.

Platform activation per community

Onboarding plus an ongoing per-community service. Activations typically take two to four weeks once your platform is ready.

Ongoing advisory

An optional retainer covering regulatory monitoring, new community onboarding support, and commercial model refinement as your footprint grows.

FREQUENTLY ASKED QUESTIONS

It's built as an extension on top of your existing ERP data model, not a replacement platform. If you already run on our platform, activation is fastest. If you run on a different one, the readiness assessment maps the integration work, and in most cases the module can sit alongside your existing core with clear data handoffs.

The Netherlands is the primary market today, with deep regulatory depth around postcoderoos and SCE. The same logic scales to Belgium, Germany, France, and Spain. Cross-border community structures are rare but possible, and the proposition adapts per market on the regulatory layer.

If you're an existing platform client and your readiness assessment is clean, first communities can be live within 8 to 12 weeks. New-platform customers typically need 16 to 20 weeks, because the readiness work and core integration come first. We're upfront on the timeline at the readiness stage.

That's part of what the consultancy layer addresses. We help you design the contract structure, the pricing and margin allocation between supplier and community, and the customer interaction model. Each community has its own commercial structure within a consistent operational framework.

All built into the platform extension. ACM obligations, CertiQ reporting, EAN management for community assets, and postcoderoos rebate calculation are handled as part of the standard module. New regulatory shifts, like the end of netting in 2027, are tracked and updated as part of the service.

Most early customers are mid-sized licensed suppliers serving 10,000 to 200,000 connections. The economics work as soon as you have inbound community demand you're declining. Even one or two communities per year typically justifies activation.

Turn community demand into recurring revenue