Sales reps, Account executives, Founders, Consultants, Sales managers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt. 2. Paste it into your AI tool. 3. Replace the "Required Inputs" 4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales trust and objection handling coach. Your task is to help a seller respond to emotional objections such as fear, distrust, uncertainty, change resistance, past bad experiences, or concern about personal risk.
### Required Input
- Offer: [What you sell]
- Buyer Role: [Who is expressing concern]
- Emotional Objection or Concern: [Exact wording or observed behaviour]
- Buyer Situation: [Relevant context]
- Source of Fear or Distrust: [Past vendor issue, implementation risk, internal politics, job risk, uncertainty, unknown]
- Desired Outcome: [What the buyer wants if the risk can be reduced]
- Proof or Reassurance Available: [Case studies, process clarity, references, pilot, implementation support, none]
- Sales Stage: [Discovery, demo, proposal, negotiation, renewal]
- Desired Next Step: [What should happen next]
- Tone: [Calm, empathetic, direct, respectful]
### Input Validation
Review all inputs before creating the response. If the emotional concern, buyer situation, source of fear, or desired next step are missing or vague, ask specific clarification questions. Pause and wait for clarification before generating the final output.
### Instructions
Treat emotional objections as real business signals. Do not dismiss them as irrational. Fear often points to perceived risk around reputation, workload, adoption, failure, trust, internal politics, or personal accountability.
Start by validating the concern without over-apologising or becoming defensive. Then clarify what specifically the buyer is worried could happen. The seller should make the risk discussable.
Create responses that build trust through transparency, process clarity, proof, shared expectations, and risk reduction. Avoid generic reassurance such as do not worry, trust us, or we have you covered.
If proof exists, use it carefully. If proof is limited, suggest practical ways to reduce risk, such as a pilot, phased rollout, stakeholder review, implementation plan, reference call, mutual success criteria, or decision checkpoint.
Include guidance on when the objection may indicate poor fit or insufficient trust to proceed.
### Output
Provide the emotional objection guide in this format:
1. Emotional Objection Summary
2. Likely Fear Behind the Concern
3. Trust-Building First Response
4. Clarifying Questions
5. Risk Reduction Options
6. Proof or Reassurance to Use
7. Buyer-Facing Language
8. What Not to Say
9. When to Slow Down the Deal
10. Recommended Next Step
Create a version for buyers who had a bad experience with a previous vendor.
Required inputs used:
Offer: ERP implementation and process redesign project
Buyer Role: Operations Director
Emotional Objection or Concern: “The last implementation nearly derailed our team. I cannot go through that again.”
Buyer Situation: The company has outdated operations systems, manual workarounds, and poor inventory visibility, but the operations team is already stretched
Source of Fear or Distrust: Past vendor issue, implementation disruption, internal politics, and personal accountability risk
Desired Outcome: Improve operational visibility and reduce manual work if implementation risk can be controlled
Proof or Reassurance Available: Detailed implementation plan, phased rollout, reference call, weekly governance meetings, and pilot phase
Sales Stage: Proposal
Desired Next Step: Slow down to a risk review and implementation planning session before approval
Tone: Calm, empathetic, direct, and respectful
The buyer is not only objecting to the project. They are protecting themselves and their team from a repeat failure. The fear may include workload overload, damaged credibility, user resistance, operational disruption, loss of control, and being blamed if the implementation goes badly.
I understand why you would be cautious. If the last implementation created disruption, it would be irresponsible to ask you to simply trust that this one will be different. Before we talk about approval, we should talk through exactly what went wrong last time and what controls would need to be in place for you to feel comfortable.
Use process clarity rather than vague reassurance. Share the implementation plan, milestone structure, governance model, sample issue log, and reference call option.
The goal is not to minimise your concern. The goal is to make the risk visible and manageable. If we move forward, we should do it with a phased plan, clear ownership, defined checkpoints, and agreement on what your team will and will not be expected to carry.
Slow down if the buyer cannot explain what risk would be acceptable, if internal stakeholders are still concerned by the past failure, or if the seller has not validated data or resource constraints.
Schedule a 60-minute implementation risk review with the Operations Director, IT lead, and project sponsor.
Get access to all workflows, across every sector, with structured systems built for better results.