Synthesize a deal review prep narrative

intermediateClaude SonnetSalesAesalesdeal-reviewforecastingpipelineae

Use case

Use this before forecast calls or pipeline reviews when you need to walk leadership through a deal in 2 to 3 minutes without rambling. Most deal reviews fall apart because the AE narrates the deal chronologically. This prompt forces a structured narrative that ends with a clear ask, which is what leadership actually wants.

The prompt

You are a senior sales coach prepping an AE for a deal review with sales leadership. Synthesize a 2-to-3-minute spoken narrative the AE can use, plus a 1-page written summary.

Deal context:
- Company: {{company_name}}
- Deal size: {{deal_size}}
- Stage: {{stage}}
- Forecast category: {{forecast_category}} (commit, best case, pipeline)
- Original close date: {{original_close}}
- Current close date: {{current_close}}
- What has been tested or validated: {{tested}}
- What has not been tested: {{untested}}
- Stakeholders engaged: {{stakeholders_engaged}}
- Stakeholders not yet engaged: {{stakeholders_missing}}
- Known risks: {{risks}}
- Specific ask from leadership: {{ask}}

Output two artifacts:

1. Spoken narrative (250 to 350 words) structured as:
   - Where the deal stands in 1 sentence
   - 2 to 3 sentences on what has been validated and how
   - 2 to 3 sentences on what is at risk and what would push the date
   - 1 to 2 sentences on the specific ask

2. 1-page written summary in this format:
   - Header: company, size, stage, forecast category, close date (with slip flag if relevant)
   - Bullets: validated, unvalidated, engaged, missing, top 3 risks, the ask

Rules:
- No chronology. Never start with "we got introduced in March."
- No hedging language ("things are looking pretty good"). Leadership wants probability and risk.
- End with the ask. Always.
- If the deal has slipped, name it explicitly in the first sentence.

Variables

{{{{company_name}}}}Replace with your {{company name}}
{{{{deal_size}}}}Replace with your {{deal size}}
{{{{stage}}}}Replace with your {{stage}}
{{{{forecast_category}}}}Replace with your {{forecast category}}
{{{{original_close}}}}Replace with your {{original close}}
{{{{current_close}}}}Replace with your {{current close}}
{{{{tested}}}}Replace with your {{tested}}
{{{{untested}}}}Replace with your {{untested}}
{{{{stakeholders_engaged}}}}Replace with your {{stakeholders engaged}}
{{{{stakeholders_missing}}}}Replace with your {{stakeholders missing}}
{{{{risks}}}}Replace with your {{risks}}
{{{{ask}}}}Replace with your {{ask}}

Example

Input

company_name: Vantage Systems
deal_size: $420K ARR
stage: in procurement
forecast_category: commit
original_close: end of Q2
current_close: mid-Q3
tested: technical eval passed, security review approved, 2 reference calls completed
untested: CFO has not signed off on multi-year vs annual term, legal redlines outstanding on data residency clause
stakeholders_engaged: VP Operations (champion), CIO (sponsor), procurement lead
stakeholders_missing: CFO has not been on a call with us yet
risks: data residency clause, CFO timing, competing priorities at fiscal year end
ask: VP Sales to do a 20-minute exec align with the CFO this week

Output

Spoken narrative:

Vantage is a $420K commit that has slipped from end of Q2 to mid-Q3, driven by procurement timing and a CFO we have not yet engaged. Technical eval passed clean — performance benchmarks landed above their threshold and the SE called it the smoothest eval he ran this quarter. Security review came back approved on the first pass, and we ran two reference calls with peers in their segment, both of which the champion described as decisive. So the value and the technical fit are not in question.

Two things are at risk. The CFO has not been on a call with us, and we are now in a multi-year term discussion that needs his blessing. The legal team has flagged a data residency clause we need to negotiate, which historically adds 5 to 7 business days. If both slip together, we are looking at end of Q3, not mid-Q3.

The ask: I need our VP Sales to do a 20-minute exec align with the CFO this week. The champion has offered the intro and is waiting on us. If we get that meeting on the calendar by Friday, the mid-Q3 commit holds. If we miss it, I am moving this to best case.

Written summary:

Vantage Systems — $420K ARR — Procurement — Commit — Close: mid-Q3 (slipped from end of Q2)

Validated:
- Technical eval passed
- Security review approved
- 2 reference calls completed

Unvalidated:
- CFO sign-off on term length
- Legal redlines on data residency

Engaged: VP Operations (champion), CIO (sponsor), procurement lead
Missing: CFO

Top 3 risks:
1. CFO not yet engaged — biggest risk to current close date
2. Data residency clause adds 5 to 7 days to legal cycle
3. Fiscal year end competing priorities

Ask: VP Sales to do a 20-minute exec align with the CFO this week. Champion has the intro ready.

Tips for best results

1Forecast calls are not storytelling sessions. Lead with stage, size, category, close date — leadership orients on those four things.
2If the deal has slipped, name it in the first sentence. Trying to hide a slip is the fastest way to lose credibility with your manager.
3Always end with a specific ask. 'I need X person to do Y by Z.' Without it, the deal review was not actually a review.
4Validated vs unvalidated is the most useful frame for sales leaders. It maps directly to risk and to where they can help.
5Run this prompt the night before forecast call. Read the spoken version out loud once. If it feels long, cut the validated section first — leadership cares more about risk.

Related prompts

Write a cold outbound email to a VP of Sales

intermediate

Generate a revenue-focused cold email to a sales leader that speaks their language: quota, pipeline, and rep productivity.

Salesoutboundemailcold-outreach

Draft a mutual action plan for a live deal

advanced

Draft a mutual action plan (MAP) tailored to deal stage with milestones, owners on both sides, dates, dependencies, and a clear path to signature.

Salessalesmutual-action-plandeal-management

Prep a renewal conversation with risk and expansion signals

intermediate

Prep a renewal conversation using usage data, sentiment signals, and an expansion hypothesis, with risk flagging and a proposed agenda.

Salessalesrenewalcustomer-success

Need help implementing this prompt in your workflow?

Book a call

Use case

You are a senior sales coach prepping an AE for a deal review with sales leadership. Synthesize a 2-to-3-minute spoken narrative the AE can use, plus a 1-page written summary. Deal context: - Company: {{company_name}} - Deal size: {{deal_size}} - Stage: {{stage}} - Forecast category: {{forecast_category}} (commit, best case, pipeline) - Original close date: {{original_close}} - Current close date: {{current_close}} - What has been tested or validated: {{tested}} - What has not been tested: {{untested}} - Stakeholders engaged: {{stakeholders_engaged}} - Stakeholders not yet engaged: {{stakeholders_missing}} - Known risks: {{risks}} - Specific ask from leadership: {{ask}} Output two artifacts: 1. Spoken narrative (250 to 350 words) structured as: - Where the deal stands in 1 sentence - 2 to 3 sentences on what has been validated and how - 2 to 3 sentences on what is at risk and what would push the date - 1 to 2 sentences on the specific ask 2. 1-page written summary in this format: - Header: company, size, stage, forecast category, close date (with slip flag if relevant) - Bullets: validated, unvalidated, engaged, missing, top 3 risks, the ask Rules: - No chronology. Never start with "we got introduced in March." - No hedging language ("things are looking pretty good"). Leadership wants probability and risk. - End with the ask. Always. - If the deal has slipped, name it explicitly in the first sentence.

Variables

{{{{company_name}}}}Replace with your {{company name}}

{{{{deal_size}}}}Replace with your {{deal size}}

{{{{stage}}}}Replace with your {{stage}}

{{{{forecast_category}}}}Replace with your {{forecast category}}

{{{{original_close}}}}Replace with your {{original close}}

{{{{current_close}}}}Replace with your {{current close}}

{{{{tested}}}}Replace with your {{tested}}

{{{{untested}}}}Replace with your {{untested}}

{{{{stakeholders_engaged}}}}Replace with your {{stakeholders engaged}}

{{{{stakeholders_missing}}}}Replace with your {{stakeholders missing}}

{{{{risks}}}}Replace with your {{risks}}

{{{{ask}}}}Replace with your {{ask}}

Example

Input

company_name: Vantage Systems
deal_size: $420K ARR
stage: in procurement
forecast_category: commit
original_close: end of Q2
current_close: mid-Q3
tested: technical eval passed, security review approved, 2 reference calls completed
untested: CFO has not signed off on multi-year vs annual term, legal redlines outstanding on data residency clause
stakeholders_engaged: VP Operations (champion), CIO (sponsor), procurement lead
stakeholders_missing: CFO has not been on a call with us yet
risks: data residency clause, CFO timing, competing priorities at fiscal year end
ask: VP Sales to do a 20-minute exec align with the CFO this week

Output

Spoken narrative:

Vantage is a $420K commit that has slipped from end of Q2 to mid-Q3, driven by procurement timing and a CFO we have not yet engaged. Technical eval passed clean — performance benchmarks landed above their threshold and the SE called it the smoothest eval he ran this quarter. Security review came back approved on the first pass, and we ran two reference calls with peers in their segment, both of which the champion described as decisive. So the value and the technical fit are not in question.

Two things are at risk. The CFO has not been on a call with us, and we are now in a multi-year term discussion that needs his blessing. The legal team has flagged a data residency clause we need to negotiate, which historically adds 5 to 7 business days. If both slip together, we are looking at end of Q3, not mid-Q3.

The ask: I need our VP Sales to do a 20-minute exec align with the CFO this week. The champion has offered the intro and is waiting on us. If we get that meeting on the calendar by Friday, the mid-Q3 commit holds. If we miss it, I am moving this to best case.

Written summary:

Vantage Systems — $420K ARR — Procurement — Commit — Close: mid-Q3 (slipped from end of Q2)

Validated:
- Technical eval passed
- Security review approved
- 2 reference calls completed

Unvalidated:
- CFO sign-off on term length
- Legal redlines on data residency

Engaged: VP Operations (champion), CIO (sponsor), procurement lead
Missing: CFO

Top 3 risks:
1. CFO not yet engaged — biggest risk to current close date
2. Data residency clause adds 5 to 7 days to legal cycle
3. Fiscal year end competing priorities

Ask: VP Sales to do a 20-minute exec align with the CFO this week. Champion has the intro ready.

Tips for best results

1Forecast calls are not storytelling sessions. Lead with stage, size, category, close date — leadership orients on those four things.

2If the deal has slipped, name it in the first sentence. Trying to hide a slip is the fastest way to lose credibility with your manager.

3Always end with a specific ask. 'I need X person to do Y by Z.' Without it, the deal review was not actually a review.

4Validated vs unvalidated is the most useful frame for sales leaders. It maps directly to risk and to where they can help.

5Run this prompt the night before forecast call. Read the spoken version out loud once. If it feels long, cut the validated section first — leadership cares more about risk.