Working · 2026-04AnecdotalRevenuePricing

Gate enterprise needs, not core value

Reserve compliance and admin features (SSO, audit logs) for upper tiers; keep the features that deliver first value available early.

Also called: Gate enterprise needs, not core value

Claim and evidence

The claimCutting the SSO tax is an important security win here, and we'd like to see more companies follow suit.

Tailscale · tailscale.com · 2024-04-18

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Entry: core value openTeam: collaborationand scaleEnterprise: admin andcompliance
Entry: corevalue openTeam:collaborationand scaleEnterprise:admin andcompliance

Early gating of core value breeds resentment and stalls adoption; gating what only larger buyers need captures willingness to pay without choking activation.

How to run it

  1. List features by who needs them
  2. Keep value-delivering features open on entry plans
  3. Gate admin and security at upper tiers
  4. Review gates after each packaging change

Before / after

Before
Plans
Starter
Team
Enterprise
Core workflow: Enterprise only
Audit logs: Enterprise only
Core feature locked behind the top plan
After
Plans
Starter
Team
Enterprise
Core workflow: every plan
Single sign-on: every plan
Audit logs: Enterprise
Core open, admin needs on top

Generalised wireframe of the pattern, not a copy of any company's screen.

Ways to run it

Design options to test, not promised results.

  1. Option ASort features by who needs them

    List each feature next to the buyer who needs it and keep first-value features on entry plans.

  2. Option BBasic security everywhere

    Offer sign-in security such as SSO on every plan and keep provisioning and audit features for the top tier, as Tailscale did.

  3. Option CReview gates after repackaging

    Re-check which features sit behind which plan after every packaging change.

Timeline

  1. 12024 Tailscale — Dropped the plan gate on 'advanced' identity providers so SSO login works on every plan, after deciding SSO is basic security rather than an enterprise extra; it still frames flow logs, user/group provisioning and advanced roles as enterprise features.
  2. 22026-04 status checked: Working

Dated examples

  1. 2024

    Tailscale

    Dropped the plan gate on 'advanced' identity providers so SSO login works on every plan, after deciding SSO is basic security rather than an enterprise extra; it still frames flow logs, user/group provisioning and advanced roles as enterprise features.

    Change approved within a couple of weeks of spotting the issue; no metrics shared.

    “Cutting the SSO tax is an important security win here, and we'd like to see more companies follow suit.”
    ✓ quote checked word-for-word on the page

    tailscale.com · 2024-04-18

Does it still work?

Workingas of 2026-04

Guidance from Stripe's 2026 packaging guide; no quantified effect. source

Risks

  • Security gates draw public criticism (see SSO tax)
  • Gate set too low suppresses expansion; too high suppresses adoption

Sources

  1. stripe.com · Stripe Resources · 2026-04-07
    “Don't gate features that drive the product's core value early in adoption.”
    ✓ quote checked word-for-word on the page
  2. tailscale.com · Tailscale blog · Charlotte Brandhorst-Satzkorn · 2024-04-18
    “The core issue with this tax is that it turns basic security into a budgetary question”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — merged: pass2-enrich.jsonl:5 (gate-enterprise-features-not-core-value); revenue-expansion.jsonl:12 (gate-enterprise-features-not-core-value)
  • 2026-11-20 — harvest v0.1 (pass2-enrich, revenue-expansion)