A small UK business running a website, email and a few internal tools typically spends £300 to £1,500 per month on cloud. A scale-up running its own product spends £2,000 to £15,000. A mid-market firm with data platforms and multiple environments spends £15,000 to £80,000 plus. In our experience, most bills carry 20 to 35 percent pure waste: idle resources, oversized instances, forgotten test environments, unplanned egress and licence sprawl. A one-off FinOps review usually pays for itself inside a quarter. This guide gives you the realistic numbers and the five leaks to check first.
Cloud pricing is public. Anyone can open the AWS, Azure or Google Cloud calculator and get a number. And yet almost every finance director we speak to is surprised by their bill, in the wrong direction, within a year of migrating. The gap between the calculator and the invoice is where this article lives.
This is a senior view of what UK businesses really pay in 2026, why the bill grows faster than the business, and what to do about it without a re-platforming project.
The four layers of a real cloud bill
When people say "cloud costs", they usually mean compute. Compute is rarely more than half the story. A realistic budget has four layers:
- Compute and storage. Virtual machines, containers, serverless functions, databases, object storage. The headline layer. Predictable if your workloads are steady, spiky if they are not.
- Data movement. Egress fees for data leaving the platform, cross-region replication and inter-zone chatter. The layer nobody models up front and the one that most often produces a shock invoice.
- Licensing and marketplace. Windows Server, SQL Server, third-party security tooling, observability platforms bought through the marketplace. Grows quietly, renews automatically.
- People. Whoever operates it. A part-time contractor, a managed service, or an internal platform team. For many SMEs this layer costs more than the infrastructure itself.
Realistic monthly spend by company profile
These are the ranges we see across live UK environments in 2026, blended across AWS, Azure and Google Cloud. Your exact number depends on architecture, but if you are far outside your band, that is a signal worth investigating.
| Profile | Typical monthly cloud spend | What is usually running |
|---|---|---|
| Small business (5 to 25 staff) | £300 to £1,500 | Website, Microsoft 365 or Workspace, a line-of-business app, backups. |
| Digital SME (25 to 100 staff) | £1,500 to £8,000 | Customer-facing app, staging environment, managed database, CDN, monitoring. |
| Scale-up with own product | £2,000 to £15,000 | Production plus dev/test, Kubernetes or serverless estate, data warehouse starter. |
| Mid-market (100 to 500 staff) | £15,000 to £80,000+ | Multiple products, data platform, ML workloads, disaster recovery, several teams deploying. |
Rule of thumb: if your cloud bill has grown faster than your revenue for two consecutive quarters and nobody can explain why in one sentence, you have waste, not growth.
The five places the money leaks
1. Compute that runs while nobody is working
Dev, test and staging environments left on 24/7 cost three times what they need to. An environment used 8 hours a day, 5 days a week, is idle 76 percent of the time. Scheduling non-production workloads to switch off at night and weekends is the single fastest saving in most estates, and it needs no architectural change.
2. Oversized instances
Teams size servers for the worst day they can imagine, then never revisit. Utilisation data usually shows machines running at 10 to 20 percent. Rightsizing one tier down typically halves the cost of that machine with no user-visible impact. Do this before buying any savings plan, because commitments lock in the oversized baseline.
3. Paying on-demand prices for steady workloads
If a workload has run every day for six months, it will probably run tomorrow. Reserved instances, savings plans and committed use discounts pay 20 to 60 percent less for exactly the same machines. The catch: commit after rightsizing, and commit to less than you think, because businesses change.
4. Egress and data movement
Moving data into the cloud is free. Moving it out, or between regions, is not. Analytics tools pulling full datasets nightly, backups replicated to another provider, chatty microservices split across zones: each looks small per gigabyte and compounds into thousands per month. If your egress line is more than 10 percent of your bill, something is architected wrong.
5. Licences and tools nobody owns
Marketplace subscriptions, monitoring seats, security agents on machines that no longer exist. Nobody cancels what nobody owns. A quarterly licence review with a named owner per tool is boring and reliably saves money.
What FinOps means in plain English
FinOps is a grand name for a simple discipline: someone is accountable for cloud spend, spend is visible per team or product, and there is a monthly rhythm of review and action. You do not need a platform team or a consultancy retainer to start. You need:
- Tagging that sticks. Every resource carries an owner and a product tag. Untagged resources get chased weekly.
- One dashboard. Spend by team, by environment, by month. The native cost tools on AWS, Azure and GCP are good enough to start.
- A monthly 30-minute review. Top ten cost lines, anything growing faster than 10 percent month on month, and one action per meeting.
- Budgets with alerts. Not to punish teams, but so surprises surface in days rather than at invoice time.
Cloud or managed hosting? The honest answer
Not every workload belongs on hyperscale cloud. A steady, predictable application with no elastic demand often runs cheaper on managed hosting or a fixed-price platform, with less operational skill required. The cloud's economic advantage is elasticity and managed services. If you use neither, you are paying a premium for flexibility you never exercise.
Quick decision guide
- IF your workloads are spiky, seasonal or growing fast Hyperscale cloud with autoscaling and committed-use discounts on the steady baseline.
- IF you run a steady app with predictable traffic Consider managed hosting or a PaaS at a fixed monthly price. Re-check yearly.
- IF your bill grew 30 percent plus this year without a launch Commission a FinOps review before signing any new commitment. Rightsize first, commit second.
- IF you have no one who owns the bill Appoint an owner this week. Visibility alone typically cuts 10 percent.
Three traps to avoid
Trap one: committing before cleaning. Savings plans applied to a wasteful estate lock the waste in for one to three years. Always rightsize and schedule first, then commit to the clean baseline.
Trap two: the invisible second estate. Shadow accounts opened by developers, proof-of-concept projects that became production, a SaaS tool quietly hosting your data. Consolidate billing so every pound appears on one report.
Trap three: measuring savings, not unit cost. A bill that falls while customers leave is not a win. Track cost per customer, per order or per transaction. That is the number that tells you whether cloud spend is healthy.
What good looks like
A healthy cloud estate in 2026 has a bill that can be explained in one page, non-production environments that sleep at night, commitments covering 60 to 80 percent of steady usage, egress under 10 percent of spend, and a named owner who reviews it monthly. None of that requires new technology. It requires attention, once, and then a light monthly habit.
If you want the attention part done for you, this is exactly the kind of brief we run: a vendor-neutral cloud cost review, a prioritised savings list, and if you want it, the engineers to implement it. One brief in, one outcome out.
Suspect your cloud bill is carrying waste?
Send us a brief. A human replies within 30 minutes, day or night, and we will scope a no-obligation cloud cost review with vetted UK specialists.
Start a brief →