Skip to content
DT Nova

Build vs buy software: how to decide between custom and off-the-shelf

The build vs buy software decision comes up every time a company outgrows spreadsheets or an old system: buy a ready-made product, or have software built for the way you work. This guide gives you the decision criteria, a weighted scoring grid, the total cost of ownership logic, the risks on both sides, the questions to ask vendors and the cases where off-the-shelf is plainly the right answer.

We build custom software, and we also recommend ready-made products whenever they fit; the method below works either way.

The short version

  • There are three options, not two: buy as is, buy and extend, or build.
  • Buy for everything that works the same in every company, such as accounting, email and payroll.
  • Build where the process is how you win, where no product fits, or where several systems must act as one.
  • Compare five years of total cost, your own staff time included, never the first invoice.
  • Whatever you choose, secure the exit: your data in an open format, and the code in your name if you build.

Three options, not two

OptionWhat it meansSuits
Buy as isA SaaS or packaged product, configured but not changedStandard processes, quick start, small IT capacity
Buy and extendA product at the core, with custom integrations, reports or a portal around itA good product with gaps at the edges
BuildSoftware written for your company, owned by your companyDistinctive processes, many systems to join, product ideas

The real question is not "build or buy software" for the whole company, but which option fits each process. The same thinking applies to choosing a CRM or an ERP system.

Custom software vs off-the-shelf: what each really gives you

Off-the-shelf software, sometimes called commercial off-the-shelf (COTS), is one product sold to many customers. Today it is usually rented as SaaS, as our guide what is SaaS explains. You get a working product fast and a vendor who carries the roadmap. You also accept the vendor's idea of the process, its price list and its pace of change.

Custom software, also called bespoke software, is built for one company. It fits the process, connects to what you already run and changes when you need it to, but takes longer to reach a first version and needs maintenance. Ownership is not automatic: under the EU Software Directive, Article 2(3), the employer of the people who write a program holds its economic rights unless a contract says otherwise. When a supplier builds for you, the supplier's staff write it, so the contract must transfer the rights to your company.

Business software is now the norm. Eurostat reports that 53.47% of EU enterprises with ten or more staff used ERP, CRM or business intelligence software in 2025, up from 50.0% in 2023.

Decision criteria

  1. Differentiation. Does this process make customers choose you? Distinctive processes deserve software shaped to them; standard ones do not.
  2. Process fit. How much of the must-have list does the best product cover without workarounds? Every workaround is a cost that comes back each week.
  3. Integration. How many systems must share data, through which APIs?
  4. Data and exit. Can you export all data in an open format at any time, and what does leaving cost?
  5. Compliance. Personal data, sector, accessibility and AI rules.
  6. Time to value and scale. How soon you need it working, and how licence costs grow with users.
  7. People. Who will own the system day to day, on your side and the supplier's?

A build vs buy software matrix you can score

Agree the weights before anyone looks at a product, then score each option from 1 to 5 per criterion and multiply by the weight.

CriterionExample weightPoints toward buyingPoints toward building
Differentiation3The process is the same in every companyThe process is part of your offer
Process fit3A product covers almost all must-havesKey steps need workarounds or manual work
Integration2One or two systems with ready connectorsMany systems, or old ones without an API
Data and exit2Full export and fair exit termsData or logic you cannot afford to lose control of
Compliance2The product already proves itRules the product does not cover
Time to value and scale2Needed within weeks, few usersPhased plan acceptable, many users priced per seat
People1No one to own a custom systemA product owner and a long-term partner

A close result usually points to "buy and extend".

Total cost of ownership: compare five years

The first invoice says little. Put both options into the same five-year table with these lines, and fill in your own figures from real quotes.

  • Buy: subscriptions per user and tier, implementation, integrations, migration, training, add-ons, yearly price changes, admin time and the cost of leaving.
  • Build: discovery, the build in phases, hosting, monitoring, security updates, yearly maintenance and changes, and your product owner's time.

Staff time is the line most often left out on both sides. Our guide to custom software development cost shows how a build estimate is made, and software maintenance cost covers the years after launch.

SaaS vs custom software

SaaS is now a common way of buying, so "SaaS vs custom software" is the same question with one extra point: with SaaS you never hold the software, only access to it. The EU Data Act improves your position. From 12 January 2027 a provider of data processing services may not charge switching charges at all (Article 29), the notice period to start a switch may not exceed two months, and the switch must normally be completed within 30 calendar days (Article 25). The Regulation has applied since 12 September 2025.

Build vs buy for AI

AI adds a layer. You can buy an AI feature inside a product you already use, buy a standalone AI tool, or build on a model through its API, often with your own documents behind it. Building pays off when the AI must work on your own data, return answers you can check and stay under your control. In both cases the EU AI Act applies: Article 4, which has applied since 2 February 2025 and was replaced by Regulation (EU) 2026/1744, requires providers and deployers to take measures to support the development of AI literacy of their staff, and does not require any specific level for any individual. The AI Act applies in general from 2 August 2026, and high-risk uses listed in Annex III from 2 December 2027. See how to choose an AI development company.

Risks on each side

RiskWhen you buyWhen you build
FitThe process bends to the productRequirements were wrong or incomplete
CostPer-user prices and tier changesScope grows during the build
DependencyThe vendor changes, sells or ends the productKnowledge sits with one supplier
DataLimited export, data outside the EUSecurity and backups are your responsibility
ChangeYour request waits in the vendor's queueEvery change needs budget and a partner

Each has a contract answer: export rights and a GDPR Article 28 processing agreement when you buy, phased fixed prices and code in your repository when you build.

When off-the-shelf is the right answer

  • Accounting, payroll, email and office software: buy.
  • A product covers almost all your must-haves and the rest are nice-to-haves.
  • No one in the company can act as product owner for a custom system.
  • The vendor offers full export, an open API and an EU hosting option.

We say so when a product fits; a short software consulting engagement can test one against your requirements.

Questions to ask vendors and build partners

  1. Which of our must-have requirements does the product or plan cover, line by line?
  2. What does the total cost look like over five years at our expected user count?
  3. Can we export all data, including history and attachments, in an open format, and how?
  4. Where is the data hosted, and who are the subprocessors?
  5. What does the API cover, and are there usage limits?
  6. For a build: who owns the code, and is the repository in our account from the first day?
  7. For a build: how is the work split into phases, and what is fixed in each?

For the partner side in depth, read how to choose a software development partner. If the build route wins, see our custom software development service, and if you are weighing no-code tools as a middle way, our no-code development guide. Every guide is in the guides library.

Questions people ask

When should a company build software instead of buying it?

When the process is how the company wins, when no product fits without heavy workarounds, when several systems must work as one, or when per-user licences grow faster than the business. Otherwise buying is usually better.

Is custom software always more expensive than off-the-shelf?

Not over the whole life of the system. Off-the-shelf costs less to start, but subscriptions, add-ons and price rises continue every year. Custom software costs more up front, then needs hosting and maintenance. Compare five years of total cost.

What is the difference between custom software and off-the-shelf software?

Off-the-shelf software, also called commercial off-the-shelf or COTS, is one product sold to many customers, today usually as SaaS. Custom or bespoke software is built for one company's processes and, with the right contract, owned by that company. Many real systems combine both: a bought core with custom parts around it.

Can we start with off-the-shelf and build later?

Yes, and it is often the safest route. Choose a product with a good API and full data export, learn what you really need, then build only what the product cannot do.

How do we make the build vs buy decision objectively?

Write the requirements first, agree weighted criteria before looking at products, score each option against the same list and compare five-year total cost in the same format.

Sources