FinOps has shifted from manual cost reviews to real-time, AI-driven decisions. Here's what changed in the last 24 months — and what FinOps teams actually do now.
Lakshmi Kiranmai Guduru
Founder, CARTIEAI
Two years ago, "FinOps" mostly meant a person with a spreadsheet, reconciling AWS/Azure/GCP invoices against budget every Monday morning. By Feb 2026, the role has fundamentally changed.
A FinOps engineer's day:
The cycle was weekly. The fastest possible response to a cost spike was ~5 business days.
A FinOps engineer's day now:
The cycle is continuous. Cost spikes are now caught within minutes.
In 2023, "your AWS bill" was a 30-day-old PDF. In 2026, it's a Slack message in your channel within 15 minutes of the spike. AWS, Azure, and GCP all now expose near-real-time billing APIs. The FinOps team's job shifted from collecting data to deciding what to do with it.
Five years ago, "this EC2 instance is over-provisioned" took a human engineer 2 hours to confirm. In 2026, an AI agent reads CloudWatch, BigQuery, query logs, and your code — and tells you exactly which instance, which file, and what the right size is. The agent ships the PR. The human reviews and merges.
In 2022, FinOps was "the cost spreadsheet person." In 2026, every senior engineer is expected to know basic cost math. CFOs read cloud bills directly. Product managers track $/active-user as a primary KPI. The FinOps "team" exists to set guardrails, build dashboards, and own the strategic forecast — not to chase down individual line items.
Based on conversations with FinOps leads at 30 mid-stage SaaS companies (Feb 2026):
| Owned | Not owned anymore |
|---|---|
| Unit economics ($/ARR, $/MAU) | Cost spreadsheet reconciliation |
| Budget guardrails & alerts | Manually emailing engineers about overages |
| Forecast vs. board commitments | Catching individual EC2 anomalies |
| Vendor negotiations & RIs/Savings Plans | Per-service cost reports |
| Cross-team chargeback frameworks | Reading provider invoices line-by-line |
The shared theme: strategy stays human, tactics get automated.
We built CARTIE because we think most "FinOps tools" in 2026 are still solving the 2022 problem: showing you yesterday's bill in a fancy dashboard.
The real problem is faster:
We call this loop D-D-F. Every CARTIE customer's first month focuses on this loop.
If you're hiring a FinOps engineer this year, look for:
If you're learning FinOps yourself in 2026, the highest-leverage thing you can do is read your own cloud bill end-to-end for one month. Most people never have. The skills compound from there.
If you want to see modern FinOps in action, run the free CARTIE audit — it'll surface the top 5 leaks in your cloud in 60 seconds.
Amazon Web Services is the largest cloud platform in the world — and the source of more than half of the cloud waste we audit. This guide gives you the 14 prove…
THE FINOPS BRIEF
Built for finance & engineering teams who are tired of paying for cloud they don't use. No fluff. Just what works.
Unsubscribe anytime. We never sell your data.
ABOUT THE AUTHOR
Founder, CARTIEAI · Building in public
I'm building CARTIEAI to fix the cloud-cost problem I saw drain millions at companies I worked for — where engineering and finance kept talking past each other. If you liked this post, here's where I share unfiltered notes on building this in public:
