Cloud Cost Optimisation (FinOps)

A cloud bill you can read and explain: billing data you can query, tags and owners on every pound spent, budgets and anomaly alerts, waste sweeps, right-sizing, commitment decisions and unit costs that teams own.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Cloud Cost Optimisation (FinOps), and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Cloud Cost Optimisation (FinOps)

Understanding and reducing cloud bills through right-sizing, reserved capacity, cleaning up waste and making teams accountable for their spend.

  1. Billing data export to a queryable store
  2. First line-by-line read of the cloud bill
  3. Budget alerts on every billing account
  4. Cost allocation tagging standard
  5. Cloud accounts mapped to owning teams
  6. Unit cost metric for the main product
  7. Spend anomaly detection with sensible thresholds
  8. FinOps roles and a cost owner in every team
  9. Inventory of commitments, credits and discounts
  10. Weekly cost anomaly triage
  11. Monthly cost review with team owners
  12. Idle and orphaned resource sweep
  13. Quarterly compute right-sizing review
  14. Commitment coverage and utilisation tracking
  15. Monthly showback reports to engineering teams
  16. Off-hours schedules for non-production environments
  17. Tag compliance scorecard by team
  18. Quarterly cloud spend forecast and reforecast
  19. Cost estimates in design and pull request review
  20. Pricing models of your five biggest services
  21. FinOps framework phases and capabilities
  22. Data transfer and egress charges explained
  23. Storage classes and retrieval costs
  24. Spot and preemptible capacity basics
  25. Querying billing data with SQL
  26. Kubernetes cost allocation by namespace
  27. Savings plan or reserved capacity purchase
  28. Lifecycle rules on the ten largest buckets
  29. Moving a batch workload to spot capacity
  30. Log and metrics ingestion cost reduction
  31. Cross-zone and NAT gateway traffic reduction
  32. Managed database cost review
  33. Processor architecture switch for compute savings
  34. Multi-cloud billing normalised to one schema
  35. Commitment expiry and renewal calendar
  36. Committed spend or enterprise discount negotiation
  37. Pre-launch cost estimate for a new product
  38. Annual cloud budget submission
  39. Startup credit expiry plan
  40. Founder's cloud bill on a seed budget
  41. Cloud cost briefing for finance and leadership
  42. Cost ownership of your own service
  43. Cloud cost due diligence before fundraising
  44. Inherited cloud estate cost clean-up
  45. Six-week cost reduction sprint
  46. Cloud cost of goods sold model
  47. Per-customer cost attribution for multi-tenant systems
  48. Automated waste removal policies
  49. GPU and accelerator spend governance
  50. FinOps maturity review and next-year plan

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Billing data export to a queryable store

This is a team plan, best installed into a shared workspace so everyone with a role in it can see and own their tasks. Console cost charts are fine for a glance but useless for answering who spent what and why.

First tasks

  • List every billing account and who holds the payer or billing admin role
  • Switch on the detailed cost and usage export with resource IDs included
  • Load the export into a warehouse or query engine table
  • Reconcile last month's export total against the invoice

First line-by-line read of the cloud bill

Most teams cannot say which five services make up most of their bill, so they argue about the wrong things. Spending one sitting with last month's invoice, ranking services by cost and naming what drives each one, gives you a shared picture and usually surfaces a surprise or two worth chasing.

First tasks

  • Open last month's invoice and the cost explorer side by side
  • Rank services by cost and note each one's share of the total
  • Break the top five down by usage type and region
  • Write a one-page summary and send it to whoever approves the bill

Budget alerts on every billing account

One runaway job or a leaked access key can spend a month's budget in a weekend, and without alerts the first anyone hears of it is the invoice. Setting forecast and actual budget alerts on every account, routed to a channel people actually read, is the cheapest safety net in cloud finance and takes under an hour.

First tasks

  • Set a monthly budget figure for each billing account from last quarter's average
  • Create alerts at 50, 80 and 100 percent of actual and one on forecast
  • Route alerts to the team channel and a named owner
  • Lower one threshold briefly to confirm an alert arrives

Make it yours.

Install Cloud Cost Optimisation (FinOps), then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.