Build or buy software? When off-the-shelf is the better choice

Choose off-the-shelf for most jobs, and keep custom builds for work where your business truly stands apart from rivals. Ready-made tools suit standard jobs such as invoicing, payroll and office admin, especially when they meet your needs with little customisation. Once a product has to be bent far out of shape to fit your process, the workarounds bring back the manual effort and you still pay the licence.

Who this is for: owners, directors and operations managers of UK small and medium-sized businesses deciding whether to pay for bespoke software or stick with ready-made tools like Xero, HubSpot, Gmail and Microsoft 365.

When is off-the-shelf software the better choice for a small business?

Off-the-shelf software is usually the better choice whenever the work it handles looks the same in your business as in everyone else's. Few small firms are unique in invoicing, payroll or general office work, so a ready-made tool fits those jobs well. Where you often do differ is in how you produce and deliver your own service, and that is the place where building earns its keep.

When the product's assumptions match your way of working

Every ready-made product is built around assumptions about how the work should run. A small gap between the product and your process is normal and fine.

When a proven product already does the job

Microsoft regards ready-made Software as a Service (SaaS) as the ideal route when it covers business needs with little tailoring, since you then avoid building and looking after your own. Microsoft's view is that, wherever you can, a tried and tested product beats writing your own, and that ready-made tools give a team more value in most cases. Writing those features yourself means paying to develop them and to keep them running, and that bill may end up higher than the cost of a premium tier. Standardising on a set of tools works best when your team gets training on each one, so they can use it efficiently.

What does custom software cost over several years compared with subscriptions?

Custom software costs more at the start than a SaaS subscription. Over the longer run, though, owning a bespoke system often costs less in total, once you count per-user licence fees, integration costs, customisation limits and the workarounds staff build when a product does not quite fit. Where a business has particular operational needs, a bespoke build often works out cheaper in the long run.

Running costs belong in the estimate, not just the build

Set one-time costs against recurring ones when you compare the two routes. Switching has a price of its own, so allow for moving your data, training people and changing processes when you weigh up a replacement. Microsoft's guidance is to move a workload to SaaS when comparable features exist, the integrations meet your requirements and the total cost of ownership justifies the change.

The hidden cost of a poor fit

A large gap between a product and your process quietly recreates the manual work you were trying to remove, and you pay a licence on top. Those costs rarely show up on an invoice, which is why they are easy to miss when you compare prices.

How do you know your business has outgrown its off-the-shelf software?

A good test is how far you would have to twist a ready-made product to fit the way you actually work. Find out from your staff which jobs eat their time through repeated typing-in or double-checking of data. Listen for people saying they do a task a certain way only because the system can't do it otherwise, or that they keep their own spreadsheet for it: each one is a workaround worth investigating.

• The same details typed into more than one system.
• Spreadsheets exported to patch gaps the software leaves.
• New starters trained to ignore fields that do not apply to your business.
• Time lost to checking figures by hand.

The damage is not only financial, though the costs add up. Staff time spent on workarounds is time not spent on customers or on growing the business.

Is there a middle option between building from scratch and buying?

There is plenty of ground between a full custom build and a packaged product.

Low-code and no-code platforms

Low-code and no-code platforms sit between the two: quicker to get going than a custom build, and easier to adapt than a boxed product. Microsoft's Power Platform, for example, offers managed environment features out of the box, such as setting a maker onboarding message or limiting sharing.

Custom integrations with the tools you already use

Many business systems let you build on top of them through an application programming interface (API), and Xero invites you to build a custom solution with its own. Xero says that "you, or a developer you commission, can access Xero's APIs and manage custom integrations more easily". Joining up the systems you already use this way leaves the ready-made product handling standard work, while custom code covers only the part where your business is different.

How long does custom business software take to build?

Small internal tools are usually quicker to build, and regulated builds usually take longer. Discovery work at the start and a stabilisation period at the end add to the build time.

What stretches a software timeline

When estimates differ, skill is rarely the reason. The difference lies in hidden assumptions: how settled the scope really is, how many of your current systems the new software must connect with, and how fast you reply to questions. Each connection to another system brings a dependency outside your control, such as an undocumented API, a rate limit or a supplier's test environment being offline for days. Two integrations are usually routine, while seven make it a different project. Price the integration work honestly before you agree a delivery date. Any quote for custom work forecasts how your business will behave as much as how the code will go, so the price and timeline you agree rest on every one of those assumptions.

Who owns the code when you commission custom software?

Under the Copyright, Designs and Patents Act 1988, "the author of a work is the first owner of any copyright in it", subject to the Act's other provisions. The same Act states that an assignment of copyright "is not effective unless it is in writing signed by or on behalf of the assignor".

Licence or ownership, and what to get in writing

An implied licence typically lets you use the software only as far as your internal business needs. Its exact scope depends on the facts, and doubt over transfer, sub-licensing or commercial rights can raise serious concerns when an investor or buyer carries out due diligence. Before signing, get the handover of intellectual property put in writing, have any leftover claims waived, and ask for the full source code and documentation at delivery rather than only a hosted service.

How can you test whether custom software is worth it before committing fully?

A minimal viable product (MVP) strategy lets you build, measure and learn from an app quickly and efficiently. An MVP is not a bare set of basic features: it is a production-ready solution that delivers your most important goals with the least effort, and it is designed to drive feedback and iterations rather than be the end state. Point it at getting the biggest business benefit early, rather than cutting it down to the bare minimum. If the scope is so wide that delivery takes years, it has stopped being an MVP. If you are replacing an existing app, check its current features for parity, but do not try to copy the old app's experience.

Piloting with real users

Government guidance on testing and piloting services says testing can validate assumptions, show whether delivery needs adjusting and reveal unforeseen challenges. Trying the system with a group of people who reflect your real users helps confirm whether the approach suits them and builds their confidence in it. A pilot also gives the supplier's team and your own a chance to work together before full roll-out. Testing also helps you decide where your time and money are best spent.

How do off-the-shelf and custom software compare at a glance?

Common questions

Will our off-the-shelf software bill rise as the team grows?

Usually, yes. Google Workspace prices depend on the number of user licences you buy, and the price goes up when you add licences for a growing team. Microsoft 365 and Dynamics 365 also charge per-user licence fees.

Do we own the open-source parts of a custom build?

Not exactly. You use open-source components under their own licences rather than owning them, and what you have to do depends on the licence family. Permissive licences like MIT and Apache 2.0 tend to be simpler to comply with, while GPL-style licences can bring wider obligations in some cases.

Sources

1. Select your cloud migration strategies - Cloud Adoption Framework

   Microsoft Cloud Adoption Framework

2. How should we estimate the total cost of migrating from Haufe X360 to Microsoft Dynamics 365 -- including migration effort, licensing, integration/customization, and long-term maintenance over the next 5 to 10 years? - Microsoft Q&A

   Microsoft Q&A

3. Compare Flexible and Annual/Fixed-Term payment plans  |  Billing & subscriptions  |  Google Workspace Help

   Google Workspace Help

4. Subscriptions, licenses, accounts, and tenants for Microsoft's cloud offerings - Microsoft 365 Enterprise

   Microsoft

5. Build vs Buy: When Custom Software Beats Off-the-Shelf — ControlStandard.Tools

   ControlStandard.Tools

6. Recommendations for standardizing tools and processes - Power Platform

   Microsoft Learn

7. Recommendations for standardizing tools and processes - Power Platform

   Microsoft Learn

8. Five signs your business has outgrown off-the-shelf software

   BM Magazine

9. Five signs your business has outgrown off-the-shelf software

   BM Magazine

10. Xero Custom Development — Xero Developer

    Xero Developer

11. Custom Connections — Xero Developer

    Xero Developer

12. Custom Integration FAQs — Xero Developer

    Xero Developer

13. Drive feedback with a minimal viable product strategy - Dynamics 365

    Microsoft

14. Drive feedback with a minimal viable product strategy - Dynamics 365

    Microsoft

15. Regulation 12(5)(c)

    ICO

16. 11 First ownership of copyright.

    legislation.gov.uk (CDPA 1988 s.11)

17. Legislation

    legislation.gov.uk (CDPA 1988 s.91)

18. Copyright, Designs and Patents Act 1988 (c. 48)

    legislation.gov.uk (CDPA 1988 s.90)

19. Copyright, Designs and Patents Act 1988, Section 90

    legislation.gov.uk

20. Recommendations for standardizing tools and processes - Power Platform

    Microsoft Learn

21. Xero Custom Development — Xero Developer

    Xero Developer

22. Xero Custom Development — Xero Developer

    Xero Developer

23. Drive feedback with a minimal viable product strategy - Dynamics 365

    Microsoft

24. Custom software or off-the-shelf: how to decide

    casterconsulting.hu

25. Software IP Ownership Disputes: Contractor Rights & Code…

    echelondyn.co.uk

26. How Much Does Bespoke Software Cost in the UK? 2026 Guide

    sourcecodestudio.co.uk

27. Bespoke Software Development in London: 2026 Cost Guide

    rsk-bsl.com

28. Software Development Timeline: Proven Guide to Avoid Delays

    progressiverobot.com

29. Software Development Timeline: Proven Guide to Avoid Delays

    progressiverobot.com

30. Software Development Timeline: Proven Guide to Avoid Delays

    progressiverobot.com

31. Who Owns Your App's Code? UK IP Guide for Founders (2026)

    nordstone.co.uk

32. TESTING AND PILOTING SERVICES

    assets.publishing.service.gov.uk