Most mid-market firms I speak to have a decent handle on their cloud costs. They know what they're paying for Azure or AWS. They've probably had a conversation in the last year about whether they're on the right tier. Some have even done a proper audit.
But almost none of them have thought about tariffs.
And I get why. Tariffs are a macro issue. They don't really affect our CMS hosting bill. That was broadly correct until recently. Cloud services sat outside most trade tariff frameworks - software, hosting, SaaS subscriptions were digital services, not goods in a shipping container. The rules were designed for steel and soybeans, not Kubernetes clusters.
That's changing. And if you're running a mid-market B2B service firm in the UK - a law firm, a consultancy, an accountancy practice, an MSP - with meaningful spend on US-headquartered cloud providers, you've probably not assessed how exposed you actually are.
I was on a call last month with the IT director of a 180-person professional services firm. Good firm, sensible people, reasonably well-run technology stack. He'd just opened a renewal notice from one of their SaaS vendors - a US-headquartered platform they use for document management - and the price had gone up 11%. No warning, no negotiation, just a paragraph buried near the bottom about "market adjustments reflecting current operating conditions." He read it out to me. His tone was somewhere between baffled and resigned.
That phrase - "market adjustments reflecting current operating conditions" - is doing a lot of work right now. And what it's often reflecting, though vendors won't say it directly, is the cost of US tariff policy flowing through their infrastructure.
Here's the mechanism. Cloud providers run on physical equipment - servers, networking gear, storage arrays - much of which is manufactured in Asia. When tariffs increase the cost of that hardware, those costs move through the supply chain. AWS, Microsoft, and Google aren't absorbing a 10-20% increase in infrastructure costs out of goodwill. They're adjusting pricing, restructuring tiers, or quietly reducing what's included in existing agreements. And the SaaS companies sitting on top of that infrastructure? They're doing the same thing, one renewal cycle at a time.
There's also the licensing and service agreement layer to think about. If you're paying for a US-hosted platform - and most mid-market firms are paying for several - the pricing is denominated in dollars and governed by US commercial terms. Tariff-adjacent cost increases don't always show up as a line item labelled "tariff." They show up as that 11% on your renewal notice. I've seen several of these in recent months from vendors who weren't raising prices anything like this aggressively a year ago.
And then there's the more structural risk: retaliation. If the UK or EU responds to US tariff policy with their own levies on digital services - and the Digital Services Tax conversation has been rumbling for years - you could end up paying more from both directions simultaneously.
Most of the commentary I've read on this is written for enterprise. "Review your cloud procurement strategy." "Engage your global sourcing team." "Negotiate custom enterprise agreements with your hyperscaler account manager." Right. Brilliant. Very helpful if you're Barclays.
If you're a 200-person law firm or a 150-person consultancy, you don't have a global sourcing team. You have an IT director who's also responsible for cybersecurity, the phone system, and making sure the printers work. Your "cloud procurement strategy" is whatever was agreed three years ago when someone picked a platform and signed an annual contract.
That's precisely why this matters more for firms like yours. Enterprise organisations have the leverage to negotiate bespoke pricing, the scale to absorb cost increases across a massive base, and dedicated teams whose entire job is to monitor this stuff. You don't have any of that. When a vendor raises prices by 8%, you either pay it or you embark on a migration project you haven't budgeted for. Neither option is great.
The mid-market gets hit harder on a per-seat, per-pound basis and has fewer tools to respond. That asymmetry is worth sitting with for a moment.
Cost increases are the obvious bit. But there are a couple of second-order effects that concern me more.
Data sovereignty is becoming a client question, not just a compliance question. If your client data sits on US-hosted infrastructure, you've always had a GDPR consideration. But tariff disputes tend to escalate into broader geopolitical friction, and when that happens, data sovereignty questions get louder. I had a conversation earlier this year with the COO of a mid-sized law firm - we were talking about something else entirely, a platform review - and she mentioned almost in passing that two of their larger clients had started asking where their data was physically hosted. Not the regulator. The clients. She said it with the slightly tired look of someone adding another thing to a list that's already too long. That wasn't happening two years ago. If you're in financial services or legal, this is going to become a procurement question your clients ask you, not just one you ask your vendors.
Vendor pricing power increases when switching costs are high. This is the one that really bothers me. If you're locked into a US cloud platform - and "locked in" doesn't have to mean contractually bound, it can just mean "migration would cost more than we can justify this year" - the vendor knows you're not going anywhere. Tariff-driven cost increases become an opportunity to test price elasticity. Switching from one cloud provider to another, or from a US-hosted CMS to a UK or EU alternative, is a six-figure project for most mid-market firms. The vendors know that. Some of them are using it.
The competitive pressure that kept cloud pricing in check is weakening. When all the major hyperscalers face similar tariff-related cost increases, playing them off against each other gets harder. If AWS, Azure, and Google Cloud are all passing through similar costs, the answer to "where do we go?" gets shorter.
Right, practical bit. If you're a CTO, IT director, or managing partner at a mid-market B2B service firm, here's where I'd start.
Get your US cloud exposure in one place. Most firms I speak to can't produce a complete picture of their US-hosted spend in under a day. It's spread across hosting, CMS licensing, CRM, email platforms, collaboration tools, security products, and half a dozen SaaS subscriptions that individual teams signed up for independently. Include anything hosted on US infrastructure, regardless of where the vendor is headquartered - a UK SaaS company running on AWS US-East is still US-hosted.
Read your renewal terms before you need to. Look for clauses that allow "market adjustment" pricing, pass-through of regulatory costs, or unilateral price changes with 30-day notice. These are the mechanisms through which tariff costs arrive. If you've got renewals coming up in the next six months, start the conversation with your vendor now. Not when the invoice lands.
Don't assume UK and EU alternatives aren't viable. I'm not suggesting you rip out Azure tomorrow. But for some services - particularly CMS and hosting - there are credible options that reduce your exposure. We've been helping firms evaluate this as part of broader platform reviews. In a few cases, the tariff conversation has tipped the business case in favour of a move that was already marginal on other grounds. The cost of standing still on legacy platforms was already a problem before any of this - tariffs just add another dimension that most firms haven't factored in yet.
Build hosting geography into future platform decisions. If you're about to make a technology investment - a new CMS, a CRM migration, a cloud infrastructure decision - "where is this hosted, and what's our exposure if US trade policy shifts further?" is now a legitimate question that belongs in the evaluation criteria. Twelve months ago it would have been an edge case. It isn't any more.
The firms that come out of this well won't be the ones who reacted fastest. They'll be the ones who did the audit early, had the renewal conversation from a position of knowledge rather than panic, and made a couple of marginal platform decisions differently because they'd actually thought it through.
Most haven't done that yet. Which means there's still time to be ahead of it rather than behind it.
Tariffs are one input into a broader question worth revisiting: what does your total cost of platform ownership actually look like, and is the architecture you chose three or five years ago still the right one?
If tariff changes are making you think about platform costs more seriously, there's a framework we use for assessing total cost of ownership that covers not just hosting and licensing, but the maintenance burden, the integration complexity, and the opportunity cost of being on a platform that limits what you can do next. Tariffs are the latest addition to that equation, but they're rarely the only cost that's been quietly compounding.
And if you're heading into a board conversation about digital investment or a platform review in the next quarter, that kind of analysis is what turns "we need to spend money on technology" into something the finance director can actually engage with. Worth reading alongside this, particularly if tariff exposure gives you the urgency to have a conversation that's been sitting on the backburner for a while.
The IT director I mentioned at the start - the one with the 11% renewal notice - ended up using it as the trigger to do a proper platform review he'd been putting off for two years. Sometimes the annoying invoice is the useful one.