Handle a pricing objection

Sales objection handling is an Agent Skill: a written method your AI applies on demand, in Zealos or in any client that reads SKILL.md.

A pricing objection is almost never about price: it is a value problem, a comparison to something cheaper that does less, or an internal conversation the buyer has not told you about yet.

What is in this skill

nameobjection-handling
descriptionThe objections we get and the responses that work, including what not to say. Use when drafting a reply to a hesitant prospect, preparing for a negotiation, or reviewing a stalled deal.
allowed-toolsnone — this skill adds judgement, not reach
compatibilityZealos, Claude Code, Cursor, Codex and any client that reads SKILL.md
licenseFree to use and edit

How it works

  1. 1Repeat the objection back more precisely than it was said. Doing that well is what earns the right to ask a question about it.
  2. 2Ask one question that finds what is underneath, then stop talking. The second half of the answer is the useful half.
  3. 3Answer the real objection rather than the stated one, and confirm it is resolved — an objection skipped here reappears at procurement.
  4. 4Never discount before you understand it. A discount offered too early confirms the buyer's suspicion that the price was arbitrary.

The skill itself

---
name: objection-handling
description: The objections we get and the responses that work, including what not to say. Use when drafting a reply to a hesitant prospect, preparing for a negotiation, or reviewing a stalled deal.
---

# Objection handling

An objection is information. The instinct to answer it immediately is what turns
it into an argument.

## The shape

1. **Repeat it back** in their words, more precisely than they said it.
2. **Ask one question** that finds what is underneath.
3. **Answer the real objection**, which is usually not the stated one.
4. **Confirm** it is resolved before moving on. If you skip this, it returns at
   procurement.

## Common ones, and what is usually underneath

| Stated | Usually means |
|---|---|
| "Too expensive" | Value is unclear, or they are comparing to a cheaper thing that does less |
| "Bad timing" | No trigger, or a competing priority they have not named |
| "We built something internally" | Sunk cost, and someone's reputation is attached to it |
| "Need to talk to the team" | We have not met the actual decision maker |
| "Send me some information" | Polite exit — ask what specifically they need it to answer |

## Never

- Answer a price objection with a discount before understanding it.
- Say "great question".
- Disparage the competitor. Compare on a dimension the buyer already named.
- Argue with a feeling. "It feels risky" is not resolved by facts about uptime.

Who uses it

Account executive

The reflex to concede on price gets replaced by a question, and the deals that were going to close still close — at the number you quoted.

Sales manager

Objection handling stops being tribal knowledge held by your top two reps and becomes something the other six can read.

Founder

You stop discovering your own pricing rationale mid-sentence on a call, because you wrote it down once when you were not under pressure.

Frequently asked questions

What does too expensive usually mean?

Either the value is unclear, or they are comparing you to something cheaper that does less. Both are answered by understanding, not by discounting.

Should the AI ever offer a discount?

No. Pair this with a pricing-guardrails skill that makes any concession require a human, because an anchor you cannot honour costs more than a day's delay.

How is this different from a battle card?

A battle card is about competitors. This is about the moment a buyer hesitates, which happens far more often and is rarely competitive.

Related skills

Summarize calls and update the CRM

Post-call automation turns a recorded conversation into the three things that outlive it: the commitments each side made, the fields that changed, and the follow-up that has to go out today.

MeetingsCRMZoom/call-recap-format

Brief yourself before every call

A pre-call brief is worth writing only if it changes what you ask: who is in the room, what they are measured on, what happened last time, and the one question you cannot afford to leave without answering.

CoachingMeetingsAccounts/discovery-questions

Triage your inbox by deal impact

AI email triage is worth having only when it sorts by consequence rather than by recency: what blocks a deal, what someone is waiting on you for, and what can be read at the end of the week.

EmailGmailAccount executives/email-rules

Log a call without inventing fields

CRM data hygiene survives AI only if one rule is written down first: a field left blank is a known unknown, while a field filled in by inference is an unknown unknown that will be reported on as fact.

CRMHubSpotSalesforce/crm-field-conventions

Qualify a lead against our ICP

Qualification is a claim about evidence, not a score: a deal is qualified when every criterion has a source you can quote, and unevidenced criteria are named rather than filled in optimistically.

DealsProspectingCRM/meddicc

Run a pipeline review

A pipeline review is useful in proportion to how uncomfortable it is: the job is to find the deals that are slipping quietly, not to narrate the ones everybody already knows about.

DealsCRMAccount executives/meddicc

Skills, in your workspace

Write it once. Every agent follows it.

Twelve built-in skills ship with every workspace, and you can draft your own with AI or import any public SKILL.md from GitHub.

7-day free trial. Set up in minutes. Cancel anytime.