The deal closes on a Thursday. Your sales CRM marks it won, the rep gets paid, and operations gets a PDF and a phone number. From there it's a spreadsheet for permits, texts with the crew lead, and a shared drive of roof photos that nobody can find in six months. Two years later the homeowner calls about an inverter fault. The rep has left. Nobody knows which inverter went on that roof, whether it's still under warranty, or who installed it. Most solar CRM software is built to win the deal. The hard part of solar starts after the deal is won, and it lasts 25 years.
What solar CRM software does well, and where it stops
A good solar sales CRM tracks leads, builds proposals, runs financing, and gets a signature. It's the right tool for the pipeline.
It usually stops there. That leaves operations carrying the customer through:
- A site survey and final design
- Permits and utility interconnection
- A multi-day install with more than one crew
- Inspection and permission to operate
- Commissioning and the as-built record
- Twenty-plus years of service, warranty claims and monitoring alerts
- The battery, EV charger or expansion the homeowner buys in year three
Each of those stages generates information. If it lives in five places, you lose it.
The seven stages after the signature
1. The handoff
Sales passes the deal to operations. This is where most information gets lost. Handle it with a standard checklist, not a chat message (see below).
2. Site survey and design
Roof condition, electrical panel capacity, shading and access. All of it needs photos and notes attached to the customer, not to the surveyor's phone. If the design changes after the survey, the record should show which version the crew is building to.
3. Permits and interconnection
Permit numbers, utility application status and inspection dates. These need to sit on the project, visible to whoever schedules the crew, so nobody books an install that can't start. Treat permit and utility applications as steps with an owner and a status, not as dates in someone's notebook.
4. Install
Multi-day work with crews, not individual techs, and materials staged by project. Crew scheduling is its own discipline, and it's where a missed permit or a late delivery costs the most, because a whole crew is waiting on it.
5. Inspection and permission to operate
Dates, results and any corrections. A failed inspection that sits in someone's inbox delays the homeowner's first power bill savings, and that's the moment they start to regret the purchase. Corrections should become work with a date, not a note.
6. Commissioning and the as-built record
This is the stage most installers underinvest in. What actually went on the roof: panel, inverter and optimizer serial numbers, string layout, monitoring account, and photos of the finished wiring and array. This record is what every future service call depends on.
7. Service life
Scheduled maintenance, monitoring alerts, warranty claims, and the eventual inverter replacement. The National Laboratory of the Rockies (formerly NREL) publishes a full best-practices guide for operations and maintenance of PV and storage systems, with the stated goal of reducing the cost and improving the effectiveness of O&M. O&M is its own discipline, not an afterthought to the install. Our guide to solar warranty service tracking goes deeper on the claims side.
The handoff checklist: what operations needs from sales
Make these required before a deal can move to operations:
- Homeowner contacts, with the preferred contact method and who is authorized to approve changes
- The signed contract and final design, with system size and equipment models
- Financing type and any lender or utility program requirements
- Site survey photos and notes: roof, panel, access and pets
- Promises made during the sale, such as timing, trenching, or panel placement preferences
- The utility account and rate plan the savings were calculated on
"Promises made during the sale" is the line that prevents the most angry calls. Write it down.
A checklist only works if something enforces it. The simplest rule: operations doesn't accept a deal, and sales doesn't get credit for it, until every line is filled in. It feels bureaucratic for about two weeks, and then it stops the calls that start with "but the rep told me."
What the customer record needs after the sale
Whatever system holds it, the post-sale record for each customer should have:
- The as-built system: every component with its model and serial number, its location on the roof, and install date.
- Warranty terms by component: manufacturer product and performance warranties, plus your own workmanship warranty, with start and end dates.
- Permit, utility and inspection history, with the documents themselves, not just the dates.
- Photos: before, during and after, organized by stage.
- The monitoring account, plus who gets alerts.
- Every service visit, with what was found and what was replaced.
When a fault comes in, the dispatcher should be able to see the equipment, its warranty status and the last visit before choosing a tech. That's the difference between sending the right tech with a replacement inverter under warranty and sending someone to look.
The revenue after the sale
Here's an illustrative example. Say you've installed 600 systems over four years. That base generates:
- Service calls: inverter faults, monitoring alerts, storm checks, roof work that needs panels removed and reinstalled.
- Maintenance plans, if you offer them.
- Add-ons: batteries, EV chargers and expansions, sold to homeowners who already trust you.
- Referrals, from customers whose systems have been easy to own.
None of it happens reliably if the record from stage 6 doesn't exist. A homeowner is much more likely to buy a battery from the installer who answered their inverter call in a day than from the one who couldn't find their serial numbers.
It also changes how you sell. When the record shows a homeowner's inverter warranty ending next year, or a system that was sized before they bought an EV, the add-on conversation starts from something true about their house instead of a generic offer.
One system or two?
You don't have to replace your sales CRM to fix this.
- If your pipeline works, keep it. What you need is a system that picks up at the signature and runs everything after: install stages, the as-built record, service and warranty.
- If your CRM is also trying to run installs and service, that's usually where the spreadsheets come from.
If you do run two systems, decide which one owns what. The sales CRM owns the lead and deal. The operations system owns the project, equipment and service history. Customer details flow one way at the handoff, so nobody edits the same address in two places. For the operations side of that decision, see our solar installer software buyer's guide.
Where FSM Navigator fits
FSM Navigator picks up where most solar CRM software stops:
- Installs as work orders with dependent steps. The survey, permit, install, inspection and interconnection each become a step on the work order, and a step stays blocked until the step it depends on is done. Single-day maintenance and emergency calls run on the same board.
- Permits, utility approval and inspections as steps, with the paperwork attached. The permit, inspection result and utility approval are stored as documents on the work order. The solar install workflow page walks through it.
- Photos on the job. Crews photograph roof conditions, panel layouts and wiring runs from the mobile app, and the photos stay with the job.
- Equipment, serials and warranties. Track panels, inverters, racking and optimizers as equipment at the customer's location, with serial numbers, install dates and warranty terms recorded per component.
- Maintenance. Recurring maintenance jobs generate on the schedule you set. Maintenance agreements, if you sell them, keep each customer's coverage, renewal date and fee on record.
- Your sales CRM, connected. Enterprise includes a REST API, so a developer can create the customer and first job from a closed deal instead of someone retyping it.
Work orders, equipment tracking, warranties, equipment-linked agreements and the API are Enterprise features; customer and site agreements start on Pro. Build the as-built record for your next install from day one, and the service call two years from now starts with the answer instead of a search.