A trade services business with twelve field crews was winning more work than its administration could carry. Jobs arrived by phone and email, were transcribed onto paper job cards, re-keyed into the accounting system, and scheduled on a whiteboard that only one person fully understood. The office manager — the business's indispensable human database — was working Saturday mornings to keep up, and jobs were being missed.
The problem
We were engaged after two consecutive months in which jobs were either double-booked or forgotten entirely. Measuring the baseline made the cost visible: each job was touched five times before a technician saw it, quoting lagged site visits by up to nine days, and roughly one job in twenty was invoiced late because the paperwork returned incomplete. The administration consumed an estimated sixty office hours a week, and the business had stopped quoting for work types it could not schedule reliably.
The obstacles
The solution was not simply software. Three obstacles shaped the work. First, the whiteboard scheduler was genuinely good — any replacement had to be at least as intuitive, or field and office staff would quietly revert. Second, twelve technicians worked across areas with poor mobile coverage, so any digital job card had to tolerate offline use. Third, the owner feared that a structured system would slow down the informal flexibility that customers valued — the "can you send someone today?" calls that the business was built on.
What we did
Our advisory review mapped the current flow and redesigned it before any system decision was made: one point of intake, a defined priority rule set, and a standard job record. We then configured the job management platform the business already paid for but barely used — no new software purchase — building an automated intake from email and web forms, digital job cards with offline capture, and a scheduling view with the same immediacy as the whiteboard. A two-crew pilot ran for three weeks against the paper process before full rollout, with the paper fallback available and unused by the second week.
The result
Within one quarter, administration fell by roughly twelve hours a week and Saturday work stopped. Quotes went out within two days of site visits; late invoicing fell from one job in twenty to under one in fifty; and the double-booking failures stopped entirely. The office manager's knowledge now lives in the system rather than in her head — documented, backed up, and visible to the owner for the first time. The business resumed quoting the work types it had previously avoided, with the confidence that it could schedule them.
Engagement type: Defined Project (process review, configuration, automation build, rollout), followed by a light advisory retainer.
What made this one work
Three decisions carried the engagement, and they generalise well beyond this client. First, we redesigned before we configured: the intake rules, the priority logic and the standard job record were settled on paper with the owner before a single setting was touched, which meant the system inherited a designed process instead of a photographed mess. Second, we protected the flexibility the business was famous for: the new scheduling view deliberately kept an "urgent — slot anywhere" lane, so the same-day calls that built the company's reputation still worked — they just left a record now. Third, the pilot was a real contest: two crews ran digital while the office ran paper simultaneously for three weeks, and the digital side had to win on evidence. It did, quickly — but the staff knew a fallback existed, which is what made them willing to try.
The broader pattern is worth naming for any owner facing a similar bottleneck: the constraint was never the office manager's effort but the absence of a system she could delegate to. Automation did not replace her; it gave her subordinates a structure they could execute, which is why the hours saved kept compounding after the engagement ended.
A similar bottleneck in your business?
A scoped review can size it in two weeks.