Nobody plans to run a business on a spreadsheet
It just happens. You win your first few jobs, you open Excel, you make a tab. Job name, client, start date, value, status. It takes ten minutes and it works.
Three years later that file has 14 tabs, colour coding only you understand, a column called "STATUS 2 (USE THIS ONE)", and a copy on the office PC that does not match the copy in your email. Every business I have built a system for started exactly here. The spreadsheet was never a mistake. It was the right tool for the size you were.
The problem is that spreadsheets fail quietly. There is no error message when your job tracker stops being an asset and starts being the thing holding you back. So here are the actual failure modes, the point where they start costing real money, and an honest look at what your options are.
The four ways Excel job tracking breaks
Version chaos. The file gets emailed, copied to a laptop, downloaded from OneDrive "just to check something". Now there are four versions and nobody is sure which one is true. The tell is the question "is this the latest one?" being asked in your office more than once a week. Every hour spent reconciling versions is pure waste, and the errors that survive reconciliation are worse: a job priced off last month's labour rates, a variation that only exists in the version on someone's laptop.
One owner. In most firms one person actually understands the spreadsheet. They built the formulas, they know that the yellow rows mean "waiting on the client" and the bold ones mean "invoice sent". When they are on holiday, off sick, or they leave, job tracking effectively stops. That person is usually also the busiest person in the business, which means the tracker gets updated when they have time, not when things happen.
No audit trail. A cell said £14,200 yesterday and £12,400 today. Who changed it? When? Why? Excel will not tell you. When a client disputes a variation, or a CIS deduction gets queried, or your accountant asks why the job margin moved, you have nothing to point at. Track Changes and version history exist, but be honest: nobody in a trades office is combing through OneDrive version history mid-dispute.
Useless on site. A spreadsheet on a phone is a punishment. So the people actually doing the work do not update it. They ring the office, send a WhatsApp, or write it on a day sheet that gets typed up on Friday. Which means your "live" job tracker is really a diary of what someone remembered to type up, days after it happened. The re-keying alone is hours a week, and it is where most of the errors get in.
When it starts costing real money
None of those failure modes matter much at three jobs a month. They compound at fifteen. The signals that you have crossed the line are practical, not technical:
- Someone spends part of every day updating or fixing the spreadsheet rather than doing their actual job.
- A job has been missed, double-booked, or invoiced wrong because two versions of the file disagreed.
- You cannot answer "what is the margin on the Hartley job right now?" without twenty minutes of digging.
- Site staff have stopped even pretending to update it.
- You avoid taking on more work, not because you lack the trades, but because the admin would not cope.
If two or more of those are true, the spreadsheet is the bottleneck. The question is what to replace it with, and there are only three honest answers.
Option 1: better spreadsheet discipline
Cheapest option, and sometimes the right one. One master file in one shared location, no emailed copies ever. One named owner. Data validation on the status column instead of colour coding. A short weekly routine where the file is reviewed and corrected.
This works if you are small enough that one person can genuinely own it, your jobs are simple, and your headcount is stable. It costs nothing but discipline. Its weakness is that it fixes version chaos and nothing else: still no audit trail, still useless on site, still one owner. Treat it as buying time, not solving the problem. If you are under roughly ten live jobs at a time, buy the time.
Option 2: vertical SaaS
Jobber, Tradify, ServiceM8, Simpro and the rest exist precisely because of this spreadsheet. They are cheap to start, you can be running in a week, and the mobile apps are genuinely good, which fixes the on-site problem overnight.
The honest criteria: SaaS is the right answer if your workflow is close to the industry standard the software assumes. Quote, schedule, do the work, invoice. If that describes you, buy it, and do not let anyone (including a custom developer) talk you out of it.
It becomes the wrong answer when your process does not fit their boxes. Multi-stage jobs with retentions, quoting logic that lives in your estimator's head, approval chains, pricing that depends on supplier rates you renegotiate quarterly. You can bend vertical SaaS a long way with workarounds, but every workaround is a new mini-spreadsheet growing in the gaps. I have written a separate honest comparison of Jobber, Tradify and custom systems if you are at that decision.
Option 3: bespoke
A system built around how your business actually runs. One source of truth, an audit trail on every change, works on a phone in a van, and encodes your quoting and job logic rather than a generic version of it.
The honest criteria: bespoke makes sense when the gap between your process and the SaaS template is wide, when the spreadsheet is costing you serious hours every week, and when the business is stable enough that the process is worth encoding. It costs more than SaaS and takes longer than neither. It is the wrong answer for a two-person firm with simple jobs, and anyone who tells a two-person firm otherwise is selling, not advising.
The way to de-risk it is to see it working before you commit: a working demo built against your real workflow, a written scope, and a fixed price against that scope. If a developer will not work that way, keep looking.
The one-line test
If your jobs fit a template, buy the template. If your process is genuinely yours, and the spreadsheet groaning under it is costing you hours and errors every week, it is time to build the thing the spreadsheet was always pretending to be.