What are expansion signals in product usage?

DAU is a vanity chart. Seat invites and a second workspace are expansion signals.

An expansion signal is a product event that predicts a buyer will add seats, move to a higher plan, or buy a second product. It is not "they logged in." It is a behavior that raises the chance of more revenue from an account you already won.

If you are only watching daily active users, you are measuring motion, not money. Grow lives downstream of the right events.

What counts as an expansion signal?

Events that raise the odds of upsell or cross-sell, tied to a seat, workspace, or paid threshold.

Examples that usually matter in B2B SaaS:

• Seat invite sent or accepted. Someone is pulling a teammate in. That is a buying motion inside the account.
• Second workspace or project created. The footprint is growing past the first use case.
• Integration connected. They are wiring you into a real workflow, not a sandbox click.
• Usage crossing a paid threshold. API calls, messages, seats, or storage that touch the next plan line.
• Admin role assigned to a second person. Buying power is spreading inside the company.

Name the event in plain language. "Invite teammate" beats "collaboration_engagement_score." If you use analytics such as PostHog, instrument the event so GTM can see it the same day. I covered how to turn those events into GTM signals separately.

How is this different from activation?

Activation is the first proof the product works. Expansion is proof the account wants more of it.

An activation event for an AI product might be "first successful run that saved a human an hour." That gets them past empty seats. Expansion is what happens after: they invite three peers, connect Slack, and hit the plan limit in week three. Confusing the two is how you celebrate activation while churn and flat ARR sit in the same chart.

Why do vanity metrics fail Grow?

Because they do not tell sales or CS who to call, or what to sell.

You either figure out CAC or your business fails. Expansion is how you pay CAC back. A dashboard full of DAU does not queue a commercial conversation. A "seat invite from a paid admin at an account under three seats" does. One is a chart. The other is a task.

I have watched teams ship product-led sales motions that still alert on login streaks. The AE gets a notice that someone was "active." Active at what? Without the expansion event, the call is a fishing trip.

How do I wire expansion signals into Grow?

1. List five candidate events that historically sit before expansions in your CRM. If you have no history, start with seat invite, second workspace, integration connect, and plan-limit proximity.
2. Define the threshold. One invite may be noise. Three invites in seven days from a paid account is a signal.
3. Route to a human with context. Who invited whom. What plan they are on. What integration they connected. The note must not be something that could go to anyone.
4. Attach a Grow play. Seat pack offer, plan upgrade path, or a second product demo. Message the desire: more of the outcome they already got, not a feature tour.
5. Score meetings and expansion ARR, not open rates on the in-app banner.

What should I ignore?

Login counts, page views inside the app, and "time spent" without a job completed. Those can support activation research. They are weak expansion signals. Also ignore one-off spikes from your own employees and from shared demo accounts. Filter them or you will burn AE time on ghosts.

What should I do this week?

Pick one expansion event you can already see in product analytics. Write the definition in one sentence. Wire an alert to CS or sales with account, plan, and the event. Run it for twenty accounts. Count how many turn into a commercial conversation. If zero, your event is wrong or your message is. Fix one, then the other.

Adapt or fail. Charts do not expand seats. Signals with a Grow play do.

Start Signals, Convert, Grow

FAQ

What is an expansion signal in SaaS?

A product usage event that predicts upsell or cross-sell, such as seat invites, a second workspace, connecting an integration, or crossing a paid usage threshold. It is not raw DAU.

Is a free-to-paid conversion an expansion signal?

That is usually acquisition or activation into paid. Expansion is more revenue from an account that is already paying. Treat them as different queues.

Can expansion signals live only in the product team?

No. Product owns instrumentation. GTM owns the play when the signal fires. If the event never leaves a product dashboard, it is not a GTM signal yet.

How many expansion signals should I track?

Start with two or three you can act on this month. A long list you ignore is worse than one event that books upgrade calls.

Do AI products need different expansion signals?

Often yes. Token burn past a plan line, second agent or workflow created, and first shared prompt library can matter more than classic seat invites. Still tie each one to a commercial next step.