On this page 9 sections
Key takeaways
- Off-the-shelf software keeps getting more expensive, and many SMEs now run 10 to 20 subscription tools that do not talk to each other.
- Bespoke software used to mean long, risky projects. Modern platforms, AI-assisted development and smaller phased builds have changed that.
- The evidence on AI speeding up development is real but mixed. The gains come from how a project is run, not from AI alone.
- Software you own can be built so AI agents can read from it and act on it from day one, which is much harder with a closed off-the-shelf tool.
- Off-the-shelf is still the right answer for jobs like payroll and accounts. Build where the way you work is what wins you business.
Most owner-managed businesses I speak to run on a familiar stack: quotes in one spreadsheet, jobs in another, a CRM nobody fully trusts, and a handful of subscriptions that each do about 60% of what is needed. The team fills the gaps by re-keying, chasing and remembering.
For years, the alternative (software built around your own process) was something only larger firms could justify. The question used to be "can we afford bespoke?" For a growing number of SMEs, it is now "why are we still bending our process around someone else's software?"
The subscription squeeze
Monzo Business's Money Moves Report (September 2026) found its business customers' software spending rose 15% in a year. Yet in its survey of 1,000 UK SMEs, firms still reported spending around 53 minutes every working day on financial admin, and 49% said it takes too long.1 Fasthosts estimates that many SMEs now use anywhere between 10 and 20 subscription (SaaS) tools.2
Prices keep moving in one direction. Xero raised its UK prices again from 1 September 2026, with its Grow plan going from £37 to £39 a month and Comprehensive from £50 to £55, ex VAT.3 Canva closed its Teams plan to new customers in October 2025 and moved them to Canva Business, at US$20 per person per month.4 None of these are bad products. The issue is the model: per-seat pricing grows with your headcount, and each tool solves its own slice of the problem without talking to the others.
So the people in the business become the integration. They copy a customer from the CRM into the quote, the quote into the job sheet, the job sheet into the invoice. Every hand-off is time, and every hand-off is a chance to get a number wrong.
Why bespoke used to be a big-company decision
It is worth being fair to the old advice. Bespoke software used to mean a long specification, a large upfront build and a long wait before anyone saw anything working. Projects overran, and once built, the software was often hard and expensive to change.
Given that, buying off the shelf and adapting your process to fit was the sensible call for most SMEs. The calculation was right at the time. What has changed is the calculation.
What has changed
Three things have shifted at once.
Far less is built from scratch. Modern cloud platforms provide the foundations (secure logins, databases, hosting, payments) as ready-made building blocks. A bespoke build today is mostly about the part that is specific to your business, not the plumbing underneath.
AI-assisted development. A study by economists from MIT, Princeton, Wharton and Microsoft Research, covering 4,867 developers at Microsoft, Accenture and a third large company, found those given an AI coding assistant completed 26% more tasks. The study's only quality check, whether the code built successfully, showed no significant change overall, though it did fall at one of the three companies.5
Smaller, phased builds. Instead of one large system delivered at the end, a modern build starts with the single tool that fixes the most painful problem, puts it live, and grows from there. Each phase earns its place before the next one starts.
Together, these make bespoke software far more convenient to commission than it was even three years ago: faster to see working, easier to change and lower risk to start.
What bespoke looks like in a 20 to 200-person firm
Bespoke does not have to mean replacing everything. In most firms, the first build targets one process where the off-the-shelf tools fall short.
| Type of business | Where the friction usually is | A typical first build |
|---|---|---|
| Building products and suppliers | Quotes worked out by hand from price lists and drawings | A quoting or product calculator tied to live prices |
| Manufacturing and distribution | Stock, orders and production tracked across spreadsheets | One system for orders, stock and dispatch |
| Trade services | Job sheets, photos and sign-offs scattered across phones and email | Job management with a client portal |
| Admin-heavy professional services | Client onboarding and documents chased by email | An intake and document workflow |
It is the same principle we applied with Eccles, a Walsall manufacturer, where we replaced several separate tools with one custom ERP covering CRM, stock, vendor data and operations. With the data in one place, we could then build Eccles Command, an AI analyst that answers the sales and stock questions that used to take hours in spreadsheets.
For a closer look at quoting tools specifically, see our guide to construction estimating software vs a custom quoting tool.
The benefits, stated plainly
- It fits how you work. Your process, your terms, your product rules. The software follows the business rather than the other way round.
- You own it. No per-seat fees that rise every time you hire, and no vendor deciding which features you get next year.
- Fewer tools, one source of truth. One system can replace several subscriptions, so the customer, the quote, the job and the invoice live in one place.
- It changes when you change. A new product line, a new pricing rule or a new branch becomes an update, not a migration.
- Your data stays usable. It sits in a structure you control, ready for reporting, and for AI.
Built for AI agents from day one
This is the part that makes 2026 different from any earlier year.
AI agents are tools that can read information, make a decision within rules you set and take an action, such as drafting a quote, updating a job or chasing an invoice. To do any of that, an agent needs software it can connect to: something it can read from and write to safely.
That is where off-the-shelf and bespoke diverge. With a closed product, what an agent can reach is decided by the vendor: which data is exposed, which actions are allowed, and at what price tier. With software you own, those connections can be designed in from the start, with exactly the permissions you want.
The industry is converging on how this should work. The Model Context Protocol (MCP) is an open standard for connecting AI tools to the systems and data a business already has.8 In Stacklok's December 2025 survey, nearly half of the technology leaders at software companies (all with at least 500 staff) ranked adopting MCP as a top-five priority.9 SMEs building now can design for it from day one rather than retrofit it later.
In practice, that might mean an agent that reads an incoming enquiry and drafts a quote directly in your quoting tool for someone to approve, or one that checks your own system each morning and drafts the chasers for overdue invoices. For the wider picture on choosing between rules, automation and agents, see our guide to practical AI automation strategies for SMEs, or read about how we build AI agents.
When off-the-shelf is still the right call
Bespoke is not the answer to everything. Payroll, accounts, email and file storage are jobs where the market products are good, compliance is handled for you, and your way of doing them is not what wins you business.
A simple rule: buy where everyone works the same way; build where the way you work is your advantage. Your quoting logic, your product rules, the way you run a job and how you look after customers are usually where that advantage sits. Often the best answer is both: keep your accounts package and connect your bespoke system to it.
If you are weighing up a larger system such as an ERP, our guide to off-the-shelf vs custom ERP for UK manufacturers covers that decision in detail.
How to keep the risk small
Four steps keep a first build small enough to judge quickly and cheap enough to stop if it does not pay. Start by writing down, for a fortnight, every time someone re-keys, chases or works around a tool: the pattern usually points to the first build. Then build that one tool, run it alongside the old way and check its outputs against what you do today, and add the next phase only when the first is in daily use.
Diagram
From workaround to working system
- Map the problem for a fortnightLog every re-key, chase and workaround
- Build the smallest useful toolOne process, done properly, live quickly
- Run it alongside the old wayCheck its outputs before you switch over
- Extend once it earns its keepNext phase only once the first is in daily use
Whoever builds it, make sure you own three things from day one: the code, the data and the hosting account. That keeps you free to change supplier, and makes the system something you control rather than rent. For what makes a system last as you grow, see how to build software that holds up.
Is now the time for your business?
Five questions to ask yourself:
- Are people re-keying the same data into more than one tool?
- Is a key process running on a spreadsheet only one person fully understands?
- Are your subscription bills rising faster than your headcount?
- Are you paying for features nobody uses, while missing the one you need?
- If you wanted an AI agent to help tomorrow, would it have anything sensible to connect to?
If you answered yes to three or more, bespoke software is worth a conversation. Not a big project, just the first useful tool.
Frequently asked questions
What is bespoke software, and how is it different from off-the-shelf?
Bespoke (or custom) software is built around one business's processes and owned by that business. Off-the-shelf software is built for a broad market and rented, usually per user per month. Bespoke fits your way of working; off-the-shelf asks you to fit its way.
Is bespoke software worth it for a small business?
It can be, where a process is specific to how you win or deliver work and the off-the-shelf tools leave staff re-keying or working around them. Start with one tool that fixes one problem, and judge it on the time it saves before building more.
How long does it take to build bespoke software?
It depends on scope, which is why we recommend building in phases. A focused first tool can be in use far sooner than a full system, and each later phase builds on something already working.
Can bespoke software work with AI agents and tools like Claude?
Yes, and it is one of the strongest reasons to build now. Software you own can be designed so AI agents can read from it and act on it, with the permissions you choose, using open standards such as the Model Context Protocol.
Who owns the code and data in a bespoke build?
You should. Agree before work starts that you own the code, the data and the hosting account, so you are never locked into one supplier.
Sources
- UK SMEs upbeat but finance admin slows growth plansIT Brief UK, reporting the Monzo Business Money Moves Report
- Automation for business in 2026 (and how AI agents fit in)Fasthosts
- Upcoming Xero price changesXero
- Meet Canva Business: a powerful new plan for small businesses with big ambitionsCanva Newsroom
- The Effects of Generative AI on High-Skilled Work: Evidence from Three Field Experiments with Software DevelopersManagement Science (Cui, Demirer, Jaffe, Musolff, Peng and Salz)
- Measuring the impact of early-2025 AI on experienced open-source developer productivityMETR
- We are changing our developer productivity experiment designMETR
- Introducing the Model Context ProtocolAnthropic
- State of Model Context Protocol in Software 2026Stacklok





