2026-10-20 · 6 min
The spreadsheet your operation runs on, and how to retire it
One shared spreadsheet runs your jobs, pricing or schedule, and one person understands it. How operators move it into a real system without dropping work.
Every operation has one. It started as a quick list of open jobs. Now it has fourteen tabs, highlighted rows that only two people can decode, a pricing formula that breaks if anyone sorts the wrong column, and a copy called "FINAL v3 USE THIS ONE" sitting next to the real thing. Scheduling, quotes, stock or job status all run through it.
When the person who built it takes leave, the business slows down. When they resign, it stops.
Nobody planned this. The spreadsheet won because it was the fastest way to get the work done when the CRM did not fit. That is also why ripping it out so often fails: the replacement is slower for the people who do the work, so within weeks the spreadsheet is back as a "temporary" export.
Why the spreadsheet keeps beating the system
- It fits the work exactly, because the people doing the work built it.
- Changes take seconds. Adding a column beats raising a change request and waiting for the next release.
- It holds the rules nobody wrote down. Yellow means waiting on parts. One customer gets a price override. A hidden tab lists the exceptions.
- It is the only place the whole picture exists, because sales, ops and finance data all get pasted into it.
The cost hiding in the tabs
The spreadsheet looks free. It is not.
- One person holds the key. If they are away, nobody else can safely change it, and some days nobody can read it.
- Two copies give two answers. Someone reads an old version, and a customer gets the wrong date or the wrong price.
- Formula errors stay silent. A broken cell can quote the wrong margin for weeks before anyone notices.
- There is no history. Nobody can say who moved a due date, when, or why.
- Access is all or nothing. Either everyone sees cost prices and staff rates, or the people on site cannot update anything.
- Reporting is rebuilt by hand, which is how leadership ends up with numbers it does not trust. We covered that in ops reporting leadership trusts.
Treat the spreadsheet as your requirements document
The spreadsheet is the most honest description of how your operation really works. Read it properly before anyone designs a screen.
Map every tab to a decision. Which tab tells someone what to do next, which one feeds a report, and which one nobody has opened in a long time.
Write down the hidden rules. Every highlight colour, comment, hidden column and manual override is a status, a field or a rule the new system has to carry. Miss one and the team will keep the old sheet open "just in case."
Find out who touches it. Who adds rows, who only reads, who exports it every day for someone else. Each of those is a different screen or a different alert.
Mark what gets pasted in. Columns copied from the CRM, the finance system or an email are not data entry. They are connections the new system should make for you.
Moving the work across without switching everything over at once
Start with the tab that hurts most. Job status or scheduling is usually the first win. Do not try to move the whole file in one go.
Make the new screen faster than the sheet. Design for the person who updates it most often. If logging a job takes more clicks than typing a row, the spreadsheet wins again.
Flip the source, then retire the copy. Once the system holds the live data, give anyone who still wants the spreadsheet a read-only export generated from it. When nobody has opened that export for a while, switch it off.
Bring history across clean. Match duplicate customers, sites and jobs on the way in, using the same rules we described in one customer, one record, so the new system starts trusted rather than inheriting the mess.
Keep the flexibility people loved. Let ops owners change price tables, drop-down lists and simple rules themselves, so a small tweak is still minutes, not a project.
Put it where the work happens. If updates come from site, a field mobile app turns the end-of-day spreadsheet catch-up into a one-tap update on the job.
Five questions that tell you which sheet to retire first
- If the person who maintains it disappeared for two weeks, would work stop?
- Has a customer received a wrong date, price or status because someone read an old copy?
- Do staff copy data out of the CRM into the sheet, then type it back again later?
- Could you say who last changed a job's due date, and why?
- Is there a tab nobody is allowed to sort?
A yes to the first question is reason enough to start. A yes to most of them means the spreadsheet is already running the business, and it has no backup.
What the team notices once the sheet is gone
- The person who owned the spreadsheet gets their time back and stops being the office help desk.
- Everyone reads the same status, so customers get one answer no matter who picks up the phone.
- The unwritten rules now live in the system, so new starters are useful in days instead of shadowing someone for weeks.
- Reports come straight from the work, so nobody rebuilds them before a meeting.
- Changes still happen fast, because the people who run the operation can adjust the settings themselves.
Datacat turns the spreadsheets operators depend on into systems their teams actually prefer to use. Sometimes that is a custom CRM and ops platform built around the tabs your people already know. Sometimes it is ops workflow automation that ends the copy and paste between the CRM and the sheet. If you are not sure which spreadsheet to start with, a paid discovery engagement maps every tab to a decision and gives you a fixed-scope plan to replace it. See work we have delivered, or send us the spreadsheet everyone is afraid to sort.