Renewal risk brief for account planning

Use one renewal brief per account, updated after every material customer interaction. It gives your account team a shared view of risk, expansion evidence, decision-makers and next actions before the renewal becomes urgent.

This process is for account managers and customer-facing sales teams handling renewals. It turns scattered evidence into a document that can be checked against the source material.

1. Create the brief before reviewing the account

Create a document called Renewal brief - [Account name] - [Renewal month]. Use the same headings for every account:

1. Renewal facts
2. Customer outcomes and usage
3. Support and delivery issues
4. Stakeholders and decision process
5. Risks
6. Expansion signals
7. Required actions
8. Renewal-period account plan
9. Evidence log

Add the renewal date, contract scope, account owner and internal renewal owner under Renewal facts. Leave unknown fields marked Unknown, rather than filling them with an assumption.

Set an evidence window that starts at the last renewal, or the start of the current contract if that is clearer. Include recent evidence first. An unresolved issue from two weeks ago normally matters more than a positive comment from nine months ago.

2. Gather the four evidence sets

Collect material in this order. Do not start by asking the model whether the account will renew. First give it a dated record.

1. Customer correspondence: emails, agreed follow-ups, messages about priorities, dissatisfaction, procurement and timing.
2. Usage signals: adoption trends, active teams, feature use, implementation progress and gaps against the intended use case.
3. Support and delivery issues: open cases, repeated problems, severity, promised fixes, missed dates and current status.
4. Meeting notes: business goals, objections, named stakeholders, budget comments, next steps and direct customer language.

Remove content that is unrelated to the account decision. Keep the message date and speaker where possible. If you handle customer data in an AI tool, follow your organisation's data handling rules and review the relevant xAI documentation, as available controls and limits are version-dependent.

Use a simple source label in front of each item, such as:

• Email, 14 May, Operations lead: "We still cannot produce the monthly report without manual work."
• Usage, week ending 17 May: regional team activity declined for three consecutive weeks.
• Support, 19 May: case remains open. Workaround supplied, permanent fix not confirmed.
• Meeting, 21 May, executive sponsor: expansion depends on proving adoption in two regions.

3. Ask for a structured extraction

Paste the evidence in manageable batches. Ask the model to extract facts into your headings, not to write a polished account story straight away.

Use this prompt:

Create a renewal-brief evidence table from the material below.

For each item, return:
- category: outcome, usage, support, stakeholder, risk, expansion, action or unknown
- factual claim
- source date and source type
- named person and role, if stated
- whether this is a direct customer statement, system signal or internal interpretation
- confidence: high, medium or low
- follow-up question needed

Do not infer a renewal decision. Do not merge separate events. Mark missing information as Unknown.

Review each batch before adding it to the document. Then ask for consolidation:

Using only the checked evidence table, draft these sections:
1. risks
2. expansion signals
3. decision-makers and decision process
4. required actions with owner and due date

For every risk and expansion signal, include the supporting source date. Separate facts from interpretations. List contradictions and missing evidence at the end.

4. Rate risks and assign actions

For each risk, write one row with four fields: evidence, impact, next action and owner. Avoid vague mitigations such as improve relationship.

If the evidence shows	Record the risk as	Required action
A senior sponsor has not attended recent meetings	Executive alignment is unconfirmed	Ask the day-to-day contact to confirm the sponsor's role and arrange a value review
Usage is falling in a contracted team	Adoption may not support current scope	Identify the affected group, the adoption blocker and a recovery owner
A critical support issue is unresolved	Product or service confidence may be damaged	Get a dated status from the responsible team and agree customer communication
Procurement asks for dates or paperwork	Renewal process has started	Confirm the procurement path, commercial owner and decision date

Give each action one accountable person and a date. If the action depends on another team, name both the accountable owner and the dependency. Support to resolve issue is not an action. Account manager to obtain support status by Thursday, then send the agreed update to the customer is one.

5. Write the renewal-period account plan

Turn the checked brief into a short plan for the period leading to renewal and the period immediately after it. Use four parts:

• Customer outcome: the result the customer needs to demonstrate or achieve.
• Relationship plan: who needs contact, why they matter and the next conversation.
• Value plan: evidence you will assemble to show outcomes, adoption or operational benefit.
• Risk plan: the two or three risks that need active management, with actions and review dates.

Keep expansion separate from renewal protection. An expansion signal is not a forecast. For example, an executive asking about another region is a signal. It becomes a qualified opportunity only after you confirm need, stakeholders, process and timing.

Update the brief after every customer meeting, major support change or material usage movement. At the weekly account review, read the actions first, then check whether the evidence still supports each risk. This prevents an old summary becoming the team's account truth.

Check for false confidence

The output is probably wrong when it makes a precise claim with no dated source, treats internal opinion as customer commitment, or names a decision-maker who has not been confirmed. It is also suspect when every issue is labelled a risk but none has an owner or due date.

Test the brief with these questions:

• Can you point to evidence for each renewal risk?
• Does each claimed stakeholder have a stated role, or is the role an assumption?
• Are open support issues current, resolved or merely absent from recent notes?
• Does the account plan address the customer's stated outcome, not only your internal renewal target?
• Could another account manager run the next customer conversation from this document?

When the brief does not work

If the model produces generic risks, stop refining the wording. Add missing dated evidence, especially direct customer statements and current issue status, then repeat the extraction step. If the source material contradicts itself, preserve both statements and assign an owner to resolve the conflict with the customer or internal team.

If you cannot identify the decision process, make that your first required action. Do not fill the gap with a forecast judgement. A brief with an explicit Unknown is more useful than one that gives the account team a false sense of certainty.