Buy or Build Business Software? Platform vs Bespoke

Buy when your process is standard and a product fits most of it. Build when the process is how you win work, when the workarounds around a product cost more than its licence, or when owning your data and avoiding lock-in matter to the business. That is the short answer to whether to buy or build business software, and in practice many businesses do both: they buy the commodity parts and build the piece that makes them different.

I build bespoke software for a living, so weigh what follows accordingly. The rest of this post is a set of questions for working out which side of the line your system sits on. Several are covered in more detail elsewhere on this blog, linked as they come up.

When buying off-the-shelf software is the right answer

Accounts, payroll, email, file storage and a conventional sales pipeline are solved problems. Thousands of businesses share the same process, the vendor spreads the cost of development across all of them, and when the rules change the update arrives without you commissioning it. Paying someone to build a bespoke accounts package would be poor value, and I would tell you so.

Buying is usually right when all of these hold:

• Your process is the same as most businesses in your sector, and you are content for it to stay that way.
• The product covers the bulk of what you do through configuration, tested against your own records rather than the vendor's demo.
• The number of users is modest and will not grow much.
• You can export everything in a usable shape, and could absorb a price rise or walk away from one.
• It connects to the tools you already use through connectors the vendor supports.

If all five are true, buy it and spend your money elsewhere. If one or more is shaky, the six questions below are worth working through.

A buy-or-build framework: six questions

Answer each one and note which way it points. None of them decides the matter on its own.

1. What does it cost over five years, not in year one?

Subscriptions are priced per user per month, which makes the first year look small. Write out five years for both options.

Buying: seats multiplied by the monthly price, multiplied by sixty. Then add the seats you will need as you grow, the annual price rises your subscription terms allow, implementation and configuration fees, paid add-on modules, and the staff hours spent on the workarounds in question two.

Building: the build, the hosting and the changes you will want over five years. A focused module costs far less than a full application, and how much bespoke software costs explains what drives the difference. Hosting is modest: Colehill Customs run their system in their own Azure tenant, on infrastructure they pay for directly. There is no licence fee or per-user charge; later changes are billed on time and materials as they are made.

The build column carries a risk the buy column does not. You pay for every change, and requirements nobody foresaw still cost money. A vendor spreads that across its whole customer base. How much bespoke software costs in the UK covers the numbers and what drives them in more detail.

2. How much of your process does it fit, and what is the customisation tax?

There is a difference between configuring a platform and customising it. Configuration means fields, workflow steps, permissions and reports within the settings the vendor supports. It is cheap and it survives upgrades. Customisation means scripts, plug-ins and paid consultant work to make the product do something it was not designed for. That is where the tax is: you pay to have it built, pay again when a vendor upgrade breaks it, and are tempted to delay upgrades, including security patches, to avoid the breakage.

Then there is the tax nobody invoices: the spreadsheet kept beside the platform, the orders re-keyed from one system into another, the one person who knows how to get the monthly report out. When you are building workarounds for your workarounds, that time belongs in the five-year sum.

A useful test is where the gaps sit. If the product covers the core and the gaps are at the edges, buy it and accept the edges. If the gaps are in the middle, in the thing your staff do all day, the tax compounds. Colehill Customs reached that point before they came to me. As Kitty at Colehill put it: "After months of researching existing systems, none of which matched our criteria, we decided to look into something being made bespoke."

3. Can you get all your data out, in a shape another system can use?

Construction is a good illustration. A contractor's operational software ends up holding years of timesheets, vehicle records, site allocations and staff qualifications, often with scanned certificates and photos attached. Most platforms will export the current records as a CSV. Fewer will export the history, the links between a person, their qualifications and the sites they worked on, and the attached documents, in a form another system can import. Without those, switching means rebuilding years of records by hand, which is why so few businesses switch.

For comparison, Buxted Construction, a groundworks contractor with 400+ staff, run personnel, qualifications and a 329-vehicle fleet on a system I built, with the data in Azure SQL, staff photos and certifications in Azure Blob storage, and the source code in their own GitHub organisation. Those are standard formats any database developer can query.

Before signing for any platform, ask for a full export during the trial using real records, and try loading it somewhere else. The question is not whether you plan to leave, but whether you could. The hidden cost of software lock-in goes further into how lock-in builds up and how to test for it.

4. What does it need to connect to?

If a platform has supported connectors for the tools you already use, take them; that is a real point in its favour. The trouble tends to be the one connection it does not list, or a connector the vendor controls and can change on its own timetable.

Integration is often where a bespoke build earns its keep. Colehill Customs' system joins five separate APIs (Shopify, Xero, Calendly, Outlook and Jotform), so website orders arrive in the planner and invoices reach the accounts package without a second entry. Buxted's system has a purpose-built API that connects the desktop application to the iSOS mobile platform staff clock in on. If joining systems is the main problem, data integration may be all you need.

5. Who owns the code, and does it matter here?

When you buy, you own nothing: you rent access, and the vendor sets the terms. For a commodity tool that is a perfectly reasonable trade.

When you build, ownership is not automatic. It has to be agreed in writing, with an intellectual property assignment in the contract and the source code in a repository your business controls from the first day. Without that you have swapped one dependency for another. Every client I work with holds their own source code in their own GitHub organisation. Who actually owns your business software? sets out what to check in a contract.

6. Is this process how you win work?

Software built for the typical business in your sector pulls you towards the typical way of working. For a commodity process that does not matter. For the process that sets you apart, it can.

Dugard, who sell precision engineering machines through salesmen in the field, replaced Excel quotations with a system that compiles 15–20 page PDF quotes automatically and gives headquarters live sight of every quote. NT Labs, a VMD-licensed manufacturer, needed multi-stage formulations with every change version-controlled for regulatory inspection. Neither is something a general-purpose product was going to fit closely. If your answer to this question is "no, we do it like everyone else", that is a strong point for buying.

Scoring the answers

1. Most answers point to buying: buy, run the export test once a year, and keep the spreadsheets from creeping back.
2. Mixed, with the gaps at the edges: buy the platform and build small pieces around it where the tax is highest.
3. Questions 2, 3 or 6 point to building: give these the most weight, because their cost grows every year you stay. Build, or take the hybrid route below.

The hybrid route: buy the commodity, build the difference

The choice is rarely all or nothing. Several of the projects in my portfolio are this shape:

• Colehill Customs kept Shopify for their online store and Xero for their accounts, and commissioned the production planner that sits between them.
• DollyHotDogs kept Zoho Inventory as the central hub. What was built was the integration feeding it from Shopify, Etsy and wholesale spreadsheets, which ended the manual re-keying of wholesale orders.
• Weald IT have a bespoke helpdesk that integrates with their existing accounts software, so customer records are not entered twice.

In each case the bought products do what they are good at, and the bespoke part covers the gap between them. The smallest useful build is sometimes an integration rather than a whole application.

Is bespoke software worth it for a mid-size business in 2026?

It is worth it when it passes the questions above, and not otherwise. What has changed is the cost of getting there. AI-assisted development has compressed build times, which moves the break-even point against five years of licences. Colehill Customs went live in their own Azure tenant a little over three weeks after I first saw their workbook, and Kitty wrote that the project "was also way more cost effective than we initially thought".

Bespoke is not only for small firms either. Buxted Construction turn over £74M+ and are a long-term client. And bespoke software is not built once and left: Weald IT's helpdesk has been continuously modernised over a working relationship of more than 25 years, most recently onto Azure SQL with a new customer portal.

Common mistakes when purchasing custom software, or choosing a platform

• Commissioning a commodity. If a mature product does the job, a bespoke version is money spent reinventing it.
• Judging a platform on its demo. Test it with your own records and your awkward cases, the ones the spreadsheet exists to handle.
• Signing without an IP assignment. A bespoke system you do not own is a subscription with extra steps.
• Paying for padding. Fixed-price quotes have to allow for uncertainty. Time and materials, starting with an estimate for a smaller first phase, means you pay for what is built and can change direction once you see working software.
• Forgetting the exit. Whether you buy or build, know how your data would leave before you put it in.

Talking it through

If you are weighing up a configurable platform against a bespoke build, a short conversation about how your process works usually shows which way it points. If a product would serve you better, I will say so. If it would not, you will get an honest view of what a custom application would involve and an estimate for a sensible first phase. Get in touch.

Frequently Asked Questions

Is it better to buy a configurable platform or commission bespoke software?

Buy when your process is standard and the platform fits most of it without heavy customisation. Commission bespoke software when the process is how you win work, when the workarounds around a platform cost more than its licence, or when owning your data and code matters to the business. Many businesses do both: they buy the commodity tools, such as accounts and email, and build the part that sets them apart.

Is bespoke software worth it for a mid-size business in 2026?

It is worth it when a product would leave the core of your process uncovered, and not worth it when a product fits. AI-assisted development has brought the cost of building down considerably. Compare that with five years of per-seat licences, configuration fees and the staff time spent on workarounds, not with the first year's subscription.

What is the customisation tax on off-the-shelf software?

It is the cost of making a platform do what it was not designed to do. You pay once to have scripts, plug-ins or consultant work added, again when a vendor upgrade breaks them, and continuously in the spreadsheets, re-keying and manual reports your staff keep alongside the platform. Configuration inside the vendor's supported settings is cheap. Customisation beyond it is where the tax builds up.

How do I check whether I can get my data out of construction software before switching?

Ask for a full export during the trial, using real records, and try to load it somewhere else. Check that it includes the history rather than just current records, the links between people, qualifications, vehicles and sites, and any attached documents such as scanned certificates. If the export is a flat CSV of today's data, you would be rebuilding years of records to leave.

Can I buy some software and build the rest?

Yes, and it is often the cheapest sensible answer. Keep the products that do their job well, such as Xero, Shopify or an inventory platform, and commission the application or integration that joins them up around the way you work. The smallest useful build is sometimes an integration rather than a whole application.

How is bespoke software priced?

On time and materials: you pay for the hours worked, tracked and invoiced transparently. There is no licence fee and no per-user charge, and later changes are billed as they are made. If the full scope is uncertain, the sensible start is an estimate for a smaller first phase, so you see working software before committing further.