Solar Software Development: Custom vs. Off-the-Shelf for Installation Companies

Your permitting coordinator keeps a personal notebook. It tracks which AHJs accept ePlan submissions, which ones still want paper, which utilities take six weeks to respond and which take six months. That notebook is your business continuity plan. When she leaves, 40% of your operational knowledge walks out the door.

You are at 60 jobs a month. Three crews. Two installers who showed up to a job site last Tuesday before the rough-in inspection was approved, costing you a half-day of labor to send them home and reschedule. A homeowner calling every three days asking when her system will turn on, and nobody on your team can give a straight answer without checking four different places.

This is the point where you start seriously evaluating custom solar software development. You have probably already run trials of Scoop Solar, SolarNexus, and JobNimbus. Each handles part of the job. None handles all of it - specifically not the jurisdiction-level permit logic, the interconnection tracking tied to your actual dispatch queue, or the real-time homeowner portal you promised in your last 20 sales conversations.

Here is what it actually costs, when it makes financial sense, and where builds go wrong.

What custom solar software development costs

Infrastructure after launch runs $500-$2,000 per month at typical mid-market scale. These numbers cover a custom platform built to your specific workflow. They do not include your time, internal QA, or staff training.

Scoop Solar, SolarNexus, and JobNimbus vs. custom software

This is the most important question in solar software development: what do you already have, and where exactly does it break?

Scoop Solar is purpose-built for residential and commercial solar installers. It covers lead management, proposals, permit packages, installation workflows, and some interconnection tracking. For a company doing 10-40 installs per month on a standard residential mix, it is genuinely good software. The ceiling appears when you need custom jurisdiction rules, multi-state AHJ logic, or when your workflow has diverged enough from the standard residential template that you're constantly bending Scoop to fit rather than the other way around.

SolarNexus is well-suited for commercial pre-construction: project tracking, proposal management, and job costing for larger commercial and ground-mount projects. Where it struggles is residential volume at scale and the kind of real-time homeowner visibility that residential customers increasingly expect. It is also priced for commercial projects, which makes the per-job cost high for companies running a residential-dominant book.

JobNimbus is a general-purpose field service CRM used by roofing, solar, and HVAC contractors. It handles contacts, jobs, tasks, and invoicing competently. It does not handle permit status per jurisdiction, interconnection tracking, or design tool API integration. Many solar companies use it at 10-30 jobs per month and outgrow it when permitting coordination becomes a daily fire.

The threshold for custom solar contractor software:

• You are processing 50+ installs per month and your permitting coordinator spends more than 10 hours a week on manual follow-up that software should handle

• You operate in multiple states with meaningfully different AHJ requirements, and your team maintains inconsistent local knowledge of each jurisdiction

• You need a homeowner portal where customers can check permit status, installation date, and system activation in real time - branded to your company

• You are building a software product for solar installers as a business, not just an internal tool

• Your current tools require manual handoffs between three or more platforms to move a job from signed contract to Permission to Operate

The break-even math is straightforward. If a permitting coordinator earns $55,000 per year and spends 30% of their time on tasks software would eliminate, that is $16,500 per year in direct labor before you count rescheduled crews and extended project timelines. A $140,000 MVP pays for itself in under 4 years on labor alone at 50 jobs per month. At 100 jobs, the payback period drops closer to 2 years.

Who actually builds custom solar installation software

Not every solar company should go custom. Here are four scenarios where it makes clear financial sense.

Installers at 60+ jobs per month with multi-crew dispatch. At this volume, crew scheduling tied to live permit status stops being a nice-to-have. A crew arriving at a job site before the rough-in inspection is approved costs you a half-day of labor minimum, plus the reschedule overhead. You need dispatch logic that reads actual permit status, not dispatch logic that relies on someone manually checking a shared spreadsheet before releasing the crew for the day.

Multi-state contractors with divergent AHJ requirements. If you operate in California, Arizona, and Florida, you are dealing with three meaningfully different permitting environments. California has city-by-city rules and SolarAPP+ adoption varies by municipality. Florida has its own inspection flow and utility interconnection timelines. Arizona utilities respond on different schedules than East Coast utilities. Maintaining this in a spreadsheet or inside a tool not built for it means you are paying a human to do what a jurisdiction database with automated logic should handle.

Software companies building for the solar industry. If your product is a platform that other solar contractors will pay to use, you need full control over the codebase, the data model, and the product roadmap. You cannot build a viable SaaS product on top of Scoop Solar or SolarNexus. You need your own architecture from the start, with the ability to ship features on your own timeline rather than waiting on a vendor's release cycle.

Companies that promised a homeowner portal. Residential solar customers expect self-service visibility. They want to see permit status, installation date, system activation, and production data without calling your office. None of the off-the-shelf field service tools give you a branded homeowner portal you can actually customize, integrate with your specific monitoring hardware, and iterate on based on customer feedback. Custom solar software development does.

V1, V2, and V3: how solar software gets built in phases

No solar operator should attempt to build everything at once. Here is how the build phases over time.

Phase 1 (V1) - $140K-$230K, 14-18 weeks: The core operational pipeline.

The goal of Phase 1 is to get your entire project lifecycle into one system. Everything from signed contract to PTO, tracked in one place, with no manual handoffs between tools.

What ships in V1:

• Lead intake and CRM (contact, property address, utility company, monthly electricity bill)

• System design data pulled from Aurora Solar or Helioscope via API (panel count, system size, production estimate, financial model)

• Proposal generation with financing options, system specs, and digital signature

• Permit tracking per project: status, documents submitted, submission date, expected response date

• Interconnection tracking: conditional approval, installation complete submitted, PTO received - as two separate status threads

• Crew scheduling with job phase tracking (site prep, roof install, rough-in, electrical, commissioning)

• Equipment serial number recording at delivery, matched against the permitted spec

• Basic reporting: jobs by status, jobs past target permit date, jobs waiting on PTO

Phase 1 gives you the full lead-to-PTO pipeline in one system. It eliminates the shared spreadsheet and the inter-app manual handoffs that lose time and create errors. At 50+ jobs per month, that alone recovers roughly 15-20 hours of coordination time per week across your team.

Phase 2 (V2) - $80K-$120K additional, 10-14 weeks: Jurisdiction intelligence and homeowner visibility.

• Jurisdiction database: one record per AHJ with document requirements, submission method, typical review timeline, and known local quirks

• Automated permit follow-up queue: if a permit application has been submitted with no response in 14 business days, the system flags it and queues a follow-up task for the coordinator

• Homeowner portal: permit status, scheduled installation date, system activation status, and production data pulled from the monitoring integration

• Monitoring integration: production data from Enphase Enlighten, SolarEdge Monitoring, or similar via API

Phase 3 (V3) - $100K-$160K additional, 12-16 weeks: Multi-state scale and incentive tracking.

• Multi-state AHJ rules engine with automated document checklist generated per jurisdiction and project type

• SREC tracking: which projects qualify, estimated annual generation, registration steps per state program

• Third-party financing integration: loan origination status from GreenSky, Mosaic, or similar lenders

• Fleet optimization: crew routing, multi-job day scheduling, drive time estimates

• Automated utility portal submissions where the utility's system accepts them

Where solar software development projects fail

Two failure modes account for most of the budget overruns and abandoned builds in this space.

Permitting complexity underestimated at the architecture stage. Teams scope the permit module as a simple status field: applied, approved, final. Then, six weeks into development, they realize that some AHJs have six sub-statuses. Some require specific document formats or notarized signatures. Some have different timelines for residential vs. commercial. Some send email confirmations; others update an online portal that requires manual checking. Some require the permit placard to be physically on-site before installation starts. Retrofitting jurisdiction logic into a data model not designed for it is expensive and slow. The right call is to design the jurisdiction database with full AHJ-level detail in Phase 1, not to add it later.

Interconnection and permit tracking collapsed into a single workflow. They are not one thing. The local building permit and the utility interconnection agreement run on separate timelines, with separate contacts, separate documents, and separate approval steps. A project can have an approved building permit and still be four months away from PTO because the utility's interconnection queue is backed up. Conflating them in your data model means you cannot give accurate status updates to homeowners, cannot correctly sequence your installation crews, and cannot report accurately on where your pipeline is stalled. Design them as two independent status threads from the start.

How RaftLabs approaches solar software development

RaftLabs has built field service and SaaS platforms for regulated installation businesses - including multi-phase job tracking, jurisdiction-specific compliance logic, real-time status portals, and API integrations with design and monitoring tools.

The first call covers four things: your current tool stack and where the handoffs break, job volume today and your 18-month projection, the specific AHJs you operate in and how complex your permit workflows are, and whether Phase 1 is an internal tool or the beginning of a SaaS product.

If Phase 1 is not the right move yet, we will say so. Some companies at 30-40 jobs per month are better served by a structured Scoop Solar or JobNimbus implementation before they are ready to invest in custom solar contractor software.

"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 Tracking the Sun annual report on US solar market trends.

Three data points that put the opportunity in context:

According to Lawrence Berkeley National Laboratory's Tracking the Sun dataset, the average residential solar project takes 3-4 months from signed contract to Permission to Operate, with permitting and interconnection consuming the majority of that window. Companies that reduce this cycle time through software gain a direct margin advantage as hardware costs compress.

The Solar Energy Industries Association (SEIA) reported over 32 gigawatts of US solar capacity installed in 2023 - a figure growing year over year - which means the volume problem for mid-market installers is only getting larger, not smaller.

The US Department of Energy's soft cost tracking program has documented that permitting, inspection, and interconnection represent 10-20% of total residential solar project cost - a category where software investment has a direct payoff.

If you are at 50+ jobs per month and the operational problems are concrete, see our SaaS platform engineering service or start with a scoping call.