LLenny's Podcast
← All frameworks
Marketing

Connector-Led Invitation Loop

Find natural connectors and give them repeated, optional ways to invite.

Difficulty
Moderate
Time to result
~weeks to results
Steps
5
Confidence
95%

The Connector-Led Invitation Loop recognizes that invitation behavior is unevenly distributed across a user base. Some people naturally host, introduce, and bring groups together; others rarely invite anyone. Grace argues that growth teams should identify the connector persona and make it easy for those users to invite larger groups, instead of spending disproportionate effort trying to make reluctant users send one invitation. Invitation prompts should appear early and at multiple relevant moments because a user who is ready to share can otherwise be missed. This does not justify coercion. Non-connectors should be able to skip, and the product should avoid dark patterns such as preselecting contacts or sending messages that misleadingly appear personal. The mechanism combines persona selection, repeated opportunity, and consent.

Origin

Grace observed across collaboration products that naturally social users could be encouraged to invite larger groups more easily than shy or non-hosting users could be persuaded to invite once.

Core principles

  • 01People differ in their natural willingness to convene others.
  • 02Increasing invitations from connectors is easier than converting non-inviters.
  • 03Repeated opportunities can remain ethical when they are optional and transparent.

How to run it

  1. 1

    Find the connectors

    Use interviews and behavior to identify users who already convene groups or make introductions.

    Pro tip Look for existing hosting behavior outside the product, not only invitation clicks.

    Watch out Do not assume all users have the same social motivation.

  2. 2

    Choose the growth persona

    Focus acquisition and product messaging on connectors whose normal behavior matches the product's collaborative mechanics.

  3. 3

    Offer early invitations

    Give ready users a clear invitation path during onboarding without making it mandatory.

    Pro tip Treat stated resistance in usability interviews as one signal, not a command to remove the option for everyone.

    Watch out Never block progress until a user invites someone.

  4. 4

    Repeat at natural moments

    Offer another invitation opportunity when collaboration would create obvious value inside the product.

    Watch out Repeated opportunities become spam when they ignore context or user choice.

  5. 5

    Audit consent

    Verify that contacts are not preselected and messages accurately show who initiated them.

    Watch out Dark patterns may increase sends while damaging trust.

In the wild

Collaboration tool connector

An illustrative collaboration app identifies team organizers as its strongest invitation persona. It offers an optional invite during setup and another when the organizer creates a shared workspace, while everyone else can continue alone.

→ The product captures high-intent group invitations without coercing reluctant users.

Common mistakes

Designing for the average inviter

Averages conceal that a small connector segment may drive a disproportionate share of invitations.

Turning opportunity into coercion

Auto-selecting contacts or disguising automated messages violates the framework's consent boundary.

Is it for you?

Best for

Collaboration, communication, and social products whose value increases when users bring others.

Not ideal for

Single-player tools with no meaningful network or collaborative value.

From the episode

Merci Grace (ex-Head of Growth at Slack) on PLG, interviewing, storytelling, building a diverse team, hiring salespeople, building a growth team, and much more

→