Skip to content

14 July 2026

When off-the-shelf software isn't enough: signs you need a custom application

Most businesses don't choose their software deliberately. Here are the signs that what you're running has stopped fitting the shape of how your business actually works.

Architectural cross-section of a craftsman's supply shelf with standard holders, one irregular component on the bench that fits no standard slot, and a craftsman at a fitting jig building a bespoke mount around it

Most businesses don't choose their software deliberately. They start with something that mostly works, add a tool here, a workaround there, and over time arrive at a stack that feels like it belongs to someone else's business.

Off-the-shelf software isn't a bad thing. For plenty of problems, it's the right answer: well-supported, well-priced, with a community of users who've already hit the edge cases you haven't encountered yet. If the problem is common, the solution probably is too.

But there's a class of business where the shape of the problem stops fitting any box on the market. When that happens, you're not using software any more. You're working around it.

Here are the signs.

Your staff have their own version of the manual

When a new person joins, they learn the tool from whoever trained them, not from the tool itself. There's a right way to enter an order, a correct sequence for closing a job, a set of fields you have to fill in even though the system marks them optional. If every person on your team carries a mental model of how to use the software correctly, the software isn't doing its job.

The spreadsheet in the middle

A surprising number of business processes look like this: information goes into one system, someone exports it to a spreadsheet, does something to it, and puts it into another system. The spreadsheet is not a database. It is not a process. It is a symptom. It means two systems that should be talking to each other aren't, and a human is absorbing the gap.

You're paying for things you don't use, and missing the one thing you need

Subscription software is priced for a market, not for your business. You might be paying for five modules you've never opened while the one workflow you actually need sits behind an enterprise tier that's three times your current spend. When the gap between what you're paying for and what you're getting becomes too wide, the economics stop making sense.

The vendor's priorities aren't yours

Off-the-shelf software evolves in the direction the vendor chooses. The feature you need might be on their roadmap, might not be, and you have no real say either way. If your business is growing in a direction the market isn't serving, you'll keep waiting for an update that may never come.

A process changed and the software didn't flex

Your business adapted. You merged two teams, changed how you price your services, started handling a new kind of customer. The software didn't move. So you bolted something on, or found a workaround, and now the seams are showing. Custom software is shaped around the way your business actually works, not the way the vendor assumed it would.

You can't get the report you actually need

The data is all there. It's in the system. But the report you need to run your business doesn't exist in the interface, and the export function gives you a spreadsheet of thirty columns that you then spend two hours turning into the thing you actually wanted. A system built for your business gives you the view of your business you need.


None of this means you should rush to build something bespoke. Custom software is an investment, and for a lot of problems, a better-configured off-the-shelf tool or a simple integration is the right answer. But when you've hit the ceiling of what the market offers, and your team is quietly absorbing the cost of that gap every week, it's worth having the conversation.

If any of this sounds familiar, I work with small businesses to figure out what they actually need and whether a custom build is the right way to get there. The first step is always understanding the problem, not reaching for the solution.


Have you hit the ceiling on a tool that used to work? I'd like to hear about it in the comments.

Found this useful? Share on LinkedIn

Comments load automatically via GitHub (Utterances), which may set cookies. See the privacy policy.

Get new notes in your inbox

I publish a few times a month on platform engineering, Azure infrastructure, and building platforms that don't rely on heroics. No spam, unsubscribe anytime.

Your email is sent to my self-hosted endpoint and stored via Resend. See the privacy policy.