Free Sales Objection Response Generator

Every objection, and what to say

• It's too expensive

  Usually not a verdict on the number. The buyer has not yet seen enough value to justify it, or they need a way to defend it internally.

  • Ask what it is compared with. That's fair, and I'd rather understand it than argue with it. Too expensive compared with what: another option, a number you had in mind, or the cost of the problem today?
  • Anchor on the cost of waiting. You told me earlier that this costs the team about ten hours a week. At your rates that is more than the subscription every month. What would it take for the numbers to line up for you?
  • Agree, then narrow. Agreed, it is not the cheapest option on the market. If I could show you the one part that pays for itself first, would it be worth ten minutes to look at that?

  Then ask. If price were not a factor, is this the right fit?

• We don't have budget for this

  Often means the problem is not important enough to fund this quarter. Occasionally it is literally true and the cycle just needs to move.

  • Separate budget from priority. Understood. When a problem is painful enough, budget usually shows up. Is this not a priority right now, or is it a priority with no money assigned yet?
  • Find where the money lives. That makes sense for this quarter. Which budget does this kind of spend normally come from, and when does that one get planned?
  • Shrink the first step. Then let's not ask for a big number. If we started with a single team for one month, what would you need to see to take it forward?

  Then ask. Who decides when budget gets assigned to a problem like this?

• Can you give me a discount?

  A standard negotiating move. The buyer is checking whether the price has room, and often wants something to show their own boss.

  • Trade, never give. I can look at that. What I can usually do is adjust the price when something changes on our side, such as a longer term or a faster start. Which of those works for you?
  • Ask what they need it to reach. Help me understand the target. What number do you need to hit, and what is it based on?
  • Hold, with a reason. I want to be straight with you. The price already reflects what the team gets, so a discount would mean taking something out. Would you prefer the full version or a smaller scope?

  Then ask. If we agreed on the number today, what else needs to happen before you sign?

• Now isn't a good time

  On a cold call, a polite exit. On an active deal, a sign that something else outranks this, which is worth finding out.

  • Ask for thirty seconds. Fair enough, I'll be quick. I called because teams like yours often lose track of follow-ups after calls. If that sounds familiar, would a better time be worth booking, or is it not an issue for you?
  • Name what is competing. Sounds like there is a lot on. What is taking the attention at the moment, and does this connect to it or sit apart?
  • Book it now. No problem. Instead of guessing, can we put fifteen minutes on the calendar next week while I have you? You can move it if something comes up.

  Then ask. What does your week look like on Tuesday or Wednesday?

• Call me back next quarter

  A deferral. It is honest when a project or budget cycle really starts later, and a soft no when nothing is attached to it.

  • Ask what changes by then. Happy to. What will be different next quarter that makes this the right moment, a budget, a hire or a project starting?
  • Use the wait to prepare. That works. If you will decide then, it helps if we do the groundwork now so you are not starting from zero. Could we spend twenty minutes on what you would need to see?
  • Set the date together. Sure. Which week should I call, and what should I have ready for you when I do?

  Then ask. If nothing changed between now and then, would it still be a no?

• We already use something for that

  Having a tool is not the same as being happy with it. The buyer may be satisfied, or may simply not want to re-open a decision.

  • Respect it, then probe. Good, that means you already take this seriously. What works well about it, and where does it fall short for your team?
  • Position next to it. I wouldn't ask you to replace it. Most of our customers kept what they had and added us for the part it does not cover. Which part of your process still depends on people remembering things?
  • Ask about the gap. If you could change one thing about how it works today, what would it be?

  Then ask. How would you know if it stopped being enough?

• Another vendor is cheaper

  They are comparing, which is a good sign. The risk is that price becomes the only axis because nothing else has been made concrete.

  • Compare what is included. That's useful to know. Can you share what the quote covers? I want to be sure we are comparing the same things before we talk about price.
  • Return to their criteria. When we spoke earlier you said speed to value and setup effort mattered most. How does the other option do on those two?
  • Name the trade-off honestly. They may well be the better choice if price is the only factor. If the way you work matters as well, it is worth ten minutes to compare the two on what you told me you need.

  Then ask. Beyond price, what would make you confident in the choice?

• I need to talk to my team

  Either a real approval step, or a polite way to end the call. The way to tell is to ask who else is involved and what they will want to see.

  • Make the next conversation easier. Of course. What do you think they will ask first? I can put together a one page summary so you are not carrying the whole case.
  • Offer to join. That makes sense. Would it help if I joined a short call with them, so you do not have to relay my answers?
  • Learn the process. Who is involved in a decision like this, and how does it usually go from here?

  Then ask. When do you expect to speak with them, and can we book a follow-up for after?

• Just send me some information

  Most often a brush-off. Occasionally a genuine request from someone who prefers to read first.

  • Make it specific. Happy to. So I send the right thing and not a brochure, what would be most useful: pricing, how it works, or what a similar team got out of it?
  • Trade the email for a step. I'll send it today. When you have had a look, can we take ten minutes on Thursday to go through what stood out?
  • Ask if it is interest or exit. Sure. Is that because it is interesting and you want to read more, or because it is not a fit and you would rather not say?

  Then ask. What would you need to see to decide whether this is worth a proper call?

• We're happy with how we do it today

  Inertia. The current way is familiar and the change feels riskier than the problem, so the cost of staying put has to become visible.

  • Quantify the present. Glad to hear it. How long does the process take today, and how often does something slip through?
  • Ask about the edge. What happens when your best person is out, or when you double the volume? Does it still hold up?
  • Offer a comparison. Then it should be easy to compare. If we looked at one real example from last month, we would both see quickly whether there is anything to gain.

  Then ask. If you could fix one thing about it, what would it be?

• I'm not sure we need this

  The problem has not been connected to a result the buyer cares about. More features will not fix that. A better question will.

  • Return to their words. You mentioned earlier that missed follow-ups cost you deals. Has that changed, or is it still a problem?
  • Test the pain. On a scale of one to ten, how much does this problem cost you today? What would make it a three?
  • Make it small and testable. Then let's not decide it in theory. Try it on one real call this week and judge it by whether you would miss it.

  Then ask. What happens if this stays exactly as it is for another year?

• We tried something like this and it didn't work

  A real scar, so treat it as information. The buyer wants proof you will not repeat what went wrong.

  • Ask what happened. I'm sorry it went that way. What happened, and what would have had to be different for it to work?
  • Reduce the risk. That's a fair reason to be careful. What if we ran a short trial on a few real calls first and you decided from what you saw?
  • Separate the cause. Was the problem the idea, or how it was rolled out? If it was setup or adoption, we can plan around that from day one.

  Then ask. What would a successful first month look like for you?

• How do I know it will work for us?

  A request for evidence from someone they would trust. Generic claims will not do. Something close to their own situation will.

  • Offer proof close to home. Good question. The most useful thing I can show you is a team of your size and type. Can I share how they set it up and what changed?
  • Let them test it. You don't have to take my word for it. Try it on your next few real calls and tell me honestly whether it earned its place.
  • Agree on the measure first. Let's decide upfront what success looks like. What would you need to see in the first weeks to call it a yes?

  Then ask. Who else would you want to hear from before deciding?