What are the design rules for free tier seat limits, feature gates, and API quotas that trigger expansion motions?
Self-Serve Tier Design for Expansion
Free tier constraints must signal upgrade intent without friction—too permissive, users stay free; too restrictive, they churn.
Tier Architecture (Typical SaaS)
| Constraint | Free | Pro | Enterprise |
|---|---|---|---|
| Seats | 3 | 10–25 | Unlimited |
| API calls/mo | 50k | 500k | Custom |
| Workflows | 5 | 50 | Unlimited |
| Audit log retention | 7 days | 90 days | 1 year |
| SAML/SSO | — | — | Yes |
Expansion Trigger Points
SaaStr benchmark: Free-tier expansion accounts for 12–18% of ARR in pure freemium models. Set seat caps at 3–5 users to force collaboration signal; API quotas at 50–100k calls/month to match typical pilot workloads.
Create 5-day forgiveness window after quota breach—users expect 1–2 overage incidents before hard enforcement. Track "gate hit" conversion rate (users who hit limit → upgrade) separately from general signup-to-paid metrics.
TAGS: tier-design,seat-limits,api-quotas,feature-gating,expansion-triggers,freemium-architecture