1. TL;DR & Definition
Feature Gating is a monetization strategy where specific functionalities of a SaaS platform are restricted to higher-tier pricing plans. While initially used to differentiate premium value (e.g., advanced analytics), aggressive feature gating involves locking essential, foundational features—like SSO (Single Sign-On), basic data exports, or role-based access control (RBAC)—behind expensive enterprise tiers, forcing growing companies to upgrade merely to maintain basic security and operability.
2. The Dark Mechanism
The underlying mechanism is dependency exploitation. A SaaS product enters an organization at a low tier via product-led growth (PLG). Teams build their workflows around the tool. As the adopting company scales, its requirements shift from mere utility to governance, security, and compliance.
At this exact point of high switching cost, the vendor gates the solutions to these new requirements. By categorizing standard security protocols (like SAML/SSO) as "Enterprise Features," the vendor effectively imposes a tax on the client's growth. The customer is not paying for more value or better software; they are paying a ransom to secure the workflows they have already built.
3. SaaS Teardown
Consider a rapidly growing mid-market company using a popular project management SaaS. They started on the "$10/user/month" Pro plan, which works perfectly for a team of 30. As they hit 150 employees, their IT department mandates Single Sign-On (SSO) across all applications for compliance and offboarding security.
The SaaS vendor offers SSO, but only on the "Enterprise" tier, which costs "$40/user/month" and requires an annual contract for a minimum of 200 seats. The SaaS platform hasn't provided 4x the value; it simply recognized that the client's switching costs (migrating 150 users to a new platform) are higher than the cost of the forced upgrade. This "SSO Tax" is one of the most widely debated forms of hostile feature gating in B2B software.
4. Execution & Decision Matrix
| Feature Gated | Justification (Vendor) | Reality (Customer) | Impact on Buyer |
|---|---|---|---|
| SSO / SAML | "Enterprise security requires enterprise support." | Basic security is a fundamental requirement, not a luxury. | Forced 3x-10x price increase. |
| Data Exports (CSV/API) | "High server load." | Holding customer data hostage to prevent churn. | Lock-in; inability to migrate. |
| Role-Based Access (RBAC) | "Advanced administrative control." | Necessary for any team larger than 5 people. | Operational chaos or forced upgrade. |
| Audit Logs | "Compliance requires premium storage." | Essential for debugging and basic security forensics. | Blind spots in IT security. |
5. The Backfire Risk
Aggressive feature gating, particularly around security and data ownership, generates immense buyer resentment. When a vendor taxes security (the SSO Tax), they signal to the market that they do not view security as a baseline right. This leads to the rise of disruptors who offer these features out-of-the-box. Furthermore, procurement teams are becoming increasingly savvy; they now evaluate "Time-to-Enterprise-Tier" during the initial purchase. If a tool is perceived as a Trojan horse that will extort the company upon scaling, IT will block the adoption at the ground level, neutralizing the vendor's PLG motion entirely.