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
Status
Ongoing partnership
Tech stack
Nimbu, custom cloud code, CoffeeScript/JavaScript, SAP, Haugazel, Odoo
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.
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.
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.
Some organisations outgrow their website. Ecopower is a good example.
When our collaboration began, a classic website was still largely enough. The emphasis was on information, forms and a clear intake for people who wanted to become a cooperant or customer. But Ecopower changed fast. The organisation professionalised, the offering expanded and customers' digital expectations rose with it.
On top of that, Ecopower operates in a context that rarely stands still. The energy market changes constantly. Regulation shifts. Products evolve. Internal processes move along with market and system choices. Which means the website cannot remain a static communication channel either.
So the challenge was: how do we build a digital platform that can grow year after year with an organisation in motion?
This is about more than development alone. Ecopower was looking for a partner who knew the organisation, could switch gears technically, and could think along whenever the context changed. Not only at big releases, but in the space between them too.
This story is not about a single launch. It is about a series of deliberate steps.
The first version of the Ecopower website took shape in 2015 and 2016. In 2017, online payments and digital contract flows were added. In 2019 came a thorough rework of the website, together with an external design partner and a broader repositioning of the platform. In 2020 and 2021 we built out integrations with SAP and Haugazel, in several phases. Late 2025 and early 2026 that foundation shifted again, this time towards Odoo.
That rhythm says a lot about the collaboration: together we built a digital environment that could absorb change without starting from scratch every time.
A large part of the evolution was the shift from loose contact and request forms to real digital processes.
Where the first version still revolved around information and intake, the platform later grew with online payments, contract flows, webshop functionality and a customer zone. There, users can not only sign up, but also manage their details, consult contract information, view invoices and move through operational flows step by step.
On paper that looks like a logical extension. In practice it completely changes the nature of the website. From that moment on you are no longer just building pages. You are building processes with validation, exceptions, statuses, integrations and consequences in the systems behind them.
For Ecopower that was crucial. The website had to remain usable for new intake, while also becoming a reliable extension of daily operations and connecting to their internal way of working.
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.
Perhaps even more important than the technology: Ecopower needed a partner who could reason along when the context shifted.
In a journey like this you constantly run into new questions. How far do you digitalise a contract flow? What should happen on the website and what belongs in the ERP? What do you do when regulation changes, products shift or a migration to a new system lands on the table? How do you make sure small improvements today do not become a millstone within six months?
That is exactly where a long-term collaboration makes the difference. Because we knew the domain and the history, we could switch quickly. Not only in execution, but as a sparring partner too. That covered technical feasibility, but just as much timing, risks and the question of which step was the right one at that moment.
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.
Ecopower.be is no longer a classic corporate website.
The platform combines communication, intake and operations in one whole. Visitors find information about the cooperative, energy products and projects. At the same time, concrete processes run through the site: becoming a customer, paying online, managing contract information, logging in to MijnEcopower, running price calculations and exchanging data with the systems behind it.
And it does not stop there. Around the main website a broader digital ecosystem grew, with separate needs for private customers, businesses and local governments. That is exactly what makes this an interesting case for us: you see very concretely how a website slowly shifts towards a platform, without the front losing its clarity.
A digital environment that could grow from simple forms to fully fledged user flows
Support for multiple audiences and contexts, from public information to a customer zone and specialised journeys
One partner guarding both the public story and the technical back end
A platform that has absorbed several system switches and integration phases
Room for continuous optimisation, instead of repeated big restarts
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.
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.
