Partner program

You bring the energy operators.
We hand you the keys.

A Gridline partner runs their own organization: the security boundary that owns your customers, your reusable workflows, and your encrypted provider connections. You sign up clients inside it, run the demos, own the implementation and the relationship. We run the platform and stay out of the room when you are with your client.

See the demo

The partner model

An organization of your own

When you sign, you do not get a login to our system. You get an organization: the boundary that owns everything you build. Your customers live inside it. Your reusable workflows live inside it. Your provider connections live inside it, encrypted, and nowhere else.

Inside your organization you sign up customers, each with their projects, members, and approved workflows. You run the demos. You own implementation, support, and the client relationship. Gridline runs the platform and does not appear on your org chart.

When your customer's own analysts join, they work as operators: they run approved workflows, respond to approvals, and read evidence. They cannot change what you configured, so your setup stays exactly as you tested it.

That structure is the deal in one picture: what is yours stays yours, including the customer list.

org_yourfirm boundary

YOUR ORGANIZATION
├─ customers/
│  └─ bellevue_apartments/
│     └─ riverside_solar/
│        ├─ members (12)
│        └─ approved workflows (2)
├─ workflows/      reusable
└─ connections/    encrypted

The first hour

Ship one customer workflow safely in 60 minutes

This is the first exercise in the partner handbook, and it is not a demo script. It is the real path you will use for every customer after the first.

00-10

Qualify the lead.

Confirm the customer, the program, and the billing shape before you touch anything.

qualified
10-20

Create the customer.

Confirm you are in your organization first, then create the customer, a project, and one test member.

workspace ready
20-40

Build the bill reader.

A customer-scoped reader in the guided builder: point it at the utility data, name the fields, test as you go.

draft passed
40-50

Publish the exact snapshot that passed.

Drafts test against an immutable server snapshot. When the test passes, you publish exactly the snapshot that passed, never a newer draft.

published
50-60

Deploy paused, test, activate.

The first project setup is created paused. You test it against this customer's settings and connections. Activation is its own decision, made by you, on purpose.

paused → active

An hour in, your customer has a working workflow, a deployment that passed its test, and an evidence chain that proves all of it.

Guardrails

Every guardrail buys speed later

You have used software where the guardrails were paperwork. Each of these exists because it removes a category of 2 a.m. problem.

Confirm the organization first.

Customer creation starts by confirming which organization you are in. Tenant ownership is never ambiguous, so a customer can never land in the wrong boundary.

Drafts test against immutable snapshots.

A draft run executes against a server snapshot that cannot shift under you. When a test passes, it stays passed.

Publishing is not deployment. Deployment is not activation.

Three separate acts, three separate decisions. Nothing goes live because you saved a file.

First deployments are born paused.

A new project setup cannot bill anyone until someone on your team activates a passing setup revision.

Credentials live in Connections only.

Encrypted at the organization level, and never exposed in workflow code, run inputs, or evidence.

Every run leaves an immutable chain.

When an operator asks what happened, you show them, line by line.

workflow → version → revision → run → steps → attempts

The green checks

Two green checks, two different promises

DRAFT TEST · PASSED

The recipe works. The authored actions, schemas, and sample inputs passed from one immutable draft-test snapshot.

PROJECT TEST · PASSED

It works for this customer. The published version passed with this project's settings and this customer's connections.

ACTIVATION · YOUR DECISION

Gridline never lets one green imply the other, and never lets either imply the workflow is live. Activation is always a third thing: an explicit decision you make after both checks are green. Nothing on this platform goes live as a side effect.

The console

The console that runs your book of business

Overview

Your whole book at a glance. Customers, recent runs, what needs you today.

Pipeline

Action items

Typed, prioritized, with attachments and history. Nothing lives in someone's inbox.

Workflow requests

When a customer needs a capability we do not have natively yet, file it here. It feeds the roadmap and you can see where it stands.

Asset library

Decks, IT one-pagers, and case studies, ready before the client meeting.

And a sandbox organization you create yourself

Full guided-builder access, zero-write test runs, every deployment starts paused
Demo on real screens, rehearse onboarding, build proof-of-concepts before a contract is signed
Nothing in a sandbox can touch anyone's production data
At contract, the client gets a dedicated production organization. Data never mixes between the two.

The handbook

It ships with an operating manual

Everything on this page comes from the Partner Handbook: twenty-four indexed topics, from qualifying a lead to reading an evidence chain. Your customer's analysts get a field guide of their own, the eleven-topic operator guide, so you never write training docs for a client. Both are versioned because the platform is: when behavior changes, the manual changes with it, and you can see both.

partner-guide · v2026.07.1 · 24 topics operator-guide · v2026.07.1 · 11 topics

05 Qualify a lead
06 Create a customer
07 Drafts and snapshots
08 Publish the passing snapshot
09 Paused deployments
10 Evidence chains
11 Connections and secrets
12 Cutover without duplicates

You know it worked when...

The project test is green with this customer's connections.
The deployment shows paused, not active, until you decide otherwise.

Every topic closes with this checklist. You will not be guessing whether you did it right, and neither will we.

Fit

Who this is for, and who it is not

We would rather lose a signup than surprise a partner in month three.

This works if

You have energy operators who trust you, and you want billing to stop being the reason they call.
You own implementation and support as a business, with implementation fees you set and invoice yourself.
You want your name on the client relationship, and a platform that makes you look careful in front of it.
You run community solar billing in the US, or PPA, ZEV, vZEV or LEG billing in Switzerland. That is what is in production today.
You will spend the first hour in the guided path before your first customer, because you know exactly what skipping the manual costs.
You want auditability you can hand to a client: every run's evidence chain, not a support ticket.

This is not for you if

You want passive referral income. Partners own implementation and ongoing support. If you hand off after the intro call, this will frustrate you and your client.
Your business is one-off EPC handoffs with no ongoing client relationships. The revenue share follows clients you support over time.
You need non-billing workflows today. Interconnection and project finance workflows are planned for Q3. They are not available now, and we will not sell them to you as if they were.
You are not willing to spend the first hour learning the guided path. The 60 minutes is the training. Skipping it makes everything after it slower.

If the second list is you today, keep the page bookmarked: Q3 changes one of those answers.

Economics

The economics, in one paragraph

You earn a recurring revenue share on platform fees for the clients you bring and support, for as long as you support them. Implementation fees are yours to set and invoice directly. The exact numbers live in the partner agreement.

full terms: partner agreement

Getting started

Your first two weeks

01 Get your approved partner account and open the console.
02 Create your sandbox organization yourself. No ticket, no waiting.
03 Run the 60-minute path end to end in the sandbox, until the hour is actually an hour.
04 Review the asset library: deck, IT one-pager, case studies.
05 Register your first leads in Pipeline.
06 Book a joint first-customer onboarding with Gridline. We do the first one together. The rest are yours.

Start

Bring one customer. Leave with a live workflow.

Write to us with the customer, the program, and the billing shape. If it is a fit, you will be building inside your own organization the same week.