When off the shelf software stops fitting
Workarounds, spreadsheets and too many subscriptions are signs your software no longer fits. Learn when a custom application makes sense.
For: Businesses working around the limits of their tools
Lorenzo DevereuxFounder & CEO, Devereux Digitals

Off the shelf software is usually the right starting point. It’s quick to adopt, affordable and good enough for common needs. But as a business grows, its processes become more specific and the software stops fitting.
The symptoms creep in slowly: workarounds, extra spreadsheets, more subscriptions and staff copying information between systems. At some point, adapting the business to the software costs more than building software for the business.
Signs you are outgrowing your software
- Staff keep spreadsheets alongside the software to track what it can’t.
- The same data is entered into several systems.
- You pay for multiple tools that each do part of a job.
- Key processes rely on one person who knows the workarounds.
- Customers experience delays or errors caused by your systems.
- You’ve asked vendors for features that never arrive.
Your options, from light to heavy
- Configure better
- Integrate tools
- Add a custom module
- Build a full application
Before building anything, check whether better configuration or integrations would solve the problem. If not, a custom module, such as an internal dashboard or a portal, can bridge the gap without replacing systems that work well.
Build where you are different, buy where you are not
Accounting, email and payroll work much the same in most businesses, so buying makes sense. But the way you quote, schedule, deliver or serve customers may be what sets you apart. That’s where custom software can create a lasting advantage.
Start with a focused first version
- Pick one painful processChoose the workflow that wastes the most time or causes the most errors.
- Define the minimumList only the features needed to replace the workaround.
- Build and test with real usersShort cycles with your team catch problems early.
- Expand from evidenceAdd features based on actual use rather than assumptions.
What to consider before you build
- Ownership of the code and data.
- Hosting, security and backups.
- Ongoing maintenance, and who provides support.
- Integrations with your existing tools.
- How the system will grow as the business grows.
Illustrative example: a cleaning company outgrowing its job app
Imagine a commercial cleaning company using a popular job management app plus three spreadsheets: one for recurring contract schedules, one for staff availability and one for supplies per site. Managers copy information between them every week, and mistakes lead to missed cleans.
Rather than replacing everything, the company could build a focused scheduling tool that reads contracts and availability, generates the weekly rota and pushes jobs into the existing app through its API. The job app keeps doing what it does well, and the spreadsheets disappear.
If the tool proves its value, later versions could add supplies tracking and a client portal.
Common mistakes to avoid
- Building custom software before trying configuration and integrations.
- Replacing systems that work well.
- Specifying every possible feature up front.
- Not agreeing code and data ownership.
How to measure success
Track time spent on workarounds, the number of spreadsheets used alongside your software, error rates in the affected process and total software subscription cost.
After a custom tool launches, measure the same numbers again. The difference is the clearest evidence of whether building was the right call.
Your action checklist
- List workarounds and spreadsheets used alongside your tools.
- Estimate the time they cost each month.
- Check configuration and integration options.
- Identify where your process is unique.
- Define a focused first version.
- Agree ownership, hosting and support.
Questions to ask before you start
- Which workarounds do we rely on every week?
- What would it cost to keep working this way for three more years?
- Is this process a competitive advantage?
- Who will own and support the custom software?
Tools and technologies
- Next.js
- React
- Node.js
- PostgreSQL
- Supabase
- Vercel or AWS
Frequently asked questions
Conclusion
Off the shelf software is a great start, but not always a great finish. When workarounds pile up, a focused custom application can remove them and give you a system that fits how you actually work.


