Nobody decides to outgrow their software. It happens a workaround at a time. Someone builds a spreadsheet to cover a gap. Someone else exports from one system to key into another. A report that used to take an hour takes a day, and a person gets hired to produce it. By the time anyone says the system is holding the company back, the company has been running on top of it for years.
Here is how it shows up in the four places we see most often, and what the sensible next step is for each.
QuickBooks
QuickBooks is a good accounting system. It was never meant to run operations, and the signs you are asking it to are hard to miss.
- Inventory, jobs, or projects are tracked in QuickBooks with custom fields and a naming convention only two people understand.
- Month-end close depends on exports to Excel, manual adjustments, and re-imports.
- You have more than one company file, or one file so large it has slowed down.
- Sales, operations, and finance each have their own version of the customer list.
What to do. Keep QuickBooks for the books. The problem is everything you bolted onto it. Usually that means an operations system that owns jobs, inventory, or scheduling and posts summary transactions to accounting, rather than a bigger accounting package.
Spreadsheets
Every growing company runs part of the business on spreadsheets, and that is fine until the spreadsheet becomes the system of record.
- One person owns the spreadsheet, and the business stops when they are out.
- Several copies exist, and nobody is sure which one is right.
- It has macros, lookups into other spreadsheets, or a tab called “DO NOT TOUCH.”
- Decisions wait for the spreadsheet to be updated, and it is updated after the fact.
What to do. Do not replace the spreadsheet with a bigger spreadsheet, and do not assume you need a large system. Most spreadsheet-run processes become a narrow internal application: a few screens, one workflow, one or two integrations. It is the smallest and most common kind of custom software, and we wrote about how long that takes to build.
An off-the-shelf ERP or industry package
Packaged software fits the average company in its category. If you have grown past average, or you compete on how you operate, the fit breaks.
- Your team works around the system: parallel spreadsheets, manual steps between modules, “we just don’t use that part.”
- Customizations from an implementer have made upgrades risky or impossible.
- The vendor’s roadmap does not include the thing you need most.
- License and support costs keep rising while the system does less of your work.
What to do. This is where an honest build-versus-buy call matters. Sometimes a different package fits. Often the right answer is to keep the package for what it does well and build the piece that makes you different around it, connected properly. A System Evaluation of what you run today is the fastest way to know which.
A vendor’s platform or a system built by a former partner
The system was built for you, by a vendor, a freelancer, or a former employee, and now you depend on it without being able to change it.
- Changes take months, cost more each time, or are refused.
- Only the vendor can deploy, and you do not have the source code or the cloud accounts.
- Bugs recur, and every fix seems to break something else.
- The person who built it has left, or the vendor has gone quiet.
What to do. Get an independent read before deciding anything. A System Evaluation tells you what you actually have, what it would take to stabilize it, and whether to modernize it in slices or replace it. Modernizing behind the running system is far more common than a rewrite, and far less risky. If the relationship itself is the problem, see project rescue.
The common thread
In every case, the software stopped being a tool and became a constraint, and the constraint showed up as people: the person who owns the spreadsheet, the hire who produces the report, the team that works around the system. If you are adding people to compensate for a system, you have outgrown it.
The next step is the same regardless of which system it is: find out exactly what you are depending on, then decide. Here is how getting started works, and here is what custom software typically costs so you can size the decision before the first call.