Building the Close Plan on the Call: How to Get a Buyer to Agree to Dates Out Loud

A document is not a commitment

I have sent a lot of close plans as attachments. Nicely formatted. Owner column, date column, a little RAG status thing I was proud of. Almost none of them changed what the buyer actually did.

The ones that worked were different in exactly one way. The buyer had said the dates out loud, on the call, in their own voice, before I ever typed them. The document was just a receipt.

That is the whole idea here. A mutual action plan sales call is not a call where you present a plan. It is a call where you get the buyer to build the plan in front of you, using their own knowledge of how their company buys things, and then you write down what they said. If you build it and send it, you own it. If they build it and you send it, they own it. Ownership is the only thing that makes a close plan worth anything in week six when the deal has gone quiet.

Why the last eight minutes, and not the follow-up email

The close plan conversation belongs at the end of a demo or a strong second call, and it belongs there for a reason that has nothing to do with time management.

Right after a good demo, the buyer is in the most cooperative state they will be in for the rest of the cycle. They have just told you they like it. They have just asked implementation questions. Their guard is down because they are imagining owning the thing. That is the window where a question like "who else has to see this before you can sign" reads as helpful rather than pushy.

Send that same question by email three days later and it reads as a sales rep chasing a deal. Same words. Completely different reception. The buyer answers with "let me check" and you have lost a week.

So I stop the demo with time left. Not five minutes, which turns into two. Eight, which turns into six. I say a version of this:

"I want to leave the last few minutes for something boring but useful. If you did decide to move forward — and I'm not asking you to decide that today — I want to understand what actually has to happen at your end. Mostly so I don't waste your time on steps you don't have, and so I don't miss one that takes three weeks."

That framing does two jobs. It removes the commitment pressure, which is what makes people vague. And it positions the questions as risk reduction for them, not pipeline hygiene for you. Every buyer has had a vendor blindside them with a procurement step nobody planned for. Nobody wants that again.

Start at the end and make them name a date

Most reps ask about timeline in a way that guarantees a useless answer. "What's your timeline look like?" gets "we're looking to move in the next quarter or so." That is not a date. That is a mood.

Ask for the go-live instead. Not the decision, not the signature — the day the thing is actually working.

"When do you need this live and running? Not signed. Actually being used by the team."

This question is harder to dodge because it points at an operational reality rather than a purchasing intention. People who have no idea when they will sign often know exactly when they need something working, because the need is attached to something real — a contract expiring, a new team starting, a season, an audit, a system being switched off.

When they give you something soft, tighten it once. Just once, gently.

If they say "Q3," ask: "Is that live at the start of Q3, or live by the end of it?" That is a fair clarifying question and it costs you nothing. It usually produces an actual month.

If they say "as soon as possible," say: "I hear that a lot and it usually means one of two things. Either there's a hard date driving it, or it just means it's a priority but nothing breaks if it slips. Which one is this?" I have had buyers laugh at that and then tell me the truth. Both answers are useful. "Nothing breaks if it slips" is a real answer and you would rather know now.

Then the follow-up that matters more than the date itself: "What happens on that date?" or "What's driving that?"

A date with a reason behind it is a deal. A date with no reason behind it is a guess the buyer will abandon the moment something louder lands on their desk. If the answer is "our current contract renews on the fourteenth" or "the new warehouse opens in March" or "the board asked for this by the end of the half," you have something to work backwards from. If the answer is "just, you know, sooner is better," you have a nice conversation and no deal yet, and the rest of this call should be about finding the real driver rather than pretending you found it.

Work backwards, out loud, and let them do the arithmetic

Once you have a go-live date, do not jump to next steps. Count backwards from the date, out loud, and make the buyer supply the numbers.

"Okay, so live by March 1. Working back from that — how long does onboarding usually take for a tool like this on your side? Not our side, yours. Getting people trained, getting the data in."

Let them answer. Whatever number they give, take it. If they say two weeks, that means signature by mid-February.

"So paper signed by roughly the middle of February. Before that, what does legal usually need? Do you redline, or do you sign on standard paper?"

Let them answer.

"And security — has anything like this gone through a security review here recently? What did that look like?"

Let them answer. Then procurement, then the vendor onboarding portal, then the insurance certificates, then whatever else exists at their company that does not exist at anyone else's.

The magic is in who does the subtraction. When I say "security takes four weeks so we'd need to start Monday," that is a sales rep applying pressure. When the buyer says "security is usually about four weeks, so honestly we'd need to kick that off pretty soon," that is a person discovering their own deadline. I have watched buyers talk themselves into urgency I would never have gotten away with manufacturing.

When they land on an uncomfortable conclusion, do not rescue it. Do not say "no problem, we can be flexible." Say nothing for two seconds. Let the discomfort sit. The silence after a buyer realises they are already late is the most productive silence in sales.

The best single question in this whole sequence is not about your deal at all: "What was the last piece of software your team bought, and what did it have to go through?"

People describe past processes accurately and future processes optimistically. Ask about the future and you get the version where everything goes smoothly. Ask about the last purchase and you get the security questionnaire that took six weeks, the procurement person who was on leave, the legal team that rejected the standard MSA. That is the real map.

Get names, not roles

"Who else needs to be involved?" gets you "we'll need to loop in IT." That is a role. Roles do not attend meetings. People do.

Push one level: "Who in IT specifically? Is that someone you work with regularly?" And then the question that turns a name into a step: "What would they want to see? If we did thirty minutes with them, what would make that thirty minutes worth their time?"

Now you have a named person, a reason for a meeting, and an implicit agreement that the meeting should happen. Ask for the date on that one too. "When could we get that on the calendar? Does it make sense for you to introduce us, or do you want me to reach out?"

In multi-stakeholder rooms this gets interesting, because the person who names the date is very often not the person asking the hardest questions. In the kind of room I describe in the freight and 3PL demo script, where everyone is hunting for where the product breaks, the ops lead grilling you on exception handling may have no budget authority at all. Ask the whole room who owns the date and watch who they look at.

And in rooms where the buyer has been burned before, the close plan question does something extra. When I wrote up the clinical demo for a CMIO who has already killed two vendors, the thing that changed the temperature was not the product — it was demonstrating that I knew their process would be brutal and I wanted it mapped rather than glossed over. Buyers who have killed vendors respect a rep who plans for their own execution.

Read it back and let them correct you

Before the call ends, read the whole thing back. Out loud. In order.

"Let me make sure I've got this. Live by March 1. Two weeks of onboarding on your side, so signed by mid-February. Legal needs about a week if we're on your paper. Security review kicks off once we've done the session with Priya, and that's three to four weeks. Which means we'd want Priya's session in the next two weeks. Did I get any of that wrong?"

End with "did I get any of that wrong," not "does that sound right." People correct more willingly than they confirm. "Sounds right" is a reflex. "No, actually, security is more like six weeks in December because of the freeze" is information you would never have gotten from a yes.

This is also where you find out whether they are actually agreeing. A buyer who is genuinely bought in will edit your read-back. A buyer who is being polite will accept every word of it, and you should treat unbroken agreement as a warning sign rather than a win.

One more thing worth doing here: name the commercial step explicitly. "And somewhere in there we'd need to agree commercials — do you want to do that before or after security?" Buyers who intend to grind you on price will often reveal it right here by pushing pricing to the very end, after you have spent your leverage on a technical win. That is the setup I deal with in the pricing negotiation script for holding price after the technical win, and the close plan call is where you first see it coming.

When the buyer refuses to commit to anything

Sometimes you run all of this and get nothing. No date. No names. "Let us digest it and we'll come back to you."

This is not a failure. It is the most useful thing you will learn all week, and it is worth more than three cheerful calls that go nowhere.

But you have to work out which kind of nothing it is. There are two, and they look identical.

The first is can't. The buyer does not know the process because they have never bought anything before, or they do not have the authority to name a date, or the real decision maker has not been told this evaluation is happening. This buyer wants to help and physically cannot. You find out by asking: "Totally fair. Who would know what the process looks like? Is that something you'd need to check internally?" If they say yes and name someone, you have a coach with no power, which is workable but requires you to get to the person with power.

The second is won't. The buyer knows exactly how it works and is not telling you, because you are not a priority, or they are using you to price a competitor, or the project is not funded. You find out by naming it plainly and without any edge in your voice:

"That's fine, and I'm not going to push. Can I ask you something straight though — is this something you're actively trying to solve this quarter, or is it more of a nice-to-have that you're keeping an eye on? Both are completely reasonable answers. I just want to know which one so I follow up appropriately and stop bothering you if it's the second one."

I have never had a buyer take offence at that question. I have frequently had them tell me the truth, which is usually the second one. Then you thank them, agree a genuinely light touch cadence, and move the deal out of your forecast. The cost of that honesty is one deal you were never going to close. The return is every hour you were about to spend on it.

What you must not do is send a close plan anyway. A close plan to a buyer who refused to give you a date is a document you wrote to yourself, and you will spend the next month updating it and feeling productive.

The one-page format that goes in the recap

Send it in the body of the email. Not an attachment, not a link to a shared doc the buyer will not open, not a slide. Body of the email, in a table, so it is visible on a phone in the ten seconds they give it.

Four columns: step, who owns it, date, what has to be true first. That last column is the one everyone leaves out and it is the one that does the work, because it makes dependencies visible. "Security review — Priya — starts Feb 3 — needs the technical session done and our SOC 2 report shared."

Order it backwards from the go-live, or forwards from today, but be consistent. Put the go-live date at the top as a header line so the whole thing reads as a plan to hit their date, not a plan to close your deal.

Then this line at the bottom, which matters more than the table:

"I've written these down as I heard them. If I've got any of the dates or owners wrong, reply with the corrections and I'll update it."

You are asking for a correction, not a confirmation. Corrections get replies. Confirmations get ignored. And the reply is the artefact you actually want, because a buyer who has typed "actually legal takes two weeks not one" has now co-authored the document.

Bring the plan to every subsequent call. Open with it. "Last time we said the technical session by the eleventh — we did that. Next up is security. Is the third still realistic?" Two minutes at the top of each call, every time. That is what turns it from a document into a shared object.

The rule for when to stop maintaining it

Here is the rule I use, and I would rather have one clear rule than judgement calls at eleven at night.

If the buyer has not edited the plan in two consecutive touchpoints, stop maintaining it and go back to the phone.

A close plan is alive when the buyer changes it. Dates move, owners change, a step gets added — all of that is health. Movement means someone on their side is still thinking about it.

A close plan is dead when only you are touching it. If you have updated it twice and every date on it has slipped and the buyer has said nothing about any of it, the document is no longer describing reality. It is describing your hope. Continuing to update it feels like deal management and is actually avoidance, because updating a spreadsheet is much more pleasant than calling someone who is dodging you.

When you hit that point, do not send another version. Call. And if they do not pick up, send the shortest email in your arsenal: "Are we still trying to hit March 1, or has that moved? Happy either way, I just need to know which."

That email gets answered more often than any polished recap I have ever written, because it asks for one thing and gives them permission to say no.

Practise the eight minutes, not the demo

Most reps rehearse the product walkthrough and improvise the close plan. It should be the other way round. The demo you have done a hundred times. The backwards-counting sequence you do badly, under time pressure, with a buyer who is already reaching for their next meeting.

If you want to get better at this, the drill is narrow and repeatable: run the last eight minutes only, against a buyer who answers in vagueness, and practise tightening "soon" into a month and a month into a date without sounding like you are interrogating them. That is exactly the kind of thing I would put on repeat in DrillCall — a handful of reps, same eight minutes, until asking "who else has to see this before you can sign" comes out as naturally as asking whether they can see your screen.

Get the dates said out loud. Everything else is transcription.