The simplicity gap: why getting your customer portal UX right is the right retention strategy

Advisory · Energy Operations

When energy suppliers think about customer portals, they tend to think about features. Can it handle long-term trading? Does it support day-ahead and intraday? Can customers set limit orders, manage baskets, see their weighted average position?

These are the right questions. But they are not the only questions. Underneath the feature conversation is a more fundamental one that gets far less attention: who, exactly, is the customer using this portal, and is the interface built for them?

Get that wrong, and the features do not matter. A portal that is too complex for its audience will not be used. And a portal that is not used is a commercial liability, not an asset.

Not all energy customers are energy professionals

There is a category of customer that sits in an uncomfortable middle ground for most energy suppliers. They are not large industrials with in-house trading desks and dedicated risk managers. They are not household consumers who just want a bill. They are businesses, often mid-market, who consume or produce meaningful volumes of energy, who are aware that prices move, and who want some level of control over their exposure, but who are not, and do not want to become, energy wizards.

This customer is increasingly common. More businesses are asking to see their position. More are asking to be able to click rather than just call. They want to understand where they are hedged, what is still open, and when their current prices expire. They want to do something about it if the price looks right. But they do not want to learn a new profession to do so.

The challenge for suppliers is that the platforms most commonly in use were not designed for this audience. They were designed for sophisticated buyers who understand 30-minute settlement calculations and want to see every variable. For that audience, the complexity is a feature. For the mid-market customer who just wants a simple chart showing open versus closed position, the same complexity is a barrier.

The consequence is predictable. The platform gets deployed. The customer logs in once, finds it overwhelming, and goes back to calling the account manager. The supplier has paid for software that its customers will not adopt. The self-service value never materialises. 

Simplicity is not the same as capability

The answer is not to strip out functionality. It is to separate the interface from the engine.

A customer who wants to see their position, trade against a price, set a notification if the market moves, and understand what their weighted average cost looks like at the end of the period does not need access to the full architecture of a professional trading platform. They need a clean front end that surfaces the relevant information at the right moment and makes the action obvious.

The engine behind it can be just as powerful. Prices are still published from the supplier side, with full margin control. Trades still route to the supplier for acceptance or rejection. Positions still update in real time. The difference is that the customer sees a dashboard showing their open percentage for the year, a list of available products with current prices, and a simple two-step checkout. Not a matrix of settlement calculations.

Some customers will grow into greater sophistication and want more. The right approach is to design for a spectrum, where simpler and more complex interfaces sit on the same underlying platform, and a customer can be placed on the right one for their current needs. A customer who starts on the simpler view and grows into more active hedging can be moved up. One who only ever needs the basics stays where they are comfortable and keeps using the product.

Platform familiarity is a retention lever

Here is where the commercial logic becomes particularly clear, and it is a point that does not get enough attention in conversations about energy software.

Customers who know a portal follow it when they move supplier.

This is not a hypothesis. It is a pattern that plays out repeatedly in the UK and European markets. When a consultant or broker is managing energy on behalf of a portfolio of customers, and the supplier they have been using runs a platform their customers know and trust, the barrier to switching those customers to a different supplier is meaningfully lower, because the customer experience does not change. The customer logs into the same interface. The pricing process works the same way. The position view looks the same.

The inverse is also true. If a supplier switches to a platform that requires its customers to learn something new, adoption is slower, support calls go up, and some customers decide the disruption is not worth it. This is not a theoretical risk. Suppliers who have tried to migrate customers to unfamiliar systems report exactly this friction. The cost of retraining thousands of customers, many of whom are not energy professionals, is rarely factored into a software procurement decision. It should be.

Platform familiarity compounds over time. A customer who has used a portal for two or three years, who knows where to find their invoices and their position and their price history, has a high threshold for switching away. That familiarity is an asset for the supplier who built it, and a liability for any competitor trying to displace them.

What this means in practice

For suppliers evaluating or building customer-facing portal capability, the strategic question is not just what the platform can do. It is: does the interface match the sophistication of the customers who will actually use it, and is the design choice being made deliberately rather than by default?

A supplier that puts every customer on a complex professional interface, regardless of whether they need it, is leaving adoption on the table. One that makes the conscious choice to offer a simpler front end for the right segment, backed by the same underlying capability, gets higher usage, lower support overhead, and a stickier customer relationship.

Simplicity, in this context, is not a compromise. It is a commercial strategy.

Explore how Eneve works here.