Solar Installer Software: Custom Build vs Off-the-Shelf Project Tools

What Sitetracker, Scoop Solar and Procore actually do well

Buying is the right call far more often than firms like ours admit, so here is the plain version. If you install commercial solar in one region, run under roughly 30 projects a year and your workflow is conventional, Scoop Solar or Sitetracker will fit and you should not write software. Spend the capital on a second crew.

Be fair about what those products deliver. Sitetracker was built for high volume, repeatable deployment programmes and it handles portfolios of similar jobs with proper stage gates, bulk actions and forecasting that generic tools cannot match. Scoop Solar is genuinely solar aware, with field forms, photo capture and checklists shaped around installation crews rather than office staff. Procore is strong on the construction side, particularly submittals, requests for information and subcontractor management, and if your commercial jobs involve significant structural or electrical subcontracting it earns its place. Enerflo and SolarNexus cover the sales to install handoff well at the residential and small commercial end.

Keep the design and financial tools whatever you decide. Aurora Solar and OpenSolar do array layout, shading and production modelling to a standard nobody should attempt to reproduce, and PVWatts remains the reference production model. QuickBooks or NetSuite stays your ledger. Replacing best in class design or accounting adds cost and risk for no operational gain, and any developer proposing it is scoping for revenue rather than for you.

The build question here is narrow. It is about two things every generic project tool models loosely and every commercial installer eventually pays for.

Where they stop: the jurisdiction library and the tax credit evidence

The first is the jurisdiction. Every authority having jurisdiction publishes its own plan set requirements, fee schedule and turnaround. Every utility runs its own interconnection process with its own milestones, and some queues sit months deep. A utility asks for supplemental review with a response window measured in days, the notice lands in a project coordinator's personal inbox while she is on site, the window closes, and the project drops behind everyone else in the queue. In a spreadsheet that miss is invisible until it is expensive, and the cost is not the fee. It is the position in the queue.

SolarAPP+ has made permitting genuinely faster in the jurisdictions that adopted it, and where it applies you should use it. It does not track your deadlines across the dozen authorities and four utilities you actually touch, and neither does a generic task list, because neither holds a jurisdiction requirement template or a milestone clock. Status becomes whatever somebody last typed.

The second is tax credit evidence. Since the Inflation Reduction Act, the full investment tax credit rate depends on prevailing wage and apprenticeship compliance, with domestic content and energy community adders on top, and the claim runs through IRS Form 3468 with a placed in service date you must be able to support. Certified payroll hours per worker per day, apprentice labour hour ratios, and domestic content attributes attached to the bill of materials are evidence captured at the point of work or reconstructed under pressure at tax time. QuickBooks tracks money, not compliance evidence. Generic project tools have no schema for an apprentice ratio. So the documentation protecting your single largest financial line is the one thing nobody owns.

Add the survey gap underneath both. A technician measures a roof, notes membrane thickness, flags a service panel with a busbar near its rating and photographs the point of interconnection. That lives in a camera roll. The designer never sees the busbar constraint, specs a system the service cannot accept, and the crew discovers it on the roof.

The arithmetic: per-seat pricing against projects per year

Commercial project platforms price per user per month, often with a floor and a configuration engagement on top. Work from your own quote. Add licence, the implementation amortised over three years, and the administrator time somebody spends keeping it configured, then divide by projects completed last year.

Here is a worked example to replace with your figures. Say your platform, implementation and admin time come to $96,000 a year across 40 named users, and you completed 55 projects, so about $1,745 per project. Say the custom platform you would build lands at $150,000 with $27,000 a year to keep and carries unlimited internal users. Over three years the build totals $204,000 against $288,000, and the crossover sits at roughly 35 seats, or about 70 projects a year at your current staffing ratio.

Two honest corrections. Seats grow faster than projects, because every field crew member you add is a licence while contributing no additional project. And if the platform fits your process, the build never repays itself no matter what the seat maths says, because you will spend six figures recreating software that already exists. The number that overturns the arithmetic is different anyway: one contested tax credit basis on a large commercial job can exceed the entire build.

What a custom build actually costs to build and keep

Across delivered projects, Digital Heroes sees two honest bands. A focused first release covering your highest pain workflow, usually an offline capable structured site survey feeding permit and install tracking with the jurisdiction library behind it, runs $60,000 to $130,000 and ships in 12 to 16 weeks. A full platform spanning procurement with lead time driven backward scheduling, milestone financing draws, commissioning and operations handoff runs $150,000 to $400,000, phased over 6 to 12 months so crews adopt it in stages.

Data migration takes 10 to 25 percent of the build. New jobs start in the new system while in-flight projects finish where they are, then open projects import once the team trusts the tool. Closed historical projects usually come in as flat records for reporting rather than fully modelled, which keeps the bill at the lower end. What pushes it up is the jurisdiction library itself, because somebody has to read and structure the requirements for every authority and utility you work in, and that is research rather than data entry.

Year two runs 15 to 20 percent annually. Authorities revise plan set requirements, utilities change interconnection procedures, the National Electrical Code adoption cycle moves state by state, and tax credit guidance keeps being clarified. Budget it as maintenance of a rule library, not as bug fixing, and name the person responsible for keeping the library current.

The four situations where building wins

• Regulatory fit. Your tax credit basis depends on prevailing wage and apprenticeship records, domestic content documentation and a defensible placed in service date, and you carry tax equity or a lender who will test them. Interconnection under IEEE 1547 and code compliance under NEC Article 690 and 705 also generate evidence obligations that outlive the crew who created them.
• Scale economics. Per seat pricing has crossed the line above and keeps climbing as you hire field staff who each need read access. Multi location operators feel this fastest, because a regional office adds seats before it adds margin.
• A workflow that is your competitive advantage. If your win rate comes from quoting a realistic energisation date when competitors guess, the survey to permission to operate chain is your product. So is the ability to white label the platform across regional installers you have acquired.
• Integration sprawl across three or more systems. Aurora or OpenSolar for the bill of materials, Salesforce or HubSpot for the deal, QuickBooks or NetSuite for the ledger, SolarEdge and Enphase monitoring interfaces for commissioning, plus a utility portal and a permitting portal per jurisdiction. When a coordinator opens five tabs to answer why one job missed a milestone, that reconciliation is the system.

Digital Heroes is the wrong firm if what you need is a Sitetracker implementation partner. We do not configure other people's platforms. If configuration is the real job, hire a specialist consultancy and keep the difference.

How to decide in a week: reconstruct your last missed milestone

Take the most recent project that missed a permission to operate date or a financing draw, and give one person an afternoon to reconstruct exactly what happened, hour by hour, from the systems you already have. Not what people remember. What the records prove.

Count two things while they work. How many separate systems they had to open, and how many gaps they could only fill by asking someone. Fewer than three systems and a handful of gaps means your process is fine and a tool change will not help. Five systems and a dozen gaps means the reconstruction cost you more than a day and you will be paying it again on the next dispute, because a lender will ask the same question and expect an answer with evidence.

Then commission a paid discovery phase rather than a build. At Digital Heroes that means a signed product requirements document before any code, covering the survey schema down to busbar rating and point of interconnection, the jurisdiction and utility milestone model, the tax credit evidence fields captured at the point of work, integration contracts, and acceptance criteria. Ask any shortlisted firm to whiteboard that data model in front of you. If they treat it as generic project management with custom fields, walk. You keep the specification either way and can take it to any other firm.

We hold India LLP, US LLC and UK LTD entities so intellectual property assigns under your own law. Over 2,000 projects, more than fifty specialists, and a named team you meet before signing. We run our own products, ShopScore, HeroCheckout and Section Vault. Verify us on Clutch, Trustpilot, Fiverr Vetted Pro and D-U-N-S.

Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.