Upgrade prompt when limits approach
Catches an account nearing its plan limits, shows the decision maker an upgrade inside the app, and calls an AE in on the bigger ones.
Authored by Sid Chaudhary
Founder & CEO at Intempt
Agentic workflow
Coming soon5 steps Blu runs end to end. It drafts a plan and nothing runs until you approve it.
- 1
Find the bottleneck limit
Coming soonBlu builds a step
- 2
Find accounts near a limit
Coming soonBlu builds a step
- 3
Write the in app prompt
Coming soonBlu builds a step
- 4
Prompt, then call in an AE
Coming soonBlu builds a step
- 5
Compare prompt against AE
Coming soonBlu builds a step
About this recipe
When to use it
By the time a renewal call happens, the moment a user actually felt the plan limit is long gone. This prompts right when the limit is approached, when intent is highest.
What it delivers
When a user approaches their plan's usage limit - API calls, contacts, seats, storage - triggers an in-app upgrade prompt and creates an AE task for high-MRR accounts.
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
“Catches an account nearing its plan limits, shows the decision maker an upgrade inside the app, and calls an AE in on the bigger ones.”
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.
- 01Find the bottleneck limitCreate an AI-derived attribute 'usage_capacity_used' on the Account object. For each metered usage dimension on the account's current plan (API calls / contacts / events / seats / storage / sends), compute current_usage / plan_limit as a fraction. Output: the maximum across all dimensions (the bottleneck), with which dimension is at threshold. Flag thresholds: 0.8 = approaching, 0.95 = near-limit, 1.0+ = over-limit (overage charges or service throttling).
- 02Find accounts near a limitBuild a segment 'Upgrade-ready accounts' capturing paying accounts where usage_capacity_used >= 0.8 AND the account isn't already on the highest plan AND no upgrade conversation occurred in last 30 days. Splits implicitly: (a) approaching (0.8-0.94) to in-app prompt, (b) near-limit (0.95-1.0) to in-app prompt + AE task, (c) over-limit to urgent AE task + customer notification. Use the result of "Find the bottleneck limit".
- 03Write the in app promptThis step builds a page. Generate in-app upgrade prompt content. Personalized to which dimension is approaching limit: 'You've used 84% of your monthly events on the Starter plan. Upgrade to Pro for 10x capacity + advanced reporting.' Include current usage stat, plan comparison, and a one-click upgrade CTA. Tone: helpful (we noticed) not pushy (we're charging you). Suppress display for users not in plan-decision-maker role (avoid spamming end users about upgrades they can't approve). Use the result of "Find accounts near a limit".
- 04Prompt, then call in an AECreate a workflow firing when usage_capacity_used crosses 0.8 (and on each subsequent threshold). Step sequence: (1) trigger in-app upgrade prompt for plan-decision-makers on the account; (2) for accounts with MRR > $500/month, create AE expansion task immediately (don't wait for prompt-clickthrough: these are high-value, deserve human outreach); (3) for over-limit cases, additionally send an email notification to billing-contact about overage; (4) emit upgrade_signal event for analytics tracking. Throttle: don't re-fire for the same account within 14 days even if it's still over threshold (avoid prompt fatigue). Use the result of "Find the bottleneck limit", "Find accounts near a limit", "Write the in app prompt".
- 05Compare prompt against AECompose an upgrade conversion dashboard: usage-trigger volume per week (accounts crossing 0.8 threshold), in-app-prompt-to-upgrade conversion rate, AE-task-to-upgrade conversion rate (for high-MRR cohort), ARR uplift from usage-based expansion this quarter, and median time from threshold-cross to upgrade-completed. Compare upgrade-via-prompt vs. upgrade-via-AE-outreach as motion-effectiveness signal. Use the result of "Find the bottleneck limit", "Find accounts near a limit", "Write the in app prompt", "Prompt, then call in an AE".
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-based-upgrade-trigger 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 