← Back to prompts
SalesAccount Executiveintermediate 30 min saved

Late-Stage Deal Close Plan

Turn late-stage opportunity data into a clear, evidence-based plan to reach a buying decision.

Customise & copy

Add the context you have. The prompt updates as you work.

Include the current stage, recent progress, target decision date, and any timeline pressure.

List each known stakeholder, role, influence, position, and level of engagement.

Include confirmed objections, unresolved concerns, dependencies, and anything that may delay the decision.

Paste the criteria, requirements, scoring factors, or evaluation checklist provided by the prospect.

List agreed actions, owners, dates, meetings, deliverables, and current completion status.

Live prompt

5 fields
Create a practical, evidence-based close plan for the late-stage opportunity using only the information provided below.

Deal status and timeline:
{{deal_status_timeline}}

Identified stakeholders and roles:
{{stakeholders}}

Known objections, risks, and blockers:
{{risks_objections_blockers}}

Prospect's decision criteria or evaluation checklist:
{{decision_criteria}}

Committed next steps and follow-up agreements:
{{commitments}}

Use this exact output structure:

## 1. Close Assessment
State the current stage, decision readiness, timeline pressure, and the most important gap to resolve. Base every point on the provided information. Identify unknowns rather than filling them in.

## 2. Decision Criteria
For each criterion, include: criterion, evidence of status, remaining gap, and action required. Clearly label criteria with insufficient evidence.

## 3. Stakeholders
For each stakeholder, include: name or role, influence in the decision, current position if known, concern or need, and engagement action. Do not infer personal motivations without evidence.

## 4. Dependencies
List internal or prospect-side dependencies that could delay or prevent a decision. For each, include the dependency, responsible party if known, required outcome, and target date if provided.

## 5. Risks and Blockers
For each risk or blocker, include: issue, evidence, likely impact on the deal, mitigation, owner, and deadline where available. Separate confirmed issues from unresolved possibilities.

## 6. Commitments
List every existing commitment, including the agreed action, owner, due date, completion status, and evidence or missing confirmation.

## 7. Action Plan
List the specific actions required to reach a decision, prioritized as Critical, High, or Medium. For each action, include the owner, deadline, intended outcome, and dependency. Use only owners and dates supplied in the inputs; otherwise write "Not specified".

## 8. Recommended Close Path
Give a concise sequence of the next three to five actions, ordered by dependency and urgency. Include the decision milestone that each action supports.

Keep the tone professional, direct, and free of hype. Do not provide generic sales advice. Do not fabricate facts, dates, owners, statistics, testimonials, external research, or stakeholder opinions. Do not assume access to tools or information outside the provided inputs. Make the plan usable after one light edit.

Proof before you use it

A real example

Tested on gpt-5.6-luna on 2026-09-09

{
  "commitments": "Seller will send room-planning drawings by July 18. Biomedical engineering will confirm site requirements by July 24. Finance will confirm budget availability before the August 5 committee meeting. Dr. Patel will present the clinical evaluation summary to the committee.",
  "stakeholders": "Dr. Aisha Patel, Chief of Radiology — clinical sponsor. Mark Lewis, Biomedical Engineering Manager — technical evaluator. Sandra Kim, Chief Operating Officer — final executive approver. Hospital purchasing committee — formal decision body. Omar Haddad, Finance Director — capital budget reviewer.",
  "decision_criteria": "Image quality for cardiac studies; compatibility with the hospital's imaging archive; room and power requirements; five-year service cost; installation schedule; clinician usability; vendor service response times.",
  "deal_status_timeline": "Late-stage capital equipment purchase for a hospital network's radiology department. The clinical evaluation is complete, and the committee intends to select a vendor at its August 5 meeting. Installation is tentatively planned for the fourth quarter.",
  "risks_objections_blockers": "Biomedical engineering needs confirmation that the equipment fits existing room specifications. Finance has not released the capital budget. Clinicians prefer the incumbent vendor's user interface. The committee requires a documented service-level agreement and uptime commitment."
}

A small ritual that works

How to use it

  1. 01Enter the current deal status, recent progress, target decision date, and timeline pressure.
  2. 02List known stakeholders, roles, influence, positions, concerns, and engagement.
  3. 03Add confirmed objections, risks, blockers, dependencies, and the prospect’s decision criteria.
  4. 04Paste committed next steps, owners, dates, deliverables, and completion status.

Why it works

This prompt turns several deal inputs into a structured close plan. It explicitly separates timeline, stakeholders, decision criteria, dependencies, risks, commitments, actions, and the recommended sequence, which helps the reader inspect each part of a late-stage opportunity without blending confirmed information with assumptions. Its evidence rules are especially useful: the instructions require unknowns to be identified, prohibit inferred motivations, and distinguish confirmed issues from unresolved possibilities. The repeated fields for owners, deadlines, evidence, dependencies, and intended outcomes also make the plan operational rather than purely descriptive. The final three-to-five-step close path then compresses the larger analysis into an ordered sequence tied to decision milestones.

Where it fails

It is less suitable when the available deal information is highly informal, fragmented, or lacks dates, owners, decision criteria, and explicit commitments. The requested structure remains usable in those situations, but many fields may need to be marked as unspecified or supported by insufficient evidence. It also cannot independently verify commercial, technical, legal, financial, or implementation claims because it is restricted to the supplied inputs and has no access to external systems or stakeholders.

Customisation tips

For more precise planning, provide dated facts rather than general status statements. In the deal timeline, include the current stage, target decision date, implementation deadline, and sources of timeline pressure. For stakeholders, identify decision authority, influence, known position, concern, and engagement status without adding inferred motivations. For decision criteria, preserve the prospect's exact requirements and indicate any acceptance conditions. For risks and commitments, include a clear owner, due date, current status, evidence, and dependency where available. If your sales process uses defined stages or approval gates, add those terms to the input conventions while keeping the output headings intact. You can also adapt the priority labels, decision milestones, or required action fields to match an internal methodology, provided the prompt continues to distinguish supplied facts from unknowns.

Watch-outs

  • The prompt requires an evidence-based plan, so vague inputs will lead to explicit uncertainty rather than filled-in assumptions.
  • A commitment, target date, or stakeholder role should not be treated as completed, approved, or influential unless the supplied information supports that interpretation.
  • The action plan allows only owners and dates provided in the inputs; otherwise, it directs the response to use "Not specified."
  • The structure asks for both risks and unresolved possibilities, so speculative concerns should be labeled separately from confirmed blockers.

Works in

ChatGPTClaudeGeminiMicrosoft Copilot

Was this useful?

Submit your variation

If your version helps, it may be published with your name and a link back to you.

Want to make AI useful across your team? Explore Atul's training.