Team Expansion and Invites SKILL.md

This is the exact file agents read, including the credit header and licence notice. Save it as team-expansion-invites/SKILL.md.

---
name: team-expansion-invites
description: "Grow accounts from one user to whole teams: collaboration moments that create invites, one-click invite flows, personalised invite emails that land invitees in shared work, prompts after the value moment, domain discovery and join requests, admin controls, free viewers and guests, cross-team spread and team formation metrics. Use whenever someone asks about invite flows, viral growth inside accounts, getting users to invite teammates, seat expansion, team adoption, domain discovery, workspace joining or single-user accounts that never grow."
license: CC-BY-4.0
metadata:
  author: Afeez Adebayo
  author_url: https://afeezadebayo.com
  author_linkedin: https://www.linkedin.com/in/afeez-adebayo/
  author_x: https://x.com/za_icon
  source: https://afeezadebayo.com/skills-md/marketing/product-led-growth/team-expansion-invites/
  category: marketing
  subcategory: product-led-growth
  version: "1.0.0"
  created: "2026-10-10"
  updated: "2026-10-10"
---

# Team Expansion and Invites

In many product-led businesses, growth comes from inside accounts: one person adopts the product, invites colleagues, the team grows, other teams notice and the company eventually standardises on it. Each invite is both a retention driver (teams churn less than individuals) and an acquisition channel. Yet invite flows are often buried in settings, invited users land on a confusing screen, and nobody nudges single users to bring their team in.

This skill designs team expansion: collaboration moments that create natural invites, invite flows, the invitee experience, domain discovery and joining, admin controls, cross-team spread, seat expansion and measurement. Customer referral programmes sit in the Growth Marketing `referral-programmes` skill; growth loops broadly in `growth-loops`.

## Operating principles
1. **Invites come from collaboration, not prompts.** Sharing, commenting, assigning and reviewing create real reasons to invite.
2. **Make inviting easy.** One click from where collaboration happens.
3. **Treat invitees as new users with context.** They should land in the shared work, not a blank onboarding.
4. **Help teams find each other.** Domain discovery and join requests spread adoption across companies.
5. **Give admins control.** Larger accounts need permissions, approval and visibility to say yes.

## Collaboration moments that drive invites
| Moment | Example |
|---|---|
| Sharing work | Sharing a document, board or dashboard |
| Assigning | Assigning a task or review to someone not yet a user |
| Commenting and mentions | Mentioning a colleague by email |
| Approval workflows | Sending something for sign-off |
| Handoffs | Passing a file or project to another team |
| Viewing results | Sending a report or live link to stakeholders |

## When to use, and when not to
Use it when most accounts have one active user, when team plans are the main revenue, when invite rates are low and when larger companies use the product in isolated pockets.

Don't use it for customer-to-customer referral rewards (the Growth Marketing `referral-programmes` skill) or single-user products where collaboration doesn't apply.

## Inputs to ask for, in one message
1. Collaboration features and current invite flows.
2. Data: users per account, invite rates, invite acceptance, activation of invitees.
3. Retention and revenue by team size.
4. Plans and seat pricing.
5. Admin and permission features.
6. Domain or company data on sign-ups.

## Workflow

### Step 1. Measure team formation
Share of accounts with 2+, 5+ and 10+ active users; retention and revenue by team size.

### Step 2. Find natural collaboration moments
Where users share, assign, mention or hand off work.

### Step 3. Add invites at those moments
Invite by email or link from the share, assign and mention actions.

### Step 4. Prompt single users at the right time
After the value moment, suggest inviting the people they work with, with a reason.

### Step 5. Design the invitee experience
Personal invite email naming the inviter and the shared item; landing directly in that item; light onboarding for invitees.

### Step 6. Enable domain discovery
Show users from the same company domain that colleagues already use the product; allow join requests or automatic joining with admin settings.

### Step 7. Add admin controls
Approval for new members, roles, guest access, seat management.

### Step 8. Support cross-team spread
Templates and shared spaces for other teams; signals for product-led sales when several teams appear.

### Step 9. Measure
Invites sent per active user, acceptance rate, invitee activation, team size growth and retention.

## Invite flow checklist
- Invite buttons where collaboration happens, not only in settings.
- Invite by email, link or from a directory or calendar integration.
- Invite emails personalised with the inviter's name and the shared work.
- Invitees land in the shared item, signed up in as few steps as possible.
- Clear messaging on seats and cost if inviting adds charges.
- Reminders for pending invites, sent once or twice.

## Invitee email example
```
Subject: Maya shared "Q4 launch plan" with you
Maya invited you to collaborate on the Q4 launch plan in Acme.
[Open the plan]
You'll be able to comment and edit straight away.
```

## Team formation metrics
| Metric | Why |
|---|---|
| Accounts with 2+, 5+, 10+ active users | Team adoption depth |
| Invites sent per active user | Invite behaviour |
| Invite acceptance rate | Invite quality and email clarity |
| Invitee activation rate | Invitee experience |
| Time from first user to second active user | Speed of team formation |
| Retention and revenue by team size | Value of teams |

## Timing single-user prompts
Prompt users to invite colleagues after they've seen value, such as completing a first project or receiving a useful result, with a reason tied to the work: "Invite the people who review your designs so they can comment directly." Avoid invite prompts in the first minutes, before users know whether the product is worth sharing.

## Free viewers and guests
When pricing is per seat, charging for every viewer discourages sharing. Free viewer or guest roles let work spread widely, while editors or creators pay. Track how many viewers later become paid editors.

## Domain discovery options
| Option | Behaviour | Fits |
|---|---|---|
| Show colleagues | Tell new users others from their company use the product | Most B2B products |
| Join request | User asks to join an existing workspace; admin approves | Security-conscious companies |
| Automatic join | Users with a verified company domain join automatically | Open, collaborative cultures |
| Off | Each user starts separately | Consumer or sensitive products |
Let workspace admins choose the setting, and explain it clearly to new users.

## Pending invite reminders
Send one reminder after two or three days and a final one after a week, mentioning the inviter and the shared item. Then stop; repeated reminders look like spam and hurt deliverability.

## Cross-team spread
When several teams in one company use the product separately, offer shared templates, a company workspace and admin consolidation, and flag the account for product-led sales.

## Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Seat-based pricing discourages invites | Free viewers or guests; charge for editors |
| Security-conscious companies | Admin approval and domain restrictions |
| Personal email sign-ups | Encourage switching to work email for team features |
| Spam or abuse through invites | Rate limits and verification |
| Several workspaces in one company | Offer consolidation; flag for product-led sales |

## Handoffs to related skills
- Onboarding invites into first run: `in-product-onboarding`
- PQLs from team growth: `product-qualified-leads`
- Seat upgrades: `in-app-upgrade-prompts`
- Metrics: `plg-metrics`
- Referral programmes: the Growth Marketing `referral-programmes` skill
- Growth loops: the Growth Marketing `growth-loops` skill

## Worked example
A whiteboard tool found 70% of paid accounts had a single active user, and invites sat in a settings menu. Team accounts retained far better. The team added invite options to the share button and to mentions, prompted users to invite collaborators after their first board, sent personalised invite emails that opened the shared board directly, made viewers free so seat costs didn't block sharing and added domain discovery so new users could join colleagues' workspaces. Invites per active user and team accounts grew substantially over two quarters, and retention improved.

## Output format
```
# Team expansion plan: <product>, <date>
## Team formation metrics
## Collaboration moments and invite points
## Invitee experience
## Domain discovery and admin controls
## Cross-team spread and sales signals
## Metrics
```

## Common mistakes
- Invites hidden in settings.
- Generic invite emails.
- Invitees landing on blank onboarding.
- Seat pricing that discourages sharing.
- No admin controls for larger accounts.

## Questions to ask before you design
- Where do users naturally need colleagues in the product?
- What happens when an invited person clicks the link?
- Does pricing encourage or discourage inviting?

## Self-check before you answer
- Are invites placed at collaboration moments?
- Is the invitee experience contextual?
- Are domain discovery and admin controls considered?
- Are invite and team metrics tracked?

---
Created by Afeez Adebayo, Marketing, SEO & Growth Expert
Website: https://afeezadebayo.com
LinkedIn: https://www.linkedin.com/in/afeez-adebayo/
X: https://x.com/za_icon
Source: https://afeezadebayo.com/skills-md/marketing/product-led-growth/team-expansion-invites/

Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.