The first time I heard "we need to think about it," I thanked the prospect and said I'd follow up in a week. That was a mistake. Not because following up is wrong, but because I had no idea what I was following up on. The prospect hadn't said no. They also hadn't said yes. They had said something vaguer than either — and I had let it slide.
Most sales objections are not what they appear to be on the surface. When someone says "it's too expensive," they are rarely telling you the price is wrong. When they say "we're not ready yet," they are rarely describing a calendar problem. Objections are usually compressed expressions of something unresolved — a missing piece of information, an unanswered concern, a risk they haven't figured out how to articulate.
Once I started treating objections as questions in disguise, my close rate changed. Here are the five I hear most often, what each one actually means, and the language I use to move forward.
"It's too expensive"
This is almost never about the number. If it were, the conversation would have ended before you got here. The prospect kept talking because they see value. The price objection usually means one of two things: they haven't yet connected your price to a concrete outcome, or they're comparing it to doing nothing — which costs zero dollars on a spreadsheet and carries all its real costs invisibly.
What I say: "Help me understand what expensive means in this context. Is it that the budget isn't there, or that you're not sure the return justifies it?" That question almost always opens the real conversation. If it's a budget problem, you can discuss timing, phasing, or structure. If it's a value question, you have something concrete to address.
Then I do the math with them. What is the cost of the problem they're solving? If they're spending eight hours a week on a process my product replaces, and their team costs $80 an hour, that's $33,000 a year. I'm not $33,000 a year. Most founders never do this arithmetic out loud, so the prospect has to do it themselves — and most won't.
"We're not ready yet"
This one is the softest no in existence. Most founders hear it and schedule a follow-up for three months out. That follow-up almost never converts. "Not ready" is usually code for something more specific: they're waiting for budget approval, a competing project is consuming attention, or they haven't built internal consensus yet. The problem is you can't solve any of those things if you don't know which one it is.
What I say: "What would need to be true for the timing to be right?" This forces specificity. If they say they need sign-off from a VP, that's a solvable process problem — you can offer to send something directly to that VP, or to do a ten-minute call with them. If they say they're mid-way through a product launch and can't onboard anything new right now, that's real, and you can set a concrete date to revisit.
The vague follow-up in ninety days is a relationship killer. A specific trigger — "let's talk the week after your launch wraps up" — is a real next step that both parties remember.
"We need to think about it"
This is the objection I used to fear most. It felt impolite to push back on. But letting it sit unaddressed means the deal drifts into silence, and silence almost always becomes a no by default.
What I say: "Of course — what specifically do you need to think through? I'd rather help you with that now than leave you with open questions." Most people have one or two things sitting in their head. Given permission to say them, they will. Those things are almost always handleable in the next five minutes. The prospect wasn't trying to get rid of you — they were trying to buy time to process something they hadn't named yet.
If they genuinely need a few days, ask what the decision timeline looks like and schedule a specific follow-up before you leave the call. Do not agree to "reach out next week" without a day and time on the calendar. That meeting will never happen.
"We already have a solution for this"
If they already have a solution and they're still talking to you, something is broken. No one spends forty-five minutes in a product demo because their current setup is working perfectly. They got on the call because there's a gap — they just may not have framed it that way to themselves.
What I say: "What made you take this call if you're covered?" That question is honest, not aggressive. People respect it because it shows you're thinking rather than just pitching. The answer is almost always illuminating — they're frustrated with the speed, the reporting, the support, the price at renewal, or some workflow that doesn't quite fit. That's your opening.
Do not immediately attack their existing solution. That makes you defensive. Instead, get them to describe exactly how they're solving it today, then ask how often that breaks down or falls short. Let them build the case for switching themselves.
"I need to run this by my team"
This is a real objection and a process failure. The person in front of you cannot close the deal alone — and if you didn't know that going into the call, you need to find out earlier in future conversations. But it's also often deployed as a delay tactic by someone who is personally interested but not fully convinced.
What I say: "Totally makes sense. What does your team need to see to feel confident about this? And would it help if I joined a call with them directly, or put together something specific to their concerns?" This does two things. It makes clear you're willing to do the work, and it tests whether the team conversation is real or if you're being kept at arm's length.
If the answer is "no, I can handle it" — great, send a one-page summary they can forward. If they welcome a group call, schedule it before you hang up. If they deflect without agreeing to either, you have something more fundamental to address. You might not have the right champion in the room.
The one thing that changes how you handle all of them
Every objection I listed above becomes easier to handle when you've been doing discovery right. The price objection is weaker when you've already established the cost of the problem. The timing objection is easier to navigate when you know their Q3 planning cycle starts in August. The "need the team" objection doesn't blindside you if you asked in the first meeting who else is involved in this decision.
Most objections are not closing problems. They are discovery problems that surface late. Founders who struggle with objections usually find that the fix is not better rebuttals — it's asking better questions forty-five minutes earlier.
When you understand what is actually sitting behind an objection, you stop defending and start solving. That shift — from defending to solving — is what separates founders who close from founders who follow up forever.