Deal risk identification before close

Identify late-stage deal risks before close and create a practical mitigation plan for each risk.
Sales - Closing - Deal risk identification before close

Who it's for

Sales managers, Account executives, RevOps teams, Founders, Deal desk teams

Get Ready

Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.

How to use this prompt

1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

Workflow Prompt

				
					You are a late-stage deal risk analyst. Your task is to identify risks that could prevent a sales opportunity from closing and create a practical mitigation plan before the seller makes the final push.

### Required Input
- Offer: [Describe what is being sold, e.g. "multi-location payroll software rollout"]
- Buyer Profile: [Describe the buyer and company, e.g. "CFO at a 300-person healthcare provider"]
- Current Deal Stage: [State current status, e.g. "commercial terms agreed, security review pending"]
- Target Close Date: [State expected close date, e.g. "by 31 July"]
- Deal Value and Importance: [State value or strategic importance, e.g. "$85,000 annual contract, key logo account"]
- Stakeholders and Roles: [List known stakeholders, e.g. "champion, CFO, HR lead, legal, procurement"]
- Decision Process: [Describe how approval happens, e.g. "finance approval then procurement and legal"]
- Known Concerns: [List stated objections or hesitation, e.g. "data security, implementation workload"]
- Recent Buyer Behaviour: [Describe activity, e.g. "champion responsive, legal delayed, CFO has not joined calls"]
- Competitive or Internal Alternatives: [Mention alternatives, e.g. "current provider renewal", "build internally", "competitor under review"]

### Input Validation
Review all inputs before identifying risks. If current stage, stakeholders, decision process, recent buyer behaviour, or known concerns are missing or too vague, ask specific clarification questions. Do not invent hidden risks without marking them as assumptions. Pause and wait for clarification.

### Instructions
Analyse the opportunity for risks that commonly appear before close. Consider buyer silence, weak champion access, missing economic buyer alignment, unclear decision process, procurement friction, legal delays, budget uncertainty, competitor pressure, implementation anxiety, changing priorities, and lack of urgency.

Separate confirmed risks from possible risks. For each risk, explain the evidence, why it matters, how serious it is, and what the seller should do next. The mitigation plan must be specific and action-oriented, not generic advice like "follow up" or "build value."

Prioritise risks by likely impact on close date and deal outcome. Include recommended language the seller can use to address the top risks with the buyer or internal team. If the deal appears less ready than assumed, state that clearly and recommend a safer next step.

### Output
Provide the final answer in this structure:

1. Deal Risk Summary
- Overall risk level
- Most likely reason the deal could slip or be lost
- Confidence level based on provided inputs

2. Risk Register
For each risk include:
- Risk
- Evidence
- Severity: Low, Medium, or High
- Likely impact
- Mitigation action
- Owner
- Deadline

3. Top 3 Immediate Actions
- Action
- Purpose
- Suggested wording

4. Buyer Conversation Script
- Short script to surface or resolve the highest-risk issue

5. Close Forecast Recommendation
- Commit, best case, pipeline, or at risk
- Explanation
				
			

Optional advanced instructions

				
					Add a red/yellow/green deal inspection summary for sales leadership.
				
			

Example output

1. Deal Risk Summary

Inputs used: Offer: multi-location payroll software rollout. Buyer: CFO at a 320-person healthcare provider. Stage: commercial terms agreed, security review pending. Target close: 31 July. Value: $88,000 annual contract, strategic healthcare logo. Stakeholders: HR Director champion, CFO economic buyer, IT security, legal, procurement. Decision process: CFO approval, then security, procurement, legal. Concerns: data security and implementation workload. Behavior: champion responsive, legal delayed, CFO has not joined calls. Alternatives: current provider renewal and competitor under review.

Overall risk level: High-medium.

Most likely reason for slip or loss: security/legal delay combined with weak direct CFO access.

Confidence level: Moderate-high because the provided buyer behavior shows specific late-stage risks.

2. Risk Register

  • Risk: CFO not directly engaged. Evidence: CFO has not joined calls. Severity: High. Impact: budget or priority surprise. Mitigation: request executive alignment call. Owner: AE. Deadline: this week.
  • Risk: Security review pending. Evidence: data security concern. Severity: High. Impact: close date slip. Mitigation: submit packet and hold IT review. Owner: solutions/security lead. Deadline: 3 business days.
  • Risk: Legal delayed. Evidence: legal has not progressed. Severity: Medium. Impact: signature delay. Mitigation: identify legal owner and review window. Owner: buyer procurement + AE. Deadline: next week.
  • Risk: Current provider renewal. Evidence: alternative exists. Severity: Medium. Impact: buyer defaults to safer incumbent. Mitigation: compare renewal risk and transition plan. Owner: AE. Deadline: before procurement.
  • Risk: Implementation workload anxiety. Evidence: stated concern. Severity: Medium. Impact: buyer delays rollout. Mitigation: implementation readiness session. Owner: implementation lead. Deadline: this week.

3. Top 3 Immediate Actions

  • Action: secure CFO call. Purpose: confirm executive priority. Wording: “To protect the July 31 target, can we include the CFO for 20 minutes to confirm business approval?”
  • Action: schedule security review. Purpose: remove highest technical blocker. Wording: “Can we get IT and our security lead together this week to resolve data questions?”
  • Action: confirm legal/procurement path. Purpose: avoid silent delay. Wording: “Who owns contract review, and when can redlines begin?”

4. Buyer Conversation Script

“The commercial terms appear aligned, but I do not want to assume the deal is close if security, legal, and CFO approval still need work. To protect the July 31 date, can we confirm the remaining approval path and bring the CFO and IT security into the next step?”

5. Close Forecast Recommendation

Forecast: At risk. The deal has strong value and commercial alignment, but lack of CFO access and unresolved security/legal steps make the close date uncertain.

When to reuse this workflow

You may also like...

🔒

Unlock the Full Workflow

Get access to this workflow and 1000+ others designed to save hours and get better results with AI.

No guesswork. Just proven systems.

  • Copy & paste ready prompts
  • Step-by-step instructions
  • Works with ChatGPT instantly

BANT-Based Discovery Call Qualification Script

Qualify leads using the BANT framework to determine fit, urgency, and readiness for sales progression.

Proof Points and Case Study Insertion

Strategically insert proof points and case studies into presentations to increase credibility.

Demo Customisation Framework

Customise demos based on prospect context to increase engagement and close rates.

Unlock the full library.

Get access to all workflows, across every sector, with structured systems built for better results.

Get Free Access