How to run customer expansion with Julian
Detect expansion readiness from actual usage rather than rep memory. Seat limits, feature adoption, and renewal windows trigger a contextual conversation.
Customer expansion detects when an account is ready to grow from actual usage data rather than a rep's memory. Julian monitors usage thresholds, seat utilisation, feature adoption, renewal timelines, and new team onboarding, then opens a conversation grounded in the specific behaviour - so it reads as a natural next step rather than an upsell attempt.
The failure mode this replaces is coverage-by-memory: a CSM remembers the twelve accounts they spoke to recently, and the rest of the book goes unexamined until renewal. Usage signals cover the entire base without proportional headcount.
Expansion signals
| Signal | The conversation it justifies |
|---|---|
| Seat utilisation spike | A team that maxed out seats gets a conversation about adding more |
| Usage threshold reached | Tier or capacity discussion |
| Feature adoption | Complementary product or module |
| New team onboarding | Another department is adopting - expand the footprint |
| Renewal timeline | A decision point with a date attached |
Ground the message in the action
Relevance comes from the behaviour, not from the copy. A customer using one product gets an introduction to a complementary one; a team hitting seat limits gets a seat conversation. Because the trigger is a real thing they did, the outreach reads as helpful rather than opportunistic.
Route anything contractual to a human. Pricing beyond your published posture, contract terms, and renewal negotiation belong with a person - see call flows for unconditional transfer topics.
Configuring
Push usage data into 11x
Product usage lives in your systems. Send it via the API or as Dynamic Triggers.
Set thresholds per signal
Sustained utilisation, not a single spike.
Exclude accounts in trouble
An account with open escalations or a poor health score should not receive an upsell call. Check support state before expansion outreach.
Map each signal to its own conversation
Seats, capacity, and cross-sell are different conversations.
Route to the account owner
Expansion conversations should reach whoever owns the relationship. See lead routing.
The exclusion in step 3 matters more than it looks. Calling a frustrated customer about buying more is the fastest way to convert a renewal risk into a churn event. Wire support and health state into your exclusions before enabling this.
Troubleshooting
Next steps
Customer onboarding
The motion that precedes expansion.
PLG conversion
The same idea for free-tier users.
Lead routing
Reaching the account owner.
All plays
The full play library.
Need help?
Email support@11x.ai, or book time with the team.