All articles

Custom CRM

Solar CRM vs Field Service Software: 56 to 1

A solar job runs about 112 days from contract to PTO and puts a crew on the roof for two. That ratio, not a feature grid, picks your system.

Om Patel 17 min read
Photo: Yang / Unsplash

The short answer

Field service software optimises the days your crew is on site. In residential solar that is one to three days out of roughly 112, since NREL survey data puts contract to system operation at about 16 weeks. Decide with the wait ratio: calendar days per job divided by crew days on site. Above 20 to 1, dispatch is not your constraint.

The short answer

A CRM models the customer. Field service software models the job. Residential solar spends almost none of its time being either. The average project runs about 16 weeks from contract signature to system operation, and your crew is on the roof for one to three days of that. Everything in between is a wait: a plan reviewer, a fire marshal, a utility queue, a homeowner who has not heard from you in three weeks.

That ratio is the whole decision. The HVAC version of this question turns on revenue sold before it is scheduled, the electrical version on the bid-hit ratio. Solar breaks both, because the constraint is neither selling nor installing. It is the dead time between them, and neither category was built to hold a job nobody is working on.

Why the solar version of this question is different

Every buyer's guide answers this the same way. A CRM handles pre-sale, field service software handles post-sale, use both, integrate them, done. Arrivy's guide to solar project management software says it in those words: a CRM handles sales activities, a project tool schedules the installation and assigns crews. None of that is wrong. It just describes two categories that between them cover maybe 5 percent of the calendar days in a solar project. Run the arithmetic. NREL's survey of PV installers, published in Energy Policy volume 156, found that adoptions take about 16 weeks on average from contract signature until system operation. That is roughly 112 calendar days, against an install of one to three. So a contractor buying field service software to improve crew utilisation is optimising two days out of 112. Even a heroic 30 percent gain in dispatch efficiency buys back about fourteen crew-hours per job, while one missed follow-up during the 110 days you are not working can cost the whole job.

By the numbers

About 56 to 1. The ratio of calendar days to crew days on a typical residential solar project, using NREL's 16-week average against a two-day install. In HVAC service work the same ratio is close to 1 to 1, which is precisely why field service software was invented for HVAC and not for solar.

The wait ratio, and how to run it on your own jobs

Do not take the industry average. Divide calendar days from contract to PTO by crew days on site, survey and return trips included, across your last twenty completed jobs. Then read the result:

Wait ratioWhat you are actually runningWhat to buy
Under 5 to 1Service and O and M work, or small repeat jobsField service software. It is the whole system.
5 to 1 up to 20 to 1Mixed install and service shopField service platform, with a real wait-state record bolted on
Above 20 to 1New-install solar. Almost every residential installer.The wait is the system. Dispatch is a subsystem of it.

Most residential solar contractors land between 40 to 1 and 110 to 1. If your ratio is above 20 to 1 and your software spend sits in dispatch and routing, you bought a very good tool for your smallest problem.

Run a second test alongside it. Of the days a job is open, on what share does the next action belong to someone outside your company? In solar that is usually north of 80 percent. A dispatch board tells you what your crews are doing. It has no field for what the fire marshal is doing.

Where the 112 days actually go

The delay is not one queue. It is a chain of independent bureaucracies that do not coordinate, and the failure mode is a job silently falling out of one of them. An installer in r/solar described the plan-review side precisely: "The plan checkers want one thing, the zoning people want another, there's a fire department review, and some other agency you didn't know existed. The onsite inspectors don't coordinate with any of those people and have their own nitpicks because vibes."

On the utility side, the top-voted comment in that thread was blunter about why the portals never improve: "The Utility Companies are OPENLY and AGGRESSIVELY Hostile toward home solar installations. Once you internalize this? You should understand why each one has different forms, different portals, why they will change those, on a whim, every handful of months or years."

That is the real operating environment, and it explains why the integration promise in most buyer's guides is hollow. There is no API to integrate with. There are 1,500-odd authorities having jurisdiction, each with its own forms, and roughly 140 utilities, each with its own portal and its own habit of changing it.

NREL has measured this. Its SolarTRACE tool, built from project-level timestamps contributed by 23 installers, publishes median permitting, inspection and interconnection cycle times for any AHJ with at least ten permitted projects, benchmarked against the statewide average. Almost no CRM-versus-FSM comparison mentions it, and it is more decision-relevant than any feature grid: it tells you which of your markets is quietly costing you a month per job.

Where the process has been automated, the gains are real but bounded. NREL's SolarAPP+ issues an instant permit for systems that pass an automated code compliance check, taking permit review from as much as 20 business days to zero, and NREL puts the reduction in the full permitting timeline at around 14.5 business days, roughly 31 percent. A meaningful dent, and still about 98 days of waiting left on a 112-day project.

The finding that should change what you buy

Here is where most of the industry has the wrong model.

Ask installers why customers cancel and they will tell you it is the delays. NREL asked exactly that. In the Energy Policy survey, respondents consistently identified permitting, inspection and interconnection as the key drivers of project delays, and most then said those PII delays increase cancellations.

Then NREL looked at the actual project data. Evaluating the Impact of Residential Solar Contract Cancellations in the United States used an installer-provided dataset of 199,665 residential PV-only projects, roughly 10 percent of US installs per year from 2017 to 2019. Three findings, in order of how much they should change your behaviour:

  1. 51 percent of contracts did not result in an installed PV system, with a median installer cancellation rate of 33 percent. The report's own conclusion is that the rates and impacts of cancellations "have been previously underestimated." NREL's earlier survey paper had put it at about 1 in 10.
  2. Cancellations occur earlier in project timelines than assumed, though a significant number still happen after permit and approval-to-build.
  3. Cancellations do not appear to be driven by review delays in permitting and interconnection applications.

Read those together and the standard advice inverts. Larger installers in the survey ranked the customer's financial situation above PII delays as the main cause of cancellation. So the job is not to make the utility faster, which you cannot do anyway. It is to hold a customer through 112 days of nothing happening, and to know each morning which of your open jobs has gone quiet.

Watch out

If half your signed contracts never energise, your real customer acquisition cost is roughly double what your CRM reports. NREL's point is that those sunk pre-install costs get absorbed into soft costs and passed on to the customers who do install. Any system reporting cost per signed deal rather than cost per energised system is flattering you.

The third record: money that arrives in tranches you do not control

There is one more thing neither category models, and in 2026 it is becoming the norm. Under third-party ownership the financier pays you, not the homeowner, in milestones tied to project events. Notice to proceed is an approval gate that releases no money, so you front design, permitting, equipment and labour. The install milestone is the first funded step and the large one, commonly 80 to 90 percent, with a one to three week document review lag before cash lands. Activation at PTO releases the final 10 to 20 percent, and a recent trend has funders pushing more of the payment to that last gate.

Most TPO contracts also run a clawback clock, typically starting at install and allowing 115 to 150 days to reach PTO. Miss it and the financier can claw back money already paid on a project you have already built.

The labels are genuinely confusing, which is itself evidence of how ad hoc this is. Newer schemes number the funded steps M1 for install and M2 for activation, while older shorthand used M1 for contract, M2 for install, M3 for PTO. A Houston installer recruiting reps on r/Solarbusiness still advertises the old convention: "M1s the week after being signed and M2s the week after install."

Now ask what each category does with this. A CRM closes the deal at signature and books the revenue. Field service software raises an invoice at job completion. Neither models a project that is cash-negative for two months, paid by a third party in tranches against gates controlled by a utility, under a countdown that can reverse a payment you have already spent.

For a shop running thirty concurrent projects those holdbacks stack into hundreds of thousands of dollars floating at once, each on a different funder's clock at a different gate. Which is why the hardest question in most solar offices is not when a job will pay. It is which stage every open job is sitting at right now.

If your wait ratio came back above 20 to 1 and no system you own can tell you which external party is holding each open job today, that is a build worth scoping. We put the wait state into contractors' systems so the record that governs your cash flow stops living in one person's memory.

Book a free CRM demo

What actually breaks: a line item worth $20,000

The archetypal solar failure is not a crew failure or a sales failure. It is an administrative task in a wait state that nobody owned.

A homeowner posted in r/solar in January 2026 that their installer had failed to pay the interconnection application fee. That pushed PTO past the deadline and cost them the federal tax credit. Nothing on a dispatch board would have caught it. No work order, no crew, no truck, no invoice. Just a fee due to a utility, sitting in a stage neither a CRM nor a field service platform has a field for, and it destroyed the economics of the job.

The same dynamic shows up as slow attrition. Another r/solar poster described signing with a national installer, waiting a month for utility review and three more weeks for the engineering stamp, then being told the company had nobody local who could file the permit with their county. They asked the subreddit whether they could take their drawings to a local installer instead. That is a fully de-risked job walking out the door on wait time alone.

NREL's dataset says the aggregate cause of cancellation is usually the customer's finances. Threads like that one show the mechanism: 112 days is long enough for a homeowner's circumstances, and their enthusiasm, to move.

The stack most solar contractors actually run

Most installers are not choosing between two products. They run four, and the seams are the problem.

LayerTypical toolsWhat it does not do
Design and proposalAurora Solar, OpenSolar, GetPylonNothing after signature
Sales pipelineHubSpot, Pipedrive, Sunbase, GoHighLevelCloses the record at signature
Wait stateA spreadsheet, or nothingThis is the gap
Field executionJobber, ServiceTitan, Arrivy, ScoopModels two days out of 112
AccountingQuickBooks, XeroSees the invoice, not the milestone

The tempting fix is to integrate these, and that is where a cost most buyer's guides omit shows up. An installer posting in r/Solarbusiness in April 2026 reported that OpenSolar, long marketed as free forever, had introduced a per-project API access fee for syncing designs out to a CRM or accounting system. Owners will look at the toll and tell their team to re-key by hand, reintroducing the double entry the integration was meant to remove.

Whether or not that specific policy holds, the lesson does. Free design tools are free because your data is the product. Price your stack on the cost of getting data out, not in. An Australian owner in the same subreddit, running Monday.com alongside a separate design tool, summarised the disappointment: the cost was not the problem, the value was, and it amounted to "a pretty excel sheet." A pretty spreadsheet is not a failure if it holds the right column. The failure is holding the wrong ones.

Where field service software genuinely is the right answer

I am not arguing nobody should buy it. Buy it when service and O and M is a real revenue line, because panel cleaning, inverter swaps and battery service are repeat dispatch to a known asset at a known address, exactly the problem field service software solves, and the plumbing version of this question explains why the asset record matters. Buy it if you are a commercial installer whose projects run weeks on site at a wait ratio closer to 5 to 1.

And buy it for field evidence, which is the honest bridge between the categories. The parts of the wait you control are clean stamped plan sets, as-builts matching what was approved, and accurate interconnection applications. Field service software captures that evidence well. It just does not track what happens to it afterward.

The decision framework

Five questions, in order. Stop at the first one that changes your answer.

  1. What is your wait ratio? Under 5 to 1, buy field service software and stop reading. Above 20 to 1, keep going.
  2. What is your cancellation rate, measured from signature to PTO rather than from signature to install? If you cannot compute it, that is the finding. NREL's median was 33 percent.
  3. Can you say in 60 seconds which external party is holding each open job, and since what date? If it takes a phone call, no platform you own is doing the job.
  4. Are you paid in milestones? If TPO is a growing share of volume, you need a record of gates and clawback clocks, not invoices.
  5. How many concurrent open jobs? Under about 30, a disciplined spreadsheet wins. Past 60, memory fails and the wait state has to live in a system.

The demo script

Take these to any vendor pitching you, solar-specific or not.

  • "Show me a job sitting in utility interconnection review for 41 days. Where does that 41 appear, and did the system tell anyone at day 30?"
  • "A plan check comes back with corrections. Which record changes, who is assigned, and what is the clock?"
  • "Show me revenue recognised at M1 and the 15 percent held to M2, with the clawback deadline visible on the project."
  • "Which of my open jobs are waiting on me, and which on someone else? Show me that split as one number."
  • "Cost per energised system, not cost per signed contract. Where is that report?"

Most vendors will answer three of the five and dispatch-optimise the rest.

When a custom build is the honest answer

Not often, and not first. Fix the column before you fix the system: one field on every open job for who is holding it and since when, reviewed every Monday. Most solar offices that do that discover they had a nobody-owned-the-wait problem, not a software problem, and it cost nothing to fix.

A build earns its keep when three things are true at once: volume past what a spreadsheet holds, a milestone and clawback structure that differs by funder so no off-the-shelf revenue model fits, and enough AHJs and utilities that the wait state varies by market. At that point you are encoding a process specific to your funders and jurisdictions, and no vendor will ship it because the market for it is you.

The bottom line

The CRM-versus-field-service framing is a category error in solar. One product models the fifteen minutes at signature, the other two days on a roof, and the project is 112 days long. The 110 days in between are where half your signed contracts go to die, and where an unpaid interconnection fee can cost a customer their tax credit and cost you the referral.

With the 30 percent homeowner credit gone since the end of 2025 and Ohm Analytics forecasting a 20 percent decline in 2026 installs, the margin for carrying dead jobs is gone. The contractors who survive will not be the ones with the best dispatch board. They will be the ones who can say, without making a phone call, which open jobs are stuck and on whose desk. If you are still filling the top of that funnel, the lead side of the solar problem is worth reading, but no lead volume outruns a 33 percent cancellation rate.

Buy for the wait. Everything else is a subsystem.

Sources

Frequently asked questions

What is the difference between a CRM and field service software for a solar installer?
A CRM models the customer and the deal, and it closes the record at signature. Field service software models the job: dispatch, crews, work orders, materials and the invoice. Residential solar breaks both, because the thing that consumes the job is neither selling nor installing. It is the roughly 16 weeks of permitting, inspection and interconnection between the two, when nobody in your company is working and the customer is alone with a decision they already made.
Do solar installers need both a CRM and field service software?
Most residential installers do not need a full field service platform at all. Run the wait ratio first: total calendar days from contract to permission to operate, divided by the days your crew is physically on site. NREL survey data puts the numerator at about 112 days and the install itself at one to three days, so the typical ratio is somewhere near 56 to 1. A dispatch board optimises the denominator. Your money is in the numerator.
How long does a residential solar job take from contract to PTO?
NREL's survey of PV installers, published in Energy Policy, found that adoptions take about 16 weeks on average from contract signature until system operation. Industry timelines in 2026 commonly quote 6 to 12 weeks for solar only and 8 to 12 weeks or longer for PTO on battery-paired systems, on top of permitting. The physical installation is typically one to three days of that.
What percentage of signed solar contracts never get installed?
Higher than the industry assumed. NREL analysed an installer-provided dataset of 199,665 residential PV-only projects, roughly 10 percent of US installs per year from 2017 to 2019, and found that 51 percent of contracts did not result in an installed system, with a median installer cancellation rate of 33 percent. An earlier NREL survey paper had put it at about 1 in 10, which is why the report concludes cancellation rates had been previously underestimated.
Do permitting and interconnection delays cause solar cancellations?
Installers think so, and NREL's own data disagrees. In the Energy Policy survey, respondents consistently identified permitting, inspection and interconnection as the key drivers of delay and said those delays increase cancellations. But the 199,665-project dataset concluded that cancellations do not appear to be driven by review delays in permitting and interconnection applications, and that larger installers rank changes in the customer's financial situation above PII delays. That matters, because it means buying software to speed up the utility solves the wrong problem.
Does ServiceTitan or Jobber work for a solar installation company?
They work for the two days you are on the roof and for service and maintenance callbacks afterward. They were built for trades that dispatch a technician to a customer repeatedly, which is why they have no native concept of an AHJ plan review, a utility interconnection application, a notice to proceed, or a funder milestone. If your business is mostly new installs rather than O and M, you are buying a very good tool for the smallest part of your timeline.
How do solar milestone payments change the software you need?
Under third-party ownership the financier pays you in tranches tied to project events, not on your invoice. Notice to proceed typically releases nothing, the install milestone releases the bulk, commonly 80 to 90 percent, and the final 10 to 20 percent is held until PTO. Many contracts also run a clawback clock of roughly 115 to 150 days from install to activation. No CRM models revenue that arrives in gated tranches, and no field service platform models an invoice you do not issue.
What should a small solar contractor use instead?
If you are doing under about ten installs a month, a shared spreadsheet with one honest column beats any platform: which external party is holding this job right now, and since what date. Most installers buy software to fix a visibility problem they could solve with that column. Buy a system when the number of open jobs sitting in a wait state exceeds what one person can hold in their head, which for most offices happens somewhere between 30 and 60 concurrent projects.
Bespoke pipelines, automations, 360° customer records and real-time reporting, a CRM built around how your team actually works, connected to your entire stack.
Book a free CRM demo

Free tools

Find out what your site is costing you.

Enter your address and we check the real page. Scores are free and the itemised report lands in your inbox. No account, and we change nothing on your site.