B2B contract renewal
For B2B accounts approaching contract end, run a renewal journey at 90, 60, and 30 days to the enrolled profile.
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 renewals inside 90 days
Coming soonBlu builds a step
- 2
Read the renewal health
Coming soonBlu builds a step
- 3
Write one email per role
Coming soonBlu builds a step
- 4
Reach each stakeholder in turn
Coming soonBlu builds a step
- 5
Forecast the renewal book
Coming soonBlu builds a step
About this recipe
When to use it
A renewal reminder sent to one contact ignores that most B2B renewals involve a buyer, a champion, and an economic buyer, each needing different messaging. This reaches all three, staged by days-to-renewal.
What it delivers
For B2B accounts approaching contract end (90/60/30 days out), fires a multi-stakeholder renewal journey reaching the buyer, the user-champion, and the economic-buyer with role-appropriate messaging.
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
“For B2B accounts approaching contract end, run a renewal journey at 90, 60, and 30 days to the enrolled profile.”
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 renewals inside 90 daysBuild a segment 'Upcoming B2B contract renewals - next 90 days' capturing accounts where contract_end_date is between 30 and 90 days from now AND account_tier is enterprise or mid-market AND subscription_status is active. Each account in the segment has multiple touched users, the journey reaches different contacts at the account with role-appropriate messaging.
- 02Read the renewal healthCreate an AI-derived attribute 'renewal_health_snapshot' on the Account object, computed at renewal-window entry. Aggregates: (a) usage trajectory over past 12 months (growing / flat / declining); (b) value delivered (key outcomes, milestones reached, ROI metric if tracked); (c) stakeholder health: champion still in role and engaged? economic buyer reachable? new stakeholders identified?; (d) support ticket sentiment over past 6 months; (e) competitor mentions in any meeting summaries. Output: composite health score + structured content for the renewal emails. Use the result of "Find renewals inside 90 days".
- 03Write one email per roleThis step builds a designed marketing email (HTML). Generate role-tailored renewal content. (a) User-champion (Day 90): 'Quick value-recap of the past year (what's working and what's next') focuses on product wins, usage stats, asks for help to coordinate the upcoming renewal conversation. (b) Economic buyer (Day 60): 'Your team's renewal is up in 60 days (let's connect on terms') focuses on business value, ROI, growth opportunity, available terms. (c) IT/security stakeholder if known (Day 60): 'Security/compliance update for your upcoming renewal': proactive on documentation, certifications, any changes. (d) Late reminder (Day 30): consolidated reminder to all stakeholders with proposed contract terms attached. Tone: business-formal, value-substantive, not marketing-chatty. Use the result of "Find renewals inside 90 days", "Read the renewal health".
- 04Reach each stakeholder in turnBuild a multi-touch multi-stakeholder journey triggered at renewal-window entry. Each touch goes to a DIFFERENT contact at the account based on their role: Touch 1 (Day 90 before contract_end): champion. Touch 2 (Day 60): economic buyer. Touch 3 (Day 60, parallel): IT/security if applicable. Touch 4 (Day 30): all stakeholders. Add a renewal-meeting-scheduled branch: if CSM/AE schedules a renewal meeting at any point, journey pauses (human-led from here). For high-risk accounts (renewal_health composite low or any churn signal), additionally create urgent CSM task at Day 90: automation alone won't save at-risk renewals. Use the result of "Find renewals inside 90 days", "Read the renewal health", "Write one email per role".
- 05Forecast the renewal bookCompose a B2B renewal pipeline dashboard: renewal forecast by quarter (account count + ARR at risk), renewal health distribution (green/yellow/red), days-to-renewal pipeline (which renewals are coming up when), CSM/AE engagement rate (% of renewals where a human conversation happened: target: 100% for accounts >$50K ARR), expansion-during-renewal rate (renewals that grow vs. flat vs. shrink), and renewal-rate trend over time. The strategic view that gives leadership confidence in NRR. Use the result of "Find renewals inside 90 days", "Read the renewal health", "Write one email per role", "Reach each stakeholder in turn".
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 /contract-renewal-b2b 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 