$1,097
Saved since February 2026
Tracked all-time savings visible in the dashboard after rollout began.
Anonymized case study
How a startup turned AWS waste into an owned cleanup queue
Across an anonymized rollout covering 2 connected AWS accounts, OpsCurb tracked $1,097 in savings since February 2026, recorded 138 resolved findings, and still showed about $618 per month of additional upside across 387 actionable findings.
The account set was run by a founder-led startup platform team spending about $5,000 per month on AWS. The screenshot reflects the live dashboard state after rollout began in February 2026.
The working review still centered on a short queue leadership and engineering could both read: tracked savings, visible ownership gaps, and enough evidence to move changes into review.
Real redacted product screens2 connected AWS accountsAction, owner, follow-through
Redacted live screenshot
138
Resolved findings
Findings already fixed and counted in tracked savings recovery.
~$618/mo
Current monthly upside
Approximate recurring savings still visible in the active queue.
387
Actionable findings
Live items still being worked, validated, assigned, or scheduled.
What changed
The team moved from “we should look at this” to “who owns the next step?”
The difference was not another visibility layer. The difference was turning visible savings into a believable working queue leadership and engineering could both read.
The rollout started in February 2026 and covered 2 connected AWS accounts in a founder-led startup account set spending about $5,000 per month on AWS.
By the dashboard snapshot, OpsCurb had recorded $1,097 in all-time savings and 138 resolved findings.
The remaining queue still showed about $618 per month, or roughly $7,418 annually, across active cost and hygiene work.
The open items were mainly idle compute or storage cleanup, retention and snapshot policy tightening, and other low-risk optimization tasks that still needed validation or scheduling.
Operationally, "still open" meant the finding remained visible until an owner picked it up, validated the change, or placed it into a planned change window rather than letting it disappear after the first pass.
Redacted live screenshot
Redacted live screenshot
Why it converted
Enough evidence to act, without pretending cleanup is risk-free
Teams move faster when the recommendation is concrete but still respects production risk. That is why this workflow worked: it kept validation and handoff in the same motion.
- Start with the highest-confidence findings leadership and engineering can both approve quickly.
- Separate tracked savings already recovered from the remaining monthly and annual upside still in the queue.
- Keep actionable findings visible until they are resolved, assigned, deferred, or intentionally ignored.
Use the proof
Use this case study to see what a first successful rollout actually looks like
Use this as buyer proof for what good looks like: tracked savings on the dashboard, a visible queue of remaining work, and findings that stay open until someone owns the next step.