RevOps playbook · AI Employee: Rev

Expansion Signal Detection

Expansion pipeline created continuously

Install this playbookBack to marketplace
The problem

Expansion is left to whoever remembers to ask. A customer hits a plan limit, adds users faster than expected, integrates deeper, hires more people — the buying signals are visible in product usage but sitting in a dashboard nobody reads. CSMs run quarterly business reviews and hope the customer volunteers the expansion. Meanwhile the customer is quietly evaluating a competitor because your account team hasn't touched them in two months.

At a glance
Trigger
Cron
Approvals
None
What it does
Read-only
Systems
Product usage · CRM · CS platform
How it feels in production

An hour-by-hour walkthrough.

Every night, Rev scans every active customer against a battery of expansion signals: - Usage: approaching plan limits (>80% seat utilisation, >75% storage, >90% API quota) - Growth: user-count trend up 20%+ over 90 days - Adoption: newly using premium features that map to a higher tier - Integration: newly connected to a system that unlocks upsell (adding CRM integration = usually more seats) - Hiring: LinkedIn signal of hiring surge in relevant departments - Support: opening tickets asking about features on higher tiers - Champion: champion promoted or moved to a role that unlocks broader use Acme Corp's expansion score jumps to 0.87. Rev writes an annotated note on the account: seat utilisation 92%, adding 4 users per week over the last 6 weeks, opened 3 support tickets asking about SSO (Enterprise tier feature), champion promoted from Sr Manager to Director last month. CSM Kiran gets the DM Monday morning: "Acme Corp is showing 3 expansion signals. Suggested play: schedule a Success Plan review this week, propose the Enterprise tier trial with SSO, and get intro to their new VP Product (from champion's org chart update). Estimated expansion value: $80K ARR." Kiran reviews. Approves the Success Plan meeting request; Rev sends it. Kiran edits the Enterprise trial proposal draft; Rev delivers. CSM leader sees the pipeline of expansion opportunities weekly; expansion becomes a proactive program, not a lucky outcome.
How it works

Step by step.

  1. 01

    Scan every customer nightly against expansion signals

    Usage vs. plan limits, growth trend, feature adoption, integration additions, hiring signals, upsell-topic support tickets, champion role changes. Multi-signal, multi-source.

    Product analytics · CRM · Support · LinkedIn Sales Navigator · Zendesk
  2. 02

    Score + rank expansion opportunities

    Score against your historical expansion outcomes. Higher signals + tier mismatch (paying SMB, using Enterprise-worthy features) rank highest. Estimated expansion value from historical similar-shape upsells.

    Historical warehouse · Scoring model · Pricing model
  3. 03

    Draft the CSM Monday DM with suggested plays

    CSM DM: account name, signal detail, suggested play (Success Plan review, tier trial, integration expansion, exec intro), estimated ARR value, expected time investment.

    Slack · Teams · CSM dashboard
  4. 04

    Execute the plays + coordinate stakeholders

    Approved plays: Rev sends the meeting invite, drafts the trial proposal, coordinates product-team involvement for enterprise-tier trials, tracks response.

    Google Calendar · Email · Slack · Product team registry
  5. 05

    Roll up to CSM leader + close the loop

    Weekly digest: expansion pipeline by CSM, top opportunities by ARR, conversion rate on expansion plays, next-quarter expansion forecast. Feed accepted / declined outcomes back to model.

    Analytics · Slack digest · CSM leader dashboard
Systems and wiring

What you connect to make this run.

Amplitude · Mixpanel · Pendo · Product analytics

read

Usage signals, feature adoption, integration additions, growth trends. The single strongest signal source — customers approaching plan limits or adopting higher-tier features are actively buying signals.

Salesforce · HubSpot · CRM

read+write

Account state, contract tier, historical expansion. Write expansion score + play status + estimated ARR to the account so pipeline reports include the expansion forecast.

LinkedIn Sales Navigator · Champion tracking

read

Champion role changes, hiring signals at customer companies. Champion promotion + company hiring surge together are strong external signals.

Slack · Teams · Email · Calendar

read+write

CSM coordination, meeting scheduling, proposal drafts. Playbook-driven; CSM stays in control of the execution while Rev handles the coordination overhead.

What changes

Before and after, honestly.

Net revenue retention (NRR)
Before
105-115%
After
118-135%
Expansion opportunities identified 90+ days out
Before
30-50%
After
80%+
Conversion on outbound expansion plays
Before
15-25%
After
35-50%
CSM time on expansion planning
Before
3-6 hours per week per CSM (dashboard trawling)
After
1-2 hours (review + play execution)
Related

Playbooks that pair with this one.

RevOps

Renewal Pipeline Review

Renewal cycle is often the expansion moment; joint planning saves cycles.

RevOps

Closed-Won Cascade

Expansion wins run the same cascade as new-business wins (provisioning + invoicing).

Finance

Customer Invoice & Subscription Change

Expansion converts to a subscription change; execution runs there.

Frequently asked

Answers about this playbook.

Won't customers feel pushed if we outreach on every signal?

CSM controls the play. Not every signal triggers outreach; the DM surfaces the signal + suggested play and the CSM decides. Some customers appreciate proactive attention; others prefer to be left alone until they ask. CSM knows.

How does it distinguish real expansion from temporary spikes?

Multi-week trend required, not single-day spike. Signal deduplication (a marketing campaign spike doesn't trigger; sustained user growth does). CSM sees the reasoning before deciding.

What about customers already in an active expansion conversation?

Rev knows about open expansion opportunities and doesn't double-outreach. Signals augment the existing conversation rather than starting a new one.

How does this coordinate with our AE team on expansion?

Expansion routing rules define whether CSM or AE owns the expansion motion (varies by tier + product). Rev routes to the correct owner; both are visible on the account.

Can we exclude specific customers from expansion plays?

Yes — do-not-outreach flag per account. Common for customers in active renegotiation, contract disputes, or evaluating options — expansion outreach at the wrong moment can damage the relationship.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore RevOps playbooks