How to Build Solar Installation Management Software

Most solar companies manage their projects across a combination of spreadsheets, a generic CRM, and email threads with subcontractors. That works at 10 installations per month. At 50 or 100, it breaks. Projects stall in permitting because nobody sent a follow-up. Equipment arrives at the wrong job site because the order was placed from an outdated proposal. Homeowners call asking about their system status and nobody has a quick answer.

According to the Solar Energy Industries Association (SEIA), the US installed over 32 gigawatts of solar capacity in 2023, with residential and commercial installation volume continuing to grow. The installers who can process 50+ jobs per month without adding headcount are the ones with software that covers the full lead-to-PTO pipeline, not just scheduling and invoicing.

Solar installation management software solves this. But building it is more specific than most "field service management" tools. Solar has unique regulatory requirements, specialized design tools, and a multi-month approval process that most other trades do not face.

This article covers the six modules that make up the system, the hardest engineering problem (permitting), and realistic costs.

What solar installation software actually manages

Solar projects follow a fixed sequence: homeowner lead, site assessment, system design, proposal, signed contract, permit submittal, permit approval, interconnection application, installation, final inspection, utility meter upgrade, Permission to Operate. The US Department of Energy's Lawrence Berkeley National Laboratory has tracked residential solar project timelines for over a decade. Their data shows the average time from contract to PTO for residential systems runs 3-4 months, with permitting and interconnection consuming the majority of that time in most jurisdictions.

Each step has data, documents, and dependent actions. The software needs to track all of them in a single record per project and surface what needs attention.

Generic field service tools handle scheduling and invoicing. They do not handle permit status per jurisdiction, interconnection agreement workflows, or the link between a design tool's production estimate and a signed proposal.

That specificity is why solar companies build custom or use specialized tools.

Module 1: Lead and proposal management

A homeowner lead enters the system through a web form, a referral, or a canvassing app. The system records contact details, property address, utility company, and average monthly electric bill.

From there, the sales workflow runs inside the platform:

• Site assessment scheduling and notes

• System design data pulled from Aurora Solar or Helioscope (panel count, system size in kW, estimated annual production in kWh/year)

• Proposal generation with production estimate, estimated savings, and payback period

• Financing options (loan, lease, PPA, cash) with payment amounts

• Digital signature and contract execution

The proposal is the most important document in the project. It sets customer expectations on output, savings, and payback. It documents the incentives the customer qualifies for. It becomes the basis for the permit application.

Module 2: System design integration

Aurora Solar and Helioscope are the two dominant tools for solar system design. They use satellite imagery and irradiance data to model how a panel array on a specific roof will perform over a year.

Do not rebuild these tools. Both offer APIs.

Pull the following data from the design file into the project record:

• System size (kW DC)

• Panel model and count

• Inverter model and type (string, microinverter, power optimizer)

• Estimated annual production (kWh/year)

• Shading loss percentage

• Financial model (cost per watt, gross cost, incentive amounts, net cost)

When the design changes, whether the site assessment reveals a different roof condition or the customer wants a larger system, the update in Aurora or Helioscope should sync back to the project record and mark any generated proposal as outdated.

Module 3: Permitting and interconnection tracking

This is the module that separates a real solar platform from a generic CRM.

Every solar installation requires two regulatory approvals before the system can turn on:

1. A local building permit from the Authority Having Jurisdiction (AHJ), which is the city, county, or municipality where the property sits
2. A utility interconnection agreement, which ends with Permission to Operate (PTO) from the utility

The permit covers the structural and electrical work. It requires a permit application, engineered drawings, and often a site plan showing the panel layout. Some jurisdictions accept ePlan submissions through an online portal. Others require paper plans delivered in person. Review times range from 3 days to 6 weeks.

The interconnection agreement is a separate application to the utility. The utility reviews the proposed system to confirm it meets grid connection requirements. Conditional approval allows installation to proceed. PTO is issued after the utility inspects the final installation and upgrades the meter.

The system needs to track:

• Permit status: applied, under review, approved, approved with conditions, permit pulled, final inspection scheduled, final inspection passed

• Interconnection status: applied, conditional approval received, installation complete submitted, PTO received

• Permit number and jurisdiction contact

• Documents submitted and documents outstanding

• Submission dates and expected response dates

Module 4: Installation scheduling

Once permits are approved and equipment is ordered, the installation crew is scheduled. Solar installations typically run in phases:

1. Site preparation (roof evaluation, conduit run marking)
2. Roof installation (racking, panel mounting)
3. Electrical rough-in (conduit, wiring, inverter mounting)
4. Rough-in inspection
5. Utility meter upgrade (coordinated with the utility)
6. System commissioning and functional test

Each phase has dependencies. The rough-in inspection must pass before commissioning. The utility must schedule a meter upgrade before PTO can be issued. The scheduling module must support multi-phase jobs, dependency tracking, and crew assignment per phase.

The module also handles subcontractor coordination when a solar company uses external electricians or roofing contractors for portions of the work.

Module 5: Equipment tracking

Every installed component needs to be recorded in the project record:

• Panels: manufacturer, model, quantity, serial numbers

• Inverter: manufacturer, model, serial number

• Racking system: manufacturer, model

• Battery storage (if applicable): manufacturer, model, capacity (kWh), serial number

Serial numbers are not optional. They are required for warranty claims, insurance documentation, and monitoring platform registration. The system should capture serial numbers at delivery, via barcode scan or manual entry, and confirm that the delivered equipment matches the approved permit set.

If a panel model differs from what was permitted, the project needs a permit revision before installation proceeds. Catching this at equipment delivery is far cheaper than after the panels are on the roof.

Module 6: Incentive tracking

Solar projects qualify for multiple financial incentives. Track them per project:

• Federal Investment Tax Credit (ITC): 30% of the installed system cost, claimed on the homeowner's federal tax return

• State rebates: varies by state. Some states offer per-kWh rebates, others offer flat rebates up to a cap

• Utility incentives: some utilities offer additional bill credits or upfront rebates

• SREC eligibility: in states with Solar Renewable Energy Certificate programs, the homeowner earns one SREC per 1,000 kWh generated. SRECs are sold in a secondary market. Track the state program, the homeowner's estimated annual SREC generation, and the steps to register the system

Document the full incentive stack in the proposal. Homeowners make purchase decisions based on the net cost after incentives. Getting the incentive calculation wrong creates disputes after the sale.

The hardest problem: jurisdiction-level permitting logic

Permitting is where solar projects go to slow down. RaftLabs has built project management platforms for regulated industries, and the pattern is consistent: teams underestimate permitting complexity at the architecture stage, then spend months retrofitting tracking logic they should have designed from day one.

"Permitting and interconnection delays are the single largest contributor to soft cost inflation in residential solar. Until the industry systematically digitizes these workflows, installers will keep spending more on project coordination than on the installations themselves." - Joachim Seel, Research Scientist, Lawrence Berkeley National Laboratory, from the 2023 Tracking the Sun annual report on US solar market trends.

A 90-day project and a 180-day project often have identical scopes. The difference is permitting, specifically how well the installation company manages the submission process for each jurisdiction.

The core problem: every AHJ has different requirements. One city requires engineered stamped drawings. The neighboring county accepts a standard pre-approved permit package for systems under 10 kW. A third jurisdiction switched to ePlan six months ago but nobody updated the company's internal process. The utility interconnection portal changed its form requirements in January.

Without a system, this knowledge lives in the heads of the permitting coordinators. When someone leaves, it walks out the door.

The solution is a jurisdiction database inside the platform:

• One record per AHJ (city, county, municipality)

• Required documents per AHJ (permit application, structural calcs, single-line electrical diagram, site plan, specification sheets)

• Submission method (ePlan portal URL, physical address for paper submission, or both)

• Typical review timeline in business days

• Notes on known requirements or quirks

The system generates a permit submission checklist per project based on the AHJ. When a permit application has been submitted but no response has been received after 14 days, the system sends an automated follow-up reminder to the permitting coordinator.

This is not a complex feature architecturally. It is a database table and a reminder queue. But in practice it is the difference between a 90-day project and a 180-day project. Solar companies that build this systematically and keep the jurisdiction data current close significantly more jobs per crew per year than those that do not.

Build vs. buy

Off-the-shelf options:

• JobNimbus ($100-$200/month per user): a general-purpose field service CRM. Works for small solar companies. Does not handle permitting, interconnection tracking, or design tool integration natively.

• OpenSolar (free design tier, paid project management): strong on proposal generation, limited on post-sale project tracking.

• Salesforce Solar Cloud: enterprise pricing, requires significant implementation, strong if you already run on Salesforce.

When to build custom:

• You are installing 50+ systems per month and off-the-shelf tools create manual handoffs at every stage

• You are building a software product for solar installers, a platform business rather than an internal tool

• You need custom jurisdiction logic for a specific geography

• You have a homeowner portal or financing integration that generic tools do not support

Timeline and cost

MVP (lead to PTO pipeline, permitting tracker, equipment records, basic scheduling):

• Cost: $140,000-$230,000

• Timeline: 14-18 weeks

• Team: 2 senior backend engineers, 1 frontend engineer, 1 designer, 1 project manager

Full platform (design tool integrations, monitoring connections, automated jurisdiction rules, homeowner portal, SREC tracking):

• Cost: $270,000-$440,000

• Timeline: 22-30 weeks

• Running infrastructure: $500-$2,000/month at typical scale

The highest-value module to build first is permitting and interconnection tracking. It has the most direct impact on project cycle time, which is the primary bottleneck for solar companies trying to scale.

RaftLabs builds field service and SaaS platforms. See our SaaS platform engineering service or talk to us about your build.