The Sales Review Questions That Actually Work

Most sales reviews I see follow the same pattern. The manager reads the numbers. The salesperson explains the numbers. Everyone agrees the numbers should be better. The meeting ends, and next month looks exactly like this month.

I understand why this happens. A branch manager has targets to answer for, collections to track and a call with the regional head later that afternoon. Reading the sheet feels necessary because those are the questions the manager will face. But the team needs help with the customer conversation that will happen after the review.

The problem is not the people. It is the questions.

I look at what a question makes it safe to say. If admitting uncertainty invites a lecture, people learn to sound certain. They say the order is coming even when they have not spoken to the person who approves it. I would rather hear that the salesperson does not know, while there is still time to find out.

When you ask why is this number low, you are asking for a defence. You will get one. Budget issues, market conditions, a competitor who dropped price. Some of it will be true. None of it will change anything, because a defence is not a plan.

I do not ignore these explanations. If a distributor is holding back because payments from retailers are delayed, that matters. But I want to know which payment is holding up the purchase and whether the distributor has given a date for reviewing it. That gives us something to check instead of an explanation we can use every month.

Try asking what the customer said instead. Not what the salesperson thinks the customer felt. The actual words. When someone cannot tell you what the customer said, you have found the real problem. The conversation was not deep enough to learn anything.

I am not asking for a perfect transcript. I want the salesperson to separate what they heard from what they concluded. A purchase manager saying the quote has been sent to accounts is not the same as accounts approving payment. In a small owner led business, even a positive meeting may tell us little until we understand the owner's concerns.

Suppose a salesperson tells me that the customer found our price too high. I might ask, “Did they say it was outside their budget, or that another supplier offered the same thing for less?” Those answers need different conversations. The salesperson could then ask the customer, “When you say the price is high, what are you comparing it with?”

The second question I like is simple. What is the next step, and who agreed to it. Pipeline honesty improves the day you start asking this in front of the team. Deals with no agreed next step stop being called hot.

I make a distinction between our task and an agreement with the customer. Sending a quotation is our task. A customer agreeing to review it with their plant head on Thursday is a next step we can discuss. The difference matters because a busy salesperson can complete many tasks without learning whether the customer intends to buy.

I often hear that the salesperson will follow up next week. That tells me when we will call, but not why the customer would take the call. I might suggest asking, “Can we speak on Thursday after your purchase meeting to discuss any questions about the quotation?” If the customer cannot agree, I want us to understand what needs to happen first.

The third question is about the work, not the result. What did you do differently this week. A salesperson can control calls, preparation, questions and follow ups. They cannot control a signature. If you only review what they cannot control, you are not coaching.

You are commenting. I still review results because the business needs orders and payments, not just activity. But when a result is weak, I look for a specific part of the work that we can examine. More calls will not address a missing approval if every call goes to someone who cannot give it.

I also want to know what the salesperson learned from trying something different. Perhaps they asked about delivery requirements before discussing price and discovered that the customer needed staggered deliveries across two sites. That does not mean an order will follow. It means the next proposal can address a requirement that the earlier one missed.

There is one more habit that changes reviews in Indian sales teams particularly. Spend the first ten minutes on one deal in detail rather than thirty deals in summary. Depth teaches. Summary only informs.

I would choose a deal with a question others might recognise, such as a trial that went well but has not led to an order. I would ask who accepted the trial, what acceptance meant and who must approve the purchase. The salesperson handling a similar situation in another territory can then check those same gaps. This is more useful than asking everyone to repeat an expected closing date.

I am careful not to make that discussion a public interrogation. I ask the manager to help examine the deal, not prove that the salesperson handled it badly. If I want honest answers in front of colleagues, I cannot punish the first person who gives one.

A review should leave the salesperson with one thing to do differently on Monday. If it does not, the hour was spent describing the past instead of shaping the next month.

Managers often tell me they do not have time to coach. They are already spending the time. It is sitting inside the review. They are just using it to read the scoreboard.

This week, I suggest taking one deal from your next review and asking the salesperson to write down the customer's agreed next step. If there is none, use that discussion to prepare one question they can ask the customer to clarify what happens next.