Mutual Close Plan

A Mutual Close Plan is a written agreement between a sales rep and a prospect that maps the exact steps required to finalize a transaction. It forces both sides to commit to specific dates for technical reviews, security audits, and executive sign-off. The plan operates as a shared project management document, shifting the relationship from a vendor pitching a product to two teams executing a joint project.

How a Mutual Close Plan Is Calculated

The plan is built by reverse-engineering the buyer's desired compelling-event date. The rep maps every required milestone backward to the current day.

A plan is only functional if the buyer actively edits the document. If the rep fills out the dates independently and emails it over, it is a unilateral wish list. The buyer must assign the target dates to ensure the plan accurately reflects their internal procurement and security sales-cycle-length.

Worked Example

An account-executive sells a $150,000 data integration platform. The buyer needs the system live by January 1 to support a new compliance mandate. The rep builds a Mutual Close Plan on October 15. They work backward from January 1, allocating three weeks for implementation. This sets a December 8 go-live date. To hit that date, the contract must be signed by November 20. The plan assigns the legal review to the buyer's general counsel by November 10 and the security review to the buyer's IT director by November 5. When the buyer agrees to these dates in writing, the rep gains a measurable framework to prevent deal-slippage.

When Sales Teams Use Mutual Close Plans

Reps introduce the plan during the late discovery or early proposal stage to test buyer commitment. A prospect who refuses to co-build a plan is a tire-kicker hiding behind a zombie-deal facade. VPs of Sales review these plans during deal-review sessions to assess forecast-accuracy. If a rep forecasts a deal to close this quarter but possesses no Mutual Close Plan, the VP discounts the forecast category immediately. RevOps uses the milestone completion rates to train sales-engineer teams on where technical evaluations actually bottleneck.

Common Mutual Close Plan Gaming Patterns

The primary failure mode is the phantom plan. A rep creates the document, checks the box for their CRM opportunity-stage requirements, and never shares it with the prospect. The plan sits in the CRM as a static artifact while the deal stalls in legal review.

Another manipulation involves buyer apathy. The rep shares the plan, the buyer says "looks good," and never touches it again. The rep points to the buyer's verbal approval as proof of deal-velocity, but the dates hold no real weight in the buyer's organization. The deal slips because the buyer never actually walked the timeline past their economic-buyer. A Mutual Close Plan only prevents slippage when the buyer actively updates the dates and assigns the milestones to named stakeholders on their own team. Track document edit history to ensure the buyer has actively manipulated the file.