Custom software vs off the shelf: how to decide

Buy it, if something already does the job. Off the shelf software costs less to start, has been proven by other people’s use, and someone else maintains it. Build only when the business has outgrown what can be bought, usually signalled by three subscriptions and a workaround standing in for one system.

By Jake Volkanovski, Founder. Updated .

What is off the shelf software?

Software built once and sold to many businesses as it is: an accounting package, a CRM, a project tool, most of the subscriptions a business already pays for. You adapt your process to it, and its maker decides what it does next.

Today, off the shelf mostly means software as a service: rented monthly, hosted by the vendor, updated for everyone at once.

What does custom software mean?

Software built around one business’s process: the portal your team signs in to every day, the internal tool that replaces a spreadsheet, the dashboard that finally shows the numbers in one place. It does what was scoped and nothing else, and it runs on an ongoing plan, with your data and accounts in your name.

It is what Vantic’s Software practice builds: web applications, desktop programs, internal tools and the APIs that connect them, with AI built in where it does the work.

Custom vs off the shelf: the differences that matter

Feature lists compare badly, because both sides can tick most boxes. These five are where the two actually differ.

  • Fit: off the shelf fits most businesses reasonably well; custom fits one business exactly.
  • Time to first use: off the shelf is usable today; a custom first release typically lands six to twelve weeks after a signed scope.
  • Change: off the shelf changes when its vendor decides; custom changes when you do.
  • Dependency: with off the shelf you depend on the vendor’s roadmap and pricing; with custom you depend on whoever can read the code, which is why the documentation matters.
  • Support: off the shelf support is a queue; custom is looked after by the person who built it.

When is off the shelf the right answer?

More often than most builders will admit. If an existing product already does the job well, buy it: paying to rebuild a subscription is an expensive way to own a worse one. We say so before quoting, not after.

The same goes for standard processes such as accounting, payroll and email, where the product’s way of working is the industry’s way of working, and for needs that are still being discovered, where it is too early to know what a custom system should do.

When does custom software earn its cost?

When the workarounds cost more than the build. The signal is usually the same: three subscriptions and a workaround standing in for the system the business actually needed, with someone retyping between them every day.

It also earns its cost when the process is the business’s advantage and no product models it, or when the data has to live in accounts you control. In each case the test is the same: the cost of the gap, measured, against the cost of closing it.

Is SaaS the same as off the shelf?

For this decision, yes. SaaS is off the shelf software delivered as a subscription, with the same trade: less to set up, less to own. The difference worth checking before you commit is the exit: whether your data can be exported whole, in a form another system can read, if the product or its price stops suiting you.

Building around the software you already pay for

Often the answer is neither. When the products are right but disconnected, the missing piece is not a new system. It is the connection between the ones you have: records that sync, enquiries that route themselves, reports that assemble on schedule. That is AI integration and automation work, agents and integrations that carry the work between the systems you already own, and it usually comes before any case for building from scratch.

What should stay yours once it’s built?

Agree it in writing before anything is built. Whoever builds and runs the software, four things should never be in doubt.

  • Your data: stored in accounts in your name, exportable whenever you ask.
  • The credentials: every account it runs on in your name, with the keys held by you.
  • The documentation: a runbook plain enough that the system is never a black box.
  • The terms: what the ongoing plan covers, and how you would move on if you ever chose to.

Before you build: get the scope in writing

Whichever way it goes, write down who will use the software, what each of them needs from it, and what it will not do, before a line of code. A fixed price on an unwritten scope is a guess with a deposit. How to write that document is its own guide: how to scope a software project.

Where this leads.

The Software practice

Web apps, portals, internal tools and desktop programs with the AI built in. Scoped in writing, built in the open, then run and improved for you.

Practice

How to scope a software project, in writing

Write down who will use it, what each of them needs it to do, and what it will not do, then sign it before a line of code is written.

Guide

Which business processes to automate with AI first

Hand AI the step that costs the most and needs the least judgement, found by watching a real week of work, not by reading the process document.

Guide

Ready for software that fits the business?

Scoped in writing. Built in the open. Run for you. A reply comes from the person who would build it, within one business day.