Tailscale · Strategy · Mid · 45 to 60 minutes

Should advanced SSO stay paid only?

Tailscale is a networking software company that lets people and teams securely connect devices, services, and networks through a private mesh VPN. Answer this product management case and get it graded line by line against a weighted rubric.

pricing strategy
product judgment
analytical thinking
stakeholder management
written communication

The situation

You are the PM responsible for admin and identity packaging at Tailscale. Last year, the company limited support for some advanced single sign on providers to paid plans, while simpler sign in options remained more broadly available. As the team prepares for a pricing review, leaders want to revisit whether that packaging still makes sense. The question is contentious. Finance likes the current setup because identity related controls can help justify paid upgrades. Sales says some prospects expect broader provider support during evaluation, but the issue appears to affect a relatively small share of accounts. Security and support teams report that identity setup can shape how safely and confidently teams adopt the product, yet they also want to avoid turning every admin feature into a free entitlement. Assume the directly affected group is low single digit as a share of workspaces, but the accounts involved include both new teams deciding whether to adopt Tailscale and existing customers choosing plans. Your GM asks you for a recommendation on whether to keep, relax, or remove this packaging boundary, and how to judge the tradeoffs.

What to produce

Write a 1 to 2 page strategy memo for the GM with your recommendation on packaging advanced SSO provider support.

Your answer must

State a clear recommendation, keep, relax, or remove the current packaging boundary, and name one credible alternative you did not choose.
Identify the main user or customer segments affected, and size the impact with explicit assumptions rather than unsupported facts.
Analyze tradeoffs across at least four dimensions: revenue or conversion, customer trust or security posture, sales or evaluation friction, and product or support complexity.
Propose success metrics and leading indicators to evaluate the decision over the next two quarters.
Include a rollout and communication plan for both customers and internal teams.

Constraints

Do not assume new authentication technology, major engineering work, or a net new product line this quarter.
Keep the pricing change simple enough to explain on the pricing page and in sales conversations.
Use only the context provided here plus clearly labeled assumptions, do not rely on outside market data or exact competitor claims.

Format

Use short sections: decision, assumptions, customer impact, tradeoffs, metrics, risks, and rollout.

How Tailscale actually played it

Tailscale explains why it reversed a pricing decision from a year earlier that put advanced single sign-on providers on paid tiers only. The change affected few customers, but the team explains the identity and security reasons that made the paywall wrong for them. A real example of undoing a packaging choice, with the rationale and the size of the impact stated.

Revisit packaging decisions and be willing to reverse them.
Size the affected group before and after a change (small here) and still explain why it matters.
Do not gate security basics behind higher tiers when they affect customers' safety.
Explain the domain background so customers understand the decision.

Built from Goodbye SSO tax: how Tailscale made SSO free for everyone by Charlotte Brandhorst-Satzkorn, Tailscale.