---
title: "Build or buy software? The real three-year cost (UK, 2026)"
description: "Build or buy? The real three-year cost of renting software for a UK team of twenty against a system you own, with dated sources, and when renting wins."
canonical: https://www.clientflow.ai/guides/build-or-buy-software-uk
category: Ownership
authors: ["Zac Santer"]
published: 2026-09-04
verified: 2026-09-04
language: en-GB
---

# Build or buy? What the software you already pay for really costs

Own it or rent it? The three-year arithmetic for a team of twenty, the price rises nobody budgets for, what leaving a tool involves, and the four cases where renting is still the right answer.

By Zac Santer · Published 4 September 2026 · Verified 4 September 2026 · 11 min read

**Summary:** For a team of twenty, three mainstream tools at list price cost about £73,800 over three years before a single price rise, and software prices rose 13.2% a year in the latest index, nearly five times general inflation. A focused version one you own costs from £10,000 to build and about £800 a year to run, and nothing per seat. Renting still wins when the workflow is standard, the seat count is small and stable, or the process is still changing every month. Owning wins when the workflow is yours, the team is growing, or the data has to be in your name. The break-even question is simple to ask, and we will answer it for free on a twenty-minute call.

## Contents

1. [The short answer](https://www.clientflow.ai/guides/build-or-buy-software-uk#the-short-answer)
2. [What renting costs](https://www.clientflow.ai/guides/build-or-buy-software-uk#what-renting-actually-costs)
3. [What owning costs](https://www.clientflow.ai/guides/build-or-buy-software-uk#what-owning-actually-costs)
4. [The cost of leaving](https://www.clientflow.ai/guides/build-or-buy-software-uk#the-exit-cost)
5. [When renting wins](https://www.clientflow.ai/guides/build-or-buy-software-uk#when-renting-wins)
6. [When owning wins](https://www.clientflow.ai/guides/build-or-buy-software-uk#when-owning-wins)
7. [Questions people ask before deciding](https://www.clientflow.ai/guides/build-or-buy-software-uk#questions)

## 1. The short answer

Rent software when the tool fits the way you already work and the seat count is small. Own it when the workflow is yours, the team is growing, or the data has to be in your name. Most established teams are somewhere in between, paying for the workaround while the case for owning builds. This guide puts numbers on it.

The numbers are not close. A team of twenty on three mainstream tools spends about **£73,800** over three years at today’s list prices, before a single price rise, and the latest index puts software price rises at 13.2% a year[^1].

One case is common enough to have its own guide: the process is not on a rented tool at all, it is on a spreadsheet. [When a spreadsheet stops being the right tool](https://www.clientflow.ai/guides/replace-a-spreadsheet-with-software) is the version of this question for workbooks, and most of the time the answer there is to keep it.

A focused version one that you own costs from **£10,000** to build and about **£800 a year** to run, with nothing per seat. The [cost guide](https://www.clientflow.ai/guides/bespoke-software-development-cost-uk) has the bands; this guide has the comparison.

- **SaaS price inflation**: 13.2% a year (Vertice’s index for 2026, nearly five times G7 inflation[^1])
- **SaaS spend per employee**: $9,100 a year (By the end of 2025, up from $7,900 two years earlier[^1])
- **Hit by unexpected charges**: 78% of IT leaders (For AI features or consumption pricing in the past year[^2])

## 2. What renting costs

A subscription has four costs and the price list shows one of them. The seat price is the one on the page. The tier is the second: the feature you actually need is usually one plan up, and everyone on the tool moves up with it.

The third is usage, the AI feature or the automation task that is metered on top of the seat. The fourth is time, because the price you agreed is not the price you will pay in year three.

Take a twenty-person team on the three tools that most often turn up in a first conversation: a CRM at the professional tier, a database tool at the business tier, and an automation tool for the team.

At list prices on annual billing, HubSpot’s Sales Hub Professional is $90 a seat a month[^5], Airtable’s Business plan $45 a seat a month[^6], and Zapier’s Team plan from $69 a month[^7]. Converted at the European Central Bank reference rate and rounded, that is the table below.

| Item | Year 1 | Three years, flat | Three years, rising 13.2% a year |
| --- | ---: | ---: | ---: |
| CRM, 20 seats, professional tier[^5] | £16,000 | £48,000 | £54,600 |
| Database tool, 20 seats, business tier[^6] | £8,000 | £24,000 | £27,300 |
| Automation, team tier[^7] | £600 | £1,800 | £2,000 |
| **Rented, total** | **£24,600** | **£73,800** | **£83,900** |

List prices in dollars on annual billing, converted at £1 = $1.35[^8] and rounded to the nearest £100. The last column applies the 13.2% annual rise from the Vertice index to years two and three as an illustration; your renewal letters will say what actually happened.

That table has no usage charges in it, and 78% of IT leaders reported unexpected charges for AI features or consumption pricing in the past year[^2]. And it is three tools. The average organisation in Zylo’s index runs 305 applications, with a median of 240[^2], and Vertice puts software spend at about $9,100 a year for every employee by the end of 2025[^1].

Twenty people at that rate is $182,000 a year. That is not a workaround; it is a line item.

> **The tier tax**
>
> The feature you need is one plan up, and the whole team moves up to get it. A single permission setting, a report or an integration can add a third to the bill for everyone. It is the most common reason a subscription that looked cheap at ten people looks expensive at twenty.

## 3. What owning costs

Owning has three costs, and we would rather you saw all of them than only the first.

- **The build**: From £10,000 for a focused version one, fixed from a blueprint, the written scope and clickable prototype every build starts with, before you commit. Most of what established teams ask us to scope lands between £10,000 and £50,000, and the five things that move it are integrations, data, complexity, roles and compliance. The [cost guide](https://www.clientflow.ai/guides/bespoke-software-development-cost-uk) has the bands and a worked example.
- **Running it**: Hosting, database, email and monitoring in your own accounts, at list price around $91 a month for a version one[^9][^10][^11][^12], billed by the providers to you. Priced by usage, not by seat, so the twenty-first person costs nothing.
- **Keeping it working**: A warranty window in which anything that does not do what the blueprint says is fixed at no cost, then a fixed monthly support fee if you want one. New features are scoped and priced before they are built. There is no percentage-of-build maintenance charge, and if you stop paying for support the software keeps running in your accounts with any developer you choose.

So the owned column of the comparison is a build in the first band, say £18,000, plus about £800 a year to run, which comes to roughly **£20,400 over three years** with no support fee, or a little more with one.

Against £73,800 rented, rising. The two lines cross somewhere in the first year, and after that the gap widens every month, because one side has a per-seat meter and the other does not.

- Rented, three years, no rises: £73,800
- Owned, three years, run costs included: £20,400

**Fig. 1.** Three years for a team of twenty: three rented tools at list price with no price rises, against a first-band build you own plus its run costs. Support is a choice on the owned side and is not drawn.

The caveat is scope. An £18,000 build replaces the workflows you scoped, not every feature in three products. If the team uses a hundred features of the CRM, it should keep the CRM. The comparison holds when what the team uses is the workflow, and the rest of the tool is there because it came in the box.

## 4. The cost of leaving

Every tool has an exit cost, and it is paid whether you leave the tool or the tool leaves you, through a price rise, a discontinued plan or an acquisition.

Records come out. HubSpot, to take the largest example, exports contact records with their default and custom properties and history, plus activities and associations, delivered as a file by email[^4].

What does not come out as a file is everything the team built inside the tool: the automations, the views, the lists, the way work moves from one person to the next. A spreadsheet of contacts is not a CRM. The workflow is rebuilt wherever you go next, and that rebuild is the real exit cost.

The owned side has an exit cost too, and it is deliberately small. The code lives in a repository in your name from the first week, every account is in your name, and the data is yours in law under a processor agreement as well as in practice.

Leaving us means opening the repository with someone else. We think that is the right way round: the cost of leaving should sit with the supplier, not the customer.

## 5. When renting wins

Some calls end with us telling you to keep the subscription. Rent when:

- **The tool is the category and your workflow is standard.** Accounting, payroll, email, payments. Nobody should build their own ledger. The vendor’s whole business is that workflow, and yours is something else.
- **The seat count is small and stable.** Five people on a £45 seat is £2,700 a year. The maths that makes owning cheaper needs either more seats or a workflow the tool cannot do.
- **The process is still changing every month.** Software fixes a process in place. Rent while you are still finding out what the process is, and build the version that survived.
- **The value is the ecosystem, not the screen.** If what you are paying for is the integrations, the marketplace, the templates and the community, a bespoke build gives you the screen and none of that.

There is a fifth, quieter case: the team likes the tool. That is worth something, and we will say so.

## 6. When owning wins

Own when the workflow is yours and the tool is bending to fit it, because the bending is where the cost lives. Five signals, and they are the same five that move a build between price bands. If the workflow is client-facing, the [client portal page](https://www.clientflow.ai/client-portal-development) works the same question through for a portal; if it is your own team’s, the [internal tools page](https://www.clientflow.ai/internal-tools-development) does.

| Signal | Rent | Own |
| --- | --- | --- |
| **Seats** | Few, and steady. | Growing, or the whole company plus customers and suppliers, who cannot be seats at all. |
| **The workflow** | The tool’s way is fine. | Your way is the point: approvals, exceptions, the thing that makes you better than the next firm. |
| **Integrations** | The tool connects to what you use out of the box. | Every connection is a paid add-on or a manual re-key. |
| **Data** | Nothing sensitive, nothing regulated. | Personal, financial or health data that has to be in your name, in your region, under your policies. |
| **Change** | Monthly. | Settled enough to write down, and worth building once. |

Three of five in the right-hand column and the blueprint call will almost certainly end in a firm range. Three in the left and it will end in us telling you to keep the tool.

> **The break-even question**
>
> What does the workaround cost over three years, in seats, tiers, tasks and hours, against a build you own? When the answer is close, keep the tool. When it is not close, it is usually not close by a wide margin, and the rises in the meantime only move it one way.

If you have already tried to close that gap with an AI builder and stalled, that is a different conversation and there is a [guide for it](https://www.clientflow.ai/guides/stuck-with-a-lovable-build). The arithmetic is the same; what changes is what you already have in hand.

**Bring the subscriptions and the spreadsheet** Twenty minutes, no preparation and a straight answer: keep the tools, or a firm range for the system that replaces them.

[Apply for a blueprint call](https://www.clientflow.ai/apply)

## 7. Questions people ask before deciding

### Is it cheaper to build or buy software?

For a small, stable team on a standard workflow, buy. For a growing team on a workflow of its own, building is usually cheaper within the first year and the gap widens after that, because a build has no per-seat meter and subscriptions rose 13.2% a year in the latest index[^1]. Three rented tools cost £73,800 over three years against about £20,400 for a first-band build you own.

### How much does SaaS cost per employee?

About $9,100 a year by the end of 2025 across the organisations in Vertice’s index, up from $7,900 two years earlier[^1]. Smaller companies pay more per head because the core tools are spread across fewer people: one analysis of 1.8 million purchases puts a fifty-person company at roughly $6,980 a year per employee[^3].

### Can we export our data if we leave a tool?

Usually the records, rarely the workflow. HubSpot, for example, exports contact properties with their history, activities and associations as files[^4]. The automations, views and lists the team built inside the tool are rebuilt wherever you go next. With a system you own there is nothing to export: the code and the data are already in your name.

### Does owning software mean we have to maintain it?

It means someone does, and you choose who. Every build ships with a warranty window; after it, your own developer, any developer you hire, or our support on a fixed monthly fee keeps it current, and ending support changes nothing about the software. The [running-costs guide](https://www.clientflow.ai/guides/running-costs) itemises the work.

### What if the vendor raises prices?

Budget for it, because they will: 13.2% a year on average in the latest index, and 60% of vendors were found to mask the rise rather than state it[^1]. A subscription’s price is the vendor’s decision. A build you own has run costs priced by usage, from providers you can swap, and no seat count to multiply a rise by.

### Should a small business build custom software?

Not usually, and not first. Below £10,000 the right answer is to configure a tool you already pay for, and we say so on the call. A small business builds when a specific workflow is the business, when the per-seat maths has crossed over, or when the data has to be in its own name. Version one is scoped narrow on purpose and earns the next piece.

### How do we work out our own number?

Add up every seat, at the tier you are actually on, times three years, then add the hours the team spends re-keying between tools at a loaded salary. Set that against a build in the band the cost guide gives for your workflow, plus about £800 a year to run. If you would rather we did it, bring the subscription list to a blueprint call and we will do it in twenty minutes.

## Sources

Every third-party figure above was read from the page cited, on the date shown. Vendors change prices without notice, so the date is part of the fact.

[^1]: [Vertice, SaaS Inflation Index 2026, January 2026](https://www.vertice.one/l/saas-inflation-index-report). SaaS prices rising 13.2% a year, nearly five times G7 inflation; 60% of vendors mask rises; about $9,100 spent on SaaS per employee by the end of 2025, from $7,900 in 2023. Seen 4 September 2026.
[^2]: [Zylo, 2026 SaaS Management Index](https://zylo.com/2026-saas-management-index). 305 applications on average, median 240; 78% of IT leaders reported unexpected charges tied to AI features or consumption-based pricing; 61% cut projects due to unplanned SaaS cost increases. Seen 6 September 2026.
[^3]: [Cledara, average SaaS spend per employee in 2026, 25 March 2026](https://www.cledara.com/blog/average-saas-spend-per-employee-2026). From 1.8 million purchases across 6,800 tools; a fifty-person US company at about $6,980 a year per employee, a hundred-person company at about $3,490. Seen 4 September 2026.
[^4]: [HubSpot knowledge base, export contact data](https://knowledge.hubspot.com/import-and-export/export-contact-data). Default and custom properties with history, activities and associations, delivered as a file by email; values stored elsewhere may be redacted. Seen 4 September 2026.
[^5]: [HubSpot, Sales Hub pricing](https://www.hubspot.com/pricing/sales). Shown in dollars: Professional $90 a seat a month on annual billing, $100 monthly; Enterprise from $150. Seen 4 September 2026.
[^6]: [Airtable pricing](https://airtable.com/pricing). Team $20 and Business $45 a seat a month on annual billing. Seen 4 September 2026.
[^7]: [Zapier plans and pricing](https://zapier.com/pricing). Professional from $19.99 a month, Team from $69, tasks bought in tiers from 750 a month. Seen 4 September 2026.
[^8]: [European Central Bank, euro foreign exchange reference rates, 3 September 2026](https://www.ecb.europa.eu/stats/policy_and_exchange_rates/euro_reference_exchange_rates/html/index.en.html). USD 1.1615 and GBP 0.86055 to the euro, which makes £1 about $1.35. Seen 4 September 2026.
[^9]: [Vercel pricing](https://vercel.com/pricing). Pro, $20 a month per developer seat. Seen 4 September 2026.
[^10]: [Supabase pricing](https://supabase.com/pricing). Pro, $25 a month with the first project included and 100,000 monthly active users. Seen 4 September 2026.
[^11]: [Resend pricing](https://resend.com/pricing). Pro, $20 a month for 50,000 emails. Seen 4 September 2026.
[^12]: [Sentry pricing](https://sentry.io/pricing/). Team, $26 a month on annual billing. Seen 4 September 2026.

## About the author

**Zac Santer**, Co-founder and design lead. Zac scopes every build and writes the number on every quote. [LinkedIn](https://www.linkedin.com/in/zachary-santer/)

## More guides

- [When a spreadsheet stops being the right tool](https://www.clientflow.ai/guides/replace-a-spreadsheet-with-software): The signals that a workbook has become the risk, and the cheaper answers to try first.
- [What bespoke software actually costs in the UK](https://www.clientflow.ai/guides/bespoke-software-development-cost-uk): The bands, the five things that move the price, and when not to build.

All guides: https://www.clientflow.ai/guides. Every guide is also served as Markdown at its URL with .md appended.