A $200K AI automation deal has been in your pipeline for four months. Every meeting ends with "we will get back to you next week." Next week becomes next month. You chase the prospect. They are responsive but nothing moves forward. The champion says she is working on internal approvals, but you have no visibility into what those approvals are, who needs to give them, or what information is required. You are flying blind, hoping the deal closes eventually.
Now imagine a different scenario. After the second meeting, you and the prospect co-create a document that lists every step needed to go from evaluation to signed contract. Security review needs to happen by April 15. Legal needs the MSA by April 22. The CFO needs a business case presentation by May 1. The board meets May 10. Contract signature target is May 15. Both sides know what needs to happen, who is responsible, and when it needs to be done.
That document is a mutual action plan, and it is one of the most effective tools for accelerating deal velocity in enterprise AI sales.
What a Mutual Action Plan Is
A mutual action plan (MAP), sometimes called a close plan or joint evaluation plan, is a shared document that outlines every step both the buyer and the seller need to take to reach a purchase decision. It is mutual because both sides contribute to it and both sides have responsibilities.
The MAP transforms the sales process from a series of one-sided follow-ups into a collaborative project with shared accountability. Instead of you chasing the prospect, both sides are working toward a shared timeline.
What a MAP Is Not
It is not a sales methodology. A MAP does not replace MEDDIC, SPIN, or Challenger. It complements them by providing a tactical execution framework for the close phase of the deal.
It is not a project plan. The MAP covers the purchase process, not the implementation. Once the contract is signed, the implementation project plan takes over.
It is not a one-sided timeline. If you create a timeline and hand it to the prospect, that is a sales plan, not a mutual action plan. The "mutual" part is essential.
It is not a commitment to buy. A MAP is a roadmap for making a decision, not a commitment to a specific decision. The prospect can still decide no. But the MAP ensures that the decision happens on a known timeline.
Why MAPs Work for AI Agency Sales
Enterprise AI Sales Are Complex
AI deals involve multiple stakeholders, technical evaluations, security reviews, legal negotiations, and budget approvals. Without a MAP, each of these steps happens on its own timeline with no coordination. The result is a deal that drifts indefinitely.
A MAP sequences these steps logically. Security review before legal review. Business case before budget approval. POC before implementation proposal. Each step has a date, an owner, and a dependency.
They Surface Hidden Steps
Most prospects do not tell you about all the steps in their buying process. Not because they are hiding them, but because they take them for granted. "Oh, our CISO needs to review any cloud-based solution." "Our procurement team requires three competitive bids." "The CFO will want to see the ROI model before she approves anything."
The MAP creation process surfaces these hidden steps before they become surprises. When you sit down with the prospect and map the process, they think through the full sequence and you learn about requirements that would otherwise emerge as last-minute blockers.
They Create Mutual Accountability
When both sides agree to a timeline, there is social pressure to meet it. If the prospect commits to delivering a dataset by March 15 and you commit to completing the POC by April 1, both sides are accountable. If the prospect misses their deadline, the impact on the rest of the timeline is visible.
This mutual accountability is far more effective than one-sided follow-up. "Per our mutual action plan, the dataset was due last Friday. We need it by Wednesday to stay on track for the board meeting on May 10."
They Predict Deal Health
A MAP is an early warning system. If the prospect consistently misses their milestones, the deal is in trouble. If they skip steps or stop engaging with the plan, something has changed. These signals give you time to diagnose and address issues before the deal dies silently.
Building the MAP
When to Introduce the MAP
The optimal time to introduce a MAP is after the prospect has expressed genuine interest but before the deal enters the evaluation phase. This is typically after the second or third meeting, once you have completed initial discovery and the prospect has confirmed they want to explore further.
Too early, and the prospect feels pressured. Too late, and the value of the MAP is diminished because many steps have already happened without coordination.
The introduction: "We have worked with many organizations on initiatives like this, and the evaluation and approval process usually involves several steps and stakeholders. To make sure we stay aligned and do not waste anyone's time, we have found it helpful to create a shared action plan that maps out the steps on both sides. Would you be open to spending 15 minutes co-creating that plan?"
The MAP Template
A basic MAP template includes the following columns:
Step: What needs to happen Owner: Who is responsible (buyer or seller, with specific names) Due Date: When it needs to be completed Status: Not started, in progress, completed, or blocked Dependencies: What needs to happen first Notes: Additional context or requirements
Core Steps to Include
Every AI agency MAP should cover these categories of steps:
Technical Evaluation
- Solution demonstration or POC
- Technical architecture review
- Security assessment
- Data readiness evaluation
- Integration feasibility assessment
Business Evaluation
- ROI analysis and business case development
- Executive briefing or presentation
- Reference calls with existing clients
- Competitive evaluation (if applicable)
Legal and Compliance
- NDA execution
- MSA review and negotiation
- Data Processing Agreement review
- Compliance review (industry-specific)
- Insurance and liability verification
Procurement
- Vendor registration
- Procurement documentation
- Budget approval process
- Purchase order or contract execution
Internal Alignment
- Stakeholder identification and engagement
- Internal champion presentation to leadership
- Steering committee or board approval
- Change management assessment
Co-Creating the MAP with the Prospect
This is the most important part of the process. Do not create the MAP and hand it to the prospect. Create it together.
The conversation:
"Let me walk through the typical steps we see in evaluations like this, and you tell me what applies to your organization and what I am missing."
Go through each category and ask:
- "Does your organization require a security review for cloud-based solutions? Who leads that?"
- "What is the legal review process for new vendor agreements? How long does it typically take?"
- "Who needs to approve the budget? Is there a committee or is it an individual decision?"
- "Are there any internal steps I have not mentioned that need to happen?"
As the prospect describes their process, build the MAP in real time. Assign owners and propose dates. Negotiate the timeline collaboratively.
Working backward from a target date: If the prospect has a target go-live date or a business event that creates urgency, work backward from that date to determine when each step needs to start.
"You mentioned wanting the system in production by September. That means implementation needs to start by July. To start implementation in July, the contract needs to be signed by June. To sign in June, the legal review needs to start by May. To start legal by May, the security review needs to complete by late April. Let us map out the specific dates."
Managing the MAP
The Living Document
A MAP is not a one-time exercise. It is a living document that is updated throughout the sales process. After each meeting, review the MAP, update statuses, and adjust dates as needed.
Where to host the MAP: Use a shared document that both sides can access and update. Google Docs, a shared spreadsheet, or a dedicated deal management tool. Avoid PDFs or email attachments that cannot be updated collaboratively.
Weekly Check-Ins
Schedule a brief weekly check-in (15 minutes) to review the MAP with your champion. Walk through the upcoming milestones, confirm that owners are on track, and identify any blockers.
This weekly rhythm keeps the deal moving and gives you regular face time with the champion. It also normalizes the practice of both sides reporting on progress, which reduces the awkwardness of follow-up.
Handling Slippage
When milestones slip (and they will), address it promptly and collaboratively.
Do not ignore it. If the security review was due last week and has not started, do not pretend everything is fine.
Do not blame. "The security review is behind schedule. What can we do to get it back on track?" Not "You missed the deadline for the security review."
Assess the impact. When one milestone slips, show the cascade effect on subsequent milestones. "If the security review completes two weeks late, that pushes legal review to May 15 and contract signature to June 1. That means we would miss the September go-live target by about two weeks."
Propose solutions. "Is there a way to run the security review and legal review in parallel? That would recover one week."
When the MAP Reveals a Dead Deal
Sometimes the MAP process reveals that the deal is not going to close. The prospect cannot commit to any dates. They keep adding new steps. They cannot identify who needs to approve the budget. These are signals that the deal lacks the fundamentals.
If the MAP cannot be completed because the prospect cannot define their own buying process, that is information. It tells you the prospect is not ready to buy. You can either nurture them until they are ready or redirect your effort to a more qualified opportunity.
Advanced MAP Strategies
The Executive Alignment Meeting
Use the MAP to justify a meeting with the economic buyer. "We have been making great progress on the evaluation. Before we get into the legal and procurement phases, I think it would be valuable to align with [CFO/CEO name] on the timeline and business case. Can we schedule a 30-minute meeting?"
The MAP gives you a legitimate business reason for the meeting. You are not asking for a sales presentation. You are asking for alignment on a process that is already underway.
The Urgency Lever
When a prospect is moving slowly, the MAP provides a non-confrontational way to create urgency. Instead of pressuring, you simply show the math.
"Based on our current pace, we are tracking for a November contract signature. That puts implementation starting in December and production in March. You mentioned wanting results by Q2. To hit that target, we would need to compress the timeline by about six weeks. Here are a few steps we could accelerate."
The Competitive Advantage
Most AI agencies do not use MAPs. When you introduce a collaborative, structured approach to the buying process, you differentiate yourself as professional and organized. Prospects notice. They have been through enough chaotic vendor evaluations to appreciate one that is well-managed.
Multi-Thread the MAP
Do not rely on a single contact to manage the buyer's side of the MAP. Identify owners for each buyer-side milestone and engage with them directly (with your champion's support). The security review owner should know the timeline. The legal reviewer should know when the MSA will arrive.
This multi-threading reduces dependency on any single person and increases your visibility into each step of the process.
Common MAP Mistakes
Creating it without the prospect. A plan you create alone is a sales plan, not a mutual action plan. If the prospect does not contribute to and agree on the plan, they will not feel accountable to it.
Being too rigid. Plans change. Dates shift. Steps get added. Rigidly enforcing the original plan creates friction. Be collaborative about adjustments while keeping the overall timeline in focus.
Not including buyer-side steps. If the MAP only lists your steps, it is not a mutual plan. Include the prospect's responsibilities explicitly.
Overcomplicating it. A MAP with 50 line items is overwhelming. Keep it to the 15-20 most important milestones. Details can be managed separately.
Not reviewing it regularly. A MAP that gets created and then ignored is worthless. Review it at every interaction.
Treating it as a contract. The MAP is a planning tool, not a legal commitment. Do not use it as a weapon against the prospect when dates slip.
Mutual action plans transform the enterprise sales process from a game of follow-up ping-pong into a collaborative project with shared accountability. For AI agencies selling complex, high-value engagements, this approach compresses sales cycles, surfaces hidden obstacles, and gives you unprecedented visibility into deal progress. Start using MAPs on your next enterprise deal and measure the difference in deal velocity and close rate. The improvement will be immediate and significant.