
Frameworks, core principles and top case studies for SaaS pricing, learnt and refined over 28+ years of SaaS-monetization experience.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

The most instructive case study in Monetization Engineering is OpenAI itself, not because every company will operate at OpenAI's scale, but because OpenAI's journey from manual billing to automated monetization infrastructure illustrates the exact progression that every company building agentic AI products will go through, compressed into an extraordinarily short timeframe.
In 2021, OpenAI had a homegrown billing system that ran on custom scripts and manual labor for tracking usage and invoicing customers. Lauren Workman, Senior Manager of Revenue Operations, described the experience:
"I've been part of OpenAI's commercial operations from the beginning. I experienced firsthand how painfully manual it was to change pricing and add in new products."
Evan Morikawa, who leads OpenAI's Applied Engineering team, put it more bluntly:
"We didn't have the flexibility and customization to support usage-based pricing or enterprise contract complexity."
OpenAI adopted Metronome, a usage-based billing platform founded by Scott Woody and Kevin Liu, both former Dropbox engineers who had watched seventy to eighty Dropbox engineers spend months manually changing billing code. The integration was remarkably fast. OpenAI was in production with Metronome in less than two weeks:
"Metronome was the obvious choice. We were already streaming events into our database, and we could tilt the firehose to Metronome and have it automagically work."
This is the Vendor Fallacy resolved correctly, and it is worth being precise about why it is not a contradiction. OpenAI did not buy a finished revenue engine. It bought a metering and billing primitive and connected it to a usage pipeline it had already built, the firehose of events streaming into its own database. The integration was fast precisely because OpenAI had done the hard architectural work of instrumenting its product first. The buy was the easy part. The build came before it.
The result was that OpenAI could operate with fewer than ten engineers on billing at a scale that would have required seventy to eighty at Dropbox's previous level of infrastructure maturity.
Join companies like Zoom, DocuSign, and Twilio using our systematic pricing approach to increase revenue by 12-40% year-over-year.