Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire Product Manager for Energy Companies
Senior, direct, no layers

Hire a Product Manager for Energy Companies: For energy companies, the product question is rarely whether to build. It is what to build first, for whom, and what to stop building. Billing accuracy is trust: one wrong bill or one mishandled meter read creates a complaint that costs more to fix than the bill was worth.

Energy Companies — Product Manager

A senior product manager for energy companies

For energy companies, the product question is rarely whether to build. It is what to build first, for whom, and what to stop building. Billing accuracy is trust: one wrong bill or one mishandled meter read creates a complaint that costs more to fix than the bill was worth.

The work is discovery first, roadmap second, build third. Price-cap changes and winter demand set the calendar, and every tariff change touches billing, support and communications at once. Skipping the first two is how products end up full of features nobody uses.

You get a single owner for product decisions: discovery, roadmap and launch for tariff plans and the rest of the range, judged on usage and retention rather than output. Book a free discovery call to talk through the product call you are stuck on right now.

What you get

What this engagement covers for energy companies

  • Discovery for tariff plans — conversations with real users, support themes and usage patterns, turned into problems worth solving rather than feature requests to copy.
  • Prioritised roadmap for a customer app — themes ordered by evidence, with the trade-offs stated so the team stops relitigating priorities every week.
  • Specs the team can build from for a green energy bundle — the problem, the user, the acceptance criteria, and what success looks like, written before build starts.
  • Launch plan for a business energy offer — who hears about it, what changes for existing users, and how the first weeks are measured.
  • Metrics that mean something for tariff design and billing runs — activation, retention and the one number that shows whether the product is actually working for users.
  • Learn-and-adjust loops for meter reads and customer onboarding — every release reviewed against its success measure, with weak features cut rather than carried forever.
The systems energy companies actually run

Built on your stack, not on top of it

The product already runs on Billing platforms, CRM, metering data feeds and customer portals, with regulator reporting sitting on top of all of it. The product gap is usually upstream of the tools: no discovery habit, no prioritisation method, and a roadmap that is really a wishlist.

Discovery is done with the existing team, not handed to them finished. When the commercial lead has heard users say it themselves, the roadmap stops being a matter of opinion.

A sensible first project is one product decision with real stakes — the roadmap for tariff plans is a good candidate — judged by whether the next release is smaller, sharper and better used than the last.

How it works

From kickoff to delivery for energy companies

  1. Discovery

    Users, support themes and usage patterns for tariff plans: what people actually struggle with, and which problems recur often enough to be worth solving.

  2. Roadmap and prioritisation

    Themes ordered by evidence, with trade-offs stated openly. The operations director can see what is being deferred and why, instead of discovering it later.

  3. Build with the team

    Briefs the team can build from: problem, audience, acceptance criteria and success measures for a green energy bundle, reviewed as work progresses rather than at the end.

  4. Launch and learn

    Launch measured against its own success criteria — adoption, retention, support load — with weak features cut and strong ones extended in the next cycle.

Why Omer

Why hire Omer

  • Decisions with evidence — roadmaps argued from user evidence, not from who shouted last.
  • Fewer, better releases — a shorter backlog shipped well beats a long list shipped thin.
  • Discovery before build — problems understood before sprints are committed.
  • Honest measurement — launches judged on usage and retention, not launch-day noise.
  • Roadmap the team owns — documented so the product direction survives beyond the engagement.
Outcomes

What changes in practice

The product version of the same outcome: bills that go out right first time, tariff changes that land without a support surge, and customers who stay because switching feels like more effort than staying. Fewer features, better used, with a roadmap the team can explain without notes.

What lasts is the discipline: discovery as a habit, roadmaps with reasons, and launches measured on behaviour. Browse all hire engagements or discuss your product directly.

FAQ

Questions, answered

How do you decide what to build first?
By evidence, in this order: what users struggle with most, how often it recurs, and what it costs the business. Loud requests from one large customer are weighed against patterns across many users, so the roadmap serves the whole base rather than the last conversation.
Do you talk to real users, or work from analytics alone?
Both. Analytics reveal where users stall; conversations reveal why. For tariff plans, that pairing turns a vague complaint into a problem the team can actually solve.
How do you measure whether a release worked?
Against criteria agreed before launch — typically adoption by the target audience, retention over the following weeks, and support load. If a release misses its own criteria, it is revised or cut rather than quietly carried.
What if the product already exists and feels stuck?
That is the normal starting point. First step is an audit: which features are truly used, which were built on one-off requests, and what an evidence-drawn roadmap would look like today.
Who owns the roadmap after the engagement?
Your team does, with documentation: the discovery findings, the prioritisation method and the current roadmap. The aim is a product direction the team can defend and update without outside help.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.