Document
Mutual Action Plan Document
A shared document template for aligning buyer and seller on the steps to close. Includes milestones, owners, dates, and success criteria — auto-populated by your AI agent from deal context.
Overview
A Mutual Action Plan (MAP) is a shared document between buyer and seller that maps out every step from evaluation to go-live. It creates accountability on both sides and prevents deals from stalling in "we'll get back to you" limbo. This template generates a pre-filled MAP based on your deal data.
💡 When to introduce the MAP
Introduce the MAP after your champion has confirmed interest but before the formal evaluation begins. The act of co-creating a timeline signals commitment and reveals hidden blockers (legal review timelines, budget cycles, competing priorities) early — when you can still influence them.
Template Structure
1. Deal Overview
Account name, deal name, key stakeholders from both sides, and target close date.
- AI Instruction: "Pull account name, deal name, close date, and key contacts from the deal and account records."
- Data source: CRM deal record, account record, contact records
2. Evaluation Milestones
A table of milestones with dates, owners, and status: discovery → demo → technical evaluation → POC → security review → business case → procurement → signature.
- AI Instruction: "Generate a milestone table based on the deal stage, close date, and typical evaluation timeline for this segment. Pre-fill completed milestones from activity history."
- Data source: Deal stage, activity history, meeting notes
3. Success Criteria
What both parties agree "success" looks like — specific, measurable outcomes that justify moving forward.
- AI Instruction: "Summarize the success criteria discussed in discovery and demo calls. Format as a numbered list of measurable outcomes."
- Data source: Discovery call transcripts, demo follow-up notes
4. Technical Requirements
Integration needs, security requirements, deployment preferences, and any technical blockers identified.
- AI Instruction: "List technical requirements mentioned in calls — integrations, compliance certifications, data residency, SSO, API access. Flag any unresolved items."
- Data source: Technical call notes, SE notes, security review discussions
5. Commercial & Legal
Pricing proposal reference, contract terms to negotiate, procurement contacts, and legal timeline.
- AI Instruction: "Reference the pricing proposal and note any commercial terms discussed. Identify procurement contacts and estimated legal review timeline."
- Data source: Deal record, pricing proposal, procurement discussions
6. Go-Live Plan
Post-signature implementation timeline: onboarding, data migration, training, and first-value milestone.
- AI Instruction: "Outline a standard implementation timeline based on the deal size and product scope. Include onboarding, training, and first-value milestone."
- Data source: Product configuration, standard implementation playbook
⚠️ Share it, don't hoard it
The MAP should be a shared document — not an internal sales tool. Send it to your champion after the first version and ask them to review dates and add their internal milestones. The shared nature creates joint accountability and signals professionalism.
Open it in Bigmind, change it to fit how your team sells, and every agent follows it.
- Type
- Document
- Roles
- AESales Manager
- Segment
- Mid-MarketEnterprise
- Deals
- New Business
- Motion
- Sales-led
- Industries
- SaaSFinTechInfrastructure
