Seat expansion signal to AE
Tells the AE when a customer is running out of seats or people from their domain keep signing up, which is the clearest upsell signal there is.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon4 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Measure how full the plan is
Coming soonBlu builds a step
- 2
Find accounts near a limit
Coming soonBlu builds a step
- 3
Raise the expansion task
Coming soonBlu builds a step
- 4
Track the expansion pipeline
Coming soonBlu builds a step
About this recipe
When to use it
Approaching a seat limit is one of the clearest expansion signals a customer can send, and it's easy to miss if nobody's watching plan usage in real time. This turns it into an AE task automatically.
What it delivers
When an existing customer adds users approaching their plan limit, or multiple new users from the same domain self-serve sign up, creates an AE expansion task.
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
“Tells the AE when a customer is running out of seats or people from their domain keep signing up, which is the clearest upsell signal there is.”
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.
- 01Measure how full the plan isCreate an AI-derived attribute 'seat_capacity_used' on the Account object. Compute: (active_seats / plan_seat_limit) as a fraction. Flag when >= 0.8 (approaching limit) or > 1.0 (over limit, billed as overage). Also surface: (a) net seat growth in last 30 days, (b) count of new sign-ups from the account's domain in last 14 days not yet provisioned, (c) any usage cap proximity (API calls, contacts, etc.).
- 02Find accounts near a limitBuild a segment 'Seat-expansion candidates' capturing existing paying accounts where (a) seat_capacity_used >= 0.8, OR (b) 3+ new users from the domain signed up in the last 14 days not yet provisioned, OR (c) any usage cap is >= 0.9 utilized. Excludes accounts already in active expansion deal conversations (handled by AE). Use the result of "Measure how full the plan is".
- 03Raise the expansion taskCreate a workflow firing when seat_capacity_used crosses 0.8, or when a new user_signed_up event comes from an existing customer domain. Step sequence: (1) refresh account context; (2) check whether AE already engaged this account in last 30 days (if so, skip: they're on it); (3) create an AE expansion task with the trigger context (seat-capacity threshold vs. domain-signup spike vs. usage-cap), current ARR, plan tier, expected upsell size; (4) post Slack DM to the AE owner. If the account has no assigned AE, route to RevOps queue. Use the result of "Measure how full the plan is", "Find accounts near a limit".
- 04Track the expansion pipelineCompose an expansion pipeline dashboard: count of expansion signals per week (by trigger type: seat-cap / domain-signup / usage-cap), AE response time, expansion-task-to-deal-created conversion, expansion deal cycle time (typically 2-3x faster than new-logo deals), and expansion-deal win rate. ARR uplift from expansion signals YTD vs. target. Use the result of "Measure how full the plan is", "Find accounts near a limit", "Raise the expansion task".
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 /seat-expansion-signal-to-ae-task 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.
