Answers

What is a mutual close plan?

A MAP opens the deal. A mutual close plan lands it. The scope shrinks, the pace quickens, and every row names one buyer-side owner and one seller-side owner so no task hides between inboxes while the quarter ticks.

Start free trial See pricing
Short answer

A mutual close plan is a shared, dated checklist that walks a late-stage deal through the last mile to signature. It is the mutual action plan narrowed to the tasks that remain between verbal commit and countersignature: redlines, purchase order, security questionnaire, procurement signoff, and go-live date. Every row names one owner on each side, and the plan is reviewed weekly until close. If a date slips, the go-live date slips with it, in writing.

Key points

What matters most.

The six rules that separate a mutual close plan from a glorified task list, and the one line every working MCP has that pushes a slipped date back onto the buyer, not the rep.

Scope

Verbal commit to countersignature, nothing earlier.

A mutual close plan starts after the buyer has verbally committed. Discovery, demo, business case, and executive validation live upstream in the MAP. The MCP is scoped to the tasks between verbal yes and signed order: redlines, PO, security questionnaire, procurement, and go-live. If a row belongs in the MAP, it does not belong here.

Ownership

One name on each side of every row.

Every task has one owner on the buyer side and one owner on the seller side. Not a team, not a group alias, not two people cc'd. Shared ownership is the fastest way for a close plan to stall, because when a date slips there is no single person to call. The named owner is the one the rep follows up with directly.

Cadence

Weekly review until signature.

The MCP gets a thirty-minute standing review every week with the champion and the rep, and every two weeks the rep walks it with the economic buyer. The review is not a status update. It is a joint commit to the dates on each row and a joint call-out of any row that is going to slip in the next seven days.

Rows

The last-mile tasks, in a short list.

A working MCP has eight to fifteen rows. Legal redlines, security questionnaire, data protection addendum, order form draft, order form review, PO issuance, implementation kickoff, provisioning, go-live, success criteria signoff. Enterprise plans add vendor onboarding, insurance verification, and background checks. SMB plans compress most of this to three or four rows.

Slip clause

If date X slips, go-live moves to date Y.

Every working close plan has one explicit line that says: if the buyer misses the signature date, the go-live date moves out by the same number of business days. This is the single most important sentence in the document. It transfers the cost of a slipped date from the rep's forecast to the buyer's project timeline, which is where it belongs.

Shared artifact

One document, two logos, both sides edit.

The MCP lives in a single document that both the rep and the champion can edit. Google Doc, Notion page, DocuSign CLM, the CRM record, whatever the buyer will actually open. Both logos on the top, both names on each row, both sides commit in writing. A close plan the buyer cannot edit is a seller-side wishlist, not a mutual plan.

What belongs in the plan

The rows a working mutual close plan actually has.

A mutual close plan is deliberately narrow. It is not the discovery notes, not the business case, not the ROI model, and not the demo recap. It is the dated path from verbal commit to countersignature and first provisioned user. The rows below are the ones every working MCP has in some form. Enterprise plans add vendor onboarding, insurance, and sometimes background checks. SMB plans compress the legal and procurement rows into a single order-form review. The question is not how long the plan is, it is whether every row has one owner on each side and a date both sides agreed to in writing.

Order form draft

Rep sends, champion reviews within 48 hours.

The first row on every MCP. Rep sends the order form within 24 hours of verbal commit. The champion owns the first review and commits to a 48-hour turnaround with redlines or a thumbs-up. If the champion will not commit to a 48-hour window, the deal is not actually at verbal commit. Treat it as a signal, not a scheduling conflict.

Legal redlines

Buyer's counsel owns the slot, not the champion.

Legal review is where close plans die quietly. The row names the buyer's actual counsel, with an email, and a specific date for first redlines back to the seller. Not 'legal is reviewing.' Not 'with legal.' Named counsel, named date, named escalation path if the slot slips. The champion owns the escalation, the rep owns the turnaround on the seller side.

Security questionnaire

SIG, CAIQ, or custom, with a hard return date.

Enterprise deals almost always have a security questionnaire. SIG, CAIQ Lite, or a buyer-custom one. The row names the questionnaire, the seller-side owner (usually a solutions engineer or security contact), and a specific return date. Buyers who have been through a procurement cycle before will know the exact form. Buyers who have not will often underestimate it, so the rep leads with the typical turnaround.

DPA and MSA

Data protection addendum, master services agreement.

The DPA and MSA rows are where enterprise deals absorb two to four weeks. The rep ships the seller's standard versions on day one of the plan. The champion owns getting them in front of counsel. If the buyer has their own paper, that goes on the plan as a separate row with a dated redline exchange. Shipping standard paper first is the single highest-leverage move the rep makes.

PO issuance

Named procurement owner, named ERP code.

In most enterprise and mid-market deals, the signed order form is not enough. Procurement has to issue a purchase order against the signed contract before the vendor can invoice. The row names the procurement owner, the ERP system (NetSuite, SAP, Oracle, Coupa), the vendor code, and the dated commit for PO issuance. SMB deals skip this row entirely because the champion is often the procurement owner.

Go-live date

The row that moves when another row slips.

The last row on the plan, and the only row written in both calendar time and business days. Calendar time for the champion's internal communication. Business days for the slip clause. When the signature row slips by three business days, the go-live row moves by three business days. Writing it both ways is what makes the slip clause enforceable without a renegotiation.

How to run the plan

Cadence, ownership, and the weekly review that keeps the plan alive.

A mutual close plan does not run itself. It needs a cadence, named owners on each row, and a review that both sides treat as a commit instead of a status read-out. The pattern below is what works for most mid-market and enterprise deals. SMB deals compress the cadence to a single weekly check-in with the champion. The point is that the plan is a living document the whole deal team opens on a schedule, not an attachment that gets forwarded once and never looked at again.

Weekly champion review

Thirty minutes, same slot every week.

The rep and champion hold a thirty-minute standing meeting until signature. The agenda is the plan, row by row. Each row gets confirmed as on track, slipping, or blocked. Slipping rows get an escalation plan on the call. Blocked rows get a specific unblock owner. No slide deck, no demo, no new scope. The plan is the meeting.

Biweekly executive walk

The economic buyer sees the plan twice a month.

Every two weeks the rep walks the plan with the economic buyer and the champion together. Fifteen minutes is enough. The executive is not debugging rows, they are confirming that the dates are still real and that nothing has shifted on their side of the table. Executives who see the plan twice a month surface internal blockers earlier than executives who only see it at signature.

Rep-side daily check

Not a meeting, a working file.

The rep opens the plan every day the deal is in the current quarter. Not to update the buyer, to update themselves and the deal team. The rep's manager should be able to open the plan on any Tuesday and see which rows moved in the last seven days. If the plan is only updated in the weekly review, it is already behind.

Shared ownership map

Every row has one name on each side.

The ownership column is split in half. Left is the buyer-side owner, right is the seller-side owner. The rep is not always the seller-side owner. Legal rows have the seller's counsel. Security questionnaire rows have the seller's solutions engineer or security lead. Provisioning rows have the implementation manager. The rep owns the plan as a whole, not every row.

Escalation ladder

Named at the top of the document.

A working MCP has three names at the top on each side. Champion, economic buyer, and executive sponsor on the buyer side. Rep, manager, and VP on the seller side. When a row slips twice in a row, the escalation goes up one rung on both sides at the same time. The ladder is written down so nobody has to improvise who to call at 4pm on a Friday.

Change log

Every date change is dated.

The bottom of the plan has a short change log. Date, row, old date, new date, reason, approving owner. It is three columns and five minutes a week. The change log is what prevents the plan from quietly drifting two weeks to the right over the course of a quarter. If a row moves and the change log does not record it, the row did not actually move, it is still slipping.

The common mistakes

How reps break a mutual close plan.

Most close plans fail the same way. The rep writes a seller-side task list, calls it mutual, and sends it as a PDF the buyer cannot edit. The champion forwards it internally once, nobody opens it again, and the deal slips because the plan was never actually shared. The mistakes below are the pattern. Any one of them is enough to turn a mutual close plan into a seller-side wishlist that quietly loses the quarter.

Seller-only ownership

Every row has the rep as the owner.

The fastest way to break a close plan is to put the rep's name on every row. The whole point of a mutual plan is that the buyer owns their side of the work in writing. If the rep owns legal redlines, security questionnaire, and PO issuance, those are not buyer tasks, they are seller follow-ups. The plan is a status tracker at that point, not a commit.

No dates

Rows say 'ASAP' or 'next week'.

A row without a specific date is a row that will slip without anyone noticing. 'ASAP' is not a date. 'Next week' is not a date. 'By end of month' is not a date unless it is the last Thursday of the month. Every row needs a specific calendar date that both sides agreed to on a specific call, with the agreement recorded in the change log.

PDF attachment

The buyer cannot edit the plan.

A close plan sent as a PDF is a seller-side artifact. The buyer cannot update it, cannot change dates, cannot add rows. So they do not open it after the first forward. The plan has to live in a document both sides can edit. Google Doc, Notion, DocuSign CLM, the shared CRM record. The format matters less than the shared edit access.

Scope creep

The plan expands backward into the MAP.

A close plan that has rows for business case review, additional stakeholder meetings, and reference calls has drifted backward into the MAP. Those rows mean the deal is not actually at verbal commit. The fix is not to add the rows, the fix is to admit the deal is still in validation and run the MAP for another two weeks. Adding earlier-stage rows to the MCP masks a stage mislabel.

No slip clause

Go-live is a soft commitment.

Without the explicit 'if X slips, Y slips' clause, every slipped signature date eats into the implementation window instead of the buyer's project timeline. The buyer still expects the original go-live, the implementation team still has the original scope, and the only slack in the system is the seller's calendar. A missing slip clause is the single most common reason implementations start underwater.

Weekly review as status read

The call is thirty minutes of 'in progress'.

A close plan review that is just a verbal walkthrough of 'in progress, in progress, in progress' is a status read, not a commit. The review has to force a yes-or-no commit on each row: on track for the dated commit, or slipping and here is the new date with the slip-clause consequence. If the champion is not willing to answer that question row by row, the review has turned into theater.

Run the close plan where the deal already lives, not in a side document that nobody opens.

Strkr keeps the mutual close plan on the opportunity record, with named owners on each row, dates both sides committed to, and a change log the forecast call reads from directly. One login for CRM, the close plan, and the forecast that depends on them.

Start free See the platform
People also ask

Related questions.

What is the difference between a mutual action plan and a mutual close plan?

A mutual action plan covers the whole deal from discovery through signature. A mutual close plan is the last-mile subset, scoped to the tasks between verbal commit and countersignature. Business case, executive validation, and reference calls live in the MAP. Legal redlines, security questionnaire, PO issuance, and go-live live in the MCP. The MCP is shorter, denser, and reviewed weekly. The MAP is longer, broader, and reviewed every two or three weeks.

When does a mutual close plan start?

At verbal commit, not before. The buyer has to have said yes to the business terms, the pricing, and the general shape of the contract. If the champion is still socializing the project internally, the deal is in the MAP, not the MCP. Starting a close plan before verbal commit mixes validation tasks with execution tasks, and the plan drifts backward into the MAP almost immediately.

Who owns the mutual close plan?

The rep owns the document and the overall timeline. The champion owns the buyer-side rows. The economic buyer owns the signature itself. Each row has one named owner on each side, so no single row is shared across two people in the same organization. The rep is the plan's maintainer, not the owner of every row. That split is what makes the plan mutual instead of a seller follow-up list.

How many rows should a mutual close plan have?

Eight to fifteen for a typical mid-market or enterprise deal. SMB deals compress to three or four. Fewer than eight usually means the plan is skipping security, DPA, or PO rows that will surface later and slip the signature. More than fifteen usually means the plan has absorbed MAP rows that belong upstream. Keep it narrow, keep it dated, and resist the temptation to add rows the buyer did not ask for.

What is the slip clause in a mutual close plan?

One explicit sentence that says if the buyer misses a signature date, the go-live date moves by the same number of business days. It transfers the cost of a slipped date from the seller's forecast to the buyer's project timeline, which is where it belongs. Without the slip clause, every delay on the buyer side eats into the implementation window and the only slack in the system is the seller's calendar. With it, the buyer owns the consequence of their own slip.

How often should the mutual close plan be reviewed?

Weekly with the champion for thirty minutes, biweekly with the economic buyer for fifteen minutes, and daily by the rep on their own. The weekly review is a row-by-row commit, not a status update. The biweekly executive walk is a dates-still-real check, not a scope conversation. The daily rep check is a working file update so the deal team can see which rows moved in the last seven days without waiting for the weekly meeting.

What format should a mutual close plan use?

Any shared, editable document. Google Doc, Notion page, DocuSign CLM, a shared CRM record, or a Smartsheet tab. The format matters far less than the fact that both sides can edit it in real time. A PDF close plan is a seller-side artifact the buyer forwards once and never opens again. If the buyer cannot change a date in the plan, the plan is not mutual.

What goes wrong when a mutual close plan is missing?

Signature dates slip without anyone noticing, security questionnaires surface two weeks before quarter end, procurement has not been engaged, and the champion assumes the rep is handling things the rep did not know existed. The deal still closes sometimes, but it closes late and the implementation starts underwater. The close plan is the artifact that forces every late-stage task into daylight before the quarter runs out.

More answers

Other questions in this category.

What is a mutual action plan? What is a mutual success plan? How do I negotiate with procurement? What are the best closing techniques? How do I handle price objections? What is a compelling event?

Try it free. Bring your team next week.

No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.

Start free trial See pricing