Competitor Objection Response

What it takes in

The inputs you provide on each run, validated before anything executes.

2 tasks, run in order.

Each task passes its result to the next. Here's what each does and what it produces.

1. 01
   Diagnose the objection. From {{objection}} (and {{competitor}} if named), identify what the prospect is really concerned about underneath the surface statement, and what kind of response will actually move them. Note whether it is a price, risk, trust, fit, timing, or competitor-claim objection. Present readably, never JSON.

   Expected output

   A short, readable diagnosis using headings and bullets, no JSON and no code blocks: Objection Type, The Real Concern (what is likely underneath it), and What Will Move Them (the kind of response that will land).
2. 02
   Craft the response. Using the diagnosis and {{yourProduct}}, write a response that acknowledges the concern honestly, reframes around the buyer's outcome, brings in relevant proof points from the provided product strengths, and ends with a redirect question. Do not disparage {{competitor}} or invent facts. Provide a concise spoken version for a live call and a short written version for email. Present readably, never JSON.

   Expected output

   A readable response section with no JSON and no code blocks: Spoken Version (2 to 4 sentences a rep can say naturally on a call), Written Version (a short email-ready paragraph), Proof Points to Reference (bullets, drawn only from the provided strengths), and Redirect Question (one question to regain control of the conversation).

What you can do with it