Many B2B deals do not die. They drift. The customer liked the demo, agreed the price was reasonable, and then the security review took six weeks, the legal team was on leave, and the CFO wanted one more comparison. The seller’s forecast said “close this quarter” because nobody had ever written down what had to happen, in what order, by whom, for that to be true.

A mutual action plan, often shortened to MAP and sometimes called a close plan or joint execution plan, is the remedy. It is a shared document, agreed with the customer, listing every step between today and the point where the customer is using the solution, with an owner and a date for each.

Start from the customer’s date, not the seller’s

The defining feature of a good MAP is the direction it is built in. A weak plan starts from the seller’s quarter-end and asks the customer to hurry. A strong plan starts from a date that matters to the customer and works backwards.

Imagine a logistics company in Pune evaluating a warehouse management system. During discovery, the operations head explains that the busy festive season begins in October and the new system must be live and stable by 1 September, with staff trained before the volume surge. That date is the anchor. Implementation is estimated at ten weeks. So the contract must be signed by mid-June. Working back from there:

Target dateStepOwner
1 SeptemberGo-live, before festive volumeCustomer operations head
Mid-JuneContract signed, implementation kick-offCustomer CFO, vendor sales lead
Early JuneLegal and procurement review completeCustomer legal, vendor contracts team
Late MayInformation security assessment signed offCustomer IT security, vendor security lead
Mid-MayBusiness case approved by CFOCustomer finance, champion
Early MayPilot results reviewed against agreed success criteriaCustomer operations, vendor solution engineer
Mid-AprilPilot starts in one warehouseBoth teams

Laid out like this, the plan makes an uncomfortable fact visible: if the pilot slips by three weeks, the go-live date is at risk. The customer, not the seller, now has a reason to keep things moving, because the deadline is theirs.

What belongs in the plan

Sellers new to MAPs tend to list only their own activities: send proposal, run demo, share references. The useful items are the ones on the customer’s side, because those are the steps sellers cannot see or control. A thorough plan covers:

  • Evaluation steps: demos, pilots, reference calls, and the criteria for judging them.
  • Internal approvals: business case, budget sign-off, steering committee or board approval if needed.
  • Risk and compliance reviews: information security questionnaires, data protection assessment, vendor onboarding. For Indian customers handling personal data, the Digital Personal Data Protection Act may bring additional review steps, and regulated sectors such as banking and insurance often have their own outsourcing and data localisation requirements.
  • Commercial and legal steps: redlines, procurement negotiation, purchase order creation and signature.
  • Post-signature steps: kick-off, implementation milestones, training, go-live. Including these keeps the conversation focused on outcomes rather than on the signature.

The plan as a qualification test

A MAP is not just a project tool. The way a customer responds to one is information.

If the champion engages seriously, fills in the steps the seller did not know about, and names the people who own them, the deal is real. If they cannot say who approves the budget, the seller has learned that the champion may not have the access they claimed. If they decline to commit to any dates at all, the deal is probably not a priority, whatever has been said in meetings. Sellers sometimes avoid proposing a MAP because they fear the answer. That is exactly why it is worth proposing.

The plan also reveals the paper process early. Procurement and legal reviews are a major cause of slipped deals, mainly because sellers learn about them late. Asking in the first weeks, “Once you have decided, what steps happen before a contract can be signed, and how long do they usually take?” often uncovers a vendor registration process, a security review queue or a quarterly approval committee that would otherwise appear as a surprise in the final week.

Keeping it alive

A MAP that is drafted once and filed away adds nothing. Practical habits help:

  1. Keep it in a format the customer can edit or comment on, such as a shared document, not a PDF attached to an email.
  2. Review it at the start or end of every meeting with the customer, taking a minute to mark items done or slipped.
  3. When a date slips, ask what the knock-on effect is on the customer’s goal, rather than simply moving the next date.
  4. Keep the forecast close date consistent with the plan. If the plan says signature in July, the CRM should not say June.

When a MAP is overkill

For a small, transactional purchase with one decision-maker and a click-through contract, a formal plan adds friction for no gain. MAPs earn their keep in deals with several stakeholders, technical evaluation, formal approvals and a cycle of more than a few weeks. In those deals, they turn a vague forecast into a list of checkable facts, and they give the customer’s champion a document to use when coordinating their own colleagues, which is often the most valuable thing a seller can provide.

Written by the RP Strativa Team. The company and dates in the example are illustrative.

Leave a Reply

Trending