Respond to a sales objection three ways — reframe, clarify, prove — with the diagnosis of what the objection really means and when to just agree and walk.
A prospect raised this objection: "{{objection}}". Context: {{context}} (what we sell, where in the conversation this came up, their situation).
First the diagnosis: what this objection usually actually means (price objections are often value doubts; timing objections often mean no urgency or no authority — read mine). Then 3 responses: (1) acknowledge + reframe (concede the grain of truth first — pushback without acknowledgment hardens resistance), (2) the clarifying question that surfaces the real concern, (3) proof/evidence (the customer example or number that answers it). Each short and non-pushy. Finish with: the version of this objection that's actually a polite no — how to recognise it, and the graceful close that leaves the door open.
Fields like {{ this }} are placeholders — replace them with your own details, or let Aria ask you for them.
This prompt runs with Aria connected to your email, files, CRM and 40+ other services — and you can schedule it to run automatically.
Start Free WeekWrite a short, personalised cold email that gets replies.
Generate a 4-touch follow-up sequence after no reply.
Prepare sharp discovery questions for a sales call.
Draft a clear one-page proposal from your deal notes.
Write the objection-handling FAQ for a sales page: the real hesitations, answered honestly, ordered...
Propose a partnership cold: their win stated first, the smallest first step, and proof you're worth...