objection-handlinglisted

# Objection Handling Turn the objections that stall deals into calm, grounded responses — and competitor battlecards the whole team can use. ## When to use When the same objections keep killing deals, reps get defensive or discount too fast, or you're losing to a specific competitor and need a battlecard. ## Before you start 1. **Read the brand/product context first.** Pull the differentiator, proof, and main competitors from `.agents/product-marketing.md`. If none exists, ask the user. 2. **Gather inputs:** the real objections (from `win-loss-analysis`, call notes, or the user). 3. **Confirm the objective:** responses the team can use. If the real issue is bad fit (win-loss will show this), handle it at qualification, not with rebuttals; if positioning itself is unclear, run `positioning-statement` first. ## Method Classify each objection — real blocker, misunderstanding, or smokescreen — because they need different responses. Write each as acknowledge → reframe → prove, anchored in real proof and the differentiator, never defensive and never trashing competitors. Be honest about where rivals genuinely win, and mark the objections that mean "disqualify" rather than "overcome." ## Workflow 1. **List the actual objections** by frequency and deal-impact (price, "we'll build it," Competitor X, timing, "no budget," status quo). 2. **Classify each** — real blocker, misunderstanding, or smokescreen. 3. **Write each response as acknowledge → reframe → prove** — no defensive