Cloud that fits the business, not the brochure

Three made-up stories about where to host, how to stay up, and how to stop overpaying. Not client projects.

4 min readMade-up stories, not client work

Story 1 of 3

Where to host a growing online store

The short version: Pay someone to run the boring parts so you can sell.

An application in a cloud, looked after by a provider, with a small team relaxed below it.

Picture an online shop selling outdoor gear. It runs on a self-hosted store with dozens of plugins, looked after by one part-time freelancer.

What's going wrong

The site slows down on busy days, plugin updates break things, and the freelancer spends more time fixing the server than improving the shop.

What we'd do

  1. Watch the busy daysWhere the store slows down, what breaks, and what it costs in lost orders.
  2. Compare real choicesA bigger server, a cloud rebuild, a fully hosted store platform, or a custom build.
  3. Ask who keeps it safeServers, security updates and card payments all need an owner.
  4. Move what customers useRebuild only the features shoppers rely on, and swap most plugins for built-in tools.

How we'd know it worked

  • The store stays quick on its busiest day
  • The freelancer's hours go into the shop, not repairs
The catch
A hosted platform charges a monthly plan and small fees per sale, which can look higher than server rent. Counting repair hours and lost orders, it usually comes out ahead.
What the business gets
A store that stays up when it matters, and fewer things to break.
Story 2: Removing the one server that can take you down

Story 2 of 3

Removing the one server that can take you down

The short version: Fix the one thing that can take you down, not everything at once.

Two servers share the load behind a simple switch, so if one stops the other carries on.

A small software company runs its whole product on one server. A large customer wants to sign, but first asks what happens if that server fails.

What's going wrong

Honestly, everything stops. An adviser suggests rebuilding the product as many small services on a complex platform.

What we'd do

  1. Find the real riskOne server holding the app, the database and the background jobs.
  2. Fix that, not everythingTwo app servers that share the work, and a managed database with a standby copy.
  3. Write it down as codeSo the setup can be rebuilt the same way every time.
  4. Test a failureSwitch a server off on purpose and check the product carries on.

How we'd know it worked

  • The product keeps running when one server is switched off
  • The customer gets a straight, tested answer
The catch
Two servers and a managed database cost more each month than one server. The rewrite would cost far more in time, and losing the deal would cost more still.
What the business gets
No single box that can take the product down, and no pause on new features.
Story 3: A cloud bill that grew faster than the business

Story 3 of 3

A cloud bill that grew faster than the business

The short version: Clean the house before you sign a long lease.

A receipt for the cloud bill on one side of a scale, and the people and contracts it takes to run it on the other.

A software company's cloud bill doubled in a year while customers grew far less. Nobody is sure what half of it pays for.

What's going wrong

A sales rep offers a big discount for a multi-year commitment. Signing now would lock in paying for the waste.

What we'd do

  1. Label everythingEvery resource tagged by product and purpose, so the bill can be explained.
  2. Clear out the forgottenOld servers, old backups and logs kept forever.
  3. Resize to real useServers sized to what they actually do, and test copies switched off at night.
  4. Then commit, carefullyAfter a few steady months, take a discount only on the steady base.

How we'd know it worked

  • Finance can explain every line of the bill
  • Commitments cover only what's really used
The catch
The clean-up takes some engineering time, done carefully so the live product isn't disturbed. The savings come back every month.
What the business gets
A bill finance can predict, and no paying for forgotten resources.

Want more detail?

Fifteen longer stories about hosting, moving systems, staying up, busy days and cost, each comparing the choices side by side.

See all 15 cloud examples

What all 3 stories have in common

Understand it first. Keep it simple. Count every cost.

The technology is the last thing we choose, not the first. A smaller cloud bill isn't a saving if running the new setup costs more in people and contracts.

  1. 1

    Understand it first

    What the business does, how busy it gets, and who will look after it.

  2. 2

    Keep it simple

    The tools big tech companies use solve problems most businesses don't have.

  3. 3

    Count every cost

    Not just the bill. The people, contracts, upkeep and risk that come with it.

  4. 4

    Pick what your team can run

    A managed service can beat cheaper hosting that needs expensive specialists.

Most cloud problems are solved by doing less, more carefully. The right answer is the one your team can run on a normal Tuesday.

What we count before recommending anything

  • Hosting fees
  • Software subscriptions
  • Updates and upkeep
  • Someone watching for problems
  • Backups and test restores
  • Security tools and reviews
  • Staff time and training
  • Support contracts
  • The cost of complexity itself

If you liked this, read

About these stories. These stories are made up to show how we think. They are not client projects, describe no real business, and contain no measured results.

Next: Software that earns its keep: build what customers need first

Two short stories: launching something new, and fixing what already runs the business. Made-up examples of how we think, not client projects.

Read the next story