This is what we do

The business ran its entire operation through a general-purpose customer support helpdesk. It worked, in the sense that nothing was on fire. But the software had no idea what the business did.

A job was a support ticket. The system had no concept of a quote, a consignment, a dangerous goods classification or an invoice, so all of that lived in inboxes and spreadsheets alongside it. Correspondence for a single job scattered across separate tickets, because the helpdesk grouped mail by subject line rather than by the job it belonged to. One shipment could end up as three unrelated conversations, and an operator would only find the supplier's reply by going looking for it.

Every workaround was somebody's memory. The shape of a job, which supplier was owed a reply, whether a load had been paid for: all of it lived in the heads of the people who had been there longest, held together by diligence rather than by any system.

Then the vendor contract came up for renewal with a hard end date.

A purpose-built operations platform, and now the system the business opens in the morning and works out of all day.

A job lifecycle that matches the business rather than a ticket queue: quote, approval, booking, movement, invoicing.

An inbound mail pipeline that threads incoming messages onto the right job by matching sender and subject within a rolling window. Staff replying from Outlook loop back in and land on that job rather than a separate inbox.

Freight booking integration, with quote requests and their callbacks flowing straight into the job record.

Accounts controls, including payment locks that stop a cash-on-delivery job progressing before it is paid.

Side conversations, so a supplier thread runs alongside the customer thread on the same job without either party seeing the other.

Column-level change history on the records that carry it, so a disputed value can be traced to who changed it and when.

Work across several treatment plants was coordinated by spreadsheet and phone between supervisors, operators and contractors. Recurring maintenance schedules existed largely as documents and individual knowledge, which meant the quality of the schedule depended on who was doing it that week.

Nothing was broken, exactly. But there was no single place where a supervisor could see what was happening across every plant at once, and no structural reason a recurring task would be scheduled the same way twice.

A real-time scheduling and task management application, now in daily use by the operations group.

Scheduling across multiple plants, visible to supervisors and operators at the same time rather than reconciled after the fact.

A task template library, so recurring maintenance is scheduled from a known standard instead of rebuilt from memory. 1,089 templates were imported during the build.

Contractor management, with 21 external contractors assignable to work directly in the system.

Role separation between scheduler-administrators, supervisors and operators, so the schedule cannot be quietly rewritten by anyone who opens it.

SMS notification to operators.

Workplace health and safety records lived as three disconnected sets of forms: incident reports, hazard reports, and corrective actions. Each worked on its own. None of them knew about the others.

So a hazard could be reported, and a corrective action raised in response, and nothing in the system connected the two. Nothing chased an action that had gone past its due date. Whether anything actually got fixed depended on somebody remembering that it was outstanding, which is precisely the thing a safety system exists to stop depending on.

Silver Lake had previously proposed a custom-built command centre for this firm.

On working through what the requirement actually was, that proposal was withdrawn and the recommendation reversed: do not build custom software. The firm already licensed a business software suite capable of doing this properly, and its own staff could maintain a solution built there without depending on an external developer indefinitely.

Three linked lists for incidents, hazards and corrective actions, joined so every corrective action permanently carries the report that caused it.

Three automated flows. A submission saves the record and notifies. An assigned action notifies its owner. A daily job chases everything overdue, which is the one that changes behaviour.

Delivered as a step-by-step build guide, with flowcharts and exact interface labels, so the firm's own team could implement it without further involvement.