One of the most crucial—and often overlooked decisions when introducing a new feature is how to gate its access. If you get it wrong you could be losing out on revenue. Here’s a straightforward framework to guide your decision-making. 1 / Usage-Based Gating - use this when the feature is complex, hard to explain and has a cost associated to the business OR it’s new to the market or product category. Example: Minutes available in the Free zoom call 2 / Availability-Based Gating: use when the feature is simple, visually intuitive, or an industry standard. Example: SSO functionality 3 / Depth of Capabilities Gating - use when the feature is core to the end user’s workflow but a portion of the feature is used more heavily by your higher value users. Example: What actions you can do once you integrate an app with Grammarly The Bottom Line: - If it’s clear and familiar, use availability. - If it’s complex or costly, focus on usage. - If it’s building on having a strong foundational understanding, focus on depth of capabilities. What else would you consider when figuring out how to gate it?
Use Statsig 😉 😉
Founder @Supra | Helping product leaders accelerate their careers through peer learning and community | Ex-Asana
1dValu-based gating is also a powerful tool