Zaras for Solar

The panels went up in March. The meter turned on in June.

Site assessments, approved plan sets, and the interconnection that decides when a system counts.

Site assessmentsInstallsMonitoring

Install is not the finish line.

A residential array is not finished when the crew drives away — it is finished when the utility grants permission to operate, and everything between those two dates is paperwork somebody has to chase. There is no monthly series for this trade to point at, and since the federal residential credit expired for expenditures after 2025 there is no deadline to sell against either. What is left is arithmetic, and arithmetic needs a record.

AssessmentDesignPermitInstallInspectionUtility AppPTOthe recordthe assessmentcrew donethe gappermission to operateASDSPMISINUAPOthe recordassessmentcrew donethe gapPTO

What carries the job: the assessment the approved plan set the date the meter turned.

One week in June. Three jobs, one record.

An assessment filed once, a utility application chased for weeks, and the date a system finally counts — three different jobs, one operating record.

Tue

Assessment filed

Roof, shading, and service recorded once, in the place the design and the utility application will both read from.

Record holdsroofshadingservice
Thu

Utility application chased

Submitted weeks ago, still open, with the customer asking why their array is sitting dark.

Record holdsapplicationopenchase
Sat

Permission to operate

The date the system actually starts counting, recorded against the job.

Record holdsPTOmeterstart

The assessment file and the interconnection clock.

Solar money comes from two engines — the assessment that everything downstream cites, and the interconnection clock that runs on long after the crew leaves. Every time the interconnection clock stalls, what unsticks it is something already sitting in the assessment file. Zaras runs both from the same record.

The assessment file

Recorded once, cited for the rest of the job.

Site assessmentroof, shading, and service, captured once
Design and permitthe plan set the authority actually approved, not the one drawn first
Equipmentwhat went on the roof, by serial, for the warranty
The arithmeticthe payback the customer agreed to, in writing

The interconnection clock

The half of the job that runs after the crew leaves.

Utility applicationsubmitted, tracked, and chased
Inspectionthe sign-off that gates the utility
Permission to operatethe date the system counts from
Monitoringthe first month's production against what was promised

What Zaras runs for solar.

The record, not the whiteboard — every system from the assessment to paid, with nothing re-keyed into a second system.

Site assessmentsroof, shading, and service recorded once and cited by everything downstream.

Approved plan sets and permitsthe plan set the authority actually approved, not the one drawn first.

Equipment records by serialwhat went on the roof, tracked for the warranty.

Utility applications tracked to PTOsubmitted, tracked, and chased until permission to operate lands.

Inspection datesrecorded on the job, findable months later.

First-month production against the estimatethe arithmetic the customer agreed to, checked against what the system actually did.

Deposits and financing recordsthe payback math and the paperwork that backs it, on the same record as the install.

Invoicing, payments, QuickBooks syncbilling pulls straight from the record the assessment opened, no separate system to reconcile.

Assessment → design → permit → install → interconnect → paid — every system, one record.

Straight answers.

What does it cost?

Plans and prices are public on the pricing page — no sales call to get a number.

Does it work with QuickBooks?

Yes. Invoices and payments flow straight into QuickBooks — no double entry, no bookkeeper fights.

What happens to my data?

It’s yours, both directions. Customers, open utility applications, and PTO dates come in with you when you join — and everything exports, any time.

Can it run commercial work?

Yes — commercial arrays with per-site assessment records and NET-terms billing live on the same record as your residential book.

What size shop is this for?

Solar contractors running 1–40 crews — from an owner-operator to a multi-truck shop.

What does private beta mean?

We onboard a limited number of shops at a time. Request an invite, fit is reviewed within 24 hours with a reply either way, and accepted shops get guided onboarding — pricebook and customer list loaded with you, not dumped on you.

Private beta

The price is the price.

Every plan runs the full operating system for Solar — assessments, plan sets, equipment records, utility applications, monitoring, invoicing, payments. Pick the size that fits the crews you run today.

Solo

$49/ month

One office, one assessment file. Record the roof, the shading, and the service once, chase the utility application from the same record, and let the interconnection clock run until permission to operate lands — the record keeps the assessment file and the interconnection clock straight.

  • Site assessments cited by the design, the permit, and the utility
  • Equipment recorded by serial, for the warranty
  • Utility applications tracked and chased to PTO
  • First-month production checked against the estimate
  • Invoices, payments, QuickBooks sync
Request Solo access

Team

from$149/ month

The assessment file and the interconnection clock, run from one record. Every system walking in with its own site assessment already on file.

  • Commercial site records across multiple arrays
  • Roles for the office, assessors, and install crews
  • Open utility applications and PTO dates in one view
  • Everything in Solo, for the whole shop
Up to 5 techs$149Up to 15 techs$299Up to 40 techs$599
Request Team access

Free trial first, month-to-month after — cancel anytime. Full plan detail on the pricing page.

  1. Request an invite
  2. Fit reviewed within 24 hours
  3. Guided onboarding