Tailscale · Strategy · Senior · 45 to 60 minutes

How should Tailscale redesign self-serve pricing?

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

pricing strategy
monetization
analytical reasoning
go-to-market judgment
experimentation

The situation

You are a senior PM at Tailscale. The CEO has asked you to recommend the next version of self-serve plans and pricing. Tailscale has a strong product, a popular free entry point, and paid plans for teams, but leadership believes the current structure creates avoidable friction as accounts grow from initial use into broader adoption. The company wants pricing to do more than maximize short term revenue. It should help new users get started, make team expansion feel natural, and keep paid plans aligned with the value customers believe they are getting. At the same time, any change could confuse prospects, upset current customers, and create billing or support complexity. Assume you are preparing a strategy recommendation for the next planning cycle. You need to decide whether to change plan boundaries, packaging, or the billing model for self-serve customers, and how to test and roll out the change without harming trust or growth.

What to produce

A 1 to 2 page strategy memo for the CEO and leadership team.

Your answer must

State the core pricing problem you are solving, including where current self-serve plans create friction as usage grows.
Recommend one primary pricing and packaging approach, plus one credible alternative you rejected, with tradeoffs.
Explain how your approach should affect free adoption, conversion to paid, expansion within accounts, and revenue quality.
Define the metrics you would use to judge success in the first 2 quarters, including at least 2 leading indicators and 2 lagging outcomes.
Outline a rollout plan covering customer communication, treatment of current subscribers, experiment design, and key risks.

Constraints

Focus on self-serve plans, not enterprise contracts, channel sales, or new product features.
Keep the proposal simple enough to explain on the pricing page and operationally feasible with existing billing and support systems.
Work only from the summary above and general knowledge of Tailscale's product category. Do not assume undisclosed market data or internal numbers.

Format

Use sections titled problem, recommendation, rejected alternative, metrics, rollout, and risks.

How Tailscale actually played it

Tailscale's CEO announces the third generation of its plans: the free tier grows from one to three users and monthly paid plans include three free users while billing only for additional active users. The post then 'debugs' pricing by looking at data on friction points such as the growth curves of one-user and three-user networks. An unusually transparent case of treating pricing as a product to be iterated.

Treat pricing as a product and look for friction points in the data.
Let existing customers keep their old plan so the change is opt-in.
Billing only for active users aligns price with real use.
Expand the free tier where growth data shows it feeds adoption.

Built from Pricing v3, plans, packages, and debugging by Avery Pennarun, Tailscale.