Anarock's small engineering team unified six AWS accounts under one cost lens, cut its monthly bill by roughly $28K, and got its time back from manual cost reporting.
Real estate services & proptech
~120 employees · one engineering team (~10 engineers), no dedicated FinOps role
6 AWS accounts spanning dev, staging, production, and data workloads
~$45K/month (~$540K/yr) before → ~$17K/month (~$204K/yr) after
Rapid growth meant AWS resources had been spun up as needs arose, spread across six accounts covering dev, staging, production, and data workloads. The monthly bill had climbed to roughly $45K — about $540K a year — with no consolidated view of where the money was going.
With no dedicated FinOps role, the platform lead owned the cloud bill on the side: cost data was split across six accounts with their own tags and billing quirks, the monthly check meant exporting Cost and Usage Reports into spreadsheets by hand, spend anomalies only surfaced once the invoice arrived — often two to four weeks after the spend happened — and with no per-project cost breakdown, idle and oversized resources went unnoticed for months. The breaking point: a single month's bill overran budget with no clear explanation, and leadership couldn't get a fast answer to "what changed, and what's driving it?"
All six AWS accounts were connected to Clouds Analytics in under a week, bringing the entire cloud footprint into a single cost lens.
Every account, environment, and service reports into one dashboard, with drill-down by account, environment, and service — replacing the manual spreadsheet check entirely.
Daily spend is watched automatically, with unusual days scored by severity against an expected baseline — surfacing prioritized alerts within hours of a cost shift instead of weeks.
Automated cost allocation showed which products and services were actually driving the bill — giving engineers a reason to right-size instances and retire idle resources on their own.
A few weeks after rollout, a high-severity anomaly flagged a misconfigured pipeline quietly adding roughly $8K/month to the bill — caught and shut down the same day it appeared, rather than surfacing weeks later on an invoice. Illustrative of the kind of issue multi-account visibility is designed to catch early.
| Initiative | Status | Impact |
|---|---|---|
| Multi-account visibility unified | Live | 6 accounts → 1 dashboard |
| Monthly AWS bill | Sustained | $45K → $17K (−62%) |
| Manual cost reporting time | Reduced | ~80% less time |
One dashboard across six accounts meant the team finally knew where the money was going, without a manual reconciliation step.
Severity-scored alerts meant the team investigated the days that actually mattered — not every minor wobble in spend.
Clear per-project cost visibility gave engineers a reason to right-size and retire idle resources on their own, without being asked.
Because the visibility was ongoing, savings didn't erode after the initial cleanup — cost stayed a daily signal, not a monthly surprise.