A quotation was declined. Should you lower the price?

Give the outcome a clear description before assigning a reason. A confirmed rejection, a deferred project and an unanswered follow-up are different states. A contact who has stopped replying has not necessarily compared your offer and found it wanting. Keep the uncertainty visible rather than converting silence into a price objection.

For each case, record the service offered, the approximate scope, the timing and who provided the information. Separate the buyer's explanation from the account manager's interpretation. Agree when to follow up and when to close an enquiry administratively. Closing a record does not give you evidence about why the buyer did not proceed.

This need not become a reporting project. Start with a handful of recent, comparable decisions. The discipline matters more than a sophisticated dashboard: somebody should be able to read the note and see what is known, who said it and what remains unresolved.

Offer a short conversation whose purpose is to learn. Explain that you are not asking the contact to reopen negotiations and that participation is optional. Honour that promise. A buyer who expects every answer to trigger another sales argument has little reason to give a candid account.

Ask what prompted the original enquiry, which alternatives were considered and when the direction changed. Who needed to be comfortable with the decision? What did the proposal make easy to understand, and what required further explanation? If price comes up, ask what the comparison involved. A lower total can reflect a smaller scope, a different delivery arrangement or a genuinely lower rate for comparable work.

The GOV.UK guidance on in-depth interviews recommends open, neutral questions and real experiences rather than generalisations. Applied here, that means asking the contact to describe the decision they made. Asking whether a cheaper offer would be attractive invites a hypothetical answer; it does not establish that they would have bought it.

Leave room for limits. Your contact may know the operational concern but not the full budget discussion. Record whose perspective you have instead of treating one person's account as the complete explanation of an organisation's choice.

The following situations are fictional examples, not reported IndustrylinQ client outcomes. They show how an observation can support a useful question without yet supporting a commercial conclusion.

On a small screen, scroll horizontally to read the full table.

In its guidance on analysing research, GOV.UK distinguishes observations from interpretations and subsequent actions. That is a useful discipline for a commercial review too. First agree what the notes support, then discuss possible explanations, and only then choose a response. The method helps structure your reasoning; it is not evidence of an increase in sales.

Include delivery colleagues in that discussion. A salesperson may hear an objection to the timetable; someone doing the work may recognise an unresolved dependency. Neither interpretation should overwrite what the customer actually said. Keep both as possibilities until there is a reason to prefer one.

Do not combine an established maintenance service and a complex transformation project into one verdict on your pricing. Their decision processes and delivery risks differ. Group cases by the question the customer wanted to solve and by a reasonably similar scope. Note changes in timing or circumstances that might affect the comparison.

Look at some successful quotations as well. If buyers and non-buyers both struggled to understand the same onboarding requirement, that supports a case for clearer communication. It does not establish that this requirement caused the losses. People who agree to an interview may also differ from those who remain silent. Keep unknown reasons in view and avoid presenting a small collection of conversations as representative market statistics.

Imagine a fictional service business whose prospects repeatedly ask how much of their own staff time the start will require. The team suspects that an unclear handover creates avoidable uncertainty. A focused response would be to state the required roles, information and agreed time commitment more clearly in the proposal. A blanket discount would leave that question unanswered.

Check the proposed change with the people responsible for delivery. Can the work start in a smaller stage without creating expensive rework? Which customer dependencies remain? Who can agree a different start date, and when must a change to scope or responsibility be reviewed? Give employees room to adapt the offer within boundaries they understand and can explain.

Choose one change and decide what you will look for afterwards. Are customers clearer about their responsibilities? Are fewer assumptions left unresolved? Can the team deliver what was promised? Consider the sales result alongside these observations, while recognising that one subsequent win does not prove the change caused it. A substantial redesign belongs in a broader discussion about developing the service, including its operational demands.

Set aside a short recurring conversation between commercial and delivery colleagues. Review a few comparable decisions and select one question worth investigating. Avoid turning the discussion into a league table of individual losses. Staff need to be able to say that a reason is unknown without inventing a confident explanation to protect themselves.

Keep relevant notes in an agreed place, restrict personal detail to what the work requires and make someone responsible for following up the chosen change. A simple shared record can be enough. Start with one declined proposal, one comparable win and one unresolved question. Where the same gap keeps appearing between the sales promise and delivery, business process analysis can help examine the connection before you change the price, the workflow or the software.