The demonstration went well.
The buyer asked questions, the technical team seemed interested and everyone thanked each other for their time.
Then the call ended.
Your salesperson believes the next step is a pilot. The buyer thinks they need an internal discussion first. The technical lead is waiting for an answer about an integration.
Nobody is necessarily wrong. They just left the meeting with different ideas about what would happen next.
That is an avoidable problem.
The final few minutes of a sales call are a good opportunity to make sure everyone understands the conversation and agrees on what, if anything, should happen next.
You do not need a clever closing line. You need to listen, make a useful suggestion and give the buyer room to respond.
Let’s imagine a security team has just seen a demonstration of your product.
The buyer likes what they have seen, but they are unsure how it would work with a system their infrastructure team manages.
You could finish by saying:
“Thank you for your time. I will send the presentation and follow up next week.”
Polite, but it does not address the question that matters to them.
Instead, you might say:
“Based on the integration questions you raised, I suggest a short technical session with your infrastructure lead. We can show how the connection works and discuss what your team would need. Would that help, or is there something else you need first?”
Now the buyer has something specific to react to.
They might agree. They might say their infrastructure lead needs a short explanation before joining a call. Or they may tell you that their team needs to discuss the project internally before involving anyone else.
All of those answers are useful.
The point is not to secure another meeting at any cost. It is to understand what would help the buyer make progress and whether your suggested step fits.
Before making the suggestion, it helps to confirm what you heard.
“You mentioned that your team wants to understand the integration before deciding whether to run a pilot. Have I got that right?”
That gives the buyer a chance to correct you.
Perhaps the integration is only one concern. Perhaps the bigger issue is whether the team has time to run a pilot at all.
Better to learn that on the call than send an invitation that nobody is ready to accept.
And yes, you can still ask whether they have questions.
A buyer may have been waiting for the right moment to raise something. An open question can reveal a concern you have not discussed.
The useful part is what you do with the answer.
If they ask about deployment, find out what they need to understand. If they need information for a colleague, agree what would be useful to send.
If you do not know the answer, say so and agree who will get back to them.
Once you have a next step, make it clear.
Who is doing what? Does anyone else need to be involved? When does the buyer expect an answer or want to speak again?
Sometimes the next step will be a meeting. Sometimes it will be a document, an introduction or time for the buyer to have a conversation without you.
Do not turn an internal discussion into a failure simply because it does not appear as a meeting on your calendar.
After the call, send a short note that reflects what you agreed.
You might write:
“Thanks for the conversation today. Your team will discuss the integration internally, and I will send a short explanation of the access required. Once you have had a chance to review it, let me know whether a technical session would be useful.”
That note gives the buyer something they can forward and gives your team a record of the commitment.
Then send the explanation you promised.
A clear next step will not guarantee a deal. The buyer may decide that the product is not right, the timing is wrong or another project needs their attention.
But both sides will have a better understanding of the decision and what happens next.
That is a much better way to end the call than leaving everyone to guess.

Leave a Reply