BILLING TRANSFORMATION
The Argument
One argument in three acts — diagnosis, destination, and plan. Why the billing platform has structural problems, what it looks like when they're fixed, and how we get there.
The billing platform today — three areas, five shared data stores, Stripe models leaking into domain logic. 196 rollbacks/day. 691 disagreeing accounts. 19% invoice coverage. The structural flaw named and evidenced.
Provider-agnostic models, centralized customer state, sovereign invoicing, and a policy engine for dunning. Stripe becomes one provider among many. Not a rewrite — a rotation.
Four work streams, one timeline, clear dependencies. PDE, Dunning, Checkout, and Infrastructure — what's shipped, what's in flight, what's next, and the KPI trajectories that prove progress.
- 196 → ~0
- rollbacks / day
- 691 → ~0
- disagreeing accounts
- 19% → 100%
- invoice coverage
Every failure mode traces to one decision: internal models mirror Stripe's models. PayPal is the existence proof — shimmed into a Stripe-shaped world, it takes the wrong path at every seam. The current work inverts the ordering, fixes the observability, and consolidates the code paths. What comes next is owning the domain.
Three acts. One structural flaw. The system has known problems, a clear destination, and a concrete path between them.