There is always a spreadsheet called something like final_v3_USE_THIS. Sometimes there is also a final_v3_USE_THIS_OLD sitting in the same folder, and nobody will delete it just in case.
That is usually the moment someone gets in touch. Not because spreadsheets are evil. Because this one started as a quick fix and now runs a real chunk of the business, and it is starting to creak.
Maybe you are the owner and you can feel it wobbling but you are not sure if you are being precious. Maybe you are the person who actually understands the sheet, and you are quietly worried about what happens if you are sick for a week. Either way, you want an honest answer: is it bad enough to spend money fixing, or should you just tidy the sheet and carry on?
This article is that conversation.
The honest test up front
Spreadsheets are great. I use them. Most businesses should keep using them for plenty of jobs.
The question is not "is Excel bad." The question is whether this spreadsheet has outgrown its job.
I am going to give you both answers, because both are real. Sometimes you should build something. Sometimes you should leave the spreadsheet alone, or swap it for a simpler tool that already exists. I will tell a client that when it is true. Saying it out loud is what makes the rest of this worth reading.
The signs you have actually outgrown it
These are the signals I listen for on a first call. Not a scorecard. If several of these sound familiar, you are probably past the point where a better sheet fixes it.
Version control is a filename. final_v3_USE_THIS, final_v3_USE_THIS_Jane_edits, the copy someone emailed last Tuesday. Nobody is sure which one is the truth. Meetings start with ten minutes of "which version are we looking at?" That is not a filing problem. That is a system problem wearing a filename.
One wrong formula quietly wrecked a month. A cell referenced the wrong column. A percentage was entered as a whole number. Nobody noticed until someone trusted the number in a decision and it was wrong. After that, people stop trusting the sheet even when it is right. That distrust does not go away with a fresh tab colour.
Several people need it at once and they step on each other. Two people edit at the same time. Someone overwrites a row. Someone else is working from an exported CSV that was already out of date when they opened it. The workaround becomes "don't touch it while Sarah is in there," which does not scale.
You are re-typing the same data between the sheet and everything else. Xero. A booking system. A warehouse export. Email. The spreadsheet is the hub, but nothing talks to anything. Your good people spend their day on copy and paste and "can you send that again." That is labour you are paying for twice.
It is load-bearing, but only one person can drive it. The logic lives in one head. The macros, the exceptions, the "oh, that column doesn't mean what you think." You have a key-person problem you have not named yet. The day that person is on leave, or leaves, the business slows down in a way everyone pretends is normal until it is not.
The workarounds have workarounds. Extra tabs for exceptions. Side documents. A WhatsApp thread that is really part of the workflow. The sheet was supposed to be temporary. It became infrastructure by accident.
If that sounds like your Tuesday, you have probably outgrown the sheet. Not because you failed at spreadsheets. Because the job got bigger than a spreadsheet was built to carry.
The signs you have not, and what to do instead
Here is the paragraph that matters most.
Sometimes the fix is a better structured spreadsheet. Clear tabs. Locked cells. One obvious master copy. A short note at the top that says what each column means. Boring, unglamorous, often enough.
Sometimes the answer is Airtable, Notion, or an off-the-shelf SaaS that already does the job for a fraction of a custom build. If a tool at $50 or $200 a month covers ninety percent of what you need, start there. I will say that on a call when it is true.
Sometimes the process is still changing every week. You are still figuring out what the workflow should be. In that case, a spreadsheet is the right prototype. Building software now would lock in something you will rip out in three months. Live in the sheet until the rules settle.
Sometimes the pain is process, not software. No tool fixes a handoff nobody owns. I have had conversations that ended with "sort out who approves what, then call me," and that was the right outcome.
If you are in one of those buckets, keep the spreadsheet. Or tidy it. Or buy the SaaS. Do not let anyone sell you custom software because you felt embarrassed about Excel.
The cost of staying on it too long
This is the quiet tax of the workaround. Not a dramatic collapse. A slow leak.
Errors nobody catches until they matter. Time bled on re-typing the same figures into three places. Decisions made from numbers everyone half-trusts. Knowledge trapped in one person's head, which becomes a real problem the day that person is sick, on holiday, or gone.
None of that shows up on a P and L line called "spreadsheet risk." It shows up as late nights, missed things, and good staff doing work they hate. Pair that with the money question and you get a clearer picture. What custom software actually costs in NZ is the honest pricing piece that sits next to this one.
Staying on a load-bearing sheet too long rarely feels urgent. That is why it persists.
What actually changes when you replace it
When a replacement is the right call, the payoff is concrete.
Numbers people trust. Validation, audit trails, permissions. Not faith in a formula chain nobody checked.
The thing talks to your other tools. Stripe, Xero, a booking feed, a warehouse export. Data enters once. The re-typing stops.
More than one person can use it without fear. Roles, not "please don't touch column G." Concurrent use without overwrite roulette.
The knowledge is in the system. Rules written down. Workflows visible. Less "ask Dave."
It can grow with the business. The next size up does not mean another tab called final_v4_REALLY_THIS_ONE.
Glovebox is an example from my own work: rental ops for vehicle hire businesses that used to live across spreadsheets, side tools, and manual handoffs. Fleet, bookings, bonds, operator dashboards in one place. That is what "outgrown the sheet" looks like at the platform end. Your first step might be much smaller. Same direction.
How to make the jump without it ballooning
Do not try to replace every spreadsheet in the business at once. Start with the one sheet that hurts most. The one that causes the most re-typing, the most mistrust, or the most key-person risk.
Get that working. Use it for real. Fix what is wrong. Then expand.
That is also how you keep the budget sane. A small internal tool that replaces one painful workflow is a different job to rebuilding how the whole company runs. Once you know you are in build territory, the money question is what custom software actually costs in NZ. The next fork is build versus buy: when an off-the-shelf booking system stops being enough. Buy or subscribe when you can. Build when the workflow is genuinely yours and nothing off the shelf fits without contortions.
The web apps and platforms work I do is built for that second case. Custom when custom earns its keep.
How I work
First, a free chat. Call, video, or coffee in Christchurch if that suits. I want to hear what the sheet is doing, what breaks, and what "better" would look like.
Then a written scope if we are heading toward a build: what I would replace, what it costs, and what it costs if you leave it as-is. Sometimes the scope says "keep the spreadsheet." That is a good outcome too.
If you want to talk it through, get in touch. No hard sell. Just a straight conversation about whether you have actually outgrown the sheet, or whether you just need a tidier one.