Tailscale · Strategy · Mid · 45 to 60 minutes

How should Tailscale reset pricing limits?

Tailscale is a service that lets people and teams securely connect their devices in a private network. Answer this product management case and get it graded line by line against a weighted rubric.

Pricing strategy
Segmentation
Data judgment
Tradeoff analysis
Go to market thinking

The situation

The VP of Product asks you to recommend changes to Tailscale's packaging and pricing for individual users and growing teams. Tailscale is seeing strong adoption, but the current plan structure is creating tension. Assume there is a free option for solo users with a generous device cap, paid team plans whose limits do not expand cleanly as a company adds more users, monthly billing only, and a growing stream of requests from admins for easier annual purchasing and a more premium commercial option. Finance wants better monetization and fewer exceptions. Growth wants to preserve a simple entry point and avoid damaging trust with individual users who helped spread the product. Support reports that most people use a modest number of devices, but a small set of heavy users and growing teams are creating confusing edge cases. You need to propose a pricing and plan limit strategy that scales with customer growth, uses real usage behavior rather than guesswork, and improves revenue without making the product feel nickel and dimed.

What to produce

Write a 1 to 2 page product strategy memo.

Your answer must

Define the main customer segments involved, including individual users and team buyers, and explain their different needs.
Recommend a revised packaging and pricing approach, including how many paid tiers to offer, what each tier is for, and whether to add annual billing.
Specify what plan limits should exist and what unit they should scale with, and explain why that unit fits customer growth.
Describe what usage data you would analyze to set or defend any free or paid limits, including which distribution cuts matter.
Assess the main tradeoffs, including revenue, conversion, customer trust, support load, and impact on heavy individual users.
Propose a rollout and measurement plan with success metrics and guardrails.

Constraints

Keep a free entry point for individual users.
Do not rely on new product features beyond pricing, billing cadence, tiering, and plan limits.
Your proposal should work in a mostly self serve motion, without assuming a large enterprise sales expansion.
Any reduction in access or limits should be justified by observed usage patterns and handled carefully for existing users.

Format

Use sections for recommendation, rationale, tradeoffs, data needed, and rollout.

How Tailscale actually played it

Tailscale replaces its old plans with Team and Business plans at 5 and 15 dollars per user per month, adds annual billing, and makes device limits scale with team size. It also cuts the solo device limit from 100 to 20 for new users, backed by the fact that fewer than 0.4 percent of individuals have more than 20 devices. A compact example of using usage data to set plan limits.

Use the distribution of real usage to justify limits (under 0.4 percent affected).
Scale limits with the unit customers grow by, here users.
Offer an annual option with a clear discount.
Introduce a new tier for the segment that wants to pay out of support.

Built from New Pricing Model Makes Scaling with Tailscale Less Expensive by David Carney, Ross Zurowski and Sonia Appasamy, Tailscale.