What a sales close plan template is
A close plan is the seller-side ledger of one deal's final stretch. It starts the day the buyer signals intent and ends at signature, and it holds every step still standing between the two: the commercial approval, the security review, legal's redlines, procurement's vendor setup, and the name of the person who actually signs. Each row carries an owner on a named side and a date.
It is not the mutual action plan, and keeping the two straight is most of the discipline. The mutual action plan is shared with the buyer and agreed with them; the close plan is internal, and holds what you would never put in front of a buyer: the slip risk, the concession strategy, the approval your champion may not be able to get. The two documents must agree on dates, and when they stop agreeing, the close plan is where you find out why.
The late stage is where plans earn their keep. Gartner describes six "buying jobs" that B2B buyers work through and revisit: problem identification, solution exploration, requirements building, supplier selection, validation and consensus creation (Gartner, B2B buying journey, accessed 2026-10-15). The last two are where signed-any-day deals stall, because they happen inside the buyer's organisation where the seller cannot see. A close plan tracks those jobs from the outside, by the evidence they leave: a meeting held, a document returned, a name added to the approval chain.
What separates a close plan that works from a wish list is how the steps are written. "Follow up with legal" is an intention; "legal returned redlines" is an event a second person can confirm happened or did not. Every row in this template is written as the event, with the evidence column recording what proves it.
When to use a close plan template
- A buyer has said yes in a meeting and nobody can list what still has to happen before a signature.
- Deals keep slipping from one quarter to the next at the final stage, each time for a reason that was knowable a month earlier.
- A late-stage deal runs through one contact, and the paper process on the buyer side is a guess.
- Security, legal or procurement appears in the last two weeks with requirements that restart the clock.
- A forecast commit rests on "the champion says it is fine" rather than on steps you can count.
Close plan, mutual action plan, forecast entry or account plan: which one you need
Four documents circle the same deal and get mistaken for each other. The practical differences are who sees each one and what question it answers.
| Artefact | What it holds | Who sees it | Does not tell you |
|---|---|---|---|
| Close plan | Every remaining step to signature, with owners, dates, risks and concessions | Your side only | Whether the buyer agrees with your dates |
| Mutual action plan | The steps you and the buyer have agreed, shared and edited together | Both sides | The risks and trade-offs you keep to yourself |
| Forecast entry | A stage, an amount and a date in the CRM | Your management | Why the date is credible, or what would move it |
| Account plan | The long-term map of a whole account across many deals | Your side only | What has to happen this month on this deal |
The template
Five blocks, one deal. Fill the header once, then run the plan from the steps table: everything else exists to explain why a step is late or what it will cost to fix.
Deal header
| Field | What to write |
|---|---|
| Deal and value | Account, products in scope and the amount as currently quoted. |
| Target signature date | The date the plan works backwards from. Change it only in writing, with the reason. |
| Economic buyer | The person whose budget pays, and whether they have been in any meeting yet. |
| Who signs | The named signatory and the route to them: who sends the contract, in what system. |
| Champion | Who is selling internally when you are not in the room, and what they personally gain. |
| Forecast category | What your forecast currently claims, so the plan and the number can be compared. |
Remaining steps to signature
| Step, written as a verifiable event | Owner (name and side) | Due date | Status | Evidence it happened |
|---|---|---|---|---|
| Commercial terms approved on our side | [Name], seller | [Date] | Not started / in progress / done | Approval recorded against the quote |
| Security questionnaire submitted and accepted | [Name], buyer | [Date] | Not started / in progress / done | Acceptance email or portal status |
| Legal returned redlines | [Name], buyer | [Date] | Not started / in progress / done | Marked-up contract received |
| Redlines resolved and final contract issued | [Name], seller | [Date] | Not started / in progress / done | Clean version sent for signature |
| Vendor registration completed in procurement system | [Name], buyer | [Date] | Not started / in progress / done | Supplier number issued |
| Signature | [Signatory], buyer | [Date] | Not started / in progress / done | Executed contract returned |
Approval chain on the buyer side
| Approval | Who gives it | Status | Risk if it has not started |
|---|---|---|---|
| Budget release | [Economic buyer or finance] | [Status] | The deal has a supporter but no money attached. |
| Security sign-off | [Security owner] | [Status] | A two-week review arrives in the final week. |
| Legal sign-off | [Legal owner] | [Status] | Redlines restart the commercial conversation. |
| Procurement | [Procurement owner] | [Status] | Vendor setup adds weeks after everyone has said yes. |
Risk log
| Risk | Signal you would see | Counter-move | Owner |
|---|---|---|---|
| Single-threaded through the champion | Every answer arrives second-hand | Ask the champion to bring the economic buyer to the next review | [Name] |
| Signature date rests on buyer intent, not buyer process | Nobody on the buyer side can describe the paper process | Map the approval chain above in the next call | [Name] |
| Quarter-end discount expectation | Buyer goes quiet as the date approaches | Trade any concession for a term, never for silence | [Name] |
Concession ledger
| Concession asked | What we trade for it | Approved by |
|---|---|---|
| [What the buyer asked for] | [The term asked for in return: start date, term length, case study, reference call] | [Name] |
| [What the buyer asked for] | [The term asked for in return] | [Name] |
Prefer a file? All three downloads are free and ungated.
A worked example
Example: fictional company
One deal, three weeks from target signature, filled in. The point of the example is the evidence column and the risk log: every claim about progress is tied to something that either exists or does not.
Dana Okafor is an account executive closing a reporting-platform deal with Keddington Mutual, an insurance firm. The CFO agreed the price on 3 October. The forecast says 14 November. This is her close plan ten days later.
Keddington Mutual: remaining steps on 13 October
| Step, written as a verifiable event | Owner (name and side) | Due date | Status | Evidence it happened |
|---|---|---|---|---|
| Commercial terms approved on our side | Dana Okafor, seller | 6 October | Done | Approval on the quote, 6 October |
| Security questionnaire submitted and accepted | Priya Nair, buyer IT | 17 October | In progress | Submitted 10 October; reviewer assigned, no response yet |
| Legal returned redlines | Keddington legal | 24 October | Not started | Contract sent 8 October; legal has not acknowledged receipt |
| Redlines resolved and final contract issued | Dana Okafor, seller | 31 October | Not started | |
| Vendor registration completed in procurement | Marcus Hale, buyer procurement | 7 November | Not started | No supplier number requested yet |
| Signature | CFO, buyer | 14 November | Not started |
What the plan surfaced, and what Dana did about it
| Finding | Why it matters | The move |
|---|---|---|
| Legal has not acknowledged the contract after five days | The 24 October redline date is a hope, not a plan, and every later date leans on it | Asked the champion to name the lawyer handling it and get a date in writing |
| Nobody has started vendor registration | At Keddington this takes three weeks, which already lands after the signature date | Asked procurement to open the registration in parallel with legal, not after it |
| The CFO agreed the price but has not appeared since | Budget release is an approval, not a memory of a meeting | The mutual action plan review on 20 October now has the CFO on the invitation |
Example: fictional company. Ferncastle Analytics, Harborview Metrics, Marlow & Finch Logistics and every person named in this example are invented for illustration. Any resemblance to real companies or people is coincidental.
How to fill it in
Start it at verbal intent, not at contract-sent
The day a buyer says yes in a meeting is the day the plan starts, because that is when the invisible work begins. Waiting until the contract goes out gives away two of the weeks you will later wish you had.
Write every step as an event someone could verify
If a row cannot be confirmed by a second person without asking you, rewrite it. "Chase procurement" is an activity; "supplier number issued" is a fact.
Put a named owner on both sides
A step owned by "the buyer" is owned by nobody. If you cannot name the person, that is not a formatting gap, it is a discovery gap, and it goes in the risk log until the name exists.
Date the paper process backwards from signature
Ask how long legal, security and procurement each take at this buyer, then work back from the signature date. If the arithmetic does not fit, the date moves now, in your forecast, rather than in the last week.
Reconcile it with the mutual action plan weekly
The buyer-facing plan and the internal one must agree on dates. When they diverge, one of them is wrong, and finding out which is the most useful conversation of the week.
Let an unowned step move the forecast
A step with no owner and no date by the weekly review is not a task, it is a slip you have not booked yet. Move the close date or get the name; doing neither is how a commit becomes a surprise.
Where these go wrong
Steps written as intentions
"Follow up", "align with legal" and "keep momentum" cannot be confirmed or denied, so the plan reads green until the week it turns red. Events, owners, dates.
Every owner is on the seller side
A close plan where you own all the steps is a to-do list, not a plan. Most of the remaining work in a late-stage deal happens inside the buyer, and the plan has to say who is doing it.
Discovering the paper process in the final week
Security review time, legal turnaround and vendor registration are knowable in week one. Teams that ask early close when they said they would; teams that do not, discount to recover time they gave away.
Showing the close plan to the buyer
The buyer-facing version of this document is the mutual action plan. Sharing the internal one, with its risk log and concession ledger, hands over your negotiating position along with the dates.
Forecasting from the opinion instead of the plan
If the steps table says three unowned steps and the forecast says commit, the forecast is quoting a feeling. The honest category is whatever the unfinished rows support.
One giant "contract" step
"Contract" is five steps wearing one name: approval, security, redlines, final issue, signature. Collapsed into one row, four of them have no date and no owner, which is where the slip hides.
How Revspire keeps the buyer side of the plan honest
The close plan's weakness is that its buyer-side rows are reports of things you cannot see. You learn legal has gone quiet when a date passes, which is the most expensive possible way to learn it.
Revspire Deal Rooms carry the buyer-facing half: the mutual action plan lives in a room the buying group actually uses, and engagement is visible by stakeholder, so the internal plan's risk log fills from evidence rather than instinct. When the economic buyer has never opened the room, that is a row in the risk log before it is a slipped quarter.
Sales close plan template FAQs
What is the difference between a close plan and a mutual action plan?
Audience. The mutual action plan is shared with the buyer and agreed with them; the close plan is internal and holds what you would not show a buyer: the risk log, the concession ledger, the approval you are not sure your champion can get. The dates in the two documents should match, and a divergence is an early warning.
When in a deal should you start a close plan?
At verbal intent: the point where the buyer has said they want to proceed and the remaining work is approvals, paper and process. Starting earlier makes it speculative; starting at contract-sent means the security review and procurement setup are already eating weeks you never planned.
Who owns the close plan?
The account executive writes and runs it; the manager reads it in the weekly review instead of asking for a verbal update. The useful management question is not "how is the deal feeling" but "which rows have no owner or no date", because those are where the slip is hiding.
How is a close plan different from the forecast?
The forecast is a claim; the close plan is the evidence for it. A commit should be readable straight off the steps table: owners on every row, dates that fit the paper process, no open risk without a counter-move. When the table and the forecast disagree, the table is usually right.
What belongs in a close plan that the buyer should never see?
The risk log, the concession ledger and anything about your own approvals or margins. That is precisely why it stays internal and the mutual action plan exists as the shared surface. Keeping one document for both jobs ends with either a censored plan or an overshared one.
Related templates and reading
- Free templateBusiness case templateThe one page your champion takes to the person who signs: the problem, what today costs, the options, the numbers and a dated decision ask.
- Free templateSales battlecard templateA one-page card per competitor: why you win, where they are strong, landmine questions, objection responses and pricing guardrails.
- Free templateSales call scorecard templateA weighted 1-5 rubric for scoring recorded calls on agenda, discovery, value messaging, objections, next steps and talk/listen balance.
- Free templateSDR onboarding plan templateA week-by-week ramp plan for SDRs and BDRs: ICP, messaging, sequences, cold calls, qualification and the first qualified meeting, with gates.
- Template: the buyer-facing half of the same dealMutual action plan template
- Template: who approves, who influences, who signsStakeholder map template
- Blog: reading silence before it becomes a slipped quarterDeal going dark: the signals
Sources
- Gartner, The B2B buying journey (2026-10-15 (accessed))