وقتی مشتری می‌گوید «باید بررسی کنم»، تصمیم دقیقاً کجا گیر کرده است؟

“I need to review it” can waste sales time—not because of the phrase itself, but because it often pushes the seller into the wrong reaction. They send more files, offer a discount, or increase follow-up activity while still not knowing where the decision has stopped.

This phrase is not necessarily an objection. The buyer may lack sufficient information, worry about execution or supply continuity, lack decision authority, or face a timing issue inside the organization. As long as you treat these situations as the same thing, your response will be random.

This is a diagnostic problem before it is a problem of applying pressure to close. The goal of the next conversation should not be a fast “yes”; it should be to clarify what is preventing the decision from moving.

First, distinguish opposition from a stalled decision. Opposition means the buyer has a specific reason to reject an option; for example, they find the scope, commercial terms, or delivery model unsuitable. A stall means it is not yet clear what is insufficient for the decision to continue.

The response to opposition is defending or redesigning the proposal. The response to a stall is a diagnostic question. If you confuse the two, you may offer a prepared answer to a problem that has not yet been defined.

Instead of asking, “What do you need to review?”—which often produces another vague answer—make the conversation narrower and easier to choose from. Say: “So we can close the right path, is your review mainly about solution fit, execution risk, internal alignment, or timing?”

This question does not force the buyer to disclose everything. It simply locates the conversation and helps you move from general follow-up to a decision-enabling discussion.

The first condition is insufficient information. The buyer may have seen the proposal but still be unable to compare it with their process, technical requirements, hidden costs, or available alternatives. Sending a generic document at this point usually adds ambiguity because it transfers the burden of interpretation to the buyer.

To diagnose this condition, ask: “Which part needs to be clearer for you to make a decision?” and “If you had to explain this proposal to your colleagues, which question could you not answer yet?” The second question matters because the buyer often needs to make the decision defensible internally, not merely understand it personally.

When information is missing, the right person to involve is the person who can assess the required detail. That may be an operational user, a technical owner, finance, or procurement. Do not ask the buyer simply to introduce “relevant people”; specify which uncertainty requires which role.

The next step should be a narrow, decision-enabling output. In a hypothetical example, if the uncertainty concerns compatibility with the current process, a short session with the execution owner and one relevant implementation scenario will be more useful than a general presentation.

That session should end with a decision question: was this part of the uncertainty resolved or not? If the answer is unclear, you should not yet count it as forward movement in the sales opportunity.

The second condition is execution or supply risk. Sometimes the buyer is interested in the value of the solution but worries about disruption, delay, dependency, delivery quality, support, or supply capacity. In that situation, a discount may even send the wrong signal, because the buyer is seeking lower risk, not merely a lower price.

To diagnose it, ask: “If this decision does not deliver the intended result, what is the biggest consequence for your team?” and “Which stage of execution or supply needs to become more reliable for you?” These questions invite the buyer to describe the actual risk rather than defend a position.

In this condition, the right person is not always the original buyer. An operations leader, quality owner, project manager, procurement owner, or the person accountable for continuity may need to join. On your side, someone should also be present who can answer precisely about the execution mechanism, commitment boundaries, and issue-response plan.

The next step for a risk issue is to demonstrate controllability. For example, in a hypothetical industrial scenario, instead of repeating product features, review delivery stages, control points, the owner of each stage, and the path for handling disruption.

If part of the risk cannot be eliminated, do not hide it. Agree on who will decide about it, based on what signal, and at what time. Making risk explicit is more credible than promising to remove every risk.

The third condition is lack of authority or internal alignment. The buyer may be interested but unable to decide alone. Sometimes a decision-maker is absent; at other times, roles disagree about priority, budget, risk, or how the work should be done.

Two useful questions are: “Who needs to be confident for this decision to move internally?” and “Is the main disagreement about the need itself, the solution choice, or responsibility for execution?” The second question prevents you from assuming that all internal participants share the same view.

The person who should join is not necessarily the most senior person in the organization. Involve the owner of the bottleneck: the budget owner, process owner, risk owner, or the person who must accept day-to-day execution. If roles are unclear, map the decision first and arrange a multi-person meeting afterward.

The next step can be a short alignment meeting, but only if its output is clear. Before the meeting, agree on which decision must be made: confirming the need, selecting the delivery model, assigning responsibilities, or defining a purchase condition.

A meeting held only to “review again” usually does not move the bottleneck. Every meeting should have one decision, one owner, and one clear next action.

The fourth condition is low time priority. This does not mean the proposal has no value. The issue may be real, but the organization may currently lack execution capacity, budget, management attention, or sufficient urgency to act.

Applying pressure at this point weakens the relationship and keeps the sales forecast unrealistic. An opportunity without a timing trigger should not be treated as active merely because the buyer expresses verbal interest.

To diagnose it, ask: “What would need to happen for this to become a priority for you?” and “Is the main constraint time, resources, budget, or an earlier project?” Record the answer carefully.

“Contact me later” without a specific trigger is not a next step; it is an undefined delay. When time priority is low, the owner of the timeline should enter the conversation. That may be the unit leader, budget owner, or planning owner.

If access to that role is not reasonable, use the current buyer to secure a small commitment: define the return trigger, the review date, and the information needed by then. This small commitment makes the opportunity status more realistic.

Set the next step around an event, not the seller’s calendar. In a hypothetical example, if the buyer says the decision will be reviewed after the production plan is finalized, follow-up should be tied to that event and one specific question.

Repeated messages without a change in decision status only move you further from reality. Good follow-up is not a reminder of the seller’s presence; it is connected to a specific change in the decision conditions.

For practical use, after every “I need to review it,” record four things in the opportunity file: the likely bottleneck, the evidence supporting that interpretation, the role or roles needed to resolve it, and the next step with a clear output.

If any of these four items is unclear, the opportunity is not ready for forecasting. In that condition, instead of changing the sales stage or increasing pressure, design another diagnostic conversation.

The seller’s job is not to answer every vague statement. It is to turn ambiguity into a decision-ready problem. Once you know whether the buyer faces missing information, risk, lack of alignment, or low time priority, you do not need to apply more pressure; you need to design the conversation, the participants, and the next action more precisely.