QBR & Renewal Chain: Risk → Recovery → Review → Next Steps

What this chain helps you accomplish

Make a customer renewal review actionable: validate the evidence behind renewal health, identify genuine risk drivers, decide what the team can do about them, and prepare a customer-centered QBR that addresses value and unresolved problems before any expansion discussion.

Seven connected AI prompts build a Renewal Evidence & Account Health Register, a transparent Renewal Risk & Evidence Coverage Assessment, a 30-Day Renewal Protection Plan, a Renewal-Focused QBR Agenda & Tough-Question Brief, an Expansion Readiness & Opportunity Map, an attributable Post-QBR Commitments Record, and a Renewal Follow-Up & Account Action Plan. Each step requires seller review and approved prior outputs.

Rather than inventing a renewal probability, the chain uses an explicitly defined five-factor risk rubric and reports evidence coverage. Unknown signals are not treated as healthy or unhealthy. A renewal forecast remains a distinct finance/sales judgment informed by actual buyer, commercial and historical evidence, not an AI-created win percentage.

The final result helps a CSM and AE handle an at-risk renewal without concealing issues, present a credible business review, prepare for difficult questions, and explore adjacent needs only when customer outcomes and interest justify it. Promptifi supplies reusable instructions for the seller's own AI tool; it does not connect to customer systems, calculate live churn predictions, attend meetings, send messages, or execute retention plays.

When to use it

• Before a renewal-focused QBR or executive business review: You need a defensible account health picture, real customer outcomes, unresolved issue facts, and questions for an upcoming discussion.
• At a renewal planning checkpoint: The renewal is approaching, adoption has shifted, key stakeholders have changed, or the CSM and account team disagree about risk.
• When renewal risk is uncertain: Customer telemetry and relationship sentiment point in different directions, historical baselines are weak, or there is no evidence-based way to explain a Red/Yellow/Green label.
• For a customer recovery plan: Open support, value-realization, contract or stakeholder issues need concrete internal actions before any expansion request.
• For a potential expansion: The customer has expressed an adjacent need, but the CSM must evaluate readiness, feasibility and customer interest instead of automatically pushing an upsell.
• After the actual QBR: You need to separate what stakeholders actually said from what the team had hoped to accomplish, then prepare an accurate renewal follow-up.

Do not use it to fabricate a churn prediction, misrepresent usage as satisfaction, pressure a customer with an unsupported renewal deadline, invent executive support, produce an unapproved commercial offer, or calculate costs of delay from missing financial inputs.

The chain runs manually in an authorized text-capable AI tool. It is neither a scheduled monitoring system nor an automated CRM scoring rule. The suggested 30-day protection plan is a planning horizon; actions, dates and owners are conditional on actual customer and internal commitments.

Before you begin

Required tool: A text-capable organization-approved AI application such as ChatGPT, Claude, Gemini or equivalent. A paid plan, customer-success platform, CRM connector, browser, transcript integration or automated email sender is not required. You must paste authorized source material. If live browsing or connector access is unavailable, the AI cannot claim it examined a linked dashboard, contract or health report.

Fill the following placeholders before Prompt 1. Use the same names in the Starting Renewal Context; mark missing optional fields NONE or UNKNOWN. The post-QBR record is provided only after the actual meeting.

• {{CUSTOMER_ACCOUNT}} — Required. Account name and actual service/product relationship from the customer record. Example: Alderbay Medical Logistics, subscription for service ticket routing. If identity or scope is unclear, confirm internally before continuing.
• {{REVIEW_AND_RENEWAL_DATES}} — Required as a field; date may be unknown. QBR/review period, upcoming renewal date, timezone if relevant, documented notice/cancellation requirements, and current date used to assess timing. Example: Q3 2026 health review; contract renews March 31, 2027, notice period not verified. Source: current agreement/account record. Unknown deadlines must not be assumed.
• {{CONTRACT_ARR_AND_LICENSE_SCOPE}} — Optional but important. Actual current annual recurring revenue, currency, contract term, products/modules, seats, deployment and authorized commercial source. Example: $80,000 USD ARR per approved contract; 100 assigned seats. If missing, don't invent deal exposure, prices or renewal probability.
• {{CUSTOMER_GOALS_AND_BASELINE}} — Required for success claims; otherwise UNKNOWN. Original buyer-stated objectives, baseline/target values, customer success plan and actual source. Example: R1 — customer launch plan, April 2026 — reduce manual routing handoffs; no numerical target. If none, label goals unconfirmed and ask for validation.
• {{USAGE_AND_ADOPTION_DATA}} — Optional. Active user count, feature adoption, license utilization, comparison period, metric definition, numerator/denominator and source/date. Example: R2 — September telemetry — 60 monthly active users of 100 assigned. Never infer satisfaction or cash savings from raw login counts.
• {{DELIVERED_VALUE_AND_OUTCOMES}} — Optional. Customer-confirmed business results, operational outcomes, costs, baselines and validated comparisons. Example: R3 — customer note — weekly reporting takes less manual coordination, not quantified. If no comparable measurements exist, ROI NOT CALCULABLE FROM PROVIDED EVIDENCE.
• {{SUPPORT_AND_REMEDIATION}} — Optional but material. Open critical incidents, severity, dates, actual owner, SLA obligations and customer-accepted remediation plan where known. Example: R4 — support case SR-41 still open; engineering is investigating; target fix date unconfirmed. If missing, do not claim zero open cases.
• {{STAKEHOLDERS_AND_ENGAGEMENT}} — Optional. Verified sponsor/champion/economic buyer contacts, last meaningful customer interaction, source/date, stakeholder feedback, departures and risks. Example: R5 — CSM note, Oct. 2026 — primary admin engaged; decision-maker not identified. Do not infer approval power from job titles.
• {{COMPETITIVE_AND_COMMERCIAL_SIGNALS}} — Optional. Exact buyer mentions of alternatives, procurement/finance feedback, requests to reduce seats, budget status, notice/cancellation conversations, or documented renewal commitment. Example: R6 — buyer asked about a competing tool during October call; no intention to switch stated. If absent, UNKNOWN, not 'no competitor'.
• {{PREVIOUS_COMMITMENTS_AND_HEALTH_METHOD}} — Optional. Earlier customer promises, actual completion status, existing health score and its precise documented definition/weights. Example: R7 — internal health score 65/100 based on adopted rubric, last updated Oct. 25. If formula not known, treat it as an unvalidated external score—not a probability.
• {{ATTENDEES_AND_QBR_FORMAT}} — Required as a field; may be incomplete. Verified invited customer participants/roles, CSM/AE attendees, QBR objective, and actual planned duration. Example: Operations Director invited, VP Finance not confirmed; 45-minute discussion. If incomplete, make only a proposed agenda and avoid invented attendee names.
• {{APPROVED_PRODUCTS_AND_EXPANSION_CONTEXT}} — Optional. Current purchased capabilities, genuinely available expansion products, approved positioning, limitations, buyer-expressed adjacent goals and commercial rules. Example: second department mentioned as potential use case but not buyer requested. If missing, expansion is NOT QUALIFIED.
• {{SELLER_OWNERS_AND_AUTHORITY}} — Required. Named CSM/account owner where available, AE/renewal manager responsibilities, legal/pricing escalation owners, and what the team can legitimately offer. Example: CSM may propose a service review; discounts require sales leadership approval. If not known, do not assign commitments or quote concessions.
• {{DATA_SHARING_AND_COMMUNICATION_RULES}} — Required. Approved AI tool, confidentiality/recording policy, recipient status, suppression/contact rules, customer-sharing boundaries and legal/commercial review requirements. Example: use approved enterprise AI, redact contacts, no email sending without owner review. If unclear, do not share sensitive records or send drafts.
• {{ACTUAL_POST_QBR_NOTES}} — Required only for Prompt 6 after a real QBR. Authorized notes/transcript labeled Q1, Q2 etc. with actual speaker, date, direct-quote/paraphrase, feedback, concern, action acceptance and owner/date if confirmed. If no meeting occurred, write NOT YET AVAILABLE and stop after Prompt 5.

Source format: R1 — actual source/document/speaker — date and period — direct fact or faithful paraphrase — calculation/denominator and limits — customer-shareable or INTERNAL ONLY. Use Q1, Q2 after the meeting for real statements. Label VERIFIED RECORD, CUSTOMER-REPORTED, SELLER OBSERVATION, HYPOTHESIS and UNKNOWN separately. A customer quote is not independent verification of financial savings.

Risk scoring rules: The chain defines five internal concern factors—value realization, adoption, relationship/engagement, support/delivery, and renewal process/commercial conditions. The suggested rubric uses 0 = evidenced low concern, 1 = supported concern, 2 = supported material concern. Missing evidence is UNSCORED, never an automatic zero. Only rate a 0–10 full score when all five are evidenced; otherwise show observed points, coverage, individual signals and a qualified risk status. This is an explanatory triage aid, not a validated churn prediction. A directly reported cancellation/nonrenewal instruction or other verified urgent threat can require escalation regardless of incomplete scoring.

Financial data and date safety: ARR is contract exposure, not money automatically at risk; a rating is not forecast probability; if an exact notice deadline matters, verify the signed contract and calendar. No 'cost of waiting six months' without buyer-validated baseline, incremental benefit, timeframe and actual costs.

Privacy: Use a permitted AI environment. Redact confidential customer, financial, personal and legal information as necessary. Respect organizational rules and applicable law for recording/transcribing customer meetings. Never imply the AI has accessed CRM, ticketing or telemetry unless those sources were truly made available.

How to run the chain

1. Open one conversation in an approved text-capable AI tool. Fill and paste the Starting Renewal Context in Chain Steps, with current authorized R# source records and explicit UNKNOWNs.
2. Run Prompt 1 and audit every renewal date, product scope, customer outcome, usage metric and open issue. Correct unsupported values and approve the complete Renewal Evidence & Account Health Register.
3. Run Prompt 2 using the approved evidence register. Review its five-factor rubric, source IDs, coverage and any critical override. Separate account risk assessment from revenue forecast. Approve the complete Renewal Risk & Evidence Coverage Assessment.
4. Run Prompt 3 to prioritize three realistic internal actions for a 30-day renewal protection plan. Verify authority, owners and dependencies; do not promise a customer action without agreement. Approve the 30-Day Renewal Protection Plan.
5. Run Prompt 4 to create a renewal-focused QBR agenda and speaking brief, including uncomfortable but fair customer questions and measurable-value evidence. It must use the approved risk and remediation plans without revealing confidential scoring. Approve the QBR Agenda & Tough-Question Brief.
6. Run Prompt 5 to qualify up to three expansion opportunities or decide DEFER/NO VALIDATED EXPANSION. Approve the Expansion Readiness & Opportunity Map. Expansion must not displace necessary renewal recovery work.
7. Pause for the actual QBR. Capture lawful, permissioned Q# notes that distinguish actual customer feedback from the seller's planned talking points. Run Prompt 6 after the meeting and approve the Post-QBR Evidence & Commitment Record.
8. Run Prompt 7 with all six approved prior artifacts and actual Q# notes. Review the unsent customer email, internal renewal action tracker and updated risk stance before separately authorizing any external action.

Approval format: APPROVED — [Exact Artifact Name] — v1. Use this approved version as input in later prompts. For a revised artifact, request the complete v2, verify it, approve that version and rerun affected downstream prompts. The AI does not approve its own work.

One conversation is preferred. If the chat becomes too long, paste Starting Renewal Context, full latest approved prerequisites, exact R#/Q# evidence and current unresolved issues into a fresh chat. The optional handoff template is included in Chain Steps.

Important stop conditions: Unverified contract dates trigger contract review; missing evidence cannot yield a confident risk score; any open severe support incident must be addressed; no buyer agreement means action is PROPOSED; no customer interest means expansion is hypothetical. Do not run Prompts 6–7 as if a real QBR occurred when no Q# record exists.

Success: A credible internal renewal assessment, targeted recovery steps, customer-appropriate meeting material, an honest expansion decision and an accurate post-QBR action/email package. No messages, CRM updates, calendar events, renewal quotes or support ticket edits are performed by the prompts.