Build or buy
Build or buy: buy for the jobs every business does, build for how yours works
Buy software for the jobs every business does the same way. Build where your work is different, or where people spend their week bridging tools that don’t fit. Most growing businesses need both: good bought tools, and one system that joins them up.
By Seb Lawson · 16 November 2026 · 5 min read
Buy off-the-shelf software for the jobs every business does the same way: email, payroll, the books, file storage. Build where your work is genuinely different, or where your team spends its week carrying information between tools that don’t fit. Most growing businesses need both, and the best setup we see keeps the good bought tools and builds one system around them that joins them up.
The mistake is treating it as one big decision. It’s really a series of small ones, one for each job the business does, and the hidden costs sit in different places on each side.
Buy when the job is the same in every business
Some work is identical whether you run a heating firm or an accountancy practice. Sending email, running payroll, keeping the ledger, storing files. Microsoft 365, Google Workspace and Xero have had years and a huge number of users to get those jobs right. You won’t build a better ledger than Xero, and you shouldn’t pay anyone to try.
The test is simple. If you could swap your business for any other and the job wouldn’t change, buy. The vendor carries the cost of keeping it current, secure and up to date with the rules, and that’s worth the subscription.
Build when the work is how you win
Then there’s the work that’s yours. How you price a job. The checks you run before an engineer goes to site. The way you take on a new client, who needs to see it and what they need to know. That’s often why customers pick you, and it rarely matches what a product designer somewhere else imagined.
When the software doesn’t fit, the business bends around it. People keep a spreadsheet alongside the official system. Someone exports a report every Friday and fixes it by hand. The CRM says one thing and the job board says another. None of this arrives as an invoice, which is why it’s easy to miss.
The hidden costs of buying are seats, workarounds and retyping
The subscription is the number everyone sees. The costs that hurt are the ones around it.
- Per-seat licences. Most business software charges per user per month. As a worked example, a tool at £30 a user a month across 15 people is £5,400 a year, and it goes up every time you hire. Add a second tool for the bit the first one can’t do and you pay twice for the same people.
- Workarounds. Every gap between what the product does and what you need gets filled by a person: a side spreadsheet, a manual check, a weekly export. Those hours are real. They just don’t show up on a bill.
- Retyping. When tools don’t talk to each other, the same customer name, address and job details get keyed into three places. Each time takes a few minutes and is a chance to get it wrong. We explain why that’s the best place to start in spreadsheets aren’t the problem, retyping is.
- Lock-in. Your data lives in the vendor’s format, on their terms. Prices rise, features move to a higher tier, and leaving means an export that loses half the history.
The hidden costs of building are understanding, upkeep and dependence
Building has its own bill, and anyone who says otherwise is selling something.
- Someone has to understand your business first. A bespoke system is only as good as the map it’s built from. Skip that step and you get expensive software that fits nobody.
- Upkeep. The tools you connect to keep changing. Xero changes how other software connects to it, Microsoft changes how sign-in works, a supplier changes their price file. A bespoke system needs someone watching it and fixing it. That’s why we charge a monthly fee to run and improve it after the build, instead of handing it over and walking away.
- Dependence on the builder. If only one person understands how it works, you’ve swapped vendor lock-in for builder lock-in. The fix is to own the code, the data and the documentation from day one, which we cover in owning your system.
Ask four questions about each job
Take each job your business does, from first enquiry to final invoice, and ask:
- Does this work the same way in every business like ours? If so, buy.
- Does a tool we already pay for do it well enough? If so, keep it.
- Is someone retyping, exporting or checking by hand to make it work? If so, that gap is worth building for.
- Would doing this our way win us work or save real hours every week? If so, build.
In our experience the answer is usually a short list of bought tools and one thing to build: the layer that joins them up and handles the work that’s yours.
Building got cheaper, so the sums have changed
A few years ago, building anything bespoke meant a long project and a budget most small firms couldn’t justify, so buying was the only sensible answer for a 15-person business. That’s no longer true. Ready-made components, AI-assisted building and patterns that have been proven many times have brought the cost of building down a long way. The thinking hasn’t got any cheaper, and that’s now where the real work sits. We explain what changed in why bespoke software is now within reach.
So if you asked this question a few years ago and the answer was “buy”, it’s worth asking again.
Our recommendation: keep what works and build the joins
Don’t rip out tools your team knows and likes. Keep Microsoft 365 or Google Workspace, keep Xero, keep the job app your engineers use on site if it works for them. Build one system around them that joins them up and does the work no product does your way. That’s what we do, for a fixed price, and then we stay to run it.
If you’re weighing up a single automation rather than a whole system, our older piece on build, buy or no-code covers that choice.
If you want a straight answer for your business, book a review. It’s a free 30-minute call with Mark or me. Tell us what you use and where the work gets stuck, and we’ll tell you what to keep, what to replace and what, if anything, is worth building. If you’d like to sketch it out first, you can build your system in a few minutes.