objection-handling.md

Objection Handling

Use this reference whenever a prospect raises an objection — in a cold reply, during follow-up, or as a blocker before proceeding to a trial or deal stage. The same objection may surface in different contexts; the patterns below hold across channels.

Tone rules: executive register, no filler, short dashes only, lowercase after the greeting, no sign-off. Replies to objections are shorter than the emails that provoked them.

Global rule: every response below ends with a queued draft for {{APPROVAL_OWNER}} to review — objection replies are never auto-sent. An objection means a human is engaging; a human decides what goes back.

1. Security & Compliance

Triggers: prospect asks about GDPR, SOC 2, data privacy, security posture, vendor security review, or any compliance requirement.

Approach: don't answer item-by-item. Point them to your trust/security resources, invite their security team into the thread, and get out of the way.

[First name] —

Good question. All of our security and compliance documentation is here: [trust center URL from {{RESOURCE_LIBRARY}}] — covers data handling, privacy, and certifications.

If you have something specific your team needs to review, let me know and I'll make sure the right info gets to the right person.

1a. Formal legal/compliance team review

Triggers: the prospect's legal or compliance team forwards a detailed questionnaire — DPA, sub-processor list, data-processing methodology, cookie/tracking disclosure, sample outputs. Common in EU/UK accounts where GDPR and ePrivacy apply.

Approach: don't answer the questionnaire line by line. Send the two or three resources that address the full list (trust center, DPA, relevant product docs — all from {{RESOURCE_LIBRARY}}, always plain-text URLs), CC your technical leader (CTO or equivalent) for follow-on technical questions, and invite them to add their compliance team to the thread.

Pattern: one short framing line, a clean bullet list of resources, one closing line inviting their team to join the thread. CC the technical leader. No lengthy explanations — let the resources do the work.

If a formal security review is the stated gating item before a trial or deal step, log it as an open blocker in {{CRM}} and set a follow-up task — this objection has a deadline attached.

2. Pricing & Cost

Triggers: prospect asks what you cost, wants pricing before trialing, asks about ROI or budget fit.

Approach: explain your pricing model's structure in two or three sentences — the components, what drives cost up or down — without quoting a number you can't stand behind. Then offer to size it for their situation.

[First name] —

Two components to how we price: [component 1] and [component 2].

[One-sentence explanation of each — what it covers, what drives it.]

Happy to walk through what a realistic number looks like for your team if that's useful.

Post-meeting variant: after a discovery or demo call, add one line before the closing offer:

Based on what we covered, you can expect a range of [RELEVANT RANGE] — we'll put a finer point on that after scoping.

Estimating the range: derive it from what you actually know — company size, usage drivers, use cases discussed. If you genuinely cannot estimate from context, omit the range line entirely — never fabricate a number.

3. Incumbent-Tool Displacement — "We already use [competitor]"

Triggers: prospect currently uses a competing tool and is hesitant to replace it, citing coverage gaps, cost delta, or fear of losing what they have.

Core rebuttals, in order of strength:

First-person experience beats competitive claims. If your team genuinely evaluated or used the incumbent and moved off it, lead with that story and the specific reason (accuracy, coverage, workflow fit). A real first-person reference lands 10x harder than a feature-comparison table. If you don't have one, skip this — never fabricate it.
Name the philosophical difference, not the feature list. Explain what your product optimizes for versus what the incumbent optimizes for (e.g. precision vs volume, depth vs breadth). Discrepancies between the two tools stop being a "coverage problem" and become two different philosophies resolving the same question.
Anchor on your unique capability with THEIR data. Pull a concrete number from their own trial, account, or research — "we surfaced [X] of [thing] the incumbent can't match at all." Fill in the real number before sending; a bracketed [X] left in the draft is an unfinished draft.
The budget reframe. The incumbent's budget isn't a gap to defend — it's better applied toward the capability the incumbent can't provide. End on where the money works harder, not on why the incumbent is bad.

[First name] -

We actually evaluated [competitor] ourselves and made the same call — [one-sentence honest reason].

[One sentence on the philosophical difference: what your stack optimizes for.]

What's also worth noting: [concrete, their-data proof of your unique capability — with the real number filled in]. That's a fundamentally different signal, and it's where [outcome] actually comes from. The [competitor] budget goes further pointed at that.

4. "How do we know how much we'll use?" (usage / consumption models)

Triggers: prospect or customer wants to understand consumption before committing — how to estimate needs, how to track usage by user or workflow.

Approach: point them to two resources — a self-serve usage view for their own data, and your docs for the conceptual model. Keep the email itself short; don't explain the model inline.

[First name] - happy to help with that.

Two resources that should give you exactly what you need:

1 - Usage breakdown by [dimension]: [usage dashboard URL from {{RESOURCE_LIBRARY}}]

2 - How [pricing unit] works overall: [docs URL from {{RESOURCE_LIBRARY}}]

Let me know if you have questions.

The goal is to unblock them with the right links and get out of the way. Explaining the model in prose signals the docs aren't good enough.

5. Competitive Churn Threat — "Our team wants to move to [competitor]"

Triggers: an existing customer raises a competitor by name as a potential replacement, usually citing a specific capability gap. This is a churn signal, not a cold objection — treat with urgency but zero defensiveness.

The four-move pattern:

Validate, don't deflect. Open by affirming the underlying need is legitimate. Never argue the competitor's capability doesn't matter — the customer already decided it does.
Name concrete things already shipping. Vague reassurance ("we hear you, working on it") doesn't hold back a churn risk — specifics do. Name the feature, and name who or what is behind it if there's a credible pedigree angle (a partner, a known operator, a team with track record).
Reframe their ask as proof you already understand the problem. "This is exactly what we're building" lands better than "great feedback."
Give a concrete date. "Next 30 days" beats "soon." If you don't have a real date, don't invent one — escalate internally to product instead of guessing.

Structure of the reply:

One line of genuine appreciation for the direct flag (they gave you the chance to respond — most churns are silent).
"This is exactly what we're building" + the two or three concrete near-term items, each mapped to a part of their stated gap.
Credibility anchors where real: named partners, named operators, shipped adjacent capabilities.
One specific timeframe. Close warm, not defensive.

Never: generic "we're always improving," arguing the competitor is bad, or a discount as the first response — a discount answers a question they didn't ask and confirms the capability gap is real.

Escalation rule

If the same objection arrives twice from the same account, or an objection blocks a deal above your high-tier threshold, don't just reply — flag it to {{APPROVAL_OWNER}} with the thread history and your proposed response. Repeated objections are account signals, not email problems.