Your Cloud Bill Is a Post-Mortem

By the time your cloud bill reaches you, every decision that caused it has already been made.

Ask a finance team what the company spent on cloud last month and you get one number. Ask the engineering team which service caused it and you get three browser tabs, two of which nobody has opened since the last audit. 🤷

Both answers are correct. Neither one is useful.

That gap is where cloud money quietly goes. Not in dramatic waste, and almost never in anything anyone would have called a mistake at the time. It goes in small, reasonable decisions that nobody connected to a number until the month had already closed.

🧾 An invoice is a record, not a control

A bill describes a month you can no longer change. You can read it, you can be unhappy about it, and you can resolve to do better next time. What you cannot do is spend it differently, because it is already spent.

So the question worth asking is not what did we spend. It is what are we spending, right now, and who is spending it. Those are different questions, and only the second one is answerable in time to matter. ⏰

🪟 Three consoles do not add up to one view

AWS, Azure and GCP each ship a cost view. Each is competent inside its own walls. None of them knows the other two exist.

If your estate sits on more than one of them, and most estates now do, somebody has to be the integration layer. In most organisations that somebody is a person with a spreadsheet 📊, once a month, under time pressure, working from three exports with three different ideas of what counts as a resource.

That person is doing real work. They are also the only place the full picture exists, which means the full picture is exactly as available as they are. It disappears when they take leave.

🏷️ A number with no name on it is not a finding

Compute is most of the bill. That sentence is true in almost every organisation and actionable in none of them.

A number only becomes useful when it carries a service, a team and a project. At that point it stops being a budget conversation and becomes an engineering conversation, which is the only kind that changes anything. Somebody can look at it and say that the staging cluster has been running at production size since March 😳, and nobody noticed, because nobody was ever looking at it next to its own cost.

Cost attribution is not an accounting nicety. It is what turns a number into a task. ✅

⏰ The alert has to arrive while the month is still running

There is a large difference between learning on day 9 that a budget is tracking 40 percent over, and learning on day 32 that it went 40 percent over.

The first is a decision. The second is a report. 📄

The same holds for anomalies. Spend that moves sharply with no release, no migration and no traffic event behind it is usually something you would switch off if you knew about it. The value is entirely in the timing. An anomaly you hear about four weeks later is just a line in a document.

👀 Finance and engineering have to read the same screen

The two sides usually look at cloud cost through different instruments, and then meet to reconcile them. Most of that meeting is spent agreeing on what the numbers mean rather than deciding anything.

One view both sides can read does not make the disagreement go away. It does mean the disagreement is about priorities instead of about data, which is a considerably better meeting to be in. 🤝

🛠️ What we built

MJ FinOps is our answer to this:

• ☁️ Connects AWS, Azure and GCP accounts in one place
• 🔎 Breaks cost and usage down by service, team and project
• 📊 Gives finance and engineering a shared dashboard, with reports on a schedule
• 🔔 Sends budget and anomaly alerts while the month can still be changed
• 🏢 Multi-tenant workspaces, so each team or client sees its own spend and nobody else's

It is built and running. It is not on self-serve signup yet, and we would rather say so than let you find out by clicking. We set it up with you, on your own accounts, so what you see on day one is your real spend rather than a demo dataset. 🙌

🔍 Four questions for your own estate

1. If someone asked today what you have spent so far this month, how long would the answer take, and who would have to produce it?
2. Can you attribute a cost line to a team or a project without opening a spreadsheet?
3. When a budget starts running over, do you find out during the month or in the invoice?
4. If the person who assembles the monthly cloud report left tomorrow, what would happen?

If any of those answers made you uncomfortable, the problem is not overspending. It is visibility, and visibility is fixable. 🔧

📅 Talk to us

MeJuvante runs cloud, AI and managed operations for clients across Europe and India, with teams in Linden, Germany and Bengaluru, India.

Book a 30-minute review. We will connect your first cloud account with you and show you your own numbers, broken down, before you decide anything.

Cloud cost, FinOps and advisory: mejuvante.ai/enquiry-1