For ESPs

All the service lines.
One platform.

Efficiency, demand response, distributed energy, supply, sustainability — the breadth of what an ESP sells is also the breadth of what the Suite supports. Built for the operator who refuses to pick one service line, and the customer who refuses to be served by four different vendors.

What's Hard

The shape of running
a multi-service ESP.

ESPs don't have a single-channel problem. They have a coordination problem. The breadth is the advantage; the fragmentation is the cost. Here's the cost, honestly described.

01

The customer sits across from your efficiency lead in February, your supply lead in March, your sustainability lead in April — and none of you walks in knowing what the others have already discussed.

02

You have permission to sell five service lines and a CRM that pretends only one of them exists.

03

Cross-sell is the obvious play. The data for cross-sell lives in four different systems. The cross-sell happens by accident, not by design.

04

You stood up the demand response service line in eighteen months. The next one is still in scoping. Standing up new offers is the bottleneck on every strategic deck you've shown leadership.

05

Margin reporting per service line is a quarterly exercise that takes three weeks. By the time you have the answer, the question has moved on.

What Changes

One platform.
Every service line.

Each capability maps to a specific fragmentation pattern. The Suite was designed for the breadth an ESP actually sells — not retrofitted from a single-channel product into something multi-line.

Maps to · Pain 01

Conductor + Beacon

See the Suite ↗

One customer record. Every service line.

The customer view in Conductor surfaces every interaction across every service line. The efficiency lead sees what supply has open. The supply lead sees what sustainability is recommending. Beacon shows the customer the same unified view, branded to your firm. No more arriving cold to a meeting the customer already had with you.

Maps to · Pain 02

Suite + Custom Extensions

See Custom →

A CRM that knows what you actually sell.

The Suite supports every service line natively — efficiency projects, DR enrollments, DER assets, supply contracts, sustainability commitments. When you stand up a new offer, the data model already accommodates it, and custom extensions add the workflow specifics without rebuilding the foundation.

Maps to · Pain 03

Suite Data Layer + Intelligence

See Intelligence →

Cross-sell by design, not by accident.

When every service line writes to the same customer record, cross-sell opportunities surface automatically — the supply customer with rising demand who should be talking to DR, the efficiency customer whose project ROI now justifies a sustainability roadmap. Plus monthly intelligence on what's moving in adjacent service lines.

Maps to · Pain 04

Advisory + Custom Builds

See Advisory →

Stand up new offers in weeks, not quarters.

ADV-01 New Offer Launch engagements move scoping → launch in 6-10 weeks. Custom builds operationalize the new offer on top of the Suite foundation — no need to build a new data model, new reporting, new customer portal for each service line. The platform absorbs the new offer; the team just needs to learn the workflow.

Maps to · Pain 05

Ledger + Custom Dashboards

See Custom →

Margin reporting as a query.

Service-line P&L lives in the Suite, not in monthly close. Margin by service line, by region, by customer cohort — surfaced on demand, not assembled quarterly. Custom dashboards built on the Suite data layer give leadership the answer when the question is fresh, not three weeks late.

How To Start

Three loadouts.
Pick one.

ESPs typically don't start with the full Suite — the operational shift is too big. They start with a scoped engagement on the worst bottleneck, prove the model, and expand.

01 · LIGHTScoped Engagement

Solve One
Bottleneck

Prove the model
  • Advisory engagement (ADV-01 or ADV-04). Service line launch, internal function buildout, or a strategic question.
  • Targeted custom build. Cross-sell dashboard, margin reporting, or single-service-line workflow.
  • Optional briefings layer on top — the market read your leadership wants.
Proves It OutMost ESPs start here. One bottleneck solved well demonstrates the model before the platform conversation.
02 · MEDIUMUnified Customer View

Suite as
the CRM

One platform across service lines
  • Conductor + Beacon configured for multi-service operations. One customer record across all your service lines.
  • Switchboard + Linework for the procurement-heavy service lines. Supply, DR enrollments, contract management.
  • Custom integrations with your existing CRM, ERP, and field-service tools.
Operational ShiftThe unification engagement — usually 4-6 months to deploy, then the team learns to operate on one platform.
03 · HEAVYPlatform Partnership

Full
Platform

Suite + Intelligence + Advisory + Custom
  • Full Suite across every service line, white-labeled to your brand.
  • Intelligence layer — co-branded briefings to your customer base, monthly cadence.
  • Advisory + custom builds as new service lines, new geographies, new offers come up.
For Scaled ESPsMulti-year platform partnership. Quarterly platform reviews to align Suite roadmap with your operating roadmap.
Why This Works

Built for breadth.
Independent of the channels.

Most software in the energy space is built for one service line and retrofitted for others. Gridient is structurally built for multi-line operators. Three commitments make it real.

01 · Built for Breadth

Multi-line
by design.

The Suite's data model accommodates efficiency, DR, DER, supply, and sustainability as first-class objects — not as bolt-ons. When you launch a new service line, the platform absorbs it rather than requiring a parallel system.

02 · Channel-Independent

Not on a supplier's
side of the table.

Gridient doesn't take supplier revenue, program-implementer revenue, or utility channel sponsorships. The recommendations the Suite surfaces are clean because the platform is structurally clean — your customer trusts the conclusions because nothing's paying us to bias them.

03 · Operator-Built

Built by people
who ran the work.

Every screen in the Suite traces back to a Monday-morning question in a real multi-line operation. Decisions that wouldn't survive an operator's pushback don't ship — because the people building the Suite would push back too.

First Step

Thirty minutes.
No slides.

Tell us about your service lines, where the fragmentation is costing you most, and what your leadership wants visibility into. We'll tell you which loadout fits and what it would take to get there.