Move deals forward
Make the next step a shared plan
Give your buyer and your team one clear path from first agreement to a confident decision.
Make the plan mutual in practice
A mutual action plan is useful when the buyer recognizes their own work and decisions in it. Start with the outcome they want, then work backward through evaluation, approval, implementation, and adoption. Ask the customer to correct the sequence. A plan built entirely around the seller’s close date may look organized while hiding the steps the buyer actually needs to complete.
Define a meaningful milestone
Each milestone should describe a result, an owner, and evidence that it is complete. “Send proposal” is a seller activity. “Commercial owner confirms the proposal addresses the agreed scope” describes a decision. Some milestones will involve several people; nominate the person responsible for coordinating the result rather than listing everyone as an owner. Record dependencies so a missed step can be discussed without turning the whole plan into a vague delay.
Keep changes visible
Review the plan together when scope, timing, or stakeholders change. Explain which assumption changed and update the downstream dates instead of silently moving the final deadline. If the customer stops engaging with the plan, investigate whether the outcome still matters and whether the right people are involved. A shared document is not proof of commitment. Its value comes from the conversations and decisions it supports. Customize the template below to fit the customer’s process, removing steps that add no value.
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.
Add it to your team’s library in Bigmind, where every agent can find it, and make an editable copy your own.
- Format
- Template
- Length
- Template
- Access
- Free
- Topics
- dealssales
More like this
BigmindPlaybook · PreviewCommand the CycleA practical framework for managing complex deals through preparation, follow-up, stakeholder alignment, negotiation, and closing.
Brian LaMannaPlaybook · 12 min readMake every discovery call countA practical, stage-by-stage guide to uncovering real pain, finding your champion, and building a case for change.
Bigmind