Contingency-fee AWS billing recovery firm that combines automated anomaly detection with human escalation specialists who already have AWS enterprise support relationships
AWS support is deliberately designed to exhaust individual customers, so a specialist intermediary with leverage and aligned incentives has a structural advantage that a DIY tool never will
Built for AWS users with unexplained high charges.
No-win-no-fee model removes purchase friction while pre-existing AWS account rep relationships bypass the callback-bot wall that defeats self-service attempts
“AWS has been charging me $1,500/month for near-zero usage. For over a year. That is more than $18,000 for infrastructure I barely use. I tried multiple tim…”
💰 Willingness to pay, in their words
“AWS has been charging me $1,500/month for near-zero usage.”
“That is more than $18,000 for infrastructure I barely use.”
The receipts — real demand
“AWS has been charging me $1,500/month for near-zero usage. For over a year. That is more than $18,000 for infrastructure I barely use. I tried multiple times to get a human on the phone to discuss it. Every time I requested a callback, AWS would call, a bot would tell me the human wasn't available, and promise a callback. No human ever called back. So I stopped paying. Why keep paying charges I believe are …”
Others echoing it
“Stop payment isn't the same as a chargeback, though.”
“Contract law is rather a mess, but, IIRC, one the main, generic exceptions to contract clause enforcement is if is illegal, unconscionable, or violates public policy. Many states have codified tort laws as being in the interest of public po”
“I was just thinking about this. Their operations are so opaque that if they were refusing service to people with green eyes we wouldn't even know.”
Full dossier
Unlock the full dossier — free
Every corroborating quote, the source receipts, and the community echo. One email, no payment.
demand score 7.1 — the receipts are below
Why this is a gap
Surfaced from a high-intensity complaint with clear willingness to pay and a specific, reachable audience.
The market
AWS users experiencing unexplained high charges or billing anomalies. No search volume; demand signal is strong (user paid $18k over a year for near-zero usage) but likely concentrated among smaller teams without dedicated cloud finance roles.
Competition & the opening
CloudHealth, Apptio, Spot.io, ProsperOps, Trimble, and Pileus all monitor and optimize cloud spend. The specific gap is bill *dispute* and *recovery* (fighting AWS for refunds on overcharges), not just cost optimization—most competitors focus on rightsizing and forecasting, not retroactive audit and escalation.
What's hard to build
AWS billing data is complex and often opaque; you need to parse detailed Cost and Usage Reports, cross-reference with service limits and known billing bugs, and build a defensible case for dispute. AWS rarely admits errors without strong evidence; you'll need expertise in their billing systems and a track record of successful disputes to credibly advise customers on chargeback claims.
Why now
AWS billing opacity and support friction create sustained overcharge discovery lag; no incumbent offers end-to-end dispute + recovery (only cost optimization or diagnostics).
How you'd monetize
30–40% contingency fee on recovered overcharges (disputes won) or hybrid $500–2k