Install
openclaw skills install objection-handlingHelp salespeople transform objections into opportunities using proven frameworks to clarify value, address concerns, and close more deals effectively.
openclaw skills install objection-handlingOvercome buyer objections using proven frameworks. Every objection is a buying signal — they're considering it, they just need clarity.
Sources: Gong.io (AI sales data), Thriving Tech (sales methodology), Feel-Felt-Found framework, consultative selling research.
All outputs go to workspace/artifacts/.
An objection is NOT a rejection. It's a request for more information.
When someone says "it's too expensive," they're really saying: "I don't yet see enough value to justify this price." That's a solvable problem.
The two fatal mistakes:
The correct response: Curiosity. Ask questions. Understand what's behind the objection.
Every objection falls into one of these buckets. Diagnose the category first, then apply the framework.
"It's too expensive" / "That's over our budget" / "Can you do it cheaper?"
What they really mean: The perceived value doesn't match the price.
Framework: Value Reframe
Never: Immediately discount. It signals your price wasn't real and trains them to always negotiate.
"Not right now" / "Maybe next quarter" / "I need to think about it"
What they really mean: Either no urgency, fear of commitment, or they need someone else's approval.
Framework: Urgency + Easy Entry
"I don't think I need this" / "We're doing fine without it" / "I'll just do it myself"
What they really mean: They don't see the gap between where they are and where they could be.
Framework: Gap Reveal
The "I'll do it myself" variant: Respect it, but quantify: "Absolutely. From my experience, building this from scratch takes about [X hours]. At your hourly rate of $Y, that's $Z in your time alone — vs. $[your price] to have it done in [timeframe]."
"I've never heard of you" / "How do I know this will work?" / "Our last vendor failed"
What they really mean: They're risk-averse and need proof.
Framework: De-Risk
"We're already using [competitor]" / "Someone quoted us less" / "[Other tool] does this"
What they really mean: They need a reason to switch or choose you specifically.
Framework: Differentiate
Universal technique that works on almost any objection:
Example: "I totally get that $149/mo feels like a lot for a solo practice. A lot of our massage therapist clients felt the same way. What they found was that the system paid for itself in the first week by capturing bookings they were previously missing."
Warning: Don't use this robotically. It works because it's empathetic, not because it's a formula. Adapt the language to sound natural.
The best objection handling happens BEFORE the objection is raised.
In proposals: Include an FAQ section addressing the top 3-4 objections for your market.
In conversations: "One thing clients often wonder is [common concern]. Here's how we handle that: [answer]."
On sales pages: Dedicate a section to "Common Questions" that are really objections in disguise.
For our products:
| Product | Top Objection | Preemptive Response |
|---|---|---|
| Alfred automation | "I can't afford $149/mo" | "Captures 3-5 missed appointments/week = $300-500/mo. Pays for itself week 1." |
| Reef on Gumroad | "Why not just use ChatGPT?" | "ChatGPT is cloud-only and $20/mo forever. The Reef runs locally for $0/mo after setup." |
| Upwork services | "Why should I hire you vs. cheaper devs?" | "Cheaper devs take 3x longer. I deliver working automation in [timeframe], not a project that needs fixing." |
| ClawHub skills | "Why pay when free skills exist?" | "Free skills are generic. These are battle-tested on real revenue projects with proven frameworks." |
Not every objection should be overcome. Walk away when:
Walking away well: "It sounds like the timing/budget isn't right for this. No worries — I'm here whenever it makes sense. Would it be okay if I checked in next quarter?"
This preserves the relationship and leaves the door open.