Usage-Based Pricing
Usage-Based Pricing
Stub page — auto-generated from wikilink references. Not yet written. Referenced in 3 wiki pages.
Where this appears
- Thinking This Through a Bit… (tweet)
- We Re-built Billing Systems 3x… (tweet)
- 🆕 Blog - Why Isn’t Usage… (tweet)
Saved from Roam
- Metronome
- Orb
- https://www.getoctane.io/
- Amberflo
- Emma Tang
An Apple Notes capture on this topic is held privately in the wiki.
Archived Links
Saved 2026-09-01. Bare URLs from the Apple Notes capture, archived so the citation survives the link.
Battery Ventures — “Consumption pricing models are here to stay”
Routed here by Kyle 2026-09-01 from an Apple Note titled “Usage based pricing.” He asked for a page called Consumption Based Pricing; this page already existed under the near-synonym Usage-Based Pricing, so the material was attached here and “Consumption Based Pricing” added as an alias rather than forking a duplicate (hard rule 8).
https://www.linkedin.com/posts/battery-ventures_consumption-pricing-models-are-here-to-stay-activity-7075489814988390400-zYwx — Battery Ventures, ~2023. 68 reactions · 8 reposts.
More and more software companies are developing an appetite for consumption-based pricing models — including early-stage startups.
Battery General Partner Dharmesh Thakker and Vice Presidents Jason Mendel and Danel Dayan unpack the pros and cons of consumption-based pricing — and how these sometimes-unpredictable pricing models may be affected in times of market uncertainty — in the latest post for our Condensing the Cloud Substack.
The framing worth keeping is in the caveat, not the headline. “Here to stay” is the marketing claim; “sometimes-unpredictable… in times of market uncertainty” is the real argument — consumption pricing transfers revenue volatility from the customer to the vendor, which is comfortable in growth and painful in a downturn. That is the trade the model actually makes, and it is why the same firms that championed it in 2021 were re-examining it by 2023.
⚠️ The linked Condensing the Cloud post sits behind an lnkd.in shortener (ghZi6KQE) that was not resolved in this pass. The Battery Substack is the better citation if this page gets written up.