CASE 10
8 weeks
Multi-Tenant Billing Portal for a SaaS Startup
Billing stopped being an existential risk.
- Next.js
- Postgres
- Stripe
- Redis
THE PROBLEM
Homegrown billing was breaking in subtle, expensive ways: missed dunning, manual invoices, proration mistakes, and no self-service for customers.
WHAT WE DID
- 01
Replaced the custom billing with a Stripe-backed engine — subscriptions, usage metering, proration handled correctly.
- 02
Customer self-service portal: update card, download invoices, upgrade/downgrade plans without emailing support.
- 03
Usage metering piped into Stripe from their event stream so invoices are always right.
- 04
Dunning and retry schedules tuned against their historical churn data.
OUTCOME
Zero manual invoices. Revenue reporting matches the ledger for the first time. The founder can reason about churn instead of worrying about billing bugs.