The four stages
Every trades business runs the same loop: an enquiry becomes a quote, a quote becomes a scheduled job, a job becomes a completion record, and a completion record becomes an invoice.
Off-the-shelf job software models that loop generically. Where your business differs — how you price, how you schedule, what a completion record must capture — is where the fit breaks down.
What custom usually adds
- Your pricing rules — day rates, materials markup, call-out bands, contract customers
- Your scheduling constraints — skills, certifications, geography, vehicle capacity
- Your completion requirements — the certificates and photographs a job actually needs
- Your invoicing rules — stage payments, retentions, contract terms
The pricing rules are usually the reason. A business with four price bands and material markups that vary by customer cannot express that in most generic quoting tools.
Engineers need something that works offline
- Job details available without signal
- Photographs and notes captured and synced later
- Signature capture for completion
- Nothing that requires typing in gloves
- Fast enough to use between jobs, not at the end of the day
Capture the follow-up work
Job notes contain future revenue: things that will need replacing, work the customer asked about, faults that recur at the same site. Most of it is written down and never read again.
Extracting that into a diarised follow-up list is frequently the highest-value part of a system like this.
Integrate with the accounts
Invoices raised in the job system should reach the accounting system without anyone retyping them, and payments should flow back so engineers can see what is outstanding.
That connection is usually straightforward and it removes a recurring source of both effort and error.