Expansion play on a usage spike
When an existing paying account crosses usage thresholds, enroll the contact in an expansion journey and send upgrade-focused messages to that same profile. Report journey activity in dashboards.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon7 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Score the expansion signals
Coming soonBlu builds a step
- 2
Find accounts outgrowing the plan
Coming soonBlu builds a step
- 3
Write to the champion
Coming soonBlu builds a step
- 4
Write to the budget holder
Coming soonBlu builds a step
- 5
Show the plan above theirs
Coming soonBlu builds a step
- 6
Work the account over two weeks
Coming soonBlu builds a step
- 7
Measure the expansion it makes
Coming soonBlu builds a step
About this recipe
When to use it
Fast user growth or multi-team usage on an account is a real expansion signal, and it's easy to miss without a workflow watching for it. This fires role-specific content to the champion and the economic buyer the moment it crosses a threshold.
What it delivers
When existing paying customers cross usage thresholds - fast user growth, feature-depth expansion, multi-team usage - fires a multi-stakeholder expansion journey: the champion gets 'you're scaling' content, the economic buyer gets upgrade-options content, and a recommendation surface highlights expansion features.
How you prompt this
Describe the outcome in your own words and Blu Agent maps it to this recipe, or run it by name. It drafts a plan first and nothing runs until you approve it.
Tell Blu Agent what you want
“When an existing paying account crosses usage thresholds, enroll the contact in an expansion journey and send upgrade-focused messages to that same profile. Report journey activity in dashboards.”
recipe.md preview
Built from the published catalog. Blu Agent's full step prompts load in your workspace when you run it.
Inputs & outputs
What the recipe needs before it runs, and what it leaves in your workspace.
Inputs
- Nothing declared beyond an Intempt workspace. Blu asks for anything else it needs as it goes.
Outputs
How the recipe runs
Blu follows the steps in order and shows you each one before anything goes live.
- 01Score the expansion signalsCreate an AI-derived attribute 'expansion_signal_score' on the Account object. Inputs: (a) active-user growth rate (new users added from domain in last 30 days vs. trailing 90-day baseline); (b) feature-depth expansion (count of distinct features used per active user trending up); (c) multi-team adoption (users from different functions / departments based on email domain or profile data); (d) usage-cap proximity (seats / API calls / events / storage); (e) integration-attach (new integrations connected: signals deeper commitment). Output: 0-100 score with composite reasoning string explaining which signals are firing.
- 02Find accounts outgrowing the planBuild a segment 'Expansion-ready customer accounts' capturing existing paying accounts where expansion_signal_score >= 70 in the last 14 days AND no active expansion deal already in flight (don't double-orchestrate against AE work). Partitioned by primary signal type so the journey can branch on the dominant signal (user-growth-driven vs. feature-depth-driven vs. usage-cap-driven). Use the result of "Score the expansion signals".
- 03Write to the championGenerate email content for the user-champion at the account (the most-active user, usually). Variants by signal type: user-growth ('Your team is growing on [Product]) here's how power-using teams stay organized at this scale.' Feature-depth ('You're using [Product] deeper than 85% of similar accounts) here's what's next.' Usage-cap: 'Your team is approaching the [resource] limit. Here are options.' Tone: peer-to-peer enablement, not sales pitch. The champion should feel proud, not pitched. Use the result of "Score the expansion signals", "Find accounts outgrowing the plan".
- 04Write to the budget holderGenerate email content for the economic buyer at the account (often someone NOT actively using the product day-to-day (admin / manager / finance owner). Variants by signal type: user-growth) 'Your team's usage of [Product] grew [N%] this quarter (here's a business-case summary of value delivered.' Feature-depth) 'Your team is in the top 15% of [Product] users by depth (let's discuss expansion options.' Usage-cap) 'Cost-comparison: upgrade vs. current overage costs.' Includes ROI snapshot. Tone: business-formal, value-substantive. Reply-to: assigned AE. Use the result of "Score the expansion signals", "Find accounts outgrowing the plan", "Write to the champion".
- 05Show the plan above theirsConfigure a recommendation surface 'Expansion features' that activates when the account is in the expansion segment. Renders in-app on the admin dashboard and in the email touches. Pulls: features available on higher-tier plans that the account would benefit from based on current usage patterns (e.g., 'Teams using [current features] often graduate to [advanced features]: here's what they unlock'). Includes upgrade-comparison surface for plan-decision-makers. Use the result of "Score the expansion signals", "Find accounts outgrowing the plan".
- 06Work the account over two weeksBuild a multi-stakeholder journey triggered when an account enters expansion-ready segment. Touch 1 (Day 0): champion email: 'you're growing fast / using deeply / hitting limits' content. Touch 2 (Day 3): in-app upgrade-comparison surface activates for admin users at the account on next session. Touch 3 (Day 7): economic-buyer email with ROI summary and AE meeting CTA. Touch 4 (Day 14): if no AE meeting booked, create AE task with the full account context attached (signals, decision-makers, recommended package). Recommendation surface stays active for 60 days. Exit on: Meeting scheduled (handoff to AE), upgrade_completed (success (celebrate), Deal created (AE-owned from here), or expansion_signal drops below 50 for 30 days (false signal) exit gracefully). Use the result of "Score the expansion signals", "Find accounts outgrowing the plan", "Write to the champion", "Write to the budget holder", "Show the plan above theirs".
- 07Measure the expansion it makesCompose an expansion performance dashboard: expansion-signal volume per week by signal type (which signals fire most: informs which expansion levers the product naturally creates), expansion-signal-to-meeting conversion, expansion-signal-to-deal-created conversion, ARR uplift from journey-attributed expansion (cohort-attributed vs. control), and signal-type effectiveness (does user-growth signal convert better than feature-depth: informs product/marketing focus). NRR contribution from this play. Use the result of "Score the expansion signals", "Find accounts outgrowing the plan", "Write to the champion", "Write to the budget holder", "Show the plan above theirs", "Work the account over two weeks".
Install Intempt and run it
- 1
Sign up
Create a free Intempt workspace.
- 2
Connect your data
Add the sources this recipe reads from.
- 3
Ask Blu
Type /usage-spike-expansion-play in Blu once this recipe is live there.
- 4
Review and approve
Blu builds each step and waits for your OK before anything goes live.
Related recipes
Sid ChaudharyDiscovery call qualification fieldsGenerates an AI summary for Discovery calls from meeting data using the qualification framework in the summary recipe.View recipe Sid ChaudharyPost demo nurtureKeeps a demo warm for 90 days with a playbook, a case study, an ROI calculator and a customer story, and pulls the AE in early if they bite.View recipe Sid ChaudharyReturn rate by categoryShows which product categories get returned most, and which ones have got worse since last quarter.View recipe 