The Scenario
A facilities management company with sixty staff runs its job scheduling, quoting, and invoicing through a network of Excel workbooks. The system started as a single spreadsheet eight years ago when the founder managed a team of five. It tracked jobs, costs, and client details in one place. It worked.
Eight years and twelve times the headcount later, that single spreadsheet has spawned into a constellation of linked workbooks. There is a master job tracker, a quoting template, a client database, a subcontractor rates sheet, a vehicle allocation grid, and a monthly revenue summary that references all of them. Seventeen files in total, stored on a shared network drive, maintained by a combination of the office manager, two administrators, and the managing director.
Every morning begins with the same routine. The office manager opens the job tracker, cross-references overnight emails to update statuses, checks the quoting workbook for anything awaiting approval, and reconciles yesterday’s completed jobs against the invoicing sheet. The process takes ninety minutes on a good day. On a bad day, when a formula breaks, a file is locked by another user, or someone has accidentally overwritten a row, it takes the entire morning.
The Problem
The spreadsheets have become the business, and not in the way the founder intended. Every process has been bent around the limitations of the tools rather than designed around the needs of the operation.
Job scheduling is limited by the number of rows that can practically be managed in a single view. Quoting requires copying and pasting between three separate files. Client history is scattered across tabs that were added ad hoc over the years, with no consistent structure. Finding the last five jobs for a specific client means manually searching through thousands of rows with Ctrl+F.
Errors compound. A mistyped cell reference in the invoicing sheet once caused three weeks of under-billing before anyone noticed. A sorting operation on the job tracker accidentally displaced an entire column, and it took two days to identify and correct the damage. The office manager keeps a personal backup on a USB drive because she does not trust the shared versions.
The business cannot hire another administrator because there is no way for a new person to learn the system. It exists entirely as institutional knowledge in the heads of three people. There is no documentation, no validation, and no audit trail. When the managing director asks how many jobs were completed last quarter, the answer takes a full day to compile because the data was never designed to be queried.
The Approach
The company engages Digital Royalty to replace the spreadsheet ecosystem with a purpose-built internal system. The first phase is understanding, not building. Every workbook is mapped, every formula chain traced, every manual process documented. The goal is to extract the business logic that has been encoded implicitly in cell references and colour-coded rows, and make it explicit in a system that enforces it automatically.
The replacement system is built around the actual workflow: a job comes in, gets quoted, gets approved, gets scheduled, gets completed, gets invoiced. Each stage has defined fields, validation rules, and status transitions. Client records sit in a single, searchable location with full job history attached. Subcontractor rates are managed centrally with version history so pricing disputes can be resolved against a clear record.
The quoting process, which previously required toggling between three spreadsheets and a calculator, becomes a guided form that pulls in current rates, applies margin rules, and generates a formatted PDF. Invoicing draws directly from completed job records. No re-keying. No copy-paste.
The migration is phased. The job tracker moves first because it is the most fragile and the most used. Quoting follows. Invoicing integrates last, once the data flowing into it from the other modules is reliable. At each stage, the old spreadsheet runs in parallel for two weeks so the team can verify that nothing has been lost.
The Outcome
The ninety-minute morning routine shrinks to fifteen minutes of reviewing a dashboard. The office manager no longer reconciles data between files because there is only one system and it reconciles itself. Status updates happen in real time as engineers close jobs on site via a mobile interface.
Quoting turnaround drops from two days to same-day. The managing director can generate the quarterly job count in under a minute, filtered by client, service type, region, or any combination. When a new administrator joins, she is productive within a week because the system guides the process rather than requiring memorisation of spreadsheet conventions.
The USB backup disappears. So does the anxiety that comes with it. The business has moved from a fragile, person-dependent collection of files to a structured system that will scale with the next sixty hires the same way it handles the current sixty.
Who This Applies To
This scenario is common in businesses that grew quickly from a small founding team: facilities management, construction, recruitment agencies, logistics firms, and professional services. The pattern is the same. A spreadsheet that was adequate for five people has become the operating system for fifty, and nobody planned for that transition. If the phrase “do not sort that column” is part of your team’s vocabulary, this page is for you.
Ready to Retire the Spreadsheets?
The longer a spreadsheet-led process runs, the harder it becomes to replace. The institutional knowledge embedded in those files grows less documented with every passing month, and the risk of a major error accumulates quietly. The right time to move is before something breaks, not after it. Related scenarios worth reading: data migration from Access databases, modernising paper-based workflows, and the full legacy and migration use case index. For implementation context, see replacing spreadsheet-led operations.
