#Kirk-price-modeling
lone stone
You can adjust pricing by usage or quantity, so in this case you'd use usage. Here's a good doc on what that might look like from a technical perspective: https://stripe.com/docs/products-prices/pricing-models#tiered-pricing
brittle elm
It seems like usage based billing is only achievable for retroactive billing.
Customer John Doe uses the application for January, and on February 1st I can send an invoice for the usage during January's billing cycle
Is there any way to handle this scenario when I am charging for a year's worth of usage up front at the agreed upon rate, and only upgrade price on demand when the customer exceeds the agreed upon limits?
lone stone
Ahhh, that's a good question. I believe the resolution that works best here is simply to track their usage on your side and do a standard Subscription upgrade without using our metered product: https://stripe.com/docs/billing/subscriptions/upgrade-downgrade
That allows you to adjust proration behavior and fine-tune a lot of the nuances of the billing problem-space
brittle elm
Yes, this looks like exactly what I'll need to do. Thanks for your help!