mutual-action-plan-builder

name	mutual-action-plan-builder
description	Build mutual action plans for complex deals and coordinated customer initiatives. Use when asked to create or improve a MAP, align buyers and sellers on milestones, or define stage-based execution with owners and dates. For proposal or RFP process orchestration, use proposal-rfp-orchestrator.

Mutual Action Plan Builder

Create a shared plan with the customer that makes owners, milestones, and success criteria explicit.

Confirm Inputs First

Collect the minimum required inputs:

• Whether a current revenue-enablement-context exists; if yes, use it as baseline assumptions, if no, capture only the highest-impact missing context.
• Target outcome and target date
• Current stage and major dependencies
• Internal and customer-side stakeholders
• Required milestones and approvals
• Known risks and blockers

If critical inputs are missing, ask for the smallest missing set. If the user prefers speed, proceed with labeled assumptions.

Read The Right Reference

• For MAP fields, milestone quality, and gating definitions, read references/map-framework.md.

Default Workflow

1. Anchor on target outcome. Define the concrete outcome the plan must deliver and by when.

2. Reverse-map milestones. Work backward from the target date and list the milestones needed to get there.

3. Assign shared ownership. Set internal and customer owners for each milestone. Make dependencies and handoffs explicit.

4. Add risk controls. Attach risk signals, mitigation actions, and escalation triggers to critical milestones.

5. Validate mutuality. Make sure the plan is not seller-only. Confirm customer commitments and required artifacts are clear.

6. Split customer-visible and internal-private views. Keep shared commitments in the customer-facing MAP and move internal risk commentary, negotiation strategy, and contingency notes to an internal companion view.

Tool Notes

• CRM can hold MAP status and owner fields when available.
• Docs/Sheets can act as the living source of truth shared with the customer.
• Project tools can help manage due dates and reminders.

Keep workflow tool-agnostic when these systems are unavailable.

Output Contract

Deliver:

1. Plan summary (target outcome, date, stage)
2. Stakeholder and owner map
3. Milestone table with entry/exit criteria
4. Dependency and handoff map
5. Risk and escalation plan
6. Customer-visible MAP view
7. Internal-private MAP view
8. Immediate next actions (next 14 days)
9. Open questions and assumptions

Quality Bar

• Ensure each milestone has an owner, due date, and clear completion criteria.
• Make customer-side actions explicit, not implied.
• Keep sequencing realistic and dependency-aware.
• Include escalation logic for high-risk milestones.
• Keep internal-only commentary out of customer-visible outputs.
• Do not fabricate customer commitments or approval timelines.