OutageCredit

Who it's for

Solo founders of paid AI SaaS apps built on OpenAI, Anthropic, or Google APIs; today they cope with provider status pages, Stripe dashboard refunds, and spreadsheet estimates.

The problem

payment: customers request refunds or credits during upstream outages, and founders over-credit or under-credit because they cannot tie incident windows to per-customer usage.

How to build it

Self-hosted proxy or SDK logs customer_id, provider, timestamp, status, and token/cost; dashboard polls provider status pages; exports Stripe CSV, customer email draft, and signed incident receipt.

How it makes money

Founders pay $29-$99/month because it reduces refund disputes and churn after outages; free status pages cannot calculate customer-level credits or produce Stripe-ready artifacts.

Why it doesn't exist yet

Incumbents skip it because status-page and uptime tools sell alerts rather than billing reconciliation, and payment processors do not know about provider incidents; the indie gap is a small bridge from incident windows to customer-level credit artifacts.

First users

Reply to HN threads about simultaneous OpenAI/Claude/Grok outages and offer a retroactive Sep 3 ChatGPT outage credit report; post in indie SaaS and founder communities.

Build size

1 person x 8 weeks; includes request-log ingest, status incident fetcher, credit rule engine, Stripe CSV export, dashboard, signed receipt; excludes real-time failover, non-Stripe billing reconciliation, and provider invoice reclaim.

Biggest risk

OpenRouter, LiteLLM, or another popular LLM gateway ships a native per-customer outage-credit ledger, or providers begin issuing automatic customer-facing SLA credits.

Conditions for a hit (all 3 required)

• Accepts a CSV or JSON request log with timestamp, customer_id, provider, response_status, and cost/tokens; flags records inside a selected incident window and outputs an affected-customer table for 1,000,000 rows in under 10 minutes.
• Given one credit rule, such as fixed amount per incident hour, percent of monthly plan fee, or credit per failed call, generates a Stripe CSV and plain-text customer email draft in under 5 minutes.
• Saves a signed incident receipt containing status-page HTML snapshot, incident start/end timestamps, and SHA-256 hash of the input log within 15 minutes of report creation.

How it's judged (in 6 months)

GitHub repository reaches 1,000 stars or Product Hunt daily top 5 for a tool matching these three features.(judgment date 2027-03-07)

AI self-confidence 52/100 — self-reported likelihood of meeting the criterion, not a business success rate