Custom Software for Solar Installers: Permitting, Interconnection, and Install Tracking

A residential solar company sells a system in an afternoon and then spends the next three months getting it permitted, installed, inspected, interconnected, and funded. The sale is the easy part. The hard part is the gauntlet that runs from a signed contract to a system that is actually producing power and a financing partner that has actually paid — a gauntlet with a dozen handoffs, three or four outside parties, and a homeowner who calls every week asking why their panels are on the roof but not turned on.

Most installers stitch the operation together: a design and proposal tool like Aurora or OpenSolar, a generic CRM, a financing partner portal or three, a permitting spreadsheet, a scheduling whiteboard, and QuickBooks. Each tool handles its slice. But the project — the thing everyone in the office actually cares about — has no home. Where does each job sit? What is it waiting on? Which permits are about to expire, which interconnection applications have gone quiet, and which funded milestones have not been invoiced? Nobody can answer that without opening five tabs and asking three people.

This post covers what custom software for a solar installer actually looks like, where the off-the-shelf tools stop short, and the kind of company that benefits most from building rather than renting.

Why solar is different from generic project software

Solar looks like other project-based trades on the surface — a deal is sold, a crew does the work, an invoice follows — but the operation is structurally different. The work is gated by permits and a utility, paid by a finance company on milestones, and not truly done until a meter spins backward. The differences that matter:

• The project is a regulated pipeline, not a job. Between sold and done sit a site survey, an engineered design, a structural and electrical permit from the AHJ, an install, a city or county inspection, a utility interconnection application, and a final permission to operate. Each stage has its own paperwork, its own approver, and its own way of stalling. The software has to model that pipeline, not just store a customer record.
• Two outside parties control your timeline. The Authority Having Jurisdiction issues the permit and the utility grants interconnection — and neither works on your schedule. A job can sit for weeks waiting on a plan review or a PTO letter. If you cannot see at a glance which jobs are stuck where and for how long, you cannot push the ones that are slipping.
• You get paid in milestones by someone else. Most residential solar is financed — Mosaic, GoodLeap, Sunlight, Dividend — and the loan funds in tranches tied to milestones: a portion at contract, a portion at install, the balance at PTO. Cash flow depends on hitting each milestone and submitting the right proof to the right portal at the right time. Miss the submission and the money sits.
• The design and the build have to match. The system that was sold and permitted — panel count, inverter model, racking, electrical plan — has to be the system that gets installed, or the inspection fails and the interconnection paperwork no longer matches reality. Change orders ripple through the design, the permit, and the financing all at once.
• The homeowner experience is the referral engine. Solar is sold on trust and runs on referrals, but the three-month gap between signing and switch-on is where that trust erodes. A homeowner who can see exactly where their project stands stops calling the office in frustration — and stays happy enough to refer the neighbor.
• Equipment and incentives change constantly. Panel and inverter models, utility rate schedules, net-metering rules, and tax-credit and rebate paperwork shift year to year. The system that captures a project has to flex with equipment and incentive changes instead of hard-coding last year's assumptions.

What the off-the-shelf tools get right — and where they stop

There are good tools in this space. Aurora and OpenSolar produce accurate designs and proposals. The financing portals handle their own loan applications well. A general CRM tracks leads and contacts. For the slice each one owns, they work. The cracks show up in three patterns:

A stack of tools with no project layer. The design lives in Aurora, the contact lives in the CRM, the loan lives in the finance portal, the permit status lives in a spreadsheet, and the install date lives on a whiteboard. The project that ties all of those together — this homeowner, this system, this permit, this loan, this install — exists only in the head of whoever is running operations. When that person is out, the pipeline goes dark.

No native model for permitting and interconnection. The two stages where solar jobs actually get stuck are the two stages no generic tool tracks well. A CRM has a deal stage called “in progress”; it does not know that a permit was submitted on the 3rd, kicked back for a structural revision on the 11th, and is now sitting in plan review again. That detail — who owns it, what it is waiting on, how long it has waited — is exactly what the office needs and exactly what the spreadsheet cannot keep current.

Financing milestones that fall through the cracks. The loan funds when you hit the milestone and submit the proof. But the milestone lives in the project, the submission lives in a partner portal, and the reconciliation lives in someone's memory. Installers routinely complete a milestone and forget to trigger the funding for days or weeks — an interest-free loan to the finance company that the business never meant to make.

What custom software for a solar installer typically includes

Most builds we scope cluster around the same core set of modules. The exact mix depends on whether the company self-installs or uses subcontract crews, how many AHJs and utilities it works across, and which financing partners it carries. The recurring pieces:

• Project pipeline — every job modeled as a sequence of stages from site survey through permission to operate, with the responsible owner, the due date, and the blocking item visible for each. The office sees the whole portfolio at a glance and knows exactly which jobs are stuck and where.
• Permitting tracker — submission dates, AHJ contacts, plan-review status, revision requests, approval and expiration dates, and the permit documents themselves, so a permit that is about to expire or has gone quiet surfaces on a report instead of as a missed deadline.
• Interconnection tracker — the utility application, supplemental review, approval to install, and permission to operate, each with its date and document, so the stage that most often stalls a project is the one the office watches most closely.
• Financing milestone management — the loan, its funding tranches, the milestone each is tied to, and whether the proof has been submitted and the money received, so completed milestones get funded the day they are hit, not the week someone remembers.
• Crew and install scheduling — a schedule that accounts for crew capacity, permit-ready jobs, equipment availability, and travel, with a flag when an install is booked before the permit is actually in hand.
• Site survey and design hand-off — a clean path from the surveyed roof and the engineered design into the permit package and the install plan, so the system sold, the system permitted, and the system installed are provably the same system.
• Document hub — every permit, plan set, inspection report, interconnection letter, contract, and change order attached to the project, so the packet a financing portal or an inspector wants is assembled from the job, not hunted across email.
• Homeowner status portal — a simple, branded page where the customer sees exactly where their project stands and what comes next, cutting the where-is-my-system calls and protecting the referral.
• Equipment and inventory — panels, inverters, racking, and batteries tracked against jobs, so a delayed install caused by a missing inverter is something the office sees coming instead of discovering on install morning.
• Owner reporting — jobs by stage, average days from sold to PTO, where projects stall and for how long, financing dollars funded vs. earned, and install throughput by crew, so the bottlenecks in the pipeline are measured instead of guessed.

None of these features is unique to custom software in the abstract. The point of building custom is that all of them work the way your company runs — your AHJs, your utilities, your financing partners, your install model — in one system, without the manual pipeline tracking and milestone reconciliation that comes with stitching half a dozen tools together.

The pipeline tracker is where the build pays for itself

The most undermanaged part of a growing solar company is the project pipeline between sold and PTO. A spreadsheet works for a handful of jobs. It does not work for sixty active projects, each in a different stage, each waiting on a different AHJ or utility, each tied to a financing milestone that funds on submission. The day the spreadsheet breaks is the day a permit quietly expires, a ready-to-fund milestone sits for three weeks, and an install crew shows up to a job whose permit was never approved.

A real pipeline tracker makes visibility the default output of the work. Each project carries its stage, its blocking item, its responsible owner, and its dates. When a permit is approved, the install becomes schedulable. When the install passes inspection, the interconnection clock starts and the install milestone becomes fundable. The office stops reconstructing the portfolio every Monday and starts working the jobs that are actually stuck. That recovered time, the permits that stop expiring, and the milestones that fund on schedule are, for most installers, the clearest line from a custom build to a return on it.

Days-from-sold-to-PTO is the number the tools hide

A solar company's real health is not how many systems it sold this month — it is how fast a sold system becomes a producing, funded one. The number that decides cash flow and customer satisfaction is days from sold to permission to operate, and where in that span the time actually goes. Most tools can tell an owner how many deals closed. Far fewer can tell the owner that permitting in one county averages three weeks longer than another, that one utility's interconnection queue is quietly adding a month to every job, or that the install-to-inspection gap is the real bottleneck rather than the permit everyone blames.

Custom software can treat the pipeline as the core asset it is — measure cycle time stage by stage, surface where jobs stall by AHJ and by utility, tie funded dollars to completed milestones, and give operations a board that reflects the regulated reality of the work instead of a generic deal stage. That is the difference between selling systems and running a solar business.

Who benefits most from a custom build

Not every installer needs custom software. The ones that benefit most have at least two of the following:

• A growing project volume — dozens of active jobs at once — where permitting, interconnection, and financing status have outgrown a spreadsheet and a whiteboard.
• Work across multiple AHJs and utilities, each with its own permit and interconnection process, where a single generic stage cannot capture where a job actually is.
• Several financing partners with milestone-based funding, where completed milestones routinely sit un-submitted and cash gets left on the table.
• A stack of disconnected tools — a design tool, a CRM, finance portals, a permit spreadsheet, and QuickBooks — where operations is the human integration layer holding it all together.
• A homeowner-experience problem, where the three-month gap between signing and switch-on is generating status calls and putting referrals at risk.
• A reporting gap the owner can feel but cannot quantify — days from sold to PTO, where jobs stall, and funded vs. earned dollars are on no dashboard, so operational decisions are made on instinct.

If a company is brand new or installing a handful of systems a month in a single jurisdiction, the off-the-shelf tools plus a spreadsheet are almost always the right answer. Custom software is most useful when the project volume, the number of AHJs and utilities, the financing complexity, and the disconnected tools have grown to the point where the manual tracking starts costing real money — and real referrals — every month.

What a build looks like in practice

We start with the workflow, not the screens. Before any code is written, we map the actual operation: how a sold deal becomes a site survey and a design, how the permit package gets assembled and submitted, how interconnection is filed and tracked, how the install gets scheduled against permit-ready jobs and equipment, how inspections and PTO close out the job, and how each financing milestone gets hit, proven, and funded. The custom software is built around that map.

Most solar builds ship the core operation first — the project pipeline, permitting and interconnection tracking, crew scheduling, and a homeowner portal — and add financing reconciliation, design-tool and CRM integrations, inventory tracking, and full accounting sync in later phases. That sequencing keeps the project tight and gets the business value into operations early.

Fixed price. No hourly billing. The scope and cost are agreed before any code is written, and we build against that scope.

Frequently asked questions

If your solar company has outgrown the stack you started on, start with a conversation. We will scope the workflow before talking about a build.