Renewal Risk Briefing Loop

By Juan Beltrán, Industrial B2B AI Transformation Executive.

Is this renewal healthy, at risk, or quietly drifting? Use this before renewal reviews when the available evidence is scattered across notes, usage summaries, support themes, and seller judgment. Renewal Risk Briefing Loop Decision to make: Is this renewal healthy, at risk, or quietly drifting? Decision owner: Account owner, customer success lead, or revenue leader. Working-session setup: - Timebox: 30 min working session - People in the room: Revenue owner, account or CRM owner, and the person closest to the customer evidence. - Preparation: Focused prep: gather one page of context and the decision you need. Context: [Paste your notes, excerpts, draft, meeting transcript, CRM fields, proposal text, public research, or examples here.] Context I should provide: - Renewal date - Commercial history - Usage or adoption notes - Support issues - Stakeholders - Recent customer comments - Known objections Safety boundary: - Use only information I provide in this conversation. - Do not infer personal, confidential, regulated, pricing, customer, employee, or supplier facts. - If the material belongs in an approved enterprise environment, tell me before analyzing it. Instructions: Act as a renewal risk reviewer. Analyze the renewal context below. Classify the account as healthy, watch, at risk, or unknown. Show the evidence, assumptions, missing information, rescue actions, and escalation note. Run the session in this order: 0. Inspect the context. If a missing fact could materially change the recommendation, ask no more than five focused questions and wait. If I ask you to continue, mark each missing fact as unknown. 1. State the renewal context: Summarize renewal timing, value at stake, and current confidence level. 2. Classify the evidence: Group signals into value proof, adoption, relationship, support, budget, and competitive risk. 3. Find the evidence gaps: List what the team does not know but must know before calling the renewal healthy. 4. Choose rescue actions: Recommend account moves, executive outreach, proof work, or commercial options. 5. Write the escalation note: Draft a short internal note that states the risk without drama. Evidence rules: - Separate supplied facts, interpretations, assumptions, and unknowns. - Reference the exact note, excerpt, metric, or example supporting every material claim. - Show the strongest credible counterargument to the recommendation. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Do not turn missing evidence into a confident recommendation. - Keep the answer useful for Revenue Leader. Output contract: A renewal risk brief with health verdict, evidence, gaps, objections, and rescue actions. Return: 1. BLUF: the decision, recommendation, or draft in plain language. 2. Evidence table: claim, supplied evidence, confidence, and gap. 3. Assumption ledger: what is assumed and how to verify it. 4. Counterargument: the strongest reason the recommendation may be wrong. 5. Decision record: decision status, accountable owner, next action, and due date or trigger. 6. Evidence still needed: only the gaps that could change the decision. 7. Stop condition: state when the work is complete and when it must pause. Evidence checklist: - Renewal date - Value proof - Usage signal - Stakeholder support - Support risk - Next customer action Human operating ritual: - Do not call a renewal healthy because nobody complained. - Ask what the customer would say value means. - Escalate early when value proof is missing. Do not use this loop when: Do not use it to manufacture certainty when the team has no first-party customer or CRM evidence. Stopping condition: Stop when the renewal has a risk verdict, evidence gap list, and next customer move.

Canonical URL: https://juanbeltran.ch/operating-loops/renewal-risk-briefing-loop