# Mutual Action Plan Builder

Create a buyer-and-seller action plan with shared milestones, owners, evidence, dependencies, and decision gates instead of a seller-only close schedule.

## Prompt

You are a complex-sales project manager who specializes in transparent mutual action plans for buyer decisions and implementation readiness.

Inputs:
1. Buyer objective, desired decision date, and success outcome: {{buyer_goal}}
2. Current opportunity stage and completed validation: {{current_state}}
3. Buyer and seller stakeholders with responsibilities: {{participants}}
4. Required evaluations, approvals, procurement, and implementation steps: {{decision_process}}
5. Timing, dependencies, risks, and communication constraints: {{constraints}}

Do the following:
1. Work backward from the buyer’s target outcome, distinguishing the decision date, contract date, implementation start, and value-realization milestone.
2. Convert the decision process into shared milestones with clear purpose, owner, due date, dependencies, completion evidence, and explicit buyer benefit.
3. Identify missing participants, unrealistic timing, hidden approval gates, holiday or resource conflicts, and milestones that exist only to satisfy the seller.
4. Add decision checkpoints, change-control rules, risk triggers, and a respectful process for pausing or revising the plan when the buyer’s priorities change.
5. Produce a customer-ready action-plan table, critical-path summary, immediate next commitments, email introducing the plan, and CRM version. Do not invent buyer agreement or present seller target dates as mutual commitments.

## Best for

B2B sales teams coordinating evaluations, approvals, procurement, and implementation with buyers across a complex decision process.

## Compatible tools

- Claude
- ChatGPT

## How to use

- Start from the buyer’s operational outcome.
- Verify owners and dates with the buyer.
- Separate decision, contract, implementation, and value dates.
- Update the plan jointly when dependencies change.

## Customization tips

- Include completion evidence for each milestone.
- Account for legal, security, and resource calendars.
- Remove seller-only activities from the customer version.
- Treat unconfirmed dates as proposed, not agreed.

## Example input

Buyer goal: Launch a new supplier-risk process before January 15. Current state: business workshop complete; security, data-processing review, commercial approval, and implementation planning remain. Participants: procurement director owns business case, information-security lead owns technical review, privacy counsel owns DPA, vendor team owns security evidence and project plan. Constraints: buyer legal team is unavailable December 20-January 5; implementation requires six weeks; desired go-live is more important than signing in December.

## Example output

Working backward from January 15 shows implementation must start by December 4, making a late-December signature incompatible with the buyer goal. The plan places security evidence by October 18, security decision by November 1, DPA redlines by November 8, commercial approval by November 22, and contract completion by November 29. Each milestone includes buyer benefit and completion evidence. Missing implementation ownership is flagged for confirmation rather than assigned without agreement.