Skip to content
Alex Richards
Menu

Cloud that's built properly and costs what it should.

Architecture review, cost reduction and hands-on infrastructure work across AWS, Google Cloud, Microsoft Azure, Nebius, Scaleway and DigitalOcean. Independent of any one provider.

Book a call

Who this is for

The cloud bill has doubled since the platform was built and nobody can say exactly why. The person who set it up has moved on, and what’s left is a console full of things nobody dares switch off. Or you’re about to build something new and want it done properly from the first commit, not tidied up later.

You’re running on one of the big three, or on one of the smaller European providers because the pricing or the data residency suited you, and you don’t have an infrastructure team to keep it honest.

I ran the AWS platform at evaluagent, an AI software company, across the EU, US and Australia, with the bill and the uptime both on my desk. I’ve also built and operated workloads on Google Cloud, Microsoft Azure, Nebius, Scaleway and DigitalOcean, so the recommendation you get is based on what fits, not on what I happen to know.

What you get

Concrete outputs, not a slide deck.

  • Architecture and cost baselineWhat you're running, what it costs, where the risk is and where the waste is. One document, written for the person who signs the bill.
  • Savings plan with numbersEach change, what it saves per month, what it costs to do, and whether it carries any risk. In order, so you can stop at any point.
  • Hands-on implementationThe changes made, with your team or on my own, in code and under version control. Nothing done by hand in a console.
  • Cost governanceTagging, budgets, alerts and a monthly report. So the bill doesn't creep back up once I've gone.

How an engagement runs

A review and first round of savings typically runs six to eight weeks. Larger migrations are scoped separately once the baseline is done.

  1. Week 1BaselineRead-only access to billing and the accounts, interviews with whoever runs it, and a first look at the architecture.
  2. Weeks 2 to 3Quick winsIdle resources, over-sized instances and obvious discounts. Low-risk changes that show up on the next invoice.
  3. Weeks 4 to 8RestructureThe changes that need planning. Storage tiers, reserved capacity, consolidating environments, fixing the fragile parts.
  4. OngoingGovernA monthly look at the bill and the alerts, and a short report on what changed and why.

Typical cost

An architecture and cost baseline with a savings plan starts from £2,500 fixed price. Implementation is £800 to £1,000 a day or fixed per release.

Common questions

Which providers do you work with?
AWS, Google Cloud, Microsoft Azure, Nebius, Scaleway and DigitalOcean. Most of my production experience is on AWS, where I ran a multi-region platform for years, but I've built and run workloads on all six.
How much can we save?
It depends entirely on what you're running, and anyone who gives you a percentage before looking is guessing. The baseline in week one gives you a real number before you commit to anything further.
Will we have to move providers?
Almost never. Most savings come from using the provider you're on properly. I'll only recommend a move if the numbers clearly justify the disruption, and I'll show you the numbers.
What does it cost?
Fixed price for the baseline and savings plan. Implementation is a day rate or fixed per release, agreed before we start. Governance is a small monthly retainer if you want it.

Cloud bill grown past the point anyone can explain it?

Book a call. Thirty minutes and a look at last month's invoice is enough to tell you whether it's worth a proper review.

Book a call