Spreadsheets are genuinely good software. They are flexible, everyone can use them, and they cost nothing. Most businesses that replace them do so a year or two before they needed to, and a few do so when the real problem was that nobody had agreed the process.
So rather than argue that you have outgrown them, here are the signals that actually mean it.
Five signals it is time
1. Two people can hold different versions of the truth at the same time
Not “the file gets out of date” – that is fixable with discipline. The signal is structural: it is possible for two people to both be looking at a current file and see different numbers. Once that is possible, every disagreement costs a reconciliation.
2. Someone reconciles for a living
If a portion of somebody’s week exists purely to make two records agree, that time is the cost of the current design. It is also usually the easiest cost to quantify when deciding whether a build is justified.
3. A customer or partner needs to see something
Spreadsheets have no permission model worth the name. The moment an external party – an agent, a client, a supplier – needs scoped visibility, you either build a portal or you email extracts forever. We built an agent wallet system for exactly this reason: partners wanted to book without phoning, and finance wanted a reconciled position at all times. Those requirements conflict in a spreadsheet.
4. An audit or a regulator is coming
Spreadsheets cannot show who changed what and when. If you are heading towards an audit, a licence renewal or an authority submission process, the absence of an audit trail becomes the finding.
5. The person who understands the file is a single point of failure
Every mature spreadsheet has one author who knows why a particular formula is the way it is. That is a business continuity risk that grows quietly and is only noticed when they resign.
Three signals that are not it
“It looks unprofessional.” Nobody outside the business sees it. This is a bad reason to spend money.
“A competitor has a system.” They may also be regretting it. Software is not a status purchase.
“The file is getting slow.” Usually fixable. Split it, remove volatile formulas, move history to a separate file. That is an afternoon, not a project.
The step most people skip
Before you cost a build, write down the current process – including the workarounds nobody admits to. Two things happen. Sometimes the act of writing it down reveals that the process is the problem and no software will fix it. And sometimes it reveals the process is genuinely standard, in which case an off-the-shelf product will be cheaper than anything custom.
Either outcome saves you more than a well-built system would have.