Mutual Action Plan Templates
Kevin Kho
Co-Founder & CTO · Updated March 17, 2026
The right MAP template depends on your deal size, sales cycle length, and buying committee complexity. We have broken down templates for four common scenarios — each reverse-engineered from the go-live date, which is how the best practitioners structure them.
A quick note on methodology: every template below assumes you have completed initial discovery and have enough context to understand the buyer's internal process. If you are introducing a MAP before you understand how the buyer makes decisions, you are doing it in the wrong order. Discovery first, MAP second.
Enterprise SaaS Template (8–12 Weeks)
For $100K+ ACV deals with 8 to 12+ stakeholders spanning IT, security, legal, procurement, and multiple business units. These deals have the most moving parts, and the MAP's value scales with complexity.
Phase 1: Discovery & Alignment (Week 1–2)
- Confirm key stakeholders and roles — Owner: Both. Map the full buying committee. Identify the economic buyer, champion, technical evaluator, and any potential blockers.
- Define success criteria — Owner: Buyer (with seller input). What does a successful implementation look like 90 days post-go-live? Get this in writing early.
- Map internal decision process — Owner: Buyer (champion). How many approval stages? Who signs? What committees need to review? This is the step most sellers skip and later regret.
- Agree on evaluation timeline — Owner: Both. Set the go-live target and work backward to establish phase dates.
Phase 2: Technical Evaluation (Week 3–4)
- Conduct detailed demo / technical deep-dive — Owner: Seller. Tailored to the buyer's environment and use cases, not a generic walkthrough.
- Complete POC or pilot — Owner: Both. Define scope, success metrics, and timeline for the proof of concept before it starts.
- Technical architecture review — Owner: Buyer (IT lead). Assess integration requirements, data flows, and infrastructure dependencies.
- Integration assessment sign-off — Owner: Buyer (IT lead). Written confirmation that the technical approach is feasible.
Phase 3: Security & Compliance (Week 4–6)
- Complete security questionnaire — Owner: Seller. Most enterprise buyers have a standard questionnaire (SIG, CAIQ, or custom). Budget 1–2 weeks for completion.
- SOC 2 / ISO 27001 review — Owner: Buyer (security team). Provide audit reports proactively. Do not wait for the request.
- Data residency and privacy review — Owner: Both. Where is data stored? Does it cross jurisdictions? GDPR, CCPA, or industry-specific requirements?
- Security approval — Owner: Buyer (CISO or security lead). Formal sign-off that the vendor meets security requirements.
Phase 4: Business Case & Stakeholder Alignment (Week 5–7)
- Build ROI analysis — Owner: Both. The seller provides benchmarks and case studies; the buyer provides internal cost data and strategic context.
- Executive sponsor buy-in — Owner: Buyer (champion). The champion presents the business case to the economic buyer. The seller supports but does not own this step.
- CFO / finance review — Owner: Buyer. CorporateVisions research indicates 79% of B2B purchases now require CFO approval. Do not treat this as a formality — build it into the timeline.
- Cross-functional stakeholder alignment — Owner: Buyer (champion). Ensure all departments affected by the purchase have provided input. This is where Gartner's "unhealthy conflict" data (74% of buying teams) becomes relevant.
Phase 5: Procurement & Legal (Week 7–10)
- MSA redline and negotiation — Owner: Both (legal teams). Budget 2–3 rounds of redlines. Ask during discovery how many rounds their legal team typically needs.
- Data Processing Agreement (DPA) — Owner: Both. Often runs in parallel with the MSA but involves different reviewers.
- Procurement process — Owner: Buyer (procurement). Purchase orders, vendor registration, payment terms. Some organizations require board approval above certain thresholds.
- Contract execution — Owner: Both. Signatures from authorized signatories on both sides.
Phase 6: Onboarding & Go-Live (Week 10–12)
- Implementation kickoff — Owner: Seller (CS/implementation team). Transition from sales to post-sales. The MAP should explicitly name who from the seller's side takes over.
- Data migration — Owner: Both. Define scope, test migration, validate data integrity.
- Training — Owner: Seller. Role-based training for end users, admins, and reporting stakeholders.
- Success criteria validation — Owner: Both. Go back to the success criteria defined in Phase 1. Confirm they are met or establish a timeline for measurement.
Mid-Market Template (4–6 Weeks)
For $25K–$100K deals with 5 to 8 stakeholders. The structure is similar to enterprise but compressed — fewer stakeholders means fewer approval loops, but do not mistake "smaller" for "simpler."
Phase 1: Discovery (Week 1)
- Stakeholder mapping and success criteria — Owner: Both
- Understand internal approval process — Owner: Buyer (champion)
- Agree on evaluation timeline and go-live target — Owner: Both
Phase 2: Evaluation & Demo (Week 2)
- Tailored demo for key stakeholders — Owner: Seller
- Trial or sandbox evaluation — Owner: Buyer (end users)
- Technical fit confirmation — Owner: Buyer (IT/technical lead)
Phase 3: Proposal & Business Case (Week 3)
- Pricing proposal delivered — Owner: Seller
- Internal business case circulation — Owner: Buyer (champion)
- Budget confirmation — Owner: Buyer (finance or VP)
Phase 4: Contract & Procurement (Week 4–5)
- Contract review and redlines — Owner: Both (legal). Even mid-market deals involve legal review. Do not skip this in the MAP — legal and procurement cause 60%+ of late-stage slippage across all deal sizes.
- Procurement and PO processing — Owner: Buyer
- Contract execution — Owner: Both
Phase 5: Onboarding (Week 5–6)
- Implementation kickoff and account setup — Owner: Seller
- Team training and onboarding — Owner: Seller
- Go-live and success criteria check — Owner: Both
SMB Template (1–2 Weeks)
For sub-$25K deals with 2 to 4 stakeholders. At this deal size, the MAP should be a simple checklist — not a 12-phase plan. The goal is the same (shared visibility into what happens next), but the format needs to match the buyer's speed.
Phase 1: Trial / Evaluation (Day 1–3)
- Start free trial or receive guided demo — Owner: Buyer
- Key user completes core workflow test — Owner: Buyer
Phase 2: Review & Decision (Day 4–7)
- Decision-maker reviews findings — Owner: Buyer (founder, VP, or department head)
- Pricing and plan confirmation — Owner: Seller
Phase 3: Approval & Sign-off (Day 7–10)
- Budget approval — Owner: Buyer
- Contract or order form signed — Owner: Both
Phase 4: Activation (Day 10–14)
- Account setup and data import — Owner: Both
- Team onboarding call — Owner: Seller
Even at this scale, writing down "decision-maker reviews by Thursday" instead of assuming it will happen is often the difference between a deal that closes in 10 days and one that drifts for 6 weeks.
Professional Services Template (6–10 Weeks)
For consulting, implementation, or managed services engagements. The buying process here is different from SaaS — the buyer is purchasing expertise and outcomes, not software. The MAP needs to account for scoping complexity and SOW negotiation.
Phase 1: Scoping & Requirements (Week 1–2)
- Discovery workshops with stakeholders — Owner: Both
- Requirements documentation — Owner: Seller (based on buyer input)
- Scope boundaries and assumptions agreed — Owner: Both. This is critical. Scope creep during the sales process is a leading cause of professional services deal failure.
Phase 2: Proposal & SOW (Week 2–3)
- Proposal and SOW delivered — Owner: Seller
- Internal review with stakeholders — Owner: Buyer
- SOW revisions and scope confirmation — Owner: Both
Phase 3: Legal & Procurement (Week 3–5)
- MSA review (if new vendor relationship) — Owner: Both
- Insurance and liability review — Owner: Buyer (legal/risk)
- Budget allocation and PO — Owner: Buyer (finance)
- Contract execution — Owner: Both
Phase 4: Kickoff Planning (Week 5–7)
- Project team introductions — Owner: Both
- Kickoff meeting and project plan alignment — Owner: Seller (delivery team)
- Access and environment setup — Owner: Buyer
Phase 5: Delivery & Milestones (Week 7–10)
- Phase 1 deliverable review — Owner: Both
- Milestone sign-offs per SOW — Owner: Buyer
- Project retrospective and next-phase planning — Owner: Both
How to Customize Any Template
No template works perfectly out of the box. The value is in having a starting structure that you adapt based on what you learn in discovery. Here is how to customize effectively:
- Always start from the go-live date and work backward. The go-live date anchors the entire plan. Every milestone derives from it. If the buyer says "we need to be live by Q3," that is your starting point — not the date you want to close by.
- Add stakeholder-specific milestones based on discovery. If the buyer mentions a security review, a board presentation, or an IT architecture committee, add those as explicit milestones. The template gives you phases; discovery gives you the specific steps within those phases.
- Remove phases that do not apply. A 5-person buying group at a startup does not need a dedicated "Stakeholder Alignment" phase. A deal with no data residency concerns can skip the compliance deep-dive. Over-engineering the MAP is almost as bad as not having one.
- Assign buyer owners by name, not role. "Buyer — legal" is a placeholder. "Sarah Chen, Associate GC" is accountability. During co-creation, ask the champion to assign named owners on the buyer's side.
- Build in buffer for the steps that historically slip. Security reviews, legal redlines, and CFO approvals are the three most common delay points in enterprise deals. Budget extra time for these based on what the buyer tells you during discovery about their typical timelines.
Build From a Template Now
Our free MAP builder includes all four templates above. Pick one, customize it for your deal, and share it with your buyer — no sign-up required.
Continue reading:
- Mutual Action Plan: The Complete Guide
- What is a Mutual Action Plan? — Definition, history, and methodology connections
- Mutual Action Plan Examples — Real-world scenarios by deal size