Planning and buying

Custom software vs off-the-shelf: how to decide

A practical way to choose between buying software and building it, with the questions that matter, the hidden costs on both sides and a simple scorecard.

Every growing business hits this question eventually: do we buy something that already exists, or build something that fits? Both answers are right for somebody. The trick is knowing which is right for you, and not being swayed by whoever is selling.

Compare the real cost, not the sticker price

An off-the-shelf product looks cheap because the price is on the website. A custom build looks expensive because the quote is one big number. Neither is the whole story. Over three to five years, count:

Put honest numbers against each and the gap is often smaller, or bigger, than you expected.

Where off-the-shelf wins

Buy when your process is close to how everyone else in your industry works, when the product covers around 80% of what you need, and when the remainder is a minor annoyance. You get something tested by thousands of businesses, maintained by someone else, and available this week.

Where custom wins

Build when the way you work is genuinely part of why you are good at it, when the exceptions are the job, or when generic tools keep forcing you to bend your process around them. Custom also wins when you need several systems to behave as one, because integration is where off-the-shelf options often run out of road.

The middle path

It is not binary. Many of the best results come from combining: use a proven product for the commodity parts (accounting, email, payments), and build only the piece that is specific to you, connected to those products through their interfaces. You get reliability where it is cheap and fit where it matters.

A simple scorecard

Score each statement from 0 (not true) to 2 (very true):

  1. Our process is unusual compared with others in our industry.
  2. Our team keeps a list of workarounds for the current tool.
  3. The same information is entered in more than one place.
  4. We are paying for features we never use while missing one we need.
  5. We expect to keep using this system for at least five years.

Zero to three: buy off-the-shelf and configure it well. Four to six: look hard at a hybrid. Seven or more: custom software is probably worth a proper conversation.

Decide in a week

You do not need a six-month study. Write the problem in one sentence, list the five things the system must do, shortlist two products, and talk to one custom team about the same list. Comparing a real product demo against a real proposal tells you more than any article, including this one.

If you would like a second opinion on where your situation sits, tell us about it and we will give you an honest view, including when the answer is "buy something". You can also read how we run projects to see what working together looks like.

Got a problem like this?

Tell us what you are trying to improve. A short description is plenty, and we will reply with honest thoughts.

Start a project →