Three options, not two
The choice is rarely only build or buy. A third option is to configure an existing product through its settings. The UK government's purchasing guidance recommends configuring settings rather than modifying a product, and warns that even small modifications to off-the-shelf software can remove most of the benefits of using it (GOV.UK).
When buying fits
Buying fits when an existing product meets most of your needs through its settings or features and you do not need heavy customisation. The same guidance suggests a small-scale trial before committing, testing integration, user experience, accessibility and fit with how you deploy software.
When building fits
Building gives you more control over requirements and processes, and you own the result so you can change it. It fits when the need is specific to how you work, few products can meet it, or products cannot be adapted without heavy modification. It also brings a duty: someone must maintain and operate the software afterwards.
Questions that decide it
| Question | Points to buy or configure | Points to build |
|---|---|---|
| Is the process common in your industry? | Yes, many organisations work the same way | No, the process is part of what makes you different |
| How much must change to fit? | Settings only | Code changes inside the product |
| Who will maintain it? | The vendor | Your team or a contracted team |
| How important is owning the data model? | Low | High, for integration or reporting |
| Can you trial it cheaply? | Yes, with a small pilot | A prototype is the trial |
Contract points in either case
Whichever option you choose, the guidance recommends being explicit in contracts about ownership of data and intellectual property, understanding the full cost over the product's life including upgrades and retirement, and writing down the risks you accept. For custom work, ask for the source code to live in a repository owned by you from the first day.
A mixed answer is normal
Many projects end up buying a commodity product for one part, such as e-mail delivery or identity, and building only the part that is specific to the organisation. Requirements analysis is the step where this split becomes visible.
Sources
Sources checked on 17 November 2026.