Build vs buy software: the small business view

Key takeaways

For a small business, buy standard software for standard problems and build only where the workflow is your advantage. The hidden cost of building in-house is not the first version. It is the years of maintenance, the dependence on whoever wrote it, and the features that never get finished.

• Build only where the workflow is what customers pay you for.
• Buy for standard needs: accounts, CRM, payroll, scheduling.
• Built tools: 5 years of maintenance usually costs more than the first build.
• Bought tools include support and security updates in the fee.

What does build vs buy mean?

Build vs buy is the decision between creating software for your own use and paying for an existing product. Build includes anything made internally, from a complex spreadsheet with macros to a full application. Buy includes subscriptions and licences, with or without configuration.

• The hidden costs of doing everything in-house
• Running a business on spreadsheets: when it breaks

What are the hidden costs of building in-house?

The hidden costs of building in-house arrive after launch.

• Maintenance: fixes, updates and changes every year.
• Dependence: one person understands it.
• Security: nobody patches or tests it.
• Documentation: usually none.
• Opportunity: the builder's real job is neglected.
• Stalling: version one works, version two never ships.

• The one-person department: risks and hidden costs
• The sunk cost fallacy in business decisions

When does buying win?

Buying wins when your need is common. Thousands of businesses invoice, schedule and track customers the same way, and vendors spread development cost across all of them. A subscription of £20 to £100 a user per month is hard to beat for a standard function, and you get support and security updates.

When does building win?

Building wins when the process is unusual and central to your offer, when no product fits without heavy workarounds, or when joining several systems together is the real problem. Even then, most small businesses should commission the build from specialists with a clear scope, not attempt it on the side of someone's desk.

• custom software roadmap
• In-house vs outsourced software development costs

How do you decide?

Decide with a five-year view, not a first-year one.

• Write down the ten things the software must do.
• Test two or three products against that list.
• Estimate build cost plus five years of maintenance.
• Ask who maintains a custom tool if its author leaves.
• Prefer buy unless the gap is central to how you win work.

• The cost of manual processes, and what to fix first

What does five-year cost look like?

Take a simple job-tracking tool for ten users. Buying at £30 per user per month costs £3,600 a year, or £18,000 over five years, with updates and support included. Building might cost £15,000 to commission, plus hosting, fixes and changes that commonly run to 15% to 20% of the build cost each year. Over five years that is £26,000 to £30,000, and the business owns the risk as well as the code.

These are illustrative figures. The point is that the first-year comparison flatters building and the five-year one does not.

What about spreadsheets and no-code tools?

They are builds too. A complex spreadsheet or a no-code app is quick to start and carries the same long-term costs: one author, no documentation and nobody to maintain it when that person moves on. They are a reasonable way to test what you need. Treat them as prototypes, and replace them with a supported product or a properly built system once the requirement is proven.

• DIY IT support in a small business: the hidden costs

What mistakes do small businesses make?

The frequent mistakes are building because existing products were not properly tested, underestimating maintenance, letting requirements grow during the build, and relying on one employee or one freelancer with no handover plan. A fifth is buying a product and then customising it so heavily that upgrades break it.

What should you ask before commissioning a build?

Ask who owns the code and the data, how it will be documented, what the yearly cost of hosting and support will be, and how another developer could take it over. Insist on a small first release that solves one real problem. A partner who pushes back on scope is usually protecting your budget.

What does this look like in practice?

A pattern we see with home-built systems: a quoting tool written years ago by an employee who has since left. It still runs. Nobody dares update the machine it sits on, and every price change needs a workaround.

• See client work
• About Global Bridge Labs

Build vs buy checklist

Answer these before committing.

• Is this need common to most businesses like ours?
• What do existing products cost over five years?
• What would a build plus maintenance cost?
• Who will own, document and secure it?
• What happens if that person leaves?

• The hidden cost audit: score your business in an hour

Next step

Tell us what the tool needs to do and what you use today. We will give you a straight view on build or buy in a 30-minute call.