Growth feature pattern
Team invitation feature pattern
Team invitation flows convert single-user customers into multi-seat customers — the biggest expansion-revenue lever for B2B SaaS. Designed well, invitations produce 30-60% of seat growth; designed badly, they sit unused and the customer stays solo.
Verified · editorial policy
How the pattern works
After a user signs up, an in-product CTA encourages them to invite teammates. Invitations can be email-based (send link), bulk (paste emails), or organic (share a workspace URL). Invited users join the same paid workspace, often at the same seat price.
Best for
Per-seat B2B SaaS. Products where collaboration is core value. Products at $20+/seat/month where additional seats produce meaningful revenue.
Worst for
Solo-user products (forms, calendars, individual analytics). Flat-rate-pricing products where adding seats does not lift revenue. Products where the buyer is the only user (early-stage CRMs, accounting tools).
Target growth metric
Seats-per-account growth over 90 days. Healthy indie B2B sees 1.5-2.5 seats per account at the 90-day mark; below 1.5 suggests the invitation flow is weak or the product does not need collaboration.
Implementation considerations
- Surface invitation prompt during onboarding (after first key value moment, not before). Users who have not yet seen the value will not invite teammates.
- Pre-fill invitation emails. 'Invite Sarah, John, and Mike' beats blank-state 'enter teammate email'.
- Auto-detect potential teammates from email domain. If user @acme.com invites @acme.com, the conversion is highest.
- Make invitation rewards mutual: invitee gets seamless join, inviter gets reduced friction. Two-sided benefit lifts invitation rate.
- Allow workspace-link invitations. Some teams prefer copy-paste-share over per-person email.
Common misuses
- Invitation prompts before user understands product value. Conversion plummets.
- Charging seat fees for invited users who never log in. Customer churn spikes when invoiced for non-active seats.
- Inviting via gated form that requires admin approval. Adds friction; many invites die in approval queue.
- Not surfacing invitation outside onboarding. Users hit invitation moments later in product life; the flow has to be discoverable.
Realistic outcomes
Done well: 40-60% of accounts have 2+ seats by day 90; expansion revenue is meaningful. Done badly: 80%+ of accounts stay at 1 seat; per-seat pricing fails to compound.
Frequently asked
- Should invited seats be free for the first 30 days?
- Generally no for B2B SaaS — paid-from-day-one creates real commitment. The exception is products where the invited user contributes value to the inviter (collaborative tools); a brief free trial for invitees works there.
Other feature patterns
Test the pattern's lift on your product
Growth feature patterns produce different lift on different products. The experiment recipes show you how to test the actual impact before committing to long-term implementation.