Plan the deal backward from the day they need it live — and read every stall as a step that quietly lost its owner.
A mutual close plan (or mutual action plan) is a shared, backward-timed schedule that runs from the buyer’s go-live date to signature. Every step in between — security review, legal, procurement — gets a real owner on both sides and a date.
The urgency comes from their compelling event, the date the business actually needs this working — not your quarter-end. Anchor on their date and the plan pulls itself forward on its own.
So when a deal goes quiet, don’t ask “are they still interested?” Ask which step lost its owner. A step with no name next to it is a step nobody is moving.
build the plan backward from go-live
You don’t schedule forward from today (“we’ll try to close soon”). You fix the date the buyer needs to be live, subtract the implementation runway, and lay the approval steps backward from there — each with a named owner on both sides.
Anchor: their go-live is Nov 15. Implementation needs 21 days,
so signature must land by Oct 25 (the real deadline —
not your Sep 30 quarter-end).
Lay the steps backward, each owned on both sides:
security review 18d Priya, InfoSec + Sam, sales eng
legal / MSA 14d their counsel + your legal
procurement / PO 10d procurement + deal desk
--------------------------------------------------------
start by Oct 25 − 42d = Sep 13 to sign with room
Owned + anchored -> signs Oct 13, 12 days before the deadline.
Drop security’s owner -> +12d stall -> signs Oct 25, no slack left.
Remove the event -> +10d on every step -> signs Nov 12,
past the deadline and into go-live.
The compelling event is the engine. Without it, each step loses its forcing date and drifts — the plan stops pulling and starts sagging.
| Reach for a mutual close plan when… | The trade-off |
|---|---|
| The buyer has a real, dated compelling event (a launch, a contract expiry, a fiscal deadline). | If there’s no genuine event, don’t manufacture one — a fake deadline reads as pressure and erodes trust. |
| The deal crosses several functions (security, legal, procurement) with hand-offs. | Simple, single-stakeholder deals don’t need the ceremony; keep it lightweight. |
| You want a shared artifact the champion can carry internally. | It only works if they co-own it — a plan you filled in alone is just your wish-list. |
An interviewer asks: “Your biggest deal has gone silent with two weeks left in the quarter. Walk me through what you do.” A weak answer chases the quarter: “I’d push for a decision by the 30th.” A strong answer reaches for the mutual plan. “First I’d reconfirm their go-live — the board demo in November is the real deadline, not my quarter. Then I’d walk the plan step by step and find where it stalled. If the security review lost its owner because their InfoSec lead is on leave, that’s a staffing fix, not a lost deal — I’d get a backup named and re-baseline the dates backward from Nov 15.” You’ve shown you diagnose momentum by structure, not by hope.
Check yourself
The deal stalls in the last week of your quarter. What’s the first move?
The champion loves the product but there’s no dated business event driving it. What does that tell you about your close plan?