Handling a Pricing Objection Without Getting Defensive
Most pricing objections get handled live, on the spot, with whatever justification comes to mind first. That usually sounds defensive, because it is, and the same objection tends to get a slightly different answer every time depending on how the conversation caught you.
Warning
An improvised justification defends the price. It doesn't reframe the conversation, and a prospect can tell the difference between the two even if they can't name it.
The first good answer to an objection is worth writing down. The tenth improvised one usually isn't as good as the first.
Why improvising produces a worse answer, not just an inconsistent one
Answering an objection live means thinking and talking at the same time, under mild pressure, with the prospect watching your reaction. That's a bad environment for producing your best response, and it's why the same objection often gets a weaker answer the more it catches you off guard.
Before: hear the pricing objection, respond with whatever justification comes to mind, move on and hope it landed.
After: describe the objection to Claude once, work out a response that reframes instead of defends, and save it as a starting point for the next time the same objection comes up.
A process for building a response, not a rebuttal
- 1
State the objection exactly as the prospect said it
Paste or describe their actual words, including the specific number or competitor they compared you to. A vague "they said we're expensive" gives Claude less to work with than the real comparison they made.
- 2
Ask for acknowledgment first, reframe second
Ask specifically for a response that acknowledges the gap honestly before reframing it, not a reframe that skips past the objection like it wasn't said.
- 3
Ask the response to end with a question, not a statement
A response that ends by asking something keeps the prospect talking. A response that ends by asserting your value ends the exchange with you doing all the work.
- 4
Save the version that actually worked
Once you've used a response live and it landed, keep it. That's the start of a playbook you can pull from instead of reconstructing an answer from scratch every time the objection resurfaces.
“
A prospect said our pricing is 30% higher than a named competitor. Draft a response that acknowledges the price gap honestly, reframes around total cost of ownership, and ends with one question to keep them talking.
”
Inside Claude Tutorial
Acknowledging before reframing is transferable.
Responding to pushback by acknowledging it honestly first, instead of defending immediately, applies well beyond pricing objections. The app has a full lesson on it, with practice that carries over to any conversation with real resistance in it.
Building a playbook instead of starting over each time
Once you've handled the same objection well twice, it's worth treating it as a pattern instead of a one-off. A playbook doesn't mean reciting the same words, it means starting from something proven instead of a blank reaction.
Tip
Ask Claude to pull the reusable structure out of a response that worked, separate from the specific numbers in it. That structure is what transfers to the next prospect; the numbers won't.
“
This response to a pricing objection worked well on my last call. Pull out the reusable structure, acknowledge, reframe, ask, separate from the specific numbers, so I can adapt it for a different prospect's pricing comparison.
”Continue reading
- Turning a Messy Call Transcript Into CRM-Ready Notes: where an objection like this one gets surfaced and logged in the first place.
- Turning a Discovery Call Into a One-Page Proposal: folding a handled objection into the document that addresses it in writing.
- Sharpening a Cold Email Before You Hit Send: the same acknowledge-before-you-respond discipline, applied before the conversation even starts.