AI companies should own their metering, not the billing stack

The author argues that "billing" bundles distinct jobs—usage metering, pricing, balances, invoicing, revenue recognition, and contracting—and that AI companies should own the customer-facing fast loop (event collection, aggregation, pricing, and balance pools) while buying specialist software for invoicing and revenue recognition. End-to-end billing vendors often require customers to run their own collection infrastructure, manage enterprise agreements in parallel systems, and rely on spreadsheets for ASC 606 revenue recognition, and replacing one outgrown component can force changes across a monolithic stack. The recommended architecture connects metering and back-office systems through a single shared model of commercial agreements owned by the back office.