At some point most growing UK businesses hit the limits of their software. The CRM no longer matches the sales process, the job-management tool cannot handle a new service line, or staff spend hours copying data between packages that were never designed to work together. The obvious question follows: should you buy something better off the shelf, or have software built specifically for you?
There is no universally right answer, and suppliers on both sides have an incentive to push their own option. This article sets out a neutral way to decide, including the costs that are usually left out of comparisons, a worked five-year cost model in pounds, the contractual points that matter under UK law, and a short decision process you can run in about a month.
Key takeaways
- Buy for processes that are standard in your industry; build for the processes that make you different.
- Compare total cost over five years, not the first-year price.
- Per-user subscriptions, integrations and workarounds are the most underestimated costs of packaged software.
- With bespoke software, ownership of the code and a sensible support plan are the key protections.
- A hybrid of packaged tools plus targeted custom components is often the most cost-effective outcome.
The real choice: buy, build or blend
Framing the decision as a simple either/or hides the most common answer. In practice you have three routes:
- Buy: a software-as-a-service product or licensed package, configured to your needs and used largely as designed.
- Build: an application designed and developed for your business, which you own and can change as you wish.
- Blend: standard products for commodity functions such as accounting, payroll and email, connected by integrations and supplemented by bespoke modules where you need them.
Many UK SMEs already run a blend without calling it that: Xero or Sage for the books, Microsoft 365 for collaboration, and one or two specialist tools. The question is usually where the next investment should go.
Signals that an off-the-shelf package will serve you well
- The process is common across your sector and offers no competitive advantage, for example payroll, expenses or basic bookkeeping.
- A well-supported product already covers most of what you need without heavy customisation.
- You need to be up and running within weeks rather than months.
- The vendor offers clear data export, an open API and a credible roadmap.
- Your team is willing to adapt the way it works to match the product.
In these cases, building from scratch rarely makes sense. The vendor spreads development costs across thousands of customers and keeps pace with changes such as tax rules.
When evaluating packages, involve the people who will use them daily and ask vendors to demonstrate your three or four most awkward real-life scenarios. A product that handles the happy path beautifully may struggle with partial deliveries, multi-currency invoices or approval chains, and these edge cases are where staff end up building spreadsheets around the system. Ask, too, how configuration changes are made: if every new field or workflow tweak requires a paid consultant, the running cost will be higher than the subscription suggests.
Signals that bespoke software is worth the investment
- The process is central to how you win and keep customers, such as a unique quoting method, scheduling logic or customer portal.
- You have tried packages and found yourself paying for features you do not use while missing ones you need.
- Staff rely on spreadsheets and manual workarounds to fill gaps between systems.
- Subscription costs rise steeply as you add users, locations or transactions.
- You want to offer your software, or data from it, to customers or partners as part of your service.
If a process is the reason customers choose you, it is worth owning the software that runs it.
Our custom software development team typically builds these systems with Python and React, so they are maintainable by any competent team in future.
Integration: the glue that decides success
Whether you buy, build or blend, the way systems exchange data usually determines how much manual work remains. A beautifully designed application that still requires someone to export a CSV every morning and upload it elsewhere has only solved half the problem.
Questions to ask about any option
- Does it offer a documented, stable API, and are there limits on how often you can call it?
- Can it send events (webhooks) when something changes, so other systems update immediately?
- Which integrations exist already for the tools you use, such as Xero, Sage, HubSpot, Shopify or Microsoft 365?
- Who will monitor integrations and fix them when a supplier changes something?
Integrations need the same care as any other software: error handling, retries, logging and alerts when something fails. Budget for them explicitly. In our experience, the companies that get the most from their systems treat integration as a product in its own right, with an owner and a small ongoing budget, rather than as a one-off task at the end of a project.
Owning your data
Regardless of the route you choose, make sure your core business data, such as customers, orders, products and financial records, can be extracted completely and regularly. A nightly copy into a database or data warehouse you control gives you reporting freedom today and an exit route tomorrow.
Costs that are easy to forget
| Off-the-shelf | Bespoke |
|---|---|
| Annual price rises and per-user charges as the team grows | Discovery and design time before development starts |
| Paid add-ons or higher tiers for features such as API access or SSO | Hosting, monitoring and backups |
| Integration work to connect with your other systems | Ongoing maintenance, security updates and library upgrades |
| Staff time spent on workarounds and duplicate entry | Enhancements as the business changes |
| Data migration and exit costs if you later switch | Internal time for testing and feedback |
A five-year cost model in pounds
The example below compares two options for a 40-user operations platform. The figures are illustrative assumptions, not quotes, but the structure is what matters: put every cost on the same five-year basis.
| Cost line | SaaS package | Bespoke application |
|---|---|---|
| Set-up, configuration or build | £8,000 | £60,000 |
| Integrations with existing systems | £12,000 | Included in build |
| Subscriptions (40 users × £45/month, 5% yearly rise) | £119,000 | £0 |
| Hosting and monitoring (5 years) | Included | £12,000 |
| Support and improvements (5 years) | £10,000 | £45,000 |
| Workaround time (estimated staff hours) | £20,000 | £2,000 |
| Five-year total | £169,000 | £119,000 |
With ten users the picture would reverse, which is exactly why you should run the numbers for your own situation. Sensitivity matters as well: try your model with 25% higher build costs and with faster user growth to see which option is more robust.
Risks and how to manage them
With packaged software
- Vendor lock-in: check that you can export all of your data in a usable format.
- Roadmap changes: features you rely on may be withdrawn or moved to a more expensive plan.
- Data location: confirm where data is hosted and that appropriate UK GDPR safeguards are in place for any international transfers.
With bespoke software
- Ownership: make sure the contract assigns intellectual property in the custom code to you on payment.
- Key-person dependency: insist on documentation, version control in a repository you control, and automated tests.
- Scope creep: fix priorities in phases and release a usable first version early.
- Security and maintenance: agree how dependencies will be updated and vulnerabilities patched, and who is responsible after launch.
Both routes carry risk; the aim is not to eliminate it but to know which risks you are accepting and to put simple mitigations in place. A short risk register, reviewed at each project milestone, is usually enough for an SME.
Running the decision in about four weeks
- Week 1: document the process, users and must-have requirements; separate essentials from nice-to-haves.
- Week 2: shortlist two or three packages and request demonstrations using your real scenarios, not the vendor’s script.
- Week 3: obtain a scoped estimate for a bespoke or blended solution, ideally after a short discovery workshop.
- Week 4: build the five-year cost model, score risks, and decide with the people who will use the system.
Make the final decision with a small group that includes the budget holder, an experienced user of the current process and someone responsible for IT or data. Score each option against the same criteria, for example fit to requirements, five-year cost, risk, time to value and ease of change, and write down the reasons for the choice. That short decision record is invaluable a year later, when new people join and ask why things were done a certain way, or when circumstances change and you need to revisit the choice without starting from zero.
If you are considering a customer-facing component, our web development team can also prototype the user experience during this period, which often clarifies requirements quickly.
Choosing a development partner in the UK market
Whichever route you take, the partner matters as much as the technology. Points worth checking include:
- A written contract covering scope, change control, acceptance testing and intellectual property.
- A data processing agreement where the partner will handle personal data on your behalf, as required by UK GDPR.
- Access to the source code repository throughout the project, not just at the end.
- Clear support terms: response times, hours of cover and costs.
- References or examples of comparable work you can discuss with them.
Creensight UK is the London office of Creensight Private Limited, and our projects are delivered by the company’s engineering team in India in close collaboration with UK-based project contacts, which gives clients UK-hours communication with the capacity of a larger team.
Frequently asked questions
Is bespoke software only for large companies?
No. Focused applications that replace one painful process can be affordable for SMEs, especially when built in phases. The key is to start with the highest-value part.
Can we start with a package and move to custom later?
Yes, provided you can export your data and the package has an API. Many businesses begin with a package and replace modules as their needs become clearer.
Who maintains bespoke software after launch?
Usually the original developer under a support agreement, but well-documented code with tests can be handed to another team or brought in-house. See our FAQ for how support plans work.
How long does a bespoke project take?
A first usable release of a focused application often takes eight to sixteen weeks; larger platforms are delivered over several releases. Timelines depend mostly on how quickly decisions are made and how available your subject-matter experts are for questions and testing, so it is worth planning their time as carefully as the developers’.
Get an impartial recommendation
We are happy to recommend an off-the-shelf product when that is the right answer for you. If you would like an independent view on your options and a five-year cost comparison, contact Creensight UK and tell us about the process you want to improve.
