The anchor
Pro tier as anchor
Pro at approximately $15/user/mo anchors the page for serious knowledge-platform buyers. Plus at approximately $8 reads as the natural starting tier for small teams; Free is the entry. Enterprise sits behind a sales conversation. The unusual structural element is that the entire tier ladder scales with team size rather than with knowledge volume — buyers do not pay more for writing more docs, only for adding more people.
The upgrade trigger
User-count cap plus advanced-feature need
Two triggers fire: the 5-user cap on Free forces teams to upgrade when they grow beyond initial adoption; the advanced-feature need (analytics, SSO, advanced permissions) drives Plus-to-Pro conversion. Both triggers map to natural team-growth events rather than usage-based limits, which matches how knowledge-platform adoption actually scales inside organizations.
What works
- • Per-user pricing aligns the bill with team-adoption value rather than with documentation volume.
- • 5-user cap on Free is a predictable trigger that fires when a team genuinely adopts the platform.
- • Plus tier brand-removal trigger captures the publication-moment willingness-to-pay spike.
- • Pro tier advanced-feature gating captures the team-maturity upgrade as governance and analytics matter.
- • Enterprise tier provides the procurement-driven upsell without exposing custom pricing publicly.
- • WYSIWYG editor accessibility expands the contributor base beyond developers — pricing per-user captures the broader team value.
What to copy
- • When your value scales with team adoption rather than with usage volume, per-user pricing aligns the bill with the actual value driver.
- • Layer triggers: count caps (5 users on Free) for team-growth, feature gates (SSO, analytics) for team-maturity. Both contribute to total conversion rate.
- • Brand removal as Plus-tier trigger captures the publication-moment willingness-to-pay without forcing all users to pay.
What to avoid
- • Do not adopt per-user pricing if individual users do not get clear individual value. For knowledge platforms most users get value as readers; per-user pricing on read-only access undervalues the platform.
- • Do not gate advanced features at Pro if buyers expect them at Plus. The feature-tier expectations evolve over time — what was Pro-tier three years ago may be Plus-tier now.
Trial behaviour
Free tier IS the trial for small teams; paid tiers offer time-limited trials for evaluation.
Apply this to your own idea
Run your product through the Pricing Fit Calculator to see where your intended price lands against developer documentation benchmarks, then validate whether the market supports it.
Source: unlocksaas.com — indie-saas-teardowns (CC BY 4.0). Pricing page https://www.gitbook.com/pricing. Verified 2026-05-17.