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

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

Hire a Product Manager for Solar Companies: For solar companies, the product question is rarely whether to build. It is what to build first, for whom, and what to stop building. Installs depend on surveys, parts, scaffolding and grid paperwork all lining up — and incentive deadlines punish any slip.

Solar Companies — Product Manager

A senior product manager for solar companies

For solar companies, the product question is rarely whether to build. It is what to build first, for whom, and what to stop building. Installs depend on surveys, parts, scaffolding and grid paperwork all lining up — and incentive deadlines punish any slip.

That cycle is why roadmaps matter here. Summer install peaks and incentive deadlines drive the calendar, with winter used for surveys and maintenance. Without one, every quarter's loudest request becomes the plan, and the product drifts.

This engagement puts one person in charge of the product for your solar companies: what gets built, in what order, and how success is judged — starting from a residential kit and the users who actually pay for it. Book a free discovery call and we will test the fit on one product decision before any wider scope is agreed.

What you get

What this engagement covers for solar companies

  • Discovery for a residential kit — conversations with real users, support themes and usage patterns, turned into problems worth solving rather than feature requests to copy.
  • Prioritised roadmap for a commercial system — themes ordered by evidence, with the trade-offs stated so the team stops relitigating priorities every week.
  • Build-ready briefs for a battery bundle — problem, audience, edge cases and success measures, so developers are not guessing at intent mid-sprint.
  • Launch plan for a maintenance plan — who hears about it, what changes for existing users, and how the first weeks are measured.
  • Metrics that mean something for site surveys and system design — activation, retention and the one number that shows whether the product is actually working for users.
  • Iteration cycles for installations and grid applications — learn from each release, kill what does not work, and double down on what users demonstrably value.
The systems solar companies actually run

Built on your stack, not on top of it

The product already runs on System design software, a CRM, monitoring portals and supplier ordering. 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 installations manager 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 a residential kit 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 solar companies

  1. Discovery

    Users, support themes and usage patterns for a residential kit: 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 battery 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 what users do, not from who shouted last.
  • Fewer, better releases — a shorter backlog shipped well beats a long list shipped thin.
  • Discovery before build — the problem is understood before a single sprint is 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

Installs completed on the booked date, systems monitored so faults are caught before customers notice, and maintenance that keeps generation high. On the product side, that shows up as a tighter range: a residential kit and a commercial system each with a clear audience and a reason to exist, and releases that users actually adopt.

Over time the team stops asking what to build next and starts asking what users need next — which is the whole point. 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 a residential kit, 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.