Custom software or off-the-shelf: how to choose

Once a business decides its current way of working has run out of road, the next question arrives quickly: do we buy something that already exists, or have something built for us? Both answers are right for somebody. The trouble is that the decision often gets made on the wrong basis, usually the monthly price on a pricing page, and the real costs only show up a year later.

This is a practical way to work out which side you are on, written by people who build custom software and still tell a fair number of enquirers to buy a product instead.

Start with off-the-shelf, and try to prove it wrong

If a well-known product does what you need, buy it. It is available today, somebody else maintains it, and thousands of other businesses have already found its rough edges. For accounting, payroll, email, basic customer records and online shops, a ready-made product is almost always the sensible choice, because your process in those areas is much the same as everyone else's.

So the useful question is not "which is better". It is "what would have to be true for a ready-made product to be the wrong answer for us". The five questions below are the ones that tend to decide it.

Five questions that settle it

1. Is this process the thing that makes you different?

Every business has work that is ordinary and work that is the reason customers choose it. Ordinary work suits ordinary software. But if the process in question is how you quote faster than competitors, how you schedule in a way nobody else does, or how you deliver the service itself, then forcing it into a generic product means working the way the product's designers imagined, not the way that wins you business.

2. How much would you have to bend to fit the product?

Run a trial with real work, not the demo data. Count the workarounds: the fields used for something they were not meant for, the step that still happens in a spreadsheet on the side, the report somebody rebuilds by hand each week. One or two is normal. If the trial ends with a product plus a collection of side files holding it together, you have not replaced your problem, you have added a subscription to it. That pattern is one of the clearest signs a business has outgrown its spreadsheet, and it does not go away just because the spreadsheet now sits beside a product.

3. What does it cost as you grow?

Most products charge per user, per month, and often keep the features you actually need for the higher tiers. That is good value for a team of five. Work the same sum for the headcount you expect in three years, including the add-ons, and compare it with a system you would own outright. Sometimes the product still wins comfortably. Sometimes the numbers cross over sooner than expected.

4. Does it need to talk to your other systems?

A product that cannot exchange information with your accounts package, your stock system or your website leaves your team copying data between screens. Check what connections exist, whether they cover the information you care about, and whether they sit behind a more expensive plan. If the honest answer is "we would still be rekeying", the saving on paper is smaller than it looks.

5. How settled is the process?

If you are still working out how the job should be done, do not build anything yet. Use a ready-made product, or a spreadsheet, until the process stops changing month to month. Custom software is at its best when it captures a way of working you already trust. Building too early means paying to rebuild later.

The costs that are not on the quote

Each route has costs that are easy to miss.

With a ready-made product, they are the subscription that rises with every hire, the time lost to workarounds, the features you pay for and never open, and the effort of getting your information out again if you ever want to leave.

With custom software, they are the higher cost up front, the weeks or months before you can use it, the time your own people must give to explaining how the work is really done, and ongoing upkeep once it is live. Anyone who quotes for a build without mentioning that last one is not giving you the whole picture.

Neither list is a reason to avoid that route. They are simply the figures worth having in front of you before you compare the two.

The middle route most businesses end up on

The choice is rarely all or nothing. A common and sensible outcome is to keep ready-made products for the ordinary work and build one small, focused system for the part that is unique to you, connected to the rest so nothing has to be typed twice. That keeps the build modest, puts the money where it makes a difference, and leaves somebody else responsible for the parts that are the same in every business.

A quick way to decide

If you answered the five questions and found that a product fits with only minor compromises, buy it and do not look back. If you found that the process is central to how you compete, the workarounds are piling up, and the costs climb steeply as you grow, a custom build deserves a proper look.

If you are somewhere in between, that is the conversation we have most often. Tell us what you are trying to fix and what you have already tried, and we will say honestly whether building something would pay for itself or whether a product you can buy this afternoon would do the job. Get in touch and you will get a straight answer either way.