Off-the-shelf software is usually the right starting point. It is cheaper, faster to adopt, and someone else maintains it. The trouble is that the moment it stops fitting rarely announces itself. It shows up as workarounds, double entry and a slow tax on everyone’s time. Here are the signs we see most often when a business has outgrown its tools.
1. The spreadsheet has become a system of record
There is a spreadsheet, or several, that the business genuinely cannot run without. It is emailed around, it has rules only one person understands, and it breaks when they are on leave. That spreadsheet is software you already depend on, without any of the safeguards real software has.
2. Staff are doing the integration by hand
Someone exports from one system and types it into another. Maybe daily, maybe every close. It is slow, it is error-prone, and it is a sign two tools that should talk to each other do not. Manual re-keying is one of the clearest signals that your stack has a gap worth closing with integration.
3. You are paying for features to get one you need
To unlock the single capability that matters, you are on a tier full of things you will never use, or stitching together three subscriptions that almost overlap. When the cost of bending around a product approaches the cost of building exactly what you need, the maths has changed.
4. The workaround is now the process
Every tool has quirks. The warning sign is when the workaround gets written into the training, defended in meetings, and treated as just how things are done. At that point the software is shaping your operation instead of supporting it.
5. You cannot answer a basic question quickly
Which site wastes the most stock? Which menu items actually make money? If pulling the answer means an afternoon of exports and reconciliation, the data is there but the tooling is not. Good custom software is often less about new features and more about making the numbers you already have usable.
Outgrowing off-the-shelf is not a failure - it is a sign the business has matured past the generic. The fix is rarely to rebuild everything. It is usually to build the one piece that fits exactly, and let it carry the weight the spreadsheet was never meant to. If you are weighing that, start with build versus buy and what a custom build actually costs.
Frequently asked questions
- When should a business move from off-the-shelf software to custom?
- When the cost of working around a product - in staff time, double entry, missed data and lost margin - starts to approach the cost of building exactly what you need. Clear signals include a spreadsheet that has quietly become a system of record, staff re-keying data between tools by hand, and basic questions about the business taking hours to answer.
- Does going custom mean replacing all of our existing systems?
- Almost never. The usual fix is to build the one piece that does not fit and integrate it with the tools that work fine, rather than rebuilding everything. That keeps cost and risk down and lets you keep the software your team already knows.