Case study · Custom Platform & Workflow Automation · Solar Installation

From first enquiryto final payment

Straight Line Solar is a solar and electrical installer. Like many growing trade businesses, its operation had spread across a collection of separate tools, with the same information re-entered by hand as each job moved from enquiry to installation to invoice.

Working with White Oryx, the company replaced the patchwork with a platform of its own: one record that carries every job from the first enquiry, across the roof, to the payment landing in Xero.

6 wksTo an operational platform

Office & field working on the platform six weeks after the first walkthrough, with new features added in two-week sprints since

1Record per job

Enquiry, installation, invoicing & payment held together on a single record

2Experiences, one sign-in

A desktop workspace for the office and a phone app built for the field

0Stages billed twice

A stage can be invoiced once and only once, enforced by the platform itself

Chapter 01

The opportunity

In solar installation, the information that matters is created in three places: in the office, where work is booked and scheduled; on the roof, where it is carried out; and in the accounts, where it is invoiced and paid. When those places run on separate tools, every handover depends on someone re-entering what another person already knows.

The gap is felt most at billing. Installation work is commonly invoiced in stages, so an accurate invoice depends on knowing exactly what has been completed on site, and every payment received has to be matched back to the work it pays for.

Straight Line Solar recognised that connecting a set of separate tools would only move the re-entry around. The company engaged White Oryx to build one platform shaped to how the business actually works, from the first enquiry to the final payment.

Separate tools, one record

Before

  • Separate toolsfor each part of the job
  • Re-keyed detailsbetween office & field
  • Delayed visibilityof work done on site
  • Manual matchingof payments to invoices

After

Chapter 02

The approach

Bookings that file themselves

Incoming bookings are read by the platform and turned into jobs automatically, field by field.

Anything that cannot be read with confidence is held for a person to check, with the original document beside it, rather than guessed.

One board to run the day

A scheduling board shows each installer’s day, and every job’s status is derived from the work actually recorded against it, so the board, the job list and the reports always agree.

A field app built for the roof

Installers work from a phone-first app focused on the day ahead and the job in front of them.

Photo checklists and safety documentation are completed on site in a few taps, and each person sees only what their role requires.

Staged billing, invoiced once

What is completed on site determines what can be billed.

Every amount is calculated on the server with tax applied consistently, and each stage of a job can be invoiced once and only once.

Approved before it is raised

Invoices are reviewed and approved in the platform before they are raised in Xero, and every step is recorded on the job’s permanent timeline.

Reconciliation that keeps up

Payments are matched to the invoices they settle.

Proposed matches are reviewed before anything is recorded, and a payment is applied only when the amounts agree exactly.

Quoting built in

Enquiries arriving in any form are read into structured leads, and quotes are priced consistently, with small-scale technology certificates calculated to the regulator’s published method.

An accepted proposal becomes a job at the quoted price, with no re-entry.

Service work on the same record

Service and warranty visits are linked to the original installation, with its photos and history in view, so a returning crew knows exactly what was installed and when.

Chapter 03

Inside the platform

The life of a job

From the first enquiry to the money in the bank, on a single record. Routine steps happen without anyone typing, and the decisions stay with people.

  1. 1Enquiry or booking readAutomatic
  2. 2Scheduled to a crewTeam
  3. 3Work recorded on siteTeam
  4. 4Priced & stagedAutomatic
  5. 5Approved & raised in XeroTeam
  6. 6Payment match proposedAutomatic
Automaticthe platform does itTeama person records or decides it

Reading a lead, safely

An enquiry can arrive in any form. AI turns it into structured fields, and a person always has the final word.

Any enquiry

Whatever the customer sent.

ScreenshotEmailBusiness cardPower bill
Read, extract only

The content is treated as data, never as instructions.

Fields marked to check

Contact, site and request extracted, with uncertain values flagged.

Confirmed by a person

Then quoted straight away or later.

An uncertain read never fills a financial field
Any error leaves fields empty, never half-filled
Switched on only when the business chooses
Customer details are never written to logs

Chapter 04

The difference

Built around the business, not a template

The platform began with a walkthrough of how the office and the field actually work, and the finding that they use the system for entirely different jobs.

The result is one sign-in with two experiences chosen by role: a desktop workspace for the office and a phone app for the field.

Money is never a guess

Prices, stages and tax are calculated on the server and never trusted from a browser.

The connection to Xero is deliberately narrow, nothing is marked as sent until Xero confirms it, and every attempt is logged.

Secure by default

Access is by invitation only, every action is checked against the person performing it, and sensitive credentials never reach the browser.

Each new screen is reviewed against a written security standard before it ships.

Fail safe to a person

Where the platform cannot be certain, it stops and asks.

An unreadable booking waits with the original beside it, a payment match is proposed rather than applied, and customer-facing messages stay off until the business has previewed them and switched them on.

Capability transfer, not dependency

The platform belongs to the business and is documented as it grows: a data reference, a go-live checklist, the security standard and a dated changelog.

An import specification lets historical records be cleaned and brought across in a single pass.

Chapter 05

The impact

Bookings now become jobs without re-entry, the office runs the day from one board, and installers record their work on their phones as it happens.

Every stage is priced, approved and raised in Xero once, and each payment is matched back to the work it pays for. Quotes, proposals and service visits sit on the same record as the installation itself.

The office, the roof and the books now read from one record: custom software, built to the shape of the business.

Built with
Next.js & TypeScriptPostgresXero APIInbound & outbound emailApplied AIPDF generation & parsingAutomated visual testing