Solar installer software buyer's guide: what to check before you switch

First: which kind of solar software are you actually shopping for?

"Solar software" is five different categories wearing one name, and buying the wrong category is the most common mistake in this trade. Design and engineering tools produce plan sets. Proposal and sales tools close deals. Monitoring platforms watch production. Utility-scale O&M suites manage hundred-megawatt assets for owners, not contractors. And field-service software — the category this guide covers — runs the operation: crews, schedules, permits-on-the-job, service visits, and billing.

You may legitimately need two or three of these. What sinks shops is buying one and assuming it does the others' jobs — a proposal tool with a "service module" bolted on will not run your O&M book, and a utility-scale CMMS will bury a 25-person contractor in fields nobody fills in. If your pain is crews, gates, paperwork, and a whiteboard service book, you're shopping for solar field service software. That's this guide.

Before you shop: name the moment that started this

The most expensive buying mistake after wrong-category is shopping for features instead of for the pain. Write down the single moment that sent you looking. In solar it's usually one of three: a crew sat parked outside a job whose permit hadn't cleared; a warranty call took an afternoon of archaeology; or the O&M whiteboard missed a contracted visit and the customer noticed first.

Judge every vendor against that moment. And take the trade press's advice about how to run the evaluation: involve your field crews before signing, and use the trial to run a complete real job cycle, not a tour of dashboards.

The selection checklist for solar operations

Nine areas separate solar installer software that fits this trade from a generic tool bent to fit. Score each vendor 0–3 per area with the matrix below.

1. Install workflow with real dependencies

• Multi-step projects — survey → engineering → permit → install → inspection → interconnection → activation — with predecessor rules that gate scheduling?
• Does a cleared permit pull downstream steps forward automatically?

2. Permits and paperwork on the job

• Permit applications, AHJ results, interconnection forms stored on the work order, versioned, visible from the truck?
• Per-step status so "waiting on AHJ, day 9" is a glance, not a phone call?

3. Crew scheduling and dispatch

• Crews as assignable units with designated leads, not only individuals?
• Explainable assignment with visible reasons, working from day one, no training period, no black box?
• Fair-rotation rules across crews?

4. Field capture that works offline

• Per-array results, photos, and deficiency lists captured without signal — rooftops, attics, steel-walled commercial sites?
• Native iOS and Android, not a wrapped web view?

5. Per-array asset tracking and maintenance schedules

• Every system's panels, inverter, battery — model, serial, install date, warranty — on the customer's site record?
• Maintenance schedules generated from service contracts, feeding dispatch automatically?

6. Warranty claim support

• Coverage answerable in minutes from the asset record?
• Claim evidence — fault codes, measured values, photos — assembled from the job's own records?

7. What the customer sees

• Portal quote approval with engineering documents attached?
• Milestone status — permit, install date, inspection, activation — without calling your office?

8. Office and billing in the same flow

• Job-to-invoice without re-keying; recurring billing for maintenance contracts?
• Two-way accounting sync, and ask exactly what happens when a sync fails?

9. Setup, migration, and support

• Setup measured in days, configured by your admin, no developer?
• Who imports your customers, sites, installed-base records, and history — them or you?
• Real humans through the pilot, not only a ticket queue?

Questions that cut through any vendor's demo script

• "Show me a project where the permit hasn't cleared — can I even schedule the install crew?"
• "Walk me through a warranty call: six-year-old system, inverter fault. How fast do I know what's on the roof and whether it's covered?"
• "Run a site survey on the mobile app in airplane mode — photos, measurements, notes — and show me the sync."
• "Show me the O&M book: every contracted maintenance visit for the next 90 days, generated from the contracts."
• "What's the all-in monthly cost at my headcount twelve months from now, including the tier that has the features you showed me?"

Red flags, and what each costs later

1. The wrong category in disguise. A proposal tool's "operations module" or a monitoring platform's "ticketing" is a side feature, not an operating system. You'll be back shopping in a year, with migration pain added.
2. Projects without service, or service without projects. Solar needs both halves — installs are dependency-gated projects, O&M is recurring jobs — against the same customers and equipment. Two tools means paying the re-keying tax on every activation, forever.
3. The demo tier isn't the priced tier. Per-user entry pricing that triples once the shown features turn on is the category's oldest trap. Price your 12-month headcount, all-in.
4. A wrapped web view sold as a mobile app. If it needs signal, it doesn't work where solar work happens.
5. "AI" nobody can explain. If the vendor can't show why an assignment was made, your dispatcher can't defend it — and you can't tune it. Ask for the reasons on every match.
6. No migration help. Your installed-base records are the whole value of switching. If "who imports my data" gets answered with a CSV spec, budget the pain into the price.
7. Core features gated behind an enterprise tier. API access, custom reports, and audit logs are how a growing shop runs — not luxury add-ons.

The self-scoring matrix

Copy this table. Score each shortlisted vendor 0–3 per area (0 absent, 1 partial, 2 solid, 3 fully covered), and score "the way you do it today" as its own column, because the status quo is a vendor too.

The gap between your status-quo column and the leading vendor is the value on the table. Small gap: stay put, honestly. Large gap: that's your business case, in your own handwriting.

Switching without blowing up install season

Phase 1 — import and configure (days). Customers, sites, installed-base and asset records come across; you set job types, crew structures, cadences, and dispatch priorities to match how the shop already runs. No developer.

Phase 2 — pilot with one crew. Pick a respected crew lead, not the newest hire. Run their real jobs — a survey, an install step, a maintenance visit — for a week or two while everyone else stays on the old setup. Show the app working in airplane mode first; that single demonstration defuses most of the field's resistance.

Phase 3 — full rollout. Once the pilot crew is faster on the new tool than the old one, move the board and bring the portal live. Keep the old spreadsheets readable, not active, for a few weeks.

Phase 4 — archive and shut off. When nobody's opened the old tool in a week, export a final archive and turn it off.

Plan real hours — a sensible transition takes sustained owner attention across several weeks, and underestimating switching costs is one of the most common contractor mistakes. Vendors who promise zero effort are hiding the effort somewhere.

How FSM Navigator™ scores

Run us through the same nine rows — here's where the gap usually shows for solar shops.

The install workflow and the service book are one system by architecture: dependency-gated projects with permits and inspections riding the work order, flowing into per-array assets and contract-generated maintenance schedules the day a system activates. Intelligent Dispatch handles crews as first-class units, matches the right technician or crew to every job in under 30 seconds with visible reasons, and works from day one — no training period, no black box. The mobile app is native and offline-first; field capture is per-array results, photos, and deficiency lists. Teams typically see around 20-30% less drive time, multiplied by crew size on install work.

Setup is measured in days, imports included. For the long version, read how a solar installer turned its installed base into a service business; for the field-capture standard your survey crews should hold, start with the solar site survey checklist; and for everything in one place, the solar industry page.

Score us against your own checklist — start your free trial, 5 users free, no card required.

Sources

• Contractor Magazine — What Contractors Get Wrong When Choosing Field Service Software (June 2026)