# Objection Response Builder

Builds tailored, non-pushy responses to a specific sales objection, using a proven acknowledge-reframe-evidence-ask structure.

## Prompt

You are a sales trainer who teaches reps to handle objections without sounding pushy or scripted.

Objection received (verbatim if possible): {{objection_text}}
What I'm selling: {{product_or_service}}
Deal context: {{deal_stage_and_relevant_context}}

Do the following:
1. Identify the real concern behind the objection (objections are often a proxy for a deeper worry, e.g., 'too expensive' can mean 'I don't see the ROI yet' or 'I don't have budget authority').
2. Write a response using this structure: Acknowledge (show you heard them genuinely, no fake sympathy), Reframe (shift the perspective without dismissing their concern), Evidence (a concrete proof point, e.g., data, comparison, or example), Ask (a specific next-step question that moves the conversation forward).
3. Provide 2 versions of the response: one for a written follow-up (email/chat) and one for a live conversation (shorter, more conversational).
4. Flag if this objection is a potential deal-breaker that needs escalation or extra proof, versus a routine objection that experienced reps handle easily.

## Best for

Sales reps, founders doing their own sales, and customer success teams who need clear, non-pushy language to handle common objections like price, timing, or 'need to think about it.'

## Compatible tools

- Claude
- ChatGPT

## How to use

- Paste the objection as close to verbatim as you can remember or have on record.
- Provide context about where the deal currently stands so the response is calibrated correctly.
- Use the written version for email/chat follow-ups and the live version for calls or in-person conversations.
- Escalate objections flagged as potential deal-breakers to a manager or add extra proof points before responding.

## Customization tips

- If you know the prospect's personality (analytical, relationship-driven, skeptical), mention it for a more tailored reframe.
- For recurring objections in your industry, build a small library by running this prompt once per objection type and saving the outputs.
- Ask for a role-play version if you want to practice delivering the response out loud before a call.

## Example input

Objection: 'This looks great but I think it's too expensive for where we are right now.' Selling: An AI-powered presentation tool subscription for university student groups. Deal context: Mid-funnel, spoke with the student org treasurer once, no decision-maker buy-in yet.

## Example output

An analysis identifying the real concern as likely budget authority rather than pure price sensitivity, a written follow-up response acknowledging the budget constraint, reframing around cost-per-use versus time saved, citing a comparison to hiring a designer, and asking whether a lower-tier plan or a trial would help make the case internally; plus a shorter live-conversation version and a note that this is routine, not a deal-breaker.