You probably built the spreadsheet yourself. Maybe four years ago. Maybe eight. You knew every project by name, every client by habit, every outstanding invoice without checking. The spreadsheet was a memory aid more than a system. It worked.
Then the firm grew, or the projects got more complex, or you hired someone, or all three. And now the spreadsheet is a separate job. You maintain it instead of using it. You correct it instead of trusting it. And every week you're aware that one wrong cell, one version saved over another, one row added in the wrong column, could cost you money or a client relationship or both.
The question isn't whether your spreadsheet is bad. The question is whether it still fits the firm you're actually running.
Twelve signs it doesn't
1. You've had a version control problem that cost you money. Someone worked from an old version. A fee proposal went out with last year's rates. A project tracker showed a completion date that had been updated in one copy but not the other. One incident is a warning. Two is a system problem.
2. A new hire took more than two weeks to understand your tracking system. If your project tracker requires a handover conversation to make sense, it isn't a system. It's tribal knowledge encoded in cells. When the person who built it leaves, you'll spend weeks reconstructing what it meant.
3. You've sent a quote to the wrong client. The quote was right. The name was wrong. Or the project reference was wrong. You caught it, or the client did. Either way, it was embarrassing. This happens in firms that work from templates carrying old data forward.
4. You've invoiced twice for the same job, or not at all. Twice is obvious when the client calls. Not at all is discovered at year-end when you reconcile and realise a £4,000 project completed in October was never invoiced. According to KPMG's Global Construction Survey, billing errors and revenue leakage are the most common financial issue cited by small engineering consultancies.
5. You can't tell in 30 seconds what's outstanding across all projects. Open your spreadsheet right now. How long does it take to see, clearly, which projects have unpaid invoices, which are overdue, and which clients owe you money? If it takes more than 30 seconds, that's not a reporting function. That's a manual exercise.
6. Your Xero and your spreadsheet never quite match. Maybe they're close. But there's always a timing difference, a payment recorded in one system before the other, a refund that didn't make it into the tracker. They should show the same number. They don't. So which one do you trust?
7. A client asked for a project update and you had to check three places. Email. Spreadsheet. Dropbox. Sometimes a text thread too. The information exists. It's just not in one place.
8. You've lost a drawing in Dropbox. Or SharePoint. Or a shared drive that reorganised itself when someone changed folder names. The drawing still exists, probably. It takes 20 minutes to confirm that.
9. Payment reminders are sent manually and sometimes forgotten. You have a note to yourself. Or a calendar reminder. Or you rely on the feeling that it's been long enough. This works most of the time. When it doesn't, an invoice that should have been paid in 30 days is now 60 days old and you're chasing it personally.
10. You can't show a new partner what happened on a project six months ago without a lengthy explanation. They ask for context. You have emails, a spreadsheet row, maybe a folder of drawings. But the story of how the project unfolded, who said what when, what was agreed and then revised, doesn't exist in a form you can simply hand to someone.
11. You've had a dispute that came down to 'I never received that email.' And you might have resolved it faster if you'd had the full email chain in front of you in 30 seconds rather than 30 minutes. You probably found it eventually. But the conversation had already moved past it.
12. You've turned down work because you didn't have the capacity to manage more complexity. Not more engineering. More admin. The project was there. The fee was right. But the thought of running a fifteenth project through the same system already straining at twelve was enough to make you hesitate.
What comes after the spreadsheet
You don't need enterprise software. You don't need a six-month implementation or a dedicated IT person. You need something that gives you a single project record, automated invoicing, email that attaches to projects, and a view of what's happening across your firm without running a manual report.
The comparison post on this blog covers the main options for UK structural engineering firms in detail. But the short version: the spreadsheet was good enough when the firm was smaller. What you need now is what the spreadsheet was trying to be.
