How Much Does Solar Installer Software Cost in 2026?
Custom commercial solar project software costs $60,000 to $400,000, with a focused first release at $60,000 to $130,000 shipping in 12 to 16 weeks and a full platform at $150,000 to $400,000 phased over 6 to 12 months, based on Digital Heroes delivery experience.
On this page
Custom commercial solar project software costs $60,000 to $400,000, with a focused first release at $60,000 to $130,000 shipping in 12 to 16 weeks and a full platform at $150,000 to $400,000 phased over 6 to 12 months, based on Digital Heroes delivery experience. The decision that moves the number most is how many authorities having jurisdiction and utility interconnection processes you encode, and whether you automate portal status or enter it by hand. A jurisdiction library covering five authorities with manual status entry is a fraction of the cost of thirty jurisdictions with automated milestone clocks and portal polling. Scope that library to the jurisdictions where you actually build, not the ones you might.
The bands a commercial solar build falls into
A focused first release covering your single highest pain workflow, which for most installers is survey to permit to install with a jurisdiction library, runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform spanning procurement, milestone financing, compliance capture, commissioning and handoff to operations and maintenance runs $150,000 to $400,000, phased over 6 to 12 months so crews adopt in stages.
Megawatts installed is a poor predictor. An installer doing 45 megawatts a year across two utilities and four permitting authorities costs less to serve than one doing 20 megawatts across six states, fourteen authorities and five utilities with tax equity reporting on half the portfolio. Jurisdictional spread and financing complexity set the price, not system size.
Two warning signs on quotes. Anything under $60,000 for this category is generally a project tracker with custom fields, which is the thing you already have in Smartsheet and are trying to leave. Anything that prices the survey application as a form builder has not understood that roof membrane thickness, busbar rating and point of interconnection photographs are a schema, not a checklist.
What drives a commercial solar build up
The jurisdiction library. Every permitting authority has its own plan set requirements, fees and turnaround. Every utility runs its own interconnection process with its own milestones and response windows. Encoding fourteen authorities and five utilities with deadline clocks is the largest single line after the survey application.
Portal automation versus manual status. Polling a utility interconnection portal for status, or parsing notification emails so a twenty day supplemental review window does not close unnoticed, is meaningfully more expensive than a coordinator typing the status. It is also the difference between catching a missed window and discovering it at the back of a queue.
Investment tax credit compliance depth. Certified payroll hours per worker per day, apprenticeship ratios, domestic content attributes attached to the bill of materials and placed in service dates all have to be captured at the point of work rather than reconstructed. This protects your largest financial line and it is consistently underscoped.
Offline mobile survey. Commercial roofs have no signal. Queued capture, large photograph payloads and conflict handling cost more than a web form.
Integration count. The ledger in QuickBooks or NetSuite, the customer relationship system in Salesforce or HubSpot, the bill of materials from Aurora or OpenSolar, and monitoring interfaces from SolarEdge and Enphase are four separate problems.
Multi tenant architecture if you intend to white label the platform to acquired regional installers.
What keeps the number down
Build the survey schema first and properly. One structured, offline capable survey record that design, permitting and install all read from is the cheapest thing in this project and it removes the redone measurements, the change orders and the truck rolls that cost you far more than software.
Encode only the jurisdictions you build in. A library of five authorities you use weekly beats twenty you might use next year. Adding one later is a configuration task if the model was built for it.
Manual status entry in release one. Get the deadline clocks and the alerts working with a human entering status. Automate the polling in phase two once you know which portals actually matter.
Keep Aurora and QuickBooks. Design stays in the design tool, the ledger stays in the ledger. The custom platform is the spine between them. Replacing best in class tools adds cost and returns nothing operationally.
Import closed projects as flat records. Historical jobs need to be reportable, not fully modelled. Modelling a decade of finished work to today's schema is expensive and nobody reads it.
A worked example that adds up
A commercial engineering, procurement and construction firm with six locations, roughly 80 projects a year, fourteen permitting authorities, five utilities, Aurora for design, Salesforce for the pipeline and QuickBooks for the ledger. Here is the first release we would quote.
- Discovery, project and survey data model, jurisdiction requirement schema: $13,000
- Offline capable mobile site survey with solar specific fields and geo tagged point of interconnection photographs: $28,000
- Project spine with stage gates from survey through permit, install and permission to operate: $22,000
- Jurisdiction library covering fourteen authorities and five utility interconnection processes with deadline clocks and alerts: $30,000
- Portfolio roll up showing every permit and interconnection stage across all sites: $12,000
- Salesforce and QuickBooks integration: $14,000
That totals $119,000, in the upper part of the first release band, driven almost entirely by the jurisdictional spread.
Phase two: procurement with the bill of materials pulled from the approved design, per item lead times and backward scheduling at $38,000, milestone financing draw schedule tied to stage gates at $26,000, tax credit compliance capture covering certified payroll, apprentice ratios, domestic content and placed in service dates at $44,000, commissioning and permission to operate workflow including monitoring provisioning at $30,000, operations and maintenance handoff with as built and warranty records at $22,000, and multi tenant architecture for acquired installers at $30,000. That is $190,000, taking the platform to $309,000 across roughly eleven months.
How the spend phases
Discovery here is field work, not workshops. Send the developer on a survey. A team that has stood on a commercial roof with your survey tech will model membrane thickness and service panel constraints correctly, and a team that has not will produce a form with a photo upload. That first three weeks is around eleven percent of the release and it determines whether the rest is worth building.
The survey application and the jurisdiction library run in parallel through the middle. The library is slow, unglamorous work: reading plan set requirements, transcribing milestone rules, checking response windows. It cannot be compressed by adding developers because it is bounded by how fast your permitting coordinator can answer questions.
Invoice against shipped modules across four milestones for the $119,000, then price phase two module by module. Take compliance capture before procurement if your next audit is closer than your next long lead order, and the reverse if switchgear lead times are currently costing you crew demobilisations.
Roll out by location rather than all at once, and start with the location that has the strongest coordinator. Their workarounds are the requirements document nobody wrote.
The ongoing costs nobody quotes
- Maintenance and iteration at roughly 15 to 20 percent of build cost per year. On a $309,000 platform that is $46,000 to $62,000, and in this category a meaningful share goes on changes you did not initiate.
- Jurisdiction library upkeep. Permitting authorities revise plan set requirements and fees, and utilities revise interconnection processes. Somebody has to notice and update the templates, or the alerts start firing against rules that no longer apply.
- Integration drift. Monitoring interfaces from inverter manufacturers change, as do the customer relationship and accounting platforms. Budget for it rather than treating each break as a surprise.
- Mobile device fleet. Tablets for survey crews, cases, and replacement at a realistic rate for equipment that lives on roofs.
- Photograph and document storage. Survey imagery, as builts and compliance records accumulate and have retention requirements tied to your tax and warranty obligations.
- An internal owner. A senior project coordinator needs part of their week to triage requests and own the jurisdiction library. Without that role the platform ages badly.
Comparing a build against your current renewal
Start with your own numbers. Pull your Sitetracker, Scoop Solar or Procore renewal and separate seats, module charges, implementation or reconfiguration consultancy, and support. Multiply across your locations and twelve months. That is the visible annual figure.
Then price what the renewal does not show, because in commercial solar the invisible costs are larger than the licence. Count the coordinator hours spent reconciling a master pipeline spreadsheet against a permit status sheet and a utility portal. Count redone site surveys and the change orders that follow a service panel constraint discovered on the roof. Count expedited freight on a long lead inverter or switchgear ordered late, and crew mobilisations that were cancelled because material was still six weeks out. Count the interconnection windows missed because a notification email landed in a personal inbox, and what dropping to the back of a queue did to a financing draw.
Last, and hardest to price, is tax credit basis you cannot defend because prevailing wage and apprenticeship records were reconstructed at tax time. That is not a software line item, it is an exposure, and it is the reason several installers we work with started the project.
Compare licence plus reconciliation labour plus rework plus expediting against build cost plus annual maintenance. If the first list is smaller, keep buying.
When buying beats building
If you are a single region installer under roughly 30 commercial projects a year with a standard workflow, buy. Scoop Solar is built for solar field operations and Sitetracker handles multi site project tracking competently. If either matches how you actually run, use it and spend the six figures on sales capacity instead. Procore is the right answer if solar is a line inside a broader construction business and general contracting is the bulk of your work.
Buying is also right if you have no internal owner. A custom platform with nobody maintaining the jurisdiction library is a system that will be quietly wrong within a year, and wrong deadline clocks are worse than no deadline clocks.
The signals to build are concrete. You run multiple locations. Spreadsheet reconciliation has become somebody's actual job title in practice if not on paper. Your milestone financing or tax credit documentation does not fit any template. You are integrating five or more systems by hand. And the clearest one: you are pasting solar specific data into generic cells to force a tool to fit, which means the tool is dictating your process.
Even then, keep the boundaries. Aurora or OpenSolar stays the design engine, QuickBooks or NetSuite stays the ledger, Salesforce stays the pipeline. The build is the project spine between them, and that boundary is what keeps this a $300,000 programme rather than a $700,000 one.
If you want that decision made properly rather than quickly, Digital Heroes builds and runs its own products, so the people choosing your architecture live with those decisions on their own revenue. You can take that specification to any other firm on your shortlist.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Comparesoft reports the field-service industry-average first-time fix rate is about 80%, best-in-class providers reach roughly 90%, scores below 70% put the business at risk, and providers exceeding 70% FTFR saw customer retention around 86%. Source: Comparesoft (2024) →
- Grand View Research valued the global field service management market at USD 4.43 billion in 2022 and projects it to reach USD 11.78 billion by 2030, a 13.3% CAGR, driven by growing field operations in telecom, utilities, construction and energy. Source: Grand View Research (2023) →
- Nucleus Research's analysis of published analytics deployment case studies found business intelligence and analytics returned an average of $13.01 in benefits for every dollar spent, up from $10.66 three years earlier. Source: Nucleus Research (2014) →
- The average number of formal learning hours used per employee fell to 13.7 in 2024, down from 17.4 in 2023, a decline the report attributes partly to a shift toward informal and on-the-job learning not captured in the formal-hours metric. Source: Association for Talent Development (ATD) (2025) →
Frequently asked questions
How much does custom solar project management software cost in total?
A focused first release covering survey, project stage gates and a jurisdiction library runs $60,000 to $130,000 and ships in 12 to 16 weeks, based on Digital Heroes delivery experience. A full platform adding procurement, milestone financing, tax credit compliance, commissioning and handoff runs $150,000 to $400,000 over 6 to 12 months.
A representative six location installer with fourteen permitting authorities lands at about $119,000 for the first release and roughly $309,000 for the full platform.
What does it cost to run each year after launch?
Budget roughly 15 to 20 percent of build cost annually for maintenance and iteration, so $46,000 to $62,000 on a $309,000 platform. The category specific item is jurisdiction library upkeep, because permitting authorities revise plan set requirements and utilities revise interconnection processes without asking you.
Add integration drift as inverter monitoring and accounting interfaces change, a survey tablet fleet that lives on roofs, and storage for survey imagery, as builts and compliance records with retention tied to your tax and warranty obligations.
How long does it take to build?
Twelve to sixteen weeks for a first release, then 6 to 12 months in phases. The pacing constraint is rarely engineering. It is how fast your permitting coordinator can answer questions while the jurisdiction library is being transcribed.
Roll out by location rather than all at once, starting with the site that has the strongest coordinator, because their existing workarounds are effectively the requirements document nobody wrote down.
Is Sitetracker cheaper than building our own platform?
On the invoice, usually yes, and for a single region installer under about 30 commercial projects a year it is the right call. Split your renewal into seats, modules, reconfiguration consultancy and support, then multiply across locations and twelve months.
The comparison turns when the tool's structure stops matching your interconnection and tax credit milestones, because the gap gets absorbed by coordinator hours, redone surveys and expedited freight, none of which appear on a renewal.
Which module protects the most money?
Tax credit compliance capture, at $44,000 in the worked example. Certified payroll hours per worker per day, apprenticeship ratios, domestic content attributes on the bill of materials and placed in service dates all need capturing at the point of work, because reconstructing them at tax time leaves the basis hard to defend.
Procurement with backward scheduling is a close second on a different line, since ordering a long lead inverter or switchgear late causes crew mobilisations you pay for twice.
Why does the jurisdiction library cost so much?
Because it is transcription, not code. Each permitting authority has its own plan set requirements, fees and turnaround, and each utility has its own interconnection milestones and response windows. Fourteen authorities and five utilities is $30,000 in the worked example.
Keep it to the jurisdictions where you actually build. Adding one later is a configuration task provided the model was designed for extension, so there is no saving in encoding places you might work someday.
Do we still need Aurora and QuickBooks if we build?
Yes, and you should keep both. Aurora or OpenSolar stays the design engine and QuickBooks or NetSuite stays the ledger, while the custom platform sits between them as the project spine, pulling the bill of materials from design and pushing purchase orders and invoices to accounting.
Replacing best in class design or accounting tools adds cost and risk for no operational gain, and it is the most common way a $300,000 programme becomes a $700,000 one.
Can we start with manual permit status and automate later?
Yes, and it is the sensible sequence. Get the deadline clocks, requirement templates and alerts working with a coordinator entering status, then automate portal polling or notification parsing in phase two once you know which utilities genuinely justify it.
The value in release one is the clock and the alert, not the data entry method. A supplemental review window that closes unnoticed costs you queue position regardless of who typed the status.
Do we own the code if a developer builds it?
You should own the source code, the database schema, the cloud accounts and the deployment, with the repository in your own organisation from day one and no per seat licence owed back. At Digital Heroes the installer owns the code from the first commit.
Settle it before any code is written. If a vendor keeps the code and rents it back, you have bought a subscription with a six figure deposit rather than an asset.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Is Housecall Pro enough for a growing HVAC or plumbing company, or do we need custom software?
Housecall Pro holds up well to roughly 10 to 20 technicians on standard residential jobs, with its Essentials plan listing around $129 per month for up to five users. The ceiling appears with commercial work: multi-visit projects, progress billing, equipment service history, and inventory are thin, which is when owners start managing the business in exported spreadsheets. Use the spreadsheet count as your signal: three or more recurring workarounds mean the tool no longer fits.
What does it cost to keep custom software running after launch?
Budget 15-20% of the original build cost per year, which on a $100,000 system means $15,000 to $20,000 for security patches, dependency updates, bug fixes, and small improvements as real usage reveals what the spec missed. Cloud hosting for a typical business application adds $50 to $300 a month on top. Skipping maintenance does not save the money; in Digital Heroes rescue work, unmaintained systems typically need a far more expensive rebuild within about three years.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
Can I build my product on a no-code tool like Bubble instead of hiring developers?
For testing whether anyone wants the product, yes, and Bubble's paid plans start at $29 a month, which is the cheapest validation you will ever buy. The ceiling arrives with complex data relationships, heavy integrations, performance at a few thousand users, and the fact that you cannot export a Bubble app to servers you control. A path many Digital Heroes clients take: prove demand on no-code, then rebuild custom once revenue justifies it, treating the no-code version as a paid prototype rather than a foundation.
What does it cost per year to maintain custom field service software?
Budget 15 to 20 percent of the original build cost per year, so $15,000 to $20,000 on a $100,000 platform. That covers hosting, security patches, integration API changes, a monthly block of small improvements, and the iOS and Android updates Apple and Google ship on their own schedule. Skipping it is not a savings; the technician app needs attention every OS cycle or it eventually stops opening on new phones.
What should I prepare before contacting a software development agency?
A one-page brief beats a 40-page requirements document: the business problem in plain words, who will use the system, the 5 to 10 workflows it must handle, the tools it must connect to, and your budget range and deadline driver. You do not need wireframes, a specification, or technical vocabulary; producing those is the agency's job during discovery. Stating a budget range up front is the single best move, because it gets you honest scoping instead of a quote engineered to win the meeting.
How long does it take to build a custom web or mobile app from scratch?
Plan on 8 to 16 weeks for a focused first version and 4 to 9 months for a larger platform, which is the typical spread across Digital Heroes builds. The first 2 to 3 weeks go to discovery and design before any production code ships. The two things that stretch timelines most are integrations with legacy systems and slow feedback from your side, not developer speed.
At what point does it make sense to switch from ServiceTitan to custom software?
The switch usually pencils out once your ServiceTitan bill passes roughly $75,000 a year and your team still maintains workaround spreadsheets beside it. ServiceTitan keeps pricing quote-only, and the quotes owners share in Digital Heroes scoping calls run several hundred dollars per technician per month on annual contracts, so a 30-technician shop can spend a full custom build's budget every 12 to 18 months in fees. If ServiceTitan fits your workflow cleanly, stay; the case for custom is a workflow the product forces you to bend.
How does custom field service software work when technicians have no cell signal?
Properly built field software stores the technician's entire day on the device, including job details, forms, photos, signatures, and parts, then syncs automatically when signal returns. The hard engineering is conflict resolution: deciding what happens when a dispatcher reassigns a job while the technician is working it offline. That logic has to be designed before the build starts, because retrofitting offline into an app that assumed a connection is close to a rewrite.
How much does it cost to build custom field service management software for a small business?
For a company running 5 to 25 technicians, a focused first version with scheduling, dispatch, a technician mobile app, and invoicing typically runs $40,000 to $80,000 in Digital Heroes delivery experience. A full platform with offline mode, a customer portal, GPS tracking, and accounting sync lands between $90,000 and $180,000. The two biggest cost drivers are offline sync depth and integration count, so pin both down in scoping and the quote holds.
Who can build a custom field service management software system?
Digital Heroes builds custom field service management software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other field service management software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Aria.
Senior Account Manager · Retail · Sydney · 2 posts on the site
Published · Last updated .
