Partner program
Set Gridline up for the operators you already serve, and keep the implementation fee for every customer you add. Your own team gets Gridline Pro free for 3 months, then 20% off everything it uses.
Your benefits
Every new customer you add pays an implementation fee, and it goes to you.
Your organization gets Gridline Pro free for 3 months, then 20% off every Gridline product it uses.
Lead registration in your console, a joint first onboarding, and a direct line for workflow requests.
Financial benefits
Two sources of value: what your own organization saves, and what every customer you add pays you.
For your own organization
3 months
of Gridline Pro, free
20%
off all Gridline products, ongoing
Covers your organization's own use: seats, workflow runs and test runs. Your clients subscribe under their own plans.
For every customer you add
Yours
the implementation fee, for every new customer
Your clients' Gridline subscriptions are billed under the published plans or an Enterprise agreement.
Plan prices are published in November 2026. Your partner agreement confirms these terms in writing.
The partner model
You work from a partner organization: the boundary that holds your team, your reusable workflows, and the customers you set up. You run the demos, build and test the workflows, own implementation and support, and invoice for it.
The customer's account is the customer's: its projects, its workflows, its connections, encrypted. A customer chooses a partner to set Gridline up, and can stop working with that partner and work with another without losing what was built.
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.
Customer account owned by the customer
No lock-in
A partner can close, or stop being the right fit. When that happens, the customer moves on with its account and workflows intact. This is Gridline's rule for every partner.
01
A customer chooses a Gridline partner to set Gridline up, and can stop working with that partner and appoint another. Gridline never blocks that choice.
02
Projects, workflows and connections move to the new partner. Customer and project identifiers stay the same. Deployments arrive paused until the new partner tests and activates them, and past run evidence stays unchanged.
03
You are free to design your contracts with customers as you wish, including restrictions and confidentiality on the work you deliver. Gridline does not lock customers in on any partner’s behalf.
04
More partners make Gridline a stronger platform for every partner, the way a car is worth more when many garages can service it. Customers stay with the partners who serve them well.
A customer who wants to change partner writes to Gridline, and we move the account to the new partner. We are building a control so the customer's owner can remove a partner's access directly in the account.
The console
Your whole book at a glance. Customers, recent runs, what needs you today.
Register and move leads through your stages. Lead registration lives here, so sourcing is never a dispute.
Typed, prioritized, with attachments and history. Nothing lives in someone's inbox.
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.
Decks, IT one-pagers, and case studies, ready before the client meeting.
The first hour
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.
Confirm the customer, the program, and the billing shape before you touch anything.
Confirm you are in your organization first, then create the customer, a project, and one test member.
A customer-scoped reader in the guided builder: point it at the utility data, name the fields, test as you go.
Drafts test against an immutable server snapshot. When the test passes, you publish exactly the snapshot that passed, never a newer draft.
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.
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
You have used software where the guardrails were paperwork. Each of these exists because it removes a category of 2 a.m. problem.
01
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.
02
A draft run executes against a server snapshot that cannot shift under you. When a test passes, it stays passed.
03
Three separate acts, three separate decisions. Nothing goes live because you saved a file.
04
A new project setup cannot bill anyone until someone on your team activates a passing setup revision.
05
Encrypted at the organization level, and never exposed in workflow code, run inputs, or evidence.
06
When an operator asks what happened, you show them, line by line.
workflow → version → revision → run → steps → attempts
The recipe works. The authored actions, schemas, and sample inputs passed from one immutable draft-test snapshot.
It works for this customer. The published version passed with this project's settings and this customer's connections.
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.
The handbook
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.
You know it worked when...
Every topic closes with this checklist. You will not be guessing whether you did it right, and neither will we.
Talking about Gridline
Your clients hear about Gridline from you first. Use the words we use, and keep every claim true.
Gridline turns energy paperwork into execution. It reads utility bills and other documents, applies your billing rules, pauses for human approval, and writes the result to the accounting, payment and email systems you already use. Every run keeps a complete evidence record. [Your firm] implements and supports Gridline for its clients as a Gridline partner.
For your website, proposals and social posts. Replace [Your firm] with your firm's name.
Getting help
Every run already keeps its evidence chain. When a request points at it, we can answer from the record instead of asking you to describe what happened.
Fit
We would rather lose a signup than surprise a partner in month three.
If the second list is you today, keep the page bookmarked. We update it when new workflows ship.
Becoming a partner
Tell us the customer, the program, and the billing shape. If it is a fit, you are building the same week.
Your approved partner account opens the console, and your organization gets Gridline Pro free for 3 months.
Run a demo billing cycle on the demo members in your organization, and build with zero-write tests.
Run the 60-minute path end to end on demo data, until the hour is actually an hour.
Review the asset library, then register your first leads in Pipeline.
We do the first onboarding together. The rest are yours, and so are their implementation fees.
Questions and answers
No. It applies to every Gridline product your own organization uses: seats, workflow runs and test runs. Your clients subscribe under their own plan or an Enterprise agreement.
It starts when your 3 free months of Pro end, and it continues for as long as you are a Gridline partner.
You do. You set it for each new customer, invoice it directly, and keep all of it. Gridline takes no share.
Plan prices are published in November 2026. Your 20% applies to the published price.
Yes, at any time. The customer keeps its account, projects, workflows and connections. Today the customer asks Gridline and we make the move; we are building a control so the customer can remove a partner itself.
The customer’s workflows move with the customer. Protect your work in your contract with the customer: restrictions and confidentiality are yours to agree. Gridline’s rule is only that customers are never locked in to a partner.
No. Partners own implementation and ongoing support. That is what makes the implementation fee yours.
Yes, with the partner badge, following the brand rules above. Request the files from partners@gridline.ai.
Start
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.
