Fifteen cloud decisions, choice by choice

Fifteen made-up stories about where to host, how to move, how to stay up, how to handle busy days, and how to stop overpaying. Each one shows the choices we'd weigh and the one we'd pick.

4 min readMade-up stories, not client work

What all fifteen stories have in common

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

Every story follows the same order. The technology is the last thing we choose, not the first.

  1. 1

    Understand it first

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

  2. 2

    Keep it simple

    Use only what the business needs. The fancy tools big tech companies use solve problems most businesses don't have.

  3. 3

    Compare real choices

    Two or three options side by side, including doing less, before picking one.

  4. 4

    Count every cost

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

  5. 5

    Pick what your team can run

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

  6. 6

    Grow when you need to

    Room for the next step, without paying today for capacity you may never use.

A smaller bill isn't always a saving

Illustrative figures: a 10% reduction in infrastructure costs is not a real saving if managing the new setup increases labor or vendor costs by 30%.

The hosting invoice is the easiest cost to see, and often not the biggest. The people, contracts and tools it takes to keep a system updated, watched, backed up and safe usually decide whether a choice really saves money. We put them all on the same page before recommending anything.

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