Custom Builds

Built around
how your team
actually works.

When off-the-shelf doesn't fit, we build what does. Suite extensions, data integrations, custom dashboards, and white-label apps — scoped to a deliverable, shipped on a date, yours when it deploys.

yourbrand.gridient.app/portfolio
PORTFOLIO · Q2 2026
Portfolio Overview
Active Contracts
847
▲ +12 MTD
Renewals 90D
63
▲ Acting on 41
Volume MWh
312k
▲ +4.8% QoQ
Forward Curve · NG Mar–Dec
20262027
CUSTOMER
RENEW
VOLUME
STATUS
Northbrook Manufacturing
JUN 2026
18.4k MWh
RFP OUT
Riverside Logistics
JUL 2026
9.1k MWh
REVIEW
Lakeside Healthcare
AUG 2026
31.6k MWh
CONTACTED
01 · Built on the Suite
Faster
by foundation.

Most custom work extends Beacon, Switchboard, Linework, or Ledger. The plumbing exists — auth, data layer, design system, deployment. You're paying for the feature, not the floor.

02 · Senior Engineers
Same bench
that built it.

The people writing your code wrote the Suite. No agency markup, no offshore handoff, no team you have to train on energy. The work moves at the speed of people who already know your stack.

03 · Fixed-Fee
Quoted, not
metered.

Spec'd at the top. Billed at the bottom. No hourly drip, no scope creep at the finish line. If we underestimate, that's our problem to absorb — not your invoice to swallow.

04 · Yours on Ship
Your access,
your data.

Built features deploy into your tenant. Your data stays where it lives. Source access and exit terms written into the engagement — no lock-in surprises if you ever need to walk.

What We Build

Four shapes
of custom work.

Most engagements fall into one of these four. Some combine two. Each one extends the Suite where it makes sense — and stays standalone where it doesn't.

switchboard / custom
CB-01 · SUITE EXTENSIONS

New Capability,
Native To Suite

Custom screens, custom reports, custom data feeds, custom roles. Built natively on the Suite stack — same design system, same auth, same release cycle. Your team learns one tool, your team uses one tool.

Beacon Switchboard Linework Ledger
Typically 4–10 weeks
CSV
ETL
SUITE
CB-02 · DATA INTEGRATIONS

The Pipes
Between Systems

Supplier APIs, utility data feeds, CRM, billing, sustainability platforms. Custom ETL, field mapping, error handling. So the data you need shows up where you work — without a weekly manual lift in someone's spreadsheet.

ETL APIs EDI Webhooks
Typically 3–8 weeks
executive view · q2
CB-03 · CUSTOM DASHBOARDS

The View
For The Decision

Executive views, portfolio views, customer-facing dashboards. Pulled from the Suite, your own systems, or both. Designed for the specific decision the dashboard exists to support — not "general analytics" that nobody opens twice.

Executive Portfolio Client-Facing
Typically 3–6 weeks
your brand · your domain
SUITE FOUNDATION
YOUR BRAND
CB-04 · WHITE-LABEL APPS

Your Brand,
Our Engine

A complete customer-facing application built on the Suite foundation but with your brand, your domain, your customer experience. Most common with partners who want their book to interact with software that reads as theirs — not as a vendor's.

Brand Domain SSO Theme
Typically 6–12 weeks
How It Works

From spec
to ship.

The path from first conversation to deployed software. Five steps. No black-box phases — you see working software at every milestone, not just at the end.

01

Spec Call

A free 30-minute conversation. What you need built. What problem it solves. What success looks like in six weeks and in six months. You learn whether we're the right team — and we tell you directly if we're not the build for this work.

30 MIN Free · Zoom or phone
02

Design & Estimate

Written spec, wireframes where they help, a fixed-fee quote with a clear timeline. We surface trade-offs early — Suite-extended vs standalone, must-haves vs nice-to-haves, what we'd hold for v2. You either green-light it or tell us what to adjust.

1–2 WEEKS One revision included
03

Build

Weekly working sessions, working software at each milestone. No big-bang waterfall. You see the build evolve in your tenant, give feedback as you go, and never get a "done" that turns out to be a surprise on demo day.

WEEKLY Demo + feedback
04

Ship & Train

Production deploy. Team training. Documentation in your hands. We don't disappear at deploy — there's a hand-on-the-wheel window while your team gets to first-real-use, so the launch lands instead of stalling.

CLOSE Deploy + handoff
05

Maintain — or Hand Off

Two paths. Stay on a maintenance contract and we keep the build current with Suite updates and your evolving needs. Or take it from here — we'll hand over everything you need to run it independently. Your call, no penalty either direction.

OPTIONAL You choose at handoff
What We Won't Take On

The work we say no to is part of the work we say yes to.

We're deliberate about scope. Saying yes to everything is how custom shops get slow, expensive, and bad at the work they should be good at. If you're looking for any of these, we'll cheerfully point you somewhere better — and stay on call for the parts we can actually do well.

  • Generic CRM or sales tools. Use HubSpot, Salesforce, Pipedrive. We'll integrate with them.
  • Marketing websites. Hire a designer. Use Webflow or Framer.
  • ERP, accounting, payroll. Outside our lane. We don't pretend otherwise.
  • Anything outside energy. We're operator-deep in this sector for a reason — and shallow everywhere else for the same reason.
  • Work that competes with another partner. If a build would put us across the table from a current Gridient customer, we won't take it.
Start the Build

Describe
the build.

Thirty minutes, no slides. Tell us what you want built and what problem it solves. We'll come back with whether we should build it, whether it should extend the Suite, and what it would take to ship.