Most objections are information, not resistance. The four you will hear constantly, and what each actually means.
12 min read · Level 2
Most objections are information, not resistance, and the reflex to defend converts a soft maybe into a firm no. Ask before you answer — half the time the stated objection is not the real one. And the price objection is almost never about price: it is unclear value, which is why discounting immediately addresses the wrong problem while teaching the customer that your number is negotiable.
An objection is a reason given for not proceeding. Most are one of four:
Price — 'it's too expensive' Timing — 'not this quarter' Authority — 'I'd need to check with…' Need — 'we already have a process'
Each means something different and each has a different response.
Because founders tend to treat every objection as a price problem and immediately discount. Usually price is not the issue — it is the stated reason for an unstated one.
And because objections are the most reliable product feedback you will get. The two or three you hear repeatedly tell you what is genuinely wrong with your offer.
'It's too expensive.' Usually means the value is not clear, not that the number is too high. Response: go back to the cost of the problem. 'You said it takes three hours a week. At your manager's cost that's roughly $780 a month — this is $99. Which part feels off?' If they still say no, it may genuinely be budget, which is different.
'Not this quarter.' Sometimes real, often a soft no. Response: 'What would need to be true for this to be a priority?' A real timing objection has a concrete answer — budget cycle, a project finishing. A soft no does not.
'I'd need to check with my director.' Not an objection at all — it is useful information you should have asked for earlier. Response: 'Of course. What will they want to know? Could we speak together?'
'We already have a process.' The most important one. Everyone has a process; the question is whether it is costing them. Response: 'What does that process cost you when it goes wrong?'
The pattern: ask a question rather than defending. Defending confirms it is a fight; asking treats it as information.
First-time founders often discount immediately at any price objection. This trains the customer that your price is negotiable, and it does not address the actual issue — which is usually unclear value.
The second mistake: arguing. You cannot argue someone into buying, and trying converts a soft maybe into a firm no.
The third: not distinguishing a real objection from a polite exit. 'Send me some information' and 'let's revisit next year' are usually noes. Treating them as live opportunities keeps a dead pipeline looking healthy.
'Tell me more about that' or 'which part specifically?' Half the time the real objection is different from the stated one.
Return to the cost of their problem. If value is clear, price objections mostly resolve themselves.
'What would need to be true for this to be a priority?' A real one has a concrete answer.
Offer to help make the case. Ask what the decision-maker will want to know.
It is the most honest objection. Ask what that process costs when it fails.
The reason is worth more than the deal was. And people who said no politely sometimes come back.
Every sales conversation, from the first call onwards.
Do not apply objection-handling technique in a problem interview during discovery. There you are not selling, so there is nothing to handle.
The most honest and most under-explored objection in B2B. Everyone has a process; the question is what it costs them when it fails. Founders treat it as a dead end when it is an invitation to quantify the pain the prospect has already normalised.
Answer it with a question: what does that process cost you when it goes wrong? The number is usually larger than the prospect has ever calculated.
"Send me some information", "let's revisit next quarter" and "keep me posted" are, the overwhelming majority of the time, noes delivered kindly. Recording them as live opportunities is how a pipeline stays full of deals that will never close and forecasting becomes fiction.
Learn to hear the soft no and mark it lost with a reason. A smaller honest pipeline is far more useful than a large hopeful one.
Create a free account to read the rest and apply it to your own startup.