Interconnection · Permitting · Permission to operate

Every solar and battery project, from application to permission to operate, on one verified record.

GridProjeX is the system of record for the approvals between an installed system and an energized one. Three independent tracks for the utility, the permit office, and the crew. Every value tied to the document it came from. Readiness checked before anything is submitted. And a status the homeowner can actually read.

In private beta → See how it works
3independent tracks 1record per project 0guessed values
app.gridprojex.com / projects
The GridProjeX interconnection command center: project metrics, a featured project with independent AHJ, utility, and operational tracks, document verification, a verified data conflict, and the homeowner preview.
Verified data conflict
Battery capacity: plan set says 20 kWh, contract says 30 kWh. A person decides
Homeowner sees
"Your utility is processing meter work. Nothing is required from you." Plain language

Illustrative project. No customer data.

Three tracks
Utility, permit office, and installation move independently and are never confused with each other.
Every value
Carries its source, its verification state, and who confirmed it.
Readiness first
A submission is checked against what the utility and permit office require before it leaves.
Hours saved
AI reads the documents and cross checks the values so installers and utility reviewers confirm instead of retype. A person still signs off on what matters.
The gap between installed and energized

The system is on the roof. The paperwork decides when it turns on.

Between the last panel and the first kilowatt hour sit an interconnection application, a permit, an inspection, a meter, and a final utility review. Each lives in a different portal, speaks a different vocabulary, and stalls for reasons nobody wrote down. The installer chases. The utility re-requests. The homeowner calls.

01

Corrections that could have been caught before submission

A missing single line diagram, a nameplate that disagrees with the plan set, an account number typed from memory. Each one is a round trip with the utility.

02

Status that lives in someone's head

"Waiting on the utility" means five different things. Which department, since when, and what unblocks it are rarely recorded anywhere a colleague can find.

03

Homeowners kept in the dark

They were told weeks. It has been months. The only status they get is the one they call for, in language written for a permit office.

How it works

Three approvals. Three tracks. One record they all report to.

A project opens the tracks its situation requires. Each track has its own stages, its own evidence, its own clock, and its own owner. Milestones on one track gate steps on another, so meter work cannot be requested before the inspection passed, and permission to operate cannot be recorded without a date.

Utility track

Interconnection to PTO

  • Application submitted · UA-2026-0418
  • Utility approved
  • Installation complete, awaiting inspection
  • Meter work requested
  • Final utility review
  • Permission to operate
Held by utility meter department · clock running, 6 days left
Permit office track

Permit to inspection

  • Permit application filed
  • Permit issued · BLD-2026-1001
  • Inspection scheduled
  • Inspection passed · Sep 9
Track complete · milestone released meter work on the utility track
Installation track

Install to commissioning

  • Installation started
  • Installation complete
  • Commissioning
  • Commissioned
Held by installer · commissioning waits on the meter
01

Readiness before submission

Each dimension of the project, identity, design, documents, utility application, permit, is scored on data completeness. A missing verified account number or a plan set that was never confirmed shows up before the application leaves, not as a correction three weeks later.

02

Verified data, with provenance

Every field on the project, from system size to permit number, is an observation with a source: a plan set, a utility bill, a permit card, a person who checked it. The record shows which source it came from and whether a person verified it.

Verified data conflict · battery usable capacity
Plan set, rev C20 kWhverified
Purchase agreement30 kWhverified
Two verified sources disagree. Neither displaces the other. Readiness is blocked until a person chooses, and the choice is recorded with their name and reason.

03

Ownership and clocks on every stage

Each stage names who holds the project, the installer, the customer, the utility, the permit office, or the meter department, and runs a clock against it. When a clock breaches, the queue says so. When responsibility moves, the record says why.

04

Documents kept as they arrived

Plan sets, permits, inspection reports, utility letters, and interconnection agreements are stored unchanged, typed, versioned, and verified by a person. Anything read out of them stays linked to the page it came from.

Who it serves

Three parties wait on the same approval. Each gets the view they need.

The installer runs the work, the utility reviews it, and the homeowner lives under it. GridProjeX holds one record and shows each of them the part that is theirs.

Your coordinators stop chasing portals and start clearing blockers.

Read the installer page →

GridProjeX is the console your interconnection and permitting coordinators work from. It does not replace your utility or county portal accounts. It makes sure what goes into them is complete, and it keeps the record of what came back.

  • One project, every track. Utility, permit office, and installation side by side, with the next allowed step and the evidence it needs.
  • Retrofits are first class. Battery add ons, inverter swaps, expansions, and generator additions carry existing and resulting sizes, the existing interconnection agreement, and the notice or modification path the change calls for.
  • A review queue that means something. Conflicts to decide, documents to classify, missing data, unmapped utility wording, breached clocks. Not a wall of notifications.
  • Every action audited. Who moved a stage, who chose a value, who waived an item, and why, in an append only ledger you can verify.
  • Yours to run. Human operable end to end. AI helps with the reading and the sorting; nothing depends on a model being right, and nothing important lives only in a prompt.
Review queueTuesday
4 things need a person today.
Everything else is moving, and the record says who holds it.
  • 1Decide: battery capacity, plan set 20 kWh vs contract 30 kWh
  • 2Classify: 2 documents uploaded from the field
  • 3Map wording: "Pending Engineering Review" from Duke
  • 4Breached: meter work clock, Orlando project, day 22
Ready to submit
3 projects, all data verified
Waiting on utility
12 projects, 2 past expected date
PTO this week
5

Applications that arrive complete, and correction cycles that are actually closed out.

Read the utility page →

GridProjeX works on the applicant's side of the counter. It does not log into utility systems and does not submit anything on its own. What it changes is the quality of what your interconnection team receives and how quickly a correction comes back resolved.

  • Fewer incomplete submissions. Readiness holds an application until the identity, design, and document items your program requires are present and verified.
  • Values that agree with their documents. Nameplate, inverter model, battery capacity, and account numbers are tied to the plan set, spec sheet, or bill they came from. Disagreements are resolved before submission, not discovered in review.
  • Your wording, preserved. Status text is recorded exactly as your portal or correspondence states it, mapped to a stage by a person, and never paraphrased into something you did not say.
  • Correction loops with a record. Each request for correction is a stage with an owner and a resubmission event, so a returned application is a closed loop rather than a fresh guess.
  • No invented rules. Program requirements enter the system from a source and are marked verified or unverified. Unverified requirements are shown as such and never enforced silently.
What arrivesInterconnection application
Submitted with the record behind it.
A coordinator files in your portal as usual. This is the state of the project the moment they did.
Applicant of record
Verified against the utility bill
System size AC
7.6 kW, plan set rev C, verified
Inverter
Model and spec sheet on file
Battery
13.5 kWh, spec sheet, verified
Single line diagram
On file, verified
Open data conflicts
None
Your status wording
"Application Received", recorded verbatim

You should never have to call to find out where your system stands.

Read the homeowner page →

Every project carries a homeowner view written in plain language. It says what phase the project is in, who is working on it right now, whether anything is needed from you, and when the next step is expected. It never shows a date it cannot support.

  • No jargon. "Your utility is handling meter work. Nothing is required from you." Not "meter_work_requested."
  • Who has it. Your installer, your utility, the permit office, or you. If it is you, it says exactly what is needed.
  • Honest timing. An expected date appears only while a clock is running against it. When the utility is late, the view does not pretend otherwise.
  • The milestones that matter. Permit issued. Inspection passed. Permission to operate granted. Each with its date.
  • Your documents, shared on purpose. Your installer chooses what to share with you. Nothing is exposed by default.
Homeowner viewMiller residence
Utility meter work in progress
Your utility is handling meter work. Nothing is required from you. Next update expected by October 2.
  • ✓Permit issued · August 28
  • ✓Installation complete · September 3
  • ✓Inspection passed · September 9
  • ●Meter work with your utility
  • ○Permission to operate
Principles

Built for an industry where a wrong number costs a month.

These are not preferences. They are constraints the software is built around, and they are the reason a utility, an installer, and a homeowner can rely on the same record.

01

Verified by AI, confirmed by people

We use AI wherever it saves human hours: reading plan sets, bills, permits, and inspection reports, cross checking every value against its document, flagging what is missing, drafting plain language updates. Every check carries its source and its confidence, so an installer or a utility reviewer confirms in seconds instead of retyping. Approving, submitting, resolving a conflict, or overriding a decision always has a human name on it, and the whole system runs, and can be extended, without a model in the loop.

02

Verified never yields to recency

A verified value is not replaced because something newer arrived. Two verified sources that disagree open a conflict that only a person can close, and both stay in the record.

03

No invented rules

Utility and permit requirements come from a source and carry a verification state. Nothing is fabricated to fill a gap, and unverified rules are labeled, never silently enforced.

04

An append only record

Every change is an event in a hash chained ledger that can be verified end to end. History is never rewritten, only added to.

Pricing

Pay for projects that do real work. Nothing else.

Planned pricing for general availability; nothing is sold during the beta. A project becomes billable once, for its lifetime, the first time real work is recorded on it: a document uploaded, a value verified, a stage moved. Drafts, duplicates, and test records are free. Annual plans are ten months for twelve.

Free
$0
Up to 3 active projects at a time.
  • All three tracks
  • Readiness and verified data
  • Homeowner view
  • Document storage
After beta
Core
$149/month
15 project activations included, then $12 each.
  • Everything in Free
  • Unlimited users and roles
  • Review queue and tasks
  • Ledger export
After beta
Most installers
Pro
$449/month
60 project activations included, then $9 each.
  • Everything in Core
  • Webhooks
  • Configuration publishing
  • Priority support
After beta
Enterprise
$2,000+/month
Negotiated activations, $5 floor.
  • Everything in Pro
  • API access
  • Single sign on
  • Dedicated onboarding
Talk to CivyxIQ

What counts as an activation. One project, once, at the first real activity. Canceling a project after it was activated does not refund it, and archiving a draft never counts. The billing page inside the product lists every counted project and the exact event that counted it.

Straight answers

What GridProjeX does and does not do.

Does it log into utility or permit portals for me?

Not yet. Today coordinators file in the portals they already use, and GridProjeX makes sure what they file is complete and keeps the record of what came back. Direct connections to utility and permit systems are on the roadmap and will be built with the utilities involved, one program at a time, never by guessing at a portal.

Does it use AI?

Yes, wherever it saves human hours for installers, utilities, and homeowners, and it is arriving in stages. Reading values out of plan sets, bills, and permits, suggesting a document type, flagging what is missing, and drafting the homeowner update are the first uses. Every suggestion shows where it came from, carries a lower authority than a verified value, and can never displace one. A person confirms anything that matters. The product is built so that it runs, and can be maintained and extended, without any AI in the loop; AI makes it faster, never necessary.

Where do the utility rules come from?

From your program documents and your people. GridProjeX ships with generic workflows and no fabricated utility or permit rules. Requirements you enter carry a source and a verification state, and unverified ones are labeled. Verified rule packs for specific utilities and permit offices will be published as they are confirmed with those organizations.

Can it work alongside our CRM or field service platform?

Yes. GridProjeX runs independently with its own database and storage. Other systems connect through its API and webhooks, never through a shared database. SolarProjeX, also from CivyxIQ, is the first planned connection.

Who owns the data?

You do. Documents are stored unchanged, the ledger is exportable, and nothing is shared with a homeowner or a third party unless your team chooses to share it.

Is it available today?

No. GridProjeX is in a private beta with its first installer, and it is early: screens, wording, and workflows will keep changing as findings come in. We are not onboarding new installers or utilities yet. If you want to hear when the beta opens, contact CivyxIQ.

In private beta. Built in the open, with the people who wait on these approvals.

GridProjeX is being tested with its first installer on real projects before anyone else gets a login. We are not onboarding new installers or utilities yet. If you run interconnection or permitting work and want to hear when the beta opens, tell CivyxIQ who you are.

Contact CivyxIQ → Beta testers sign in