---
name: sales-objection-handling
source: https://app.decimal.ai/s/sales-objection-handling@1/SKILL.md
source_sha256: 36288a1b976a
---

# Handling a prospect's objection

When you are drafting a seller's reply to a buyer who has pushed back — on price, timing, a rival
offer, or whether it fits — follow the move below. Left alone, the base model tends to jump straight
to a defensive rebuttal: it argues the objection is wrong, lists reasons the product is actually
fine, or subtly knocks the competitor. That wins the point and loses the deal. This move steers it
back.

The conventions govern **how the reply argues** — not its format, not which rep owns the account,
not what the price should be. Apply them to the wording of the response itself.

## The four-beat move

Answer every objection in this order. Skipping a beat is the failure mode.

1. **Acknowledge the concern as legitimate — first, and without rebutting.** Name what the buyer
   raised and grant that it is a fair thing to care about ("A jump in cost mid-year is a real thing
   to weigh"). Do this before offering any counter-argument. Leading with "Actually…" or "But…"
   reads as a shrug and hardens the buyer.

2. **Clarify what is really driving it — ask, don't assume.** A stated objection is rarely the whole
   story. "Too expensive" can mean no budget this quarter, doubt about the return, or a cheaper quote
   in hand — and each needs a different answer. Ask one open question that surfaces the real concern
   before you address it. Do not guess which one it is and argue against your guess.

3. **Reframe on the buyer's outcome, not the product's features.** Once you know the real concern,
   answer it in terms of what the buyer is trying to achieve — the cost of the problem staying
   unsolved, the result they get — rather than reciting specs. Tie the price/timing/fit back to the
   value they already told you they want.

4. **Back it with proof or a concrete next step.** Close with something solid: a specific customer
   result, a number, a short trial, a scoped pilot, or a clear next action with an owner. Vague
   reassurance ("I really think you'll love it") is not proof. Give them something to say yes to.

## Two hard constraints

- **Never get defensive or dismissive.** Do not tell the buyer the objection is wrong, insist they
  are mistaken, or brush it off ("everyone says that at first"). The objection is information; treat
  it as real even when you disagree.

- **Never bad-mouth a competitor.** When the buyer names a rival, do not disparage it, question the
  buyer's judgment for considering it, or call it inferior. Acknowledge why it is a reasonable option,
  then differentiate on the outcome you deliver. Selling against a rival is done on your strengths,
  never on their faults.

## Putting it together

> **Buyer:** "Honestly, you're a lot pricier than the other tool we're looking at. Hard to justify."
>
> **Defensive (avoid):** "Actually we're not expensive — you're comparing us to a much weaker
> product. Theirs can't even do half of what ours does. Ours is worth every penny."
>
> **The move (aim for):** "A bigger line item does need to be justified — that's fair. Can I ask
> what would have to be true for the spend to make sense to you: is it the budget for this quarter,
> or whether the return is there? [They answer: return.] Got it. Most teams your size were losing
> ~6 hours a week to the manual step this replaces — one of them, a 40-person ops team, put that at
> about $90k a year. If it'd help, we can run a two-week pilot on your own data so you see the number
> before you commit. Want me to set that up?"

Both replies disagree with the objection. Only the second one keeps the deal alive — it grants the
concern, finds the real driver, answers on value, and hands the buyer a low-risk yes.