How much should I price my API Key Management feature?
We’ve just released an API Key Management feature set for our Billing SaaS (including API roles, permissions, and expiration).
We're currently debating how much this enterprise add-on should cost, and we’d love to get some insights from the community! :)
Should it be packaged as an "enterprise security" feature?
Should we go with usage-based pricing?
Or set different prices for each part of the feature set (similar to how WorkOS handles pricing)?
Thanks in advance for your input!
3 comments
[ 3.4 ms ] story [ 17.3 ms ] threadA straightforward pricing approach could split between small teams and enterprises, with usage limits and per-unit pricing over those limits. This way you could capture the nuance between small teams with simple API key vs. enterprises with different products requiring granular permissions.
I wouldn't go with usage-based pricing from the start as you probably will not have proper numbers from the start to base how to price it, especially if serving customers with different sizes.
Ultimately the best structure will depend on the needs and patterns of your existing users.