“The meeting went well” is an easy recap to give. People asked questions, the conversation flowed, and the customer seemed interested. Everyone leaves with a little optimism before returning to the rest of the calendar. Then somebody asks what happens next, and the answer gets less precise: perhaps another call, once a few more people have been brought up to speed.
I want to know what changed because we met. Does the customer understand the proposal better? Did we resolve a concern or discover one we need to address? Is it clearer who should be involved? Those answers help us judge the value of the conversation and prepare for what follows. The energy in the room tells us much less.
What changed for the customer?
Imagine two customer conversations.
In the first, the customer likes the presentation and asks several questions about functionality. The team answers confidently. The call ends with positive feedback and a promise to reconnect. Nobody establishes whether the demonstrated workflow meets an important requirement, and nobody identifies who needs to approve the next step.
In the second, the customer challenges an assumption about access to its data. The discussion becomes more difficult. The team discovers that its proposed evaluation needs a data owner involved and a narrower scope. By the end, the customer knows what needs checking, who should join, and how that work will help determine whether the evaluation is feasible.
The second meeting has produced a more usable outcome even though it was tougher. Why? Because it improved the quality of the information both parties can use to decide what to do next.
If we consistently reward the first kind of meeting with enthusiastic internal recaps, we teach the team to avoid uncomfortable questions. People become reluctant to raise a concern that might spoil the feeling of progress. Looking at what the customer learned gives the team a reason to bring those concerns into the open.
Agree on what the meeting is for
An early conversation might help a customer decide whether a problem deserves attention. A technical session might establish whether a requirement can be met. A relationship-building call may simply help people understand each other's priorities. Knowing the purpose lets you plan a useful conversation and assess it honestly afterward.
Write the purpose in language you can share with the customer: “We'd like to work out whether a small evaluation makes sense. That means agreeing on what to try and identifying anything that would prevent us from doing it.” They can revise that proposal or tell you they aren't ready. Either answer helps you use the time well.
This also makes it easier to change direction during the meeting. If the data-access concern prevents an evaluation, it deserves attention before another product overview. The group can agree to address it and bring in the right person. Everyone then understands why the conversation has moved away from the original agenda.
Leave a record people can use
Five short entries are enough to capture the result:
- Question: What is the customer trying to determine?
- What we learned: What was shown, confirmed, or corrected?
- What remains open: Which questions or disagreements still need attention?
- Who needs to be involved: Who can help answer those questions or authorize the next step?
- Next action: Who agreed to do what, and by when?
For the data-access discussion, the record would explain that the customer is considering a limited pilot, but the proposed data source requires a separate review. The data owner needs to assess the request before the pilot can be scoped. The seller will prepare the proposed data requirements for that conversation. If the customer hasn't yet agreed to arrange it, record that too. A suggested next step shouldn't become a commitment simply because it appears in the recap.
Share the account in ordinary language: “Here's what I think we established and what we still need to work through.” Ask the customer to correct it. That exchange can reveal a misunderstanding while it's still easy to address, and it gives both sides a useful starting point when they meet again.
Sometimes the record will explain why the customer is pausing or declining to proceed. The problem may be less urgent than expected, a required capability may be missing, or changing the process may cost more than the improvement is worth. Those answers need to influence the plan. Treating each one as an objection to overcome can keep the team working on a deal the customer has already given it reason to reconsider.
Coach from the substance of the conversation
For a sales leader, these records make coaching more specific. Repeatedly leaving meetings without knowing who can approve the next step suggests a need for better questions about responsibility. Demos that generate enthusiasm but leave the same technical concern unresolved may need a different approach. The team may need to show something more convincing, involve a specialist, or acknowledge a product limitation.
The same approach makes it easier to discuss a difficult call. Ask what challenged the team's assumptions, how they responded, and what the customer now understands. People can learn from that conversation without having to defend whether the meeting “went well.” When the recap explains what changed and what follows from it, it has done something useful for the customer and the team.