Should I charge a subscription or charge per transaction for my product?
The short answer
Subscriptions win when customers get continuous, predictable value and you want smooth recurring revenue; per-transaction pricing wins when usage is spiky or the customer only feels the value at the moment of use. A useful test: would your customer resent paying in a month they barely used it? If yes, usage-based or per-transaction aligns you better, and many businesses eventually land on a hybrid (a small base fee plus usage).
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
🎧 Podcast
✓ Link checkedFreeIntermediate
Why we picked it
Madhavan Ramanujam has helped architect pricing for dozens of well-known companies, and here he walks through how real teams actually choose a value metric and a pricing structure. It covers the subscription versus usage question head-on (around the 1:03 mark) alongside willingness-to-pay and packaging. Useful for hearing how practitioners reason through the tradeoffs rather than reading a tidy summary.
Why we picked it
A16z boils the whole decision down to one honest rule of thumb: usage-based pricing tends to fit products whose main user is other software, while subscriptions tend to fit products with human users. It is short, opinionated, and gives you a lens to reason from instead of a list of pros and cons. Read it as a starting point for framing your own call, not a verdict.
Why we picked it
Before you agonize over subscription versus per-transaction, this piece shows the common middle path so you do not force yourself into a false binary. It walks through hybrid pricing (a base fee plus usage on top) with concrete examples like Twilio and Intercom. A grounding read for seeing that a fixed floor plus a usage layer is often the pragmatic answer.
