The challenge
Fire safety servicing is a recurring-revenue business whose revenue depends entirely on remembering. Extinguishers, hoses and related equipment must be inspected at intervals fixed by regulation, most commonly every twelve months. Miss the date and two things happen: the client is out of compliance, and the service visit that should have been booked simply does not happen.
Managed in spreadsheets, this fails predictably as the client base grows. Due dates are tracked per client rather than per item, so a site that had equipment added mid-year drifts out of step. Nobody is confident which list is current. The business is aware it is losing renewals but cannot say which ones.
The commercial side has a parallel problem. An offer is prepared in one document, the work is recorded somewhere else, and the invoice is typed again from scratch, with the errors that implies and no reliable link back from an invoice to the work it covers.
Approach
The equipment register is the core entity. Not the client, and not the invoice. Every individual item is recorded against a client site, with its type, identifier, installation date, and its own next-service date.
This is the decision the whole system rests on. Because compliance dates belong to items rather than to clients, equipment added at any point in the year is tracked correctly from that point, and a site with items on different schedules is represented accurately rather than approximated.
Service intervals are configurable rules. The twelve-month interval is the common case, not a universal one. Different equipment types carry different requirements, and regulation changes. Intervals are held as configuration against equipment type, so a rule change is an administrative update rather than a development task.
Reminders lead the due date, not follow it. A reminder that arrives on the day service is due is already late, because the visit still has to be scheduled and attended. Reminders are generated on a lead time that gives the office room to contact the client, agree a date and dispatch a technician before the deadline passes.
Escalation matters as much as the initial reminder. An unanswered reminder needs to resurface rather than disappear, because the silent failure mode here is a client who simply never replied.
Offer, order, service, invoice is one chain. An offer is prepared from the equipment register, so it already knows what is at the site. Accepted, it becomes scheduled work. Once the work is recorded, the invoice is generated from what was actually done. Every stage references the one before it, which removes the re-keying and makes the question “what does this invoice cover?” answerable directly.
Service history is permanent. Each visit records what was inspected, what was replaced, what failed and who attended, appended rather than overwritten. This is what allows the company to demonstrate to a client, or to an inspector, that an item has been maintained continuously rather than asserting it.
Accounting reflects the recurring model. Because the system knows every item and its schedule, it can show forward revenue from services already due, which is a materially better planning input than last year’s totals.
Results
The platform tracks statutory service intervals per item with automatic reminders ahead of each due date, holds a complete per-asset service history, and runs offers, orders and invoicing as one connected workflow rather than three disconnected documents.
The value is largely in what stops happening. Renewals are not missed because nobody noticed the date, invoices match the work because they are generated from it, and the compliance position of any client site can be answered from the system rather than reconstructed from files.