Skip navigation

Ecopower

A website that evolved from information channel to digital energy platform

Client
Ecopower

Services
Strategy, UX, front-end development, platform extension, ERP integrations, support

Sector
Energy / cooperative / civil society organisation

Timeline
Since 2015, in several phases

Region
Antwerp: websites in Antwerp

Status
Ongoing partnership

Tech stack
Nimbu, custom cloud code, CoffeeScript/JavaScript, SAP, Haugazel, Odoo

At a glance

Challenge

Ecopower grew from a small non-profit into an established name in the energy market. The website had to grow along. What started as a commercial site with forms became, step by step, a place where customers register, sign contracts, make payments, manage their details and connect to the systems behind the scenes.

Solution

We did not build “a new website” once. We helped build out a digital landscape that could grow over several years: with online payments, digital contracts, a reworked website, a customer zone, price simulation, e-commerce and integrations with SAP, Haugazel and later Odoo.

Result

Today Ecopower.be is much more than an informational website. It is a working platform that brings together commercial intake, customer interaction and operational processes, while leaving room for continuous improvement.

Challenge

Some organisations outgrow their website. Ecopower is a good example.

When we started working together, a conventional website was still largely enough. The focus was on information, forms and a clear way for people to become cooperative members or customers. But Ecopower was changing quickly. The organisation became more professional, its offering expanded and customers expected more from its digital services.

Ecopower also operates in a market that rarely stands still. The energy market changes constantly. Regulations change. Products evolve. Internal processes adapt to decisions about markets and systems. The website could no longer remain a static communication channel.

The challenge was to build a digital platform that could grow year after year with an organisation in motion.

This called for more than development. Ecopower needed a partner who knew the organisation, could respond technically and could help think through changes in context. That support mattered between major releases as much as during them.

A platform developed over time

This story covers a series of focused steps across several years.

The first version of the Ecopower website was built in 2015 and 2016. Online payments and digital contract processes followed in 2017. In 2019, we thoroughly reworked the website with an external design partner as part of a broader repositioning of the platform. In 2020 and 2021, we built integrations with SAP and Haugazel in several phases. In late 2025 and early 2026, the underlying systems changed again, this time with a move to Odoo.

That pace says a lot about the partnership: together, we built a digital environment that could handle change without having to start from scratch each time.

From forms to complete user journeys

Much of the evolution involved moving from separate contact and request forms to complete digital processes.

The first version focused heavily on information and enquiries. Later, the platform expanded to include online payments, contract processes, a webshop and a customer zone. Users can log in, manage their details, consult contract information, view invoices and complete operational processes step by step.

On paper, that sounds like a straightforward extension. In practice, it changes the nature of the website completely. Building pages becomes building processes, with validation, exceptions, statuses, integrations and consequences in the systems behind them.

For Ecopower, this mattered. The website had to remain useful for attracting new customers while becoming a reliable part of day-to-day operations and fitting the way the organisation works internally.

Integrations as the backbone

The complexity was not only in what visitors see, but above all in what has to be right behind the scenes.

In several phases we connected Ecopower.be to external systems such as SAP and Haugazel, and later to Odoo. That linked the website to contract management, customer data, shareholder information, invoicing, price simulations and other operational processes.

That kind of work demands a different way of thinking than classic websites. You have to account for data that is not always clean or complete, for processes that have grown historically, and for systems that each impose their own logic. Certainly in a regulated, fast-moving market, you do not want to lay a fragile layer on top of that.

So we chose an approach where the public website, the customer zone and the integration layer could evolve together. Not perfect in one go, but sturdy enough to absorb new phases.

A partner to think things through as circumstances change

Beyond the technology, Ecopower needed a partner who could help think through decisions when circumstances changed.

A project like this keeps raising new questions. How much of a contract process should be digital? What belongs on the website and what belongs in the ERP? What happens when regulations change, products shift or a migration to a new system comes up? How do you make sure a small improvement today does not become an obstacle in six months?

This is where a long-term partnership makes a difference. Knowing the sector and the history helped us respond quickly, both in delivery and in discussing the options. Those conversations covered technical feasibility, timing, risks and which step made sense at that point.

Ongoing support as part of the product

For a collaboration like this, ongoing support is a crucial component. We keep a short line in which we set priorities together and continuously adjust small things.

Today there are still improvements running on UX, analytics, consent, content structure, support flows and integrations. That may seem less spectacular than a big relaunch, but that is often where the real value sits.




A platform stays relevant because it is maintained, adjusted and sharpened.

For Ecopower that meant the digital environment could keep growing with the organisation, instead of falling behind every few years and having to be caught up again.

Result

Ecopower.be has grown beyond a conventional corporate website.

The platform brings communication, customer acquisition and operations together. Visitors find information about the cooperative, energy products and projects. They can also become customers, pay online, manage contract information, log in to MijnEcopower and calculate prices, while the site exchanges data with the systems behind it.

A broader set of digital services has also grown around the main website, with distinct needs for private customers, businesses and local authorities. That makes this an interesting case for us: it shows how a website gradually becomes a platform while still needing to stay clear and easy to use.

What that delivers in practice:

A scalable digital environment

A digital environment that could grow from simple forms to fully fledged user flows

Support for many audiences

Support for multiple audiences and contexts, from public information to a customer zone and specialised journeys

Full-service partner

One partner guarding both the public story and the technical back end

Flexible platform integration

A platform that has absorbed several system switches and integration phases

Continuous optimisation

Room for continuous optimisation, instead of repeated big restarts

From marketing to operations

A website that makes the shift from commercial intake to operational workings

For us, the main win is that combination of robustness and agility. Ecopower did not have to choose between stability and change. The website could carry both.

What happened next

This story did not stop after a first release, or even after a first rework.

After building out online payments, digital contracts and the broader rework came integration projects with SAP and Haugazel. Then another big shift followed with the transition to Odoo in late 2025 and early 2026. Meanwhile the support track simply continues, with smaller improvements, new needs and technical adjustments where necessary.

That may be the best summary of this collaboration: the website did not stand still next to the organisation. It grew along with it.

Other case studies

More case studies
RREUSE

2,000+ organisations, one manageable network

Partner data was spread across different structures and sources. We built a platform to keep locations, members and updates manageable.

Read the case
Abesco

From an inflexible website to digital services that can grow

A new website with manageable content types and automation that reduces manual work when handling enquiries.

Read the case
BelSECT

From association website to membership and symposium platform

Members, sponsors and volunteers work in one place, with memberships, symposium registration and online payments.

Read the case

Is your website growing beyond a marketing channel?

Forms, customer zones, e-commerce and integrations come together. We help you find an approach that works technically and stays manageable over time.

Book a conversation

You’ll speak directly with someone who can help you think through your project.

Not ready for a conversation? Explore our work