When a service business grows past a certain point, the spreadsheets that held everything together start to become the thing that holds growth back. This case study documents how one business crossed that line and what the path forward looked like.
The situation
The business — a service company managing field operations across multiple sites — had been running on three spreadsheets for years. One tracked bookings and job assignments. A second tracked inventory costs and materials usage per job. A third managed client communications and follow-up tasks.
Each spreadsheet was owned and maintained by a different person. Each had its own formatting conventions, its own update cadence, and its own tolerance for missing data. When someone needed a cross-reference — what jobs had been completed this week, and what did they cost, and which clients were awaiting follow-up — they had to open all three files and build the picture manually.
This worked when the team was small. At scale, it became a full-time reconciliation job that nobody had been hired to do.
What the portal replaced
Booking and job tracking: the first spreadsheet tracked open jobs, assigned technicians, and job status. The portal replaced this with a live job board — status updated in real time as technicians progressed through work, with automatic notifications to the operations manager when a job was completed or flagged.
Inventory and cost tracking: the second spreadsheet logged materials used against each job, with manual cost lookups from a price list. The portal connected directly to the stock list, captured materials at the point of use, and calculated job margins automatically.
Client follow-up: the third spreadsheet tracked which clients had outstanding follow-ups, manually flagged by the admin team. The portal automated follow-up scheduling based on job completion triggers, with a clear task queue that the team worked through rather than a spreadsheet they could forget to open.
Business impact
The change in day-to-day operations was immediate:
- 45% less manual processing time across the operations team. The hours previously spent copying values between spreadsheets, checking whether figures matched, and manually triggering follow-ups were redirected to actual operations work.
- Fewer data entry errors: with a single source of truth, the category of error created by two people updating the same record differently was eliminated entirely.
- Better team visibility: the operations manager could see the live state of all jobs, costs, and follow-ups from a single screen rather than assembling the picture from multiple files.
The payback period for the development investment was under six months, largely because the time savings were realised in the first week of use.
Why custom software was the right answer
The team considered off-the-shelf field service platforms before committing to a custom build. The challenge was that the existing workflow was specific to how this business operated — job types, cost categories, and client follow-up triggers that did not map neatly to any standard SaaS product.
A generic platform would have required the team to adapt their process to the software. The custom portal was built around the process as it actually worked. That distinction made adoption straightforward — the team recognised their own workflow in the interface rather than learning a new one.
"Once the portal was live, the team stopped copying values across spreadsheets and started trusting the data."
What made the build succeed
Several decisions in the design phase contributed to the outcome:
A tight initial scope: the portal launched with the core three functions — job tracking, cost capture, and follow-up management. Features requested by individual team members were logged but deferred. Starting narrow meant the team had something working quickly, which built confidence in the product.
User testing during development: key users from the operations team reviewed screens at each stage and flagged terminology, field names, and workflow steps that did not match how they worked. Catching those mismatches before launch avoided a post-launch retraining problem.
A single data owner per record type: the portal established clear ownership — the job owner updates job status, the technician captures materials, the admin team manages follow-ups. Removing ambiguity about who should update what eliminated a major source of the previous errors.
Recommended next step
If you have a similar situation — operations running on spreadsheets that have started to slow the team down — map the workflow end to end before evaluating any solution. The map will show you where the data lives, who touches it, and where the reconciliation bottlenecks are. That is the input you need to decide whether a custom build, an integration, or a SaaS tool is the right answer.