Skip to main content
Stedin EmPower website with signup flow for an energy pilot – Website
Case study

Stedin EmPower website with signup flow for an energy pilot

Website FreshConnected Studio In development

Website for EmPower, a pilot by Stedin and EemnesEnergie with a grid tariff that moves with how busy the power grid is, with explanation, FAQ, and a signup wizard with an address check that passes signups on to the EmPower app.

What is currently being built

The focus here is on product direction, the chosen foundation, and the parts currently being developed toward a first solid release.

Project overview

EmPower is a pilot by grid operator Stedin and energy cooperative EemnesEnergie. In two neighbourhoods of Eemnes, they are testing a grid tariff that moves with how busy the power grid is. Participants receive a smart device on loan that runs appliances at the moments electricity is cheap. Taking part is free, and participants keep their own energy supplier.

The website is the front door of that pilot. Residents read how it works, find answers to their questions, and sign up. Anyone living outside the pilot neighbourhoods can join a waiting list. Everything after signup runs through the EmPower app.

Collaboration

Stedin supplied the substance: a copy deck for every page, the brand portal, and the list of participating addresses. FreshConnected turned that into a website on FreshConnected Studio and built the signup flow and the connection with the app. Where the copy deck or brand portal did not yet have an answer, the open questions were bundled and put to Stedin instead of being filled in by us.

The problem behind the project

A pilot with a dynamic grid tariff requires trust. Residents want to know what it costs, what goes into their meter cupboard, and what happens to their data before they sign up. At the same time, signup cannot be open to everyone: only addresses in the pilot neighbourhoods can take part.

So the website had to explain clearly, check eligibility at address level, and let personal data land in one place instead of spread across website and app.

What is being delivered

  • Five pages: home, how it works, FAQ, sign up, and waiting list
  • A step-by-step signup wizard with an address check on postcode and house number
  • A waiting list for residents outside the pilot neighbourhoods, including their address, so it becomes visible which neighbourhoods fall outside most often
  • A connection that writes signups and the waiting list once to the EmPower app’s database
  • A visual style following Stedin’s brand portal

Technical implementation

  • Built on FreshConnected Studio: Astro as a static site, Kirby CMS as the management environment
  • The address check works at house number level, derived from the supplied address list, and is managed in the CMS
  • Signups and the waiting list go to Supabase through restricted functions; the website writes once, everything after that belongs to the app
  • Colours from the brand portal, with contrast choices where the brand colours are too light as text on white
  • Cookieless analytics via Plausible, without a cookie banner

Challenges

  • Turning an address list with inconsistent suffixes into a check that never wrongly rejects anyone
  • Not storing personal data twice: the website delivers, the app manages
  • Applying brand colours that lack contrast on white, without letting go of the brand portal
  • Moving the website onto the main domain while the EmPower app still runs there today

Result

The website and signup flow are built and are being checked in a protected test environment. Launch follows once the app has moved to its own subdomain and Stedin has settled the last content points. The foundation is in place: a clear explanation, a signup that only admits the right addresses, and a clean separation between website and app.

Reflection

EmPower shows that a Studio website can be more than a presentation. With a signup wizard, an address check, and a connection to an existing app, the site becomes a full part of a pilot, while the content stays manageable in the CMS.

Inspired by this project?

If you see similar friction or growth potential in your own business, we can translate this into a practical roadmap for you.

Other projects