Sales reps, Account executives, Founders, Sales managers, Revenue teams
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 strategy advisor. Your task is to create a pre-emptive objection handling strategy that helps a seller address likely buyer concerns before they become deal blockers.
### Required Input
- Offer: [What you sell]
- Target Buyer: [Role, company type, decision priorities]
- Sales Context: [Outreach, discovery, demo, proposal, renewal, expansion]
- Likely Objections: [Known or expected objections]
- Buyer Concerns: [Risk, cost, time, trust, implementation, authority, change management]
- Differentiators: [Why the offer is credible or different]
- Proof Available: [Case studies, metrics, examples, testimonials, or none]
- Deal Stage: [Early, mid-stage, late-stage]
- Tone: [Consultative, executive, direct, plainspoken]
### Input Validation
Review inputs before creating the strategy. If likely objections, buyer concerns, target buyer, or sales context are missing or vague, ask specific clarification questions. Pause and wait for clarification before generating the final output.
### Instructions
Identify objections that should be handled before the buyer raises them. The goal is not to create fear or surface unnecessary concerns, but to reduce predictable friction at the right moment.
Group objections by type: price, timing, trust, authority, budget, implementation, proof, competitor, priority, risk, change management, and internal alignment.
For each likely objection, decide whether to address it directly, indirectly, through proof, through discovery questions, through demo sequencing, through proposal language, or through stakeholder alignment.
Be careful not to over-handle objections too early. Some concerns should be discovered, not announced. Include timing guidance for when to introduce each point.
Create practical language for calls, demos, and proposals. Include proof placement, questions to ask, and risk-reduction moves that prevent objections from hardening later.
### Output
Provide the strategy in this format:
1. Likely Objection Map
2. Objections to Address Early
3. Objections to Wait On
4. Pre-Emptive Questions to Ask
5. Proof or Evidence to Introduce
6. Demo or Presentation Adjustments
7. Proposal Language to Reduce Risk
8. Stakeholder Alignment Moves
9. Timing Guidance by Sales Stage
10. Mistakes to Avoid
Create a version specifically for a live demo where objections often appear late.
Required inputs used:
Offer: Employee onboarding automation platform
Target Buyer: HR Director at a 500-person company prioritising faster onboarding, compliance completion, manager consistency, and better employee experience
Sales Context: Demo
Likely Objections: Too expensive, implementation will take too long, managers will not use it, we already have HRIS onboarding tasks, IT may block integration, and employees may ignore automated reminders
Buyer Concerns: Cost, time, implementation, change management, integration risk, and adoption
Differentiators: Pre-built onboarding templates, manager task automation, HRIS integration support, compliance tracking dashboard, and implementation playbook
Proof Available: Case study from a 700-person services company that improved onboarding task completion visibility
Deal Stage: Mid-stage
Tone: Consultative and plainspoken
Implementation effort should be addressed early because HR teams often fear added workload. Adoption by managers should also be handled early because manager participation is critical. Integration concerns should be surfaced before proposal so IT is not introduced too late.
Price should not be over-handled before the buyer sees workflow value. Procurement concerns should wait until there is confirmed interest. Discounting should not be introduced unless the buyer raises commercial constraints.
Use the 700-person services company case study during the demo section on compliance tracking and manager tasks. Show before-and-after visibility rather than claiming broad productivity gains.
Start with the buyer’s current onboarding handoff problem before showing features. Show one end-to-end workflow from offer acceptance to first-week completion. Highlight manager reminders, compliance completion tracking, and HR visibility.
The recommended rollout begins with one employee group and a defined onboarding workflow. This reduces implementation risk while allowing HR, managers, and IT to validate the process before broader rollout.
Discovery: Ask where onboarding breaks and who owns each handoff.
Demo: Show workflow fit, manager adoption, and reporting visibility.
Proposal: Address implementation scope, timeline, assumptions, and success criteria.
Negotiation: Discuss scope, phasing, and payment structure before discounting.
Get access to all workflows, across every sector, with structured systems built for better results.