first principles
← Company playbooks

Company playbook / 08 / Adoption & expansion

Tailscale

Give one developer a reason to bring the team

Tailscale’s founder explains a bottom-up strategy: make the individual experience valuable, let happy users recommend it, then charge companies for needs that arise at team or enterprise scale.

PLGPricing

01 / What they actually did

Free individual use with a clear reason

Tailscale described an individual free tier as a way to let people discover the product and recommend it. [T1]

Pricing reduced team friction

Its 2021 pricing change was meant to make scaling from experiments to a larger team less expensive. [T2]

Paid value is different from personal utility

Enterprise users need administration, security, support and controls that an individual may not need. [T1]

02 / What you can learn

Lesson to keep: Make it easy to get one meaningful result. Design the natural next step for a team—not a random paywall after an arbitrary number of clicks.

Don’t over-copy: A generous free tier is viable only when unit economics support it. High-ingestion infrastructure may need a sandbox or capped trial instead.

03 / How to do something similar

  1. 01Find a low-cost, self-contained job one person can finish in minutes.
  2. 02Remove unnecessary signup, setup and approval friction where safe.
  3. 03Define the moment when that user needs team collaboration, controls or more capacity.
  4. 04Build an invitation or upgrade path around that moment.
  5. 05Measure activation and team spread before optimizing payment conversion.

Examples you could publish or run

“Try [small useful task] without connecting production”“Invite your teammate to review this result”

What to measure
Time to first value, activated users who invite teammates, qualified upgrades.

04 / Copy the framework

Inspired by Tailscale

One-person-to-team growth test

Find a genuinely useful free task that creates a reason to collaborate.

ONE-PERSON JOB: [specific task solved in under X minutes]
MAX COST TO PROVIDE: [capacity/support constraint]
PROOF OF VALUE: [observable result]
TEAM MOMENT: [why would user invite a teammate?]
PAID MOMENT: [security/control/capacity/support requirement]

TEST:
- 20 users try the task with minimal help
- Track setup abandonment and time to first value
- Observe real teammate invitations
- Ask what blocks team adoption

DON'T SCALE UNTIL: the free path is useful AND economical.

05 / Original sources

Next playbookincident.io →