Building one record for every contract
45 minutes on event-sourced revenue: replay, lineage, and why your metrics never agree today.
A recorded working session on the model underneath the product: why revenue is stored as events rather than balances, and what that buys you when someone questions a number 9 months later.
What is covered
- Event sourcing for contracts, usage, invoices and payments
- Deriving metrics rather than storing them
- Replay: reconstructing any figure at any past date
- Lineage: tracing a dashboard number to its contract line
If you can only see the balance, you can only argue about the balance.
The session closes with the practical trade-offs, storage cost, replay time, and where a derived-metrics model genuinely is harder to operate than a conventional ledger.
See it in the product: ReportingARR, retention and receivables reports that tie to your invoices.
Related
Keep reading
From contract PDF to first invoice, live
Live demo: AI extraction, human approval, and the billing run that follows.
Anubhav Dubey
Usage-based billing explained: how it works and why SaaS is switching in 2026
Usage-based billing charges customers for what they actually consume. See how it works, why 38% of SaaS companies now use it, and how to adopt it without breaking finance.
Anubhav Dubey
AI token-based pricing: a practical guide to billing AI products and agents in 2026
Token-based pricing is now the default for AI products, but it breaks traditional billing and forecasting. Here's how token billing works, why costs are opaque, and how to price AI without losing margin.
Anubhav Dubey