This is a sample day-30 proof packet for a fictional 30-day managed savings pilot.
Day-30 proof packetManaged Savings Pilot
$7,600
finance-approved monthly savings
3.0x
first-month proof ROI
The pilot closes with accepted proof, explicit exclusions, and a continue/no-go decision.
CloudCostIQ separates finance-approved savings from regressed, excluded, and customer-blocked work before asking for renewal or outcome pricing.
Pilot fee
$5,000
Savings identified
$18,400/mo
Savings implemented
$9,800/mo
Finance-approved savings
$7,600/mo
Excluded or regressed
$3,200/mo
Customer-blocked
$5,400/mo
Savings action disposition
Non-production compute schedule
Owner: Platform
30-day billing comparison and scheduler change record
Monthly impact
$4,200/mo
Status
Finance approvedIdle storage cleanup
Owner: Infrastructure
Detached volume inventory, deletion ticket, next-bill reduction
Monthly impact
$3,400/mo
Status
Finance approvedSnapshot lifecycle policy
Owner: CloudCostIQ
Expected savings fell below materiality after workload returned
Monthly impact
$3,200/mo
Status
RegressedTag policy and allocation cleanup
Owner: Application team
Engineering approval pending; customer blocker clock active
Monthly impact
$5,400/mo
Status
Customer blockedDay-30 recommendation
Continue operator coverage, not outcome pricing yet.
Continue Cloud Savings Operator coverage for another 60 days.
Do not offer verified-savings success fee until customer blockers are below $2,500/mo.
Route tag policy work to engineering owner by Friday or mark the savings rejected.
Use $7,600/mo finance-approved savings as the renewal proof baseline.
Ready to scope your 30-day pilot?
Start with three low-risk categories, named owners, and a day-30 proof packet.