Service

Solar company website development

For owners and operations managers of solar, battery and heat pump installation businesses who want the survey, the proposal, the installation diary and the handover pack designed around how their surveyors and crews actually work, rather than a sales CRM with a calendar attached.

The problem

What goes wrong today

Where it usually starts

A regional installer with two survey vans and three installation crews takes enquiries through a web form, a phone line and a lead-generation site.

  • The office types each one into a spreadsheet and books a survey by ringing the householder back.
  • The surveyor arrives, measures the roof by hand, photographs the consumer unit and the loft, notes the orientation and the shading from a neighbouring tree, and writes the panel count and inverter choice on a pad.
  • Back at the desk the proposal is built in a word processor from last week's template; the customer asks for a battery to be added, a second version is emailed, and a week later nobody is certain which version was accepted or whether the deposit relates to the one with the battery.

Where it gets harder

Scheduling is a wall planner.

  • The scaffold company is booked by phone and the install crew is told on Friday what Monday looks like.
  • The grid connection application is in one person's inbox, the roof fixing kit was ordered for the wrong tile type, and the commissioning photographs sit on an installer's phone.
  • When the customer rings to ask where their job is, the office cannot say without three calls.
  • The handover pack is assembled by hand after the fact, and the registration with the certification body is the last thing anyone remembers to do.

Scope of the service

What the build covers

A custom solar installer build normally covers:

  • A survey request form capturing property type Roof construction, orientation, approximate pitch, shading, consumer unit position and recent consumption figures as the customer reports them
  • Survey appointment booking against surveyor availability and travel areas
  • A survey record with measurements Photographs, roof plan sketch and the surveyor's component recommendations
  • A proposal built from a component library of panels Inverters, batteries, mounting kits and chargers with versioning, so every change the customer asks for produces a new numbered version and the accepted one is locked
  • A project record that moves through survey Design, approval, scheduling, installation, commissioning and handover
  • An installation diary with crews Vans and scaffold as capacity
  • A commissioning record with serial numbers Test readings as recorded by the installer, photographs and sign-off
  • A handover pack assembled from the project's documents
  • A maintenance enquiry route for existing customers

How discovery works

Discovery follows one job from the first enquiry to the handover pack with you: who qualifies the lead, what the surveyor must capture to design without a second visit, how proposals are priced and approved, how crews and scaffold are booked, what the customer is told and when, and which documents the handover must contain. Each becomes a named stage in the scope document: enquire, survey, design, propose, accept, schedule, install, commission, hand over.

Deliberately out of scope

  • Design and shading simulation software, which stays with the tool your designer already uses and whose output is attached to the project
  • Grid connection portals, certification body registrations and grant scheme applications, which are recorded against the project with reference numbers and dates but remain the responsibility of the installer on the external systems
  • Accounting

When the scope grows

Scoping scenario

A commercial installer working on warehouse roofs with structural surveys, multi-week installation phases, several subcontracted crews and a client who needs stage sign-off before each payment needs a project with phases and gates, subcontractor access limited to their own jobs and document approval by the client. That is a different build from a domestic installer with three crews, and the scope document says so.

Deliverables

What you receive

  • Discovery notes from following one installation from enquiry to handover pack
  • A written scope document naming each project stage, the proposal versioning rules and what is out of scope
  • Design of the survey capture screens on tablet, the proposal builder, the installation diary and the customer status page
  • The build, deployed to your hosting or ours
  • Migration of customer, enquiry and completed project records from your current spreadsheet or CRM, where practical
  • Training for the office, surveyors, designers and crew leads, with a short written guide
  • Handover material and full ownership of the source code and your data

Process

How a project runs

Each stage maps onto the project view in your client panel. Durations are set in your proposal, never on this page.

  1. Onboarding

    Access, contacts, your current enquiry sources, proposal templates, the wall planner and the component list you install most.

    Project stage: Onboarding
  2. Planning

    Discovery with the owner, a surveyor and the installation manager; the project stage model, versioning rules and scope document are agreed with a milestone plan.

    Project stage: Planning
  3. Design

    Clickable designs of the survey form on a tablet in a loft, the proposal builder, the crew diary and the customer status page, checked on the devices surveyors and crews carry.

    Project stage: Design
  4. Development

    Built in stages: enquiries, surveys and the component library first, then proposals and acceptance, then the installation diary, commissioning and handover.

    Project stage: Development
  5. Client review

    Your team runs live enquiries through the system alongside the old spreadsheet for a fortnight, including a proposal revised and accepted by a real customer, and tells us where it does not match the job.

    Project stage: Client review
  6. Revisions

    Survey fields, proposal layout, diary rules and handover contents are adjusted from the review and re-checked against the scope document.

    Project stage: Revisions
  7. Ready for launch

    Records migrated, customer messages tested against addresses you control, document templates signed off, launch checklist completed.

    Project stage: Ready for launch
  8. Delivered

    The business runs on the new system; optional maintenance and hosting continue under their own agreement.

    Project stage: Delivered

Integrations

Commonly integrated

Systems this kind of business usually asks us to connect. Each integration is confirmed during discovery; none is assumed.

  • Lead-generation and quote platforms that send enquiries by email or API
  • Design and shading simulation tools whose exports are attached to the project
  • Distributor stock and price files for panels, inverters, batteries and mounting kits
  • Grid operator and certification body portals where an interface is published, for recording reference numbers against the project
  • Electronic signature providers for proposal acceptance
  • Card payment providers and open banking for deposits and stage payments
  • SMS and email providers for survey confirmations, status updates and handover delivery
  • Accounting software for invoices and deposit reconciliation
  • Inverter and battery monitoring platforms for maintenance enquiries from existing customers

How we would approach it

Worked example

Concept demo

A commercial roof installer with phased installations and subcontracted crews

The situation

An installer fitting arrays on warehouse and agricultural roofs ran each job over several weeks with a structural survey, a scaffold phase, two or three subcontracted crews and a client who signed off each stage before releasing a payment. Progress lived in a shared spreadsheet and photographs in a group chat.

Why it is a custom build

This needs a custom build because the job has several paying gates and several external parties, which a domestic survey-and-install flow does not model.

The scope we would propose

  • A project with named phases and gates, each gate requiring listed documents and photographs before it can be passed
  • Subcontractor logins limited to the jobs and phases assigned to them, with their crew sheets and photographs uploaded from site
  • A client approval step that records who approved which phase and when
  • A commissioning record per inverter string with serial numbers and the readings entered by the installer
  • A handover pack assembled automatically from the approved documents

Pricing

What affects the price

Every proposal is priced on scope. These are the factors that move it most for this kind of build.

  • Number of surveyors, crews and vans, and whether subcontracted crews need their own access
  • Depth of the survey capture: roof plan sketching, photograph sets and consumption inputs
  • Component library size and whether distributor price files are connected
  • Proposal versioning, electronic signature and deposit collection
  • Scaffold, grid connection and certification references tracked as project records
  • Customer status page and the channels used for updates
  • Commercial projects with phases, gates and client approvals
  • Volume of customer and project history to migrate
  • Hosting choice: your own hosting or ours

FAQ

Frequently asked questions

Would the package do, or do we need a custom build?

A domestic installer whose jobs follow survey, proposal, acceptance, scheduling, installation and handover in a predictable order is usually well served by the solar installer package configured around your crews and components. Custom work is the honest answer for commercial installers with phased projects and client gates, businesses that also sell heat pumps or EV chargers with different survey forms, franchise networks or several regional depots. Discovery settles it before anything is quoted.

Does the system generate output or savings estimates for the proposal?

No. The proposal shows system components, quantities and the figures your designer enters from the design tool you already use, attributed to that tool and that person. We do not build a calculator that generates performance claims, because the responsibility for those figures rests with the installer and the design software.

How are grid connection and certification handled?

As records against the project: application type, reference number, date submitted, date approved and the documents returned, with a checklist that shows what is outstanding before installation or handover. The applications themselves are made on the external portals; where one publishes an interface, the reference can be read in rather than typed.

Can surveyors work offline in a loft?

The survey form is designed to be completed on a tablet with patchy signal: photographs and measurements are held on the device and uploaded when connectivity returns, and the form marks what is still unsynced so nothing is lost.

Who owns the system afterwards?

You do. Source code, customer and project records, survey photographs, proposals and commissioning documents are handed over at delivery; hosting and maintenance are optional and separately agreed.

Get a project quote for solar company software

Answer a few questions about your business, your current systems and what should change. We reply with a clear, competitive proposal.

Get a project quote