Custom software vs. off-the-shelf: how SMEs should decide

The decision is not custom versus off-the-shelf, and it is not cheaper versus better. It is about fit. Most small and medium businesses lose money by getting this wrong in both directions: building what they could have bought, or forcing the team to work around a tool that never fit.

Here is the framework I use with clients, including when the honest answer is buy, not build.

Start with the honest default: off-the-shelf

Packaged software is usually the right first choice. It is cheaper upfront, faster to deploy, maintained by someone else, and already tested by thousands of users. If a standard tool fits how you actually work, use it. Do not build what you can buy.

The real cost of off-the-shelf is not the licence

The sticker price is the licence. The hidden cost is the workarounds: the spreadsheet kept alongside it, the data re-entered between it and your other tools, the manual steps your team does because the software cannot. When those workarounds grow, the cheap option quietly becomes expensive in time and errors.

When custom actually pays off

Three signals matter. First, the process is a competitive advantage, not a commodity: the way you do it is part of why customers choose you. Second, no off-the-shelf tool fits without forcing your team to work around it. Third, the manual coordination between tools is costing real hours or causing real errors. If two of these are true, a custom build usually pays back.

What drives the cost of a custom build

Four things: how many workflows are in scope, how many systems it must integrate with, how many roles and access rules it needs, and how maintainable it has to be over time. The way to keep cost proportional is to build the smallest useful version first and extend only where the business case is clear, instead of specifying everything up front.

A five-question test

Ask: 1) Does a standard tool fit our process, or would we work around it? 2) Is this workflow a competitive advantage or a commodity? 3) How many hours a week do the manual steps cost us? 4) Does it need to connect to systems we already run? 5) Do we need to own and control it long term? Your answers usually point clearly one way.

Often the answer is buy now, build later

The right sequence is frequently to use off-the-shelf for the standard parts and build custom only for the part that genuinely differentiates you, then integrate the two. It does not have to be all or nothing, and starting small keeps the risk low.

Getting a straight answer

If you are weighing this decision, I will tell you honestly which case you are in, with no push toward a build you do not need. That honesty is the point: the goal is the right system for your business, not the biggest project.