RE+ 2026 · Nov 16–19 · Las Vegas

See what replacing your entire software stack looks like — Booth W15826.

Book a booth demo
Product Development

A connected platform should keep compounding.

Powerlily develops in a direct loop with the installers using it. We ship continuously across the platform, record released work in the changelog, and use the complete customer lifecycle—not a single feature category—to set direction.

Get Started See What We've Shipped
Powerlily solar platform under continuous development
How the roadmap works

Feedback becomes shipped, connected capability.

A roadmap is useful when it explains how priorities are chosen and points to evidence of what has already arrived. Powerlily's loop is deliberately short and its scope follows the solar business end to end.

01

Listen

Start with friction from active solar teams.

The roadmap is shaped by people working real leads, designs, permits, installations and fleets—not an abstract list of market categories.

Feedback grounded in operations Roadmap input comes from work already moving through the platform.
  1. 01.01

    Direct product conversations

    Keep the people building Powerlily close to the teams encountering workflow problems.

  2. 01.02

    Look across roles

    Consider sales, design, engineering, operations, field and customer needs when deciding whether a change truly removes friction.

  3. 01.03

    Prefer the connected fix

    Solve a handoff at the shared project record where possible instead of adding another export or isolated screen.

  4. 01.04

    Validate the actual workflow

    Review whether the change works in the sequence a solar company will use, including the team downstream of the original request.

02

Ship and record

Make released work the evidence.

Short release cycles let the team deliver focused improvements, observe them in use and build the next layer without waiting for a quarterly marketing event.

Capability in the product The changelog points to delivered work, not concept art.
  1. 02.01

    Continuous releases

    Ship product capability, refinements and performance work as they are ready rather than saving them for artificial launch bundles.

  2. 02.02

    A public changelog

    Use the shipped record to understand what the platform has recently gained instead of relying on roadmap promises.

    Read the changelog
  3. 02.03

    No migration ceremony for routine improvement

    Deliver compatible platform changes into the product the team already uses.

  4. 02.04

    Observe and refine

    Treat a release as the next point in the feedback loop, with real use informing the follow-on change.

03

Compound

Deepen the lifecycle, not just the feature list.

Each useful connection raises the value of the capabilities around it: better catalog data improves design, better design improves documents, better delivery improves the customer relationship.

Depth compounds across the system A platform connection can improve more than one department.
  1. 03.01

    Acquisition improves the operating record

    Forms, canvassing and attribution create better context for the sales and delivery work that follows.

  2. 03.02

    Engineering improves every handoff

    Site, equipment and design truth can strengthen proposals, permit documents and field execution together.

  3. 03.03

    Operations improves customer experience

    Schedules, communication and project evidence create a more useful branded portal after the sale.

  4. 03.04

    Ownership returns value to acquisition

    Fleet, lifecycle outreach and referrals let the installed base feed service and the next qualified lead.

    Explore the platform

Join a platform that keeps earning its scope.

Inspect what has shipped, then bring the next real workflow problem into the loop.

Get Started Schedule Demo
Pericles
Pericles
Powerlily assistant
Replies instantly. Leave your email anytime and a human follows up.