How many product IDs are sitting in your Stripe account right now, and does anyone actually own them?
In episode #394, Ben Murray tackles the product ID sprawl quietly undermining SaaS finance teams. Every SKU created in Stripe, Chargebee, or any billing system flows downstream into pricing, revenue recognition, sales tax, general ledger accounts, MRR schedules, and retention analysis. When anyone can spin up a new ID with no process behind it, your revenue data degrades, and the cleanup lands on finance at the worst possible moment: a system migration, a fundraise, or exit due diligence.
- Why ad hoc product ID creation in Stripe, Chargebee, or Salesforce creates havoc across RevRec, the GL, and your SaaS metrics
- The five downstream links every new SKU must get right: pricing, revenue recognition policy, sales tax treatment, revenue GL account, and MRR/retention reporting
- Who should own and approve your product catalog: finance, the CFO, product, and sales working together
- A real-world lesson from Ben's time as an internal SaaS CFO, when a systems migration exposed thousands of product IDs that had to be cleaned up
- Why a messy product catalog becomes a diligence problem when you raise capital or prepare for an exit
Tune in, then go audit your product ID catalog before your next fundraise or system migration forces you to.
Resources Mentioned