This is spot on. And if it seems daunting to implement monetization that can do all of this seemlessly/frictionless then you need better monetization infrastructure.
The classic subscription vs. usage based argument is starting up again on hacker news. My take? At least for developers.... If you're selling a utility or tool that people use consistently outside of infrastructure, you've got a subscription product. (Developer productivity, hiring tests, etc) If you want people to adopt your tool as infrastructure in production code, you need to start with usage based. (CI/CD tools, Logging, etc) Here's the catch--If you "make it big" and make it into true production infrastructure within a company at scale, procurement/finance are going to want predictability and a monthly/annual line item, so you become a subscription again. That's showbiz baby. *Jazzhands*