Getting an oversized cloud bill under control

A software company's cloud bill grew faster than its customers. Cleaning up comes first; long-term discounts come only after, and only for the steady part.

1 min readMade-up stories, not client work

Cost Optimization: story 13 of 15

A made-up story

Picture a software company whose cloud bill doubled in a year while customers grew far less. Nobody is sure what half of the resources are 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 they have today

  • Many servers, some forgotten
  • Test copies running all night and weekend
  • Old backups and logs kept forever

What we can't ignore

  • The live product can't be disturbed
  • The team is busy
  • Finance wants a predictable bill

The choices

  • Not for them

    Sign a big commitment now

    Locks in today's waste for years.

  • Our pick

    Clean up and resize, then commit to the steady part

    Pay only for what's used, then lock in a discount on what's left.

  • Maybe later

    Move to a cheaper provider

    Worth pricing once the real need is clear.

What we'd do

Label every resource by product and purpose so spending is visible. Remove forgotten servers and old backups, set rules for how long logs are kept, resize servers to what they actually use, and switch test copies off at night. After a few stable months, commit only to the steady base.

Why

  • Waste goes first, before any commitment
  • Labels make the bill explainable
  • Discounts apply only to what's really needed

Where the money really goes

No prices here: this shows where the costs sit, not what they'd be for any real business.

The clean-up costs some engineering time. The savings come back every month, and the discount on the steady base comes on top.

Engineering time
A few weeks of careful clean-up.
Monthly bill
Lower once waste is gone.
Commitment
A discount on the steady base only.

Running, growing, and staying safe

If something breaks

Changes are made carefully, starting with test copies, so the live product isn't affected.

When it grows

Commitments cover the steady base, and growth is paid for as it comes.

Keeping it safe

Removing forgotten servers also removes forgotten ways in.

What the business gets

  • A bill finance can predict
  • No paying for forgotten resources
  • A clear picture of where money goes

These are the kinds of results the approach aims for, not measured results.

When we'd look again

Once the steady base is clear, we'd price the same setup with other providers to confirm the current one still fits.

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: Managed database or self-managed: a total cost comparison

Running a database yourself looks cheaper on the invoice. Counting updates, backups and the expertise to run them usually reverses the answer.

Read the next story