Objection Handling
Skill by staybased
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/staybased/objection-handlingObjection Handling — Turn Resistance Into Revenue
Overcome 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/.
Use when
- A prospect says "it's too expensive" / "I need to think about it" / "not the right time"
- Preparing responses for common objections before a sales call
- Reviewing a lost deal to understand what went wrong
- Training yourself on objection patterns for a specific market
- Writing FAQ sections for sales pages that preemptively handle objections
Don't use when
- Discovery phase (use client-discovery skill — objections come after you've proposed)
- The prospect is genuinely not a fit (respect the "no" — not every objection should be overcome)
- Internal disagreements (this is for sales, not team conflict)
- Customer support complaints (different context, different tone)
Negative examples
- "How do I find clients?" → No. That's lead generation, not objection handling.
- "Write me a proposal" → No. Use proposal-writing skill.
- "A customer is angry about our service" → No. That's support/retention, not sales objections.
Edge cases
- Upwork client pushes back on rate → YES. Price objection framework applies.
- "We already have someone for this" → YES. Competitor objection framework.
- Prospect ghosts after proposal → Borderline. Could be objection (fear) or disinterest. Use the breakup follow-up from cold-outreach skill.
The Mindset Shift
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:
- Getting defensive (arguing, justifying, discounting immediately)
- Giving up (treating it as a hard no)
The correct response: Curiosity. Ask questions. Understand what's behind the objection.
The 5 Objection Categories
Every objection falls into one of these buckets. Diagnose the category first, then apply the framework.
1. 💰 Price Objections
"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
- Acknowledge: "I hear you — price matters."
- Quantify the cost of NOT solving: "What's this problem costing you right now? [Use numbers from discovery]"
- Reframe as ROI: "So this $149/mo investment saves you $500/mo in missed bookings. That's a 3x return."
- Offer structure, not discount: "Would it help to start with the core package at $99 and add features later?"
Never: Immediately discount. It signals your price wasn't real and trains them to always negotiate.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-staybased-objection-handling": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Proposal Writing
Skill by staybased
ops-hygiene
Standard operating procedures for agent maintenance, security hygiene, and system health. Use when performing periodic checks, security audits, memory maintenance, secret rotation, dependency updates, or any recurring "housekeeping" tasks. Also use when setting up automated maintenance schedules or when asked about agent security posture.
Lead Magnets
Skill by staybased
Pricing Psychology
Skill by staybased
trade-validation
10-dimension weighted scoring framework for prediction market trade evaluation. Enforces disciplined position sizing, circuit breakers, and mandatory counter-arguments. Use when: evaluating prediction market trades, scoring opportunities, deciding position sizes, comparing Polymarket/Kalshi opportunities, running pre-trade checklists. Don't use when: general crypto analysis, DeFi yield farming, non-prediction-market investments, stock/equity analysis, sports betting (different framework needed). Negative examples: - "Should I buy ETH?" → No. This is for prediction markets with binary/discrete outcomes. - "What's the best DeFi yield?" → No. Wrong domain entirely. - "Score this sports bet" → No. Sports betting has different dimensions (injuries, matchups). Edge cases: - Crypto prediction markets (e.g., "Will BTC hit $X?") → YES, use this if on Polymarket/Kalshi. - Multi-outcome markets → Score each outcome separately. - Markets with <$25 liquidity → Auto-fail on Liquidity dimension.