Custom Web App or Off-the-Shelf SaaS: How a UK Small Business Should Actually Decide

Every growing UK business hits the same fork in the road. A process that used to run on a spreadsheet and a shared inbox starts to creak, and you have two obvious ways out: pay for another off-the-shelf tool, or have something built that fits how you actually work. Most advice on this question is written by someone with a stake in the answer. This is a framework instead. Read it, apply the checklist at the end, and you should know which side of the line your problem sits on before anyone quotes you a price.

When off-the-shelf SaaS is clearly the right call

Buying is the default for good reason, and it stays the right answer more often than people building things would like to admit. If a problem is a commodity, someone has already solved it well, priced it sensibly, and hardened it against edge cases you have not even thought of yet.

Reach for SaaS when the problem is standard and shared across thousands of businesses like yours. Email, calendars, accounting ledgers, payroll, card payments and document storage are all solved problems. The workflow you need is the workflow the tool already ships with, so you are not bending the software or your process to fit. Your integration needs are light, meaning the tool can live happily on its own without constant handoffs to five other systems. And nobody would ever describe the way you run this particular task as a competitive advantage. If that describes your problem, buy the thing, and do not let anyone talk you into a build.

When SaaS quietly becomes the wrong call

The trap with off-the-shelf tools is rarely a bad decision on day one. It is a good decision that slowly stops being good, without any single moment where it obviously flips. Here is what that drift tends to look like.

Per-seat pricing that grows with your headcount

A monthly fee per user looks trivial when there are three of you. The problem is that the cost scales with the size of your team rather than the value you get from the tool. Ten seats at a monthly fee, then twenty, then across three tools you all depend on, and suddenly you are paying a serious annual sum for software whose usefulness has not grown at anything like the same rate. Success makes it more expensive, not less.

Workflow contortions

You start doing things in a slightly odd order because the tool prefers it that way. You keep a side spreadsheet to track the one field the software will not let you add. Staff invent workarounds and pass them on to new starters as though they were the real process. When the software is quietly dictating how you work rather than supporting it, you are paying a tax in wasted time that never shows up on the invoice.

Data you cannot easily get back out

Your records, your history and your customer relationships accumulate inside someone else's system, in their format, on their terms. If the pricing changes, the product is discontinued, or you simply outgrow it, getting your own data back into a usable shape can be painful. Lock-in is easy to ignore right up to the moment it matters, and by then you have very little bargaining power.

The fifth tool that almost fits

This is the clearest warning sign of all. You are evaluating yet another subscription that handles most of what you need, and once again you will absorb the gaps with manual effort. Each tool is reasonable on its own. Together they turn into integration spaghetti: data copied between systems by hand, or held together with brittle automations that break quietly and leave you reconciling mismatches. At that point the collection of tools is costing you more in licences and lost time than the problem itself is worth.

When a custom build actually wins

Custom is not automatically better, and anyone who tells you otherwise is selling. It wins in specific situations, and it is worth being strict about them.

• The workflow is the business. If the particular way you handle enquiries, quote jobs, or manage cases is a genuine part of how you compete, forcing it into a generic tool sands down the very thing that sets you apart. A build lets the software match the process instead of the other way round.
• The licensing maths overtakes a build. When the combined annual cost of the subscriptions you are stacking would pay for a custom build within a few years, and you own the result rather than renting it indefinitely, the arithmetic starts to favour building.
• Your advantage lives in the process. If competitors can buy exactly the same off-the-shelf stack you use, your tooling is not helping you stand out. Software shaped around how you actually work is much harder for anyone else to copy.
• The integrations are the point. When the real value is in joining several systems together cleanly rather than in any single feature, a purpose-built layer often beats bolting more disconnected tools onto the pile.

The honest costs of custom that most agencies skip

Here is the part of the conversation that build-versus-buy articles tend to leave out. Custom software has two costs, and everyone talks about the first while quietly ignoring the second.

The first is the build. That is the visible number, the one on the quote, and it is the easy part to reason about. The second is what happens after launch, and it never goes away. Real software needs hosting, security updates, backups that are actually tested, monitoring, and small changes as your business shifts. A build that nobody looks after is not an asset. It slowly becomes a liability: the thing that breaks on a Friday afternoon with nobody responsible for fixing it.

A lot of agencies hand over the code, invoice the final milestone, and move on, which leaves you owning something you may not be equipped to run. Evoloop is set up the other way around. Evoloop is a Glasgow development studio that builds software for UK businesses and then runs what it builds. The founder brings over 10 years in IT infrastructure, cloud, Microsoft 365 and Azure, so the running side is treated as a first-class part of the job rather than an afterthought. A Run & Improve retainer covers the hosting, security, backups and small ongoing changes, which means the honest second cost is priced in from the start instead of landing on you by surprise. You still own the code from a Fixed-Price Build. You just are not left alone with it.

A short checklist you can apply today

Run your situation through these questions. The more that pull towards building, the stronger the case for a custom web app.

• Is this a commodity problem thousands of businesses share, or something specific to how you work? Commodity points to buy.
• Are you contorting your process to fit a tool, or keeping side spreadsheets to patch its gaps? That points to build.
• Is your subscription cost scaling with headcount rather than with value? Add up the annual figure across every tool involved.
• Would those combined licence costs pay for a build within a few years? If yes, the maths favours building.
• Are you evaluating a fourth or fifth tool that only almost fits, stitched to the others by hand? That is integration spaghetti asking to be replaced.
• Does a real competitive advantage live in this process? If it does, keep it out of generic software.
• Can you get your own data back out cleanly today? If not, factor lock-in into the true cost of staying.
• If you build, who runs it after launch? If you have no answer, a build without a running plan is a risk, not an asset.

Most businesses land in a mix: buy the commodities, build the one or two things that genuinely make you different, and make sure whatever gets built has someone responsible for keeping it alive. If you are honestly unsure which side your problem sits on, that uncertainty is itself worth resolving properly before anyone spends money either way.