What are the early signs that our off-the-shelf software is about to stop fitting?
The reliable early signal is not a missing feature. It is the growth of work that exists only to compensate for the software: shadow spreadsheets, naming conventions that encode meaning the system cannot hold, and a person whose job is moving data between screens. When compensating work grows faster than volume, the fit is already gone.
Missing features are a weak signal
Every business wants features its software does not have. That is normal and usually not worth acting on. Vendors ship roadmaps, and a feature gap that annoys you today may close on its own.
The signal worth watching is structural: whether your team has started building an unofficial second system alongside the official one. That second system is almost always a spreadsheet, a shared drive folder, or a naming convention.
Feature gaps are complaints. Compensating systems are evidence, because building one costs your team real time every week and nobody does it for fun.
Four things to look for
- Encoded meaning in free-text fields. When job names start carrying codes like -WARR or **REBOOK, the data model is missing a field the business genuinely needs.
- A shadow spreadsheet that leadership actually trusts more than the system. If the number in the weekly meeting comes from a spreadsheet, the system of record has quietly moved.
- Human copy-paste between two screens. One person moving the same data twice daily is a standing integration cost being paid in salary.
- Reports that require a person to assemble them. Not run them. Assemble them.
The growth-rate test
Measure the compensating work, not the complaint volume. Count the hours per week spent on workarounds this quarter versus two quarters ago, and compare that growth to your job or location growth.
If workaround hours grow roughly in line with volume, the software still fits and you have a staffing question. If workaround hours grow faster than volume, the software has stopped scaling with you and the gap will keep widening. That second pattern is the one that justifies looking at custom software or a targeted integration layer.
Run the count honestly. Ask each team to log workaround time for one week rather than estimating it, since estimates understate anything that has become habit.
What you do about it is usually narrower than replacement
Outgrowing a platform almost never means ripping it out. Field service platforms, CRMs and accounting systems hold enormous operational value that is expensive to rebuild and boring to maintain.
The common answer is to keep the platform as the operational system of record and build the missing capability around it through its API. That is what a ServiceTitan integration or a Jobber integration usually is in practice: the platform keeps doing what it is good at, and the specific thing it cannot do gets built once, properly, against its data.
Topics: build vs buy · saas limits · diagnostics · workarounds
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.