Mutual action plan for closing

Build a mutual action plan that maps buyer and seller steps from agreement to signed close.
Sales - Closing - Mutual action plan for closing

Who it's for

Account executives, Sales managers, Founders, RevOps teams, 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 sales deal execution planner. Your task is to create a mutual action plan that helps the buyer and seller move from verbal interest to a clear signed close.

### Required Input
- Offer: [Describe what is being sold, e.g. "annual analytics platform subscription with onboarding"]
- Buyer Profile: [Describe buyer company and role, e.g. "COO at a 200-person ecommerce business"]
- Target Close Date: [State desired close date, e.g. "by 30 June", "before next board meeting"]
- Current Deal Stage: [Explain where the deal stands, e.g. "proposal accepted in principle, legal review not started"]
- Stakeholders: [List buyer and seller stakeholders, e.g. "economic buyer, IT, legal, finance, implementation lead"]
- Required Approval Steps: [List known steps, e.g. "security review, procurement, contract redlines, finance approval"]
- Key Risks or Blockers: [List possible delays, e.g. "legal availability, unclear procurement timeline"]
- Buyer Success Outcome: [State what the buyer wants after purchase, e.g. "launch dashboard before quarterly planning"]
- Tone: [Choose tone, e.g. "structured, collaborative, professional"]

### Input Validation
Review the inputs before creating the plan. If target close date, stakeholders, approval steps, current stage, or key risks are missing or unclear, ask specific clarification questions. Do not create a fictional action plan based on unknown approvals. Pause and wait before producing the final output.

### Instructions
Create a mutual action plan that is practical enough to send to a buyer or use internally. The plan must connect the target close date to the buyer's desired success outcome, then work backward through the steps required to reach signature.

Identify every major milestone needed to close the deal. Include buyer responsibilities, seller responsibilities, decision points, dependencies, and risks. Make sure the plan does not assume the buyer will do all the work. The seller should own preparation, follow-up, documentation, and coordination where appropriate.

Build a realistic timeline. If the provided close date seems too aggressive based on the number of approval steps, flag the risk and suggest a revised path. Include checkpoints for confirming stakeholder alignment, legal/procurement progress, commercial agreement, and implementation readiness.

Create language the seller can use to introduce the mutual action plan to the buyer. It should position the plan as a way to reduce friction and protect the buyer's desired timeline, not as a pressure tactic.

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

1. Closing Objective
- Buyer outcome
- Target close date
- Why the timeline matters

2. Mutual Action Plan Table
For each milestone include:
- Step
- Owner
- Due date or timing
- Dependency
- Output required
- Risk if delayed

3. Buyer Introduction Message
- Short email or call script explaining the plan

4. Risk and Dependency Notes
- List the top risks to the close
- Recommended mitigation for each

5. Internal Seller Checklist
- Actions the seller should complete before each milestone

6. Revised Timeline Warning
- Include only if the requested close date appears unrealistic.
				
			

Optional advanced instructions

				
					Add a version formatted for enterprise deals with legal, procurement, security, and finance stages.
				
			

Example output

1. Closing Objective

Inputs used: Offer: annual analytics platform subscription with onboarding. Buyer: COO at a 220-person ecommerce business. Target close: by 15 May. Stage: proposal accepted in principle, legal review not started. Stakeholders: COO economic buyer, IT lead, finance manager, legal counsel, seller AE, seller implementation lead. Approval steps: security review, procurement intake, contract redlines, finance approval. Risks: legal availability and unclear procurement timeline. Buyer outcome: launch dashboard before quarterly planning. Tone: structured, collaborative, professional.

Buyer outcome: launch analytics dashboard before quarterly planning.

Target close date: 15 May.

Why timeline matters: onboarding takes four weeks, so signature after 15 May puts the dashboard launch at risk.

2. Mutual Action Plan Table

  • Step: Confirm commercial scope. Owner: AE + COO. Timing: this week. Dependency: proposal acceptance. Output: final scope. Risk: legal reviews wrong version.
  • Step: Security packet submitted. Owner: seller + IT lead. Timing: within 2 business days. Dependency: IT questionnaire. Output: completed security response. Risk: IT delays approval.
  • Step: Procurement intake. Owner: finance manager. Timing: same week. Dependency: vendor documents. Output: procurement file opened. Risk: unclear process.
  • Step: Contract redlines. Owner: legal + seller contracts. Timing: week 2. Dependency: legal availability. Output: redlined agreement. Risk: close slips.
  • Step: Finance approval. Owner: COO + finance. Timing: after terms agreed. Dependency: final pricing. Output: budget approval. Risk: surprise cost concern.
  • Step: Signature and kickoff scheduling. Owner: COO + AE. Timing: by 15 May. Dependency: legal and finance complete. Output: signed order and kickoff date. Risk: dashboard launch delayed.

3. Buyer Introduction Message

“To protect your goal of launching the dashboard before quarterly planning, I suggest we use a simple mutual action plan. It is not meant to create pressure; it just makes the approval steps, owners, and dates visible so nothing slips unexpectedly.”

4. Risk and Dependency Notes

  • Legal delay: book legal review window now.
  • Procurement ambiguity: ask finance to confirm required documents.
  • Security delay: submit packet before contract redlines finish.
  • Implementation readiness: involve seller implementation lead before signature.

5. Internal Seller Checklist

  • Prepare final proposal, security packet, vendor forms, contract draft, implementation timeline, and finance summary.
  • Confirm buyer-side owners for legal, procurement, IT, and finance.
  • Track every milestone in CRM with dates and owner.

6. Revised Timeline Warning

The 15 May close is achievable only if security and procurement begin immediately. If legal review cannot start within one week, revise the target close or adjust the dashboard launch expectation.

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.

Presentation Objection Anticipation

Prepare for likely objections before a sales presentation to improve confidence and outcomes.

Unlock the full library.

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

Get Free Access