“I need to understand what I am getting.”

The client asks this question before turning you down. The salesperson responds by explaining what the proposal includes, lists the stages and sends a proposal. Then a reason appears in the CRM system: “Too expensive”.

Stop.

What exactly did the client call expensive: the amount, the risk of making a mistake, an unnecessary part of the proposal or a result they never saw? The sales team does not know yet. But the owner already gets a ready-made conclusion: the price is not acceptable.

The business then starts fixing a presumed problem. It approves discounts, puts together a cheap package, changes its target audience and teaches salespeople how to respond to the objection.

But no one has reviewed the conversation.

The client’s last words are a fact. The reason for the loss is not yet established

The client did say “too expensive”. You can check this in the call or correspondence.

But that phrase does not yet tell you why they did not buy. To establish the reason, you need other facts: what the client wanted to change, who made the decision, what they compared the proposal with, what they feared, what happened after the proposal and when price first came up in the conversation.

Look at the last point when the outcome of the deal could still have been changed.

Did the salesperson find out what the client needed to achieve, or go straight into describing the product? Did they understand who controlled the budget? Did they ask what criteria would be used to compare the options? Did they examine the risk of buying? Did they agree on the next step? Or did they simply wait for a reply after sending the proposal and offer a discount at the first pause?

Different reasons now emerge. And different actions.

If the person they spoke to did not control the budget, the route to a decision needs to change. If the client did not understand what result they were paying for, you need to examine how the proposal relates to what they need to achieve. If the risk of implementation stopped them, a discount does not remove that risk. If the salesperson was the first to bring up a price reduction, the sales team itself made bargaining the main subject of the conversation.

And only if the buyer understood the result, assessed comparable options, had the authority to make a decision and still turned it down because of the amount is there a basis for the price explanation.

Not proof for the whole market. A basis for the next check.

“What if it really is too expensive for them?” is a fair question

Two different jobs are often mixed up here.

The first is to understand why a particular deal was lost. This is the job of the salesperson and the head of sales. They reconstruct the conversation from the facts and separate the client’s words from their own explanation.

The second is to decide whether the price suits the market and the segment and makes financial sense for the company. That is a decision for the owner and those responsible for the product.

The dividing line is not the word in CRM. It is the quality of the evidence.

One client may not have had the budget at that moment. Another may have been comparing the proposal with one that included less. A third may not have seen any difference between suppliers. A fourth may actually have chosen a comparable option at a lower price.

Every record may say “too expensive”. But cutting the price based on those four entries means making one decision for four different situations.

Sometimes the price really is not acceptable. I would not argue with the client or try to prove that they are getting their sums wrong. But before changing the price, you need to understand who finds it unacceptable, what they compared it with and what value they saw in it.

A discount before a review makes the loss more costly

A discount seems like a quick answer: the client mentioned the price, so we change the price.

If the problem was unclear value, the proposal will become cheaper, but no clearer. If the decision stalled with an employee who lacked authority, the discount will go to someone who still cannot buy. If implementation worries the buyer, a smaller amount does not answer the question of who will be responsible and what will happen if something goes wrong.

There is also a second effect. When a salesperson offers to lower the price before finding out what the client needs to achieve and what their selection criteria are, they tell the client two things: the price is flexible, and the salesperson has no other grounds for the decision yet.

Bargaining becomes logical.

Then the sales team records “too expensive” and brings the owner a problem it has made worse itself.

So you need to review more than the client’s last remark. You need to find out who first put price at the centre of the conversation and what was already understood about the decision at that point.

The head of sales needs action to change, not a list of reasons

You can list twenty reasons for refusal and still learn nothing. The salesperson will choose a nicer wording, the report will become more detailed, and the next conversation will go the same way.

A reason is only useful when it changes how you work on the next similar deal.

Start with one recurring part of the process. For example, clients receive a proposal before the salesperson has found out the selection criteria and who is involved in the decision.

The head of sales opens several conversations from lost deals and checks four things:

  • what the client wanted to achieve;
  • who made the decision and by what criteria;
  • when the subject of price came up and who raised it;
  • what the salesperson did after the client expressed doubt.

After the review, the head of sales does not write “identify needs better”. They change a specific requirement: before sending the proposal, the salesperson records what the client needs to achieve, the person involved in the decision, the selection criterion and the agreed next contact. The head of sales then checks this in new deals.

After a week, it is too early to judge whether the price is now right for the whole market. But behaviour is already visible: the salesperson has stopped offering a discount first; found someone with authority before making the proposal; recorded not just the refusal, but the fact on which the conclusion is based; the head of sales spotted a missed step before the deal was closed.

If nothing has changed, the new list of reasons has not worked. You need to look at whether the requirement was clear, whether the salesperson knew how to meet it and whether the head of sales checked that it was met.

A longer report does not count.

The owner needs a conclusion they can base a decision on

The owner does not have to listen to every call from a lost deal. But they must see what the sales team bases its conclusion on.

Not “clients find it too expensive”, but: which group of deals has repeated refusals, what buyers are comparing, who took part in the decision, what value they confirmed and what the head of sales has already checked.

Then price stops being the salesperson’s opinion multiplied by the number of closed records. There is a basis for choosing an action: keep the price as it is, change what is included, come back at a different time, reach another person involved in the decision, remove the risk of buying or test the proposal with another segment.

Product, price and the permitted discount remain the owner’s responsibility. The sales team’s job is to bring them a reason they have investigated, not a label.

Where RENTROP fits in

That is exactly why, in our “turnkey sales management” model, we look at more than whether CRM has been filled in.

The head of sales reviews deals daily and changes the team’s actions. The business development director then checks the quality of their work: what facts the conclusion rests on, what decision was made and whether the salesperson’s behaviour changed in the next similar situation. AI helps search data and communications for recurring refusals, missed steps and instances where the conversation does not support the conclusion.

Strategy, product, price and the marketing budget remain with the owner. RENTROP is responsible for daily sales management within the agreed scope of work.

Price is the owner’s decision. Without a review of the conversation, “too expensive” is still just the client’s last remark.

Before cutting the price, open several of the most recent refusals and find the point after which the salesperson stopped trying to understand the client’s decision.