General sales
AuraScore 79/100

Post-Demo Competitive Objection Handling Script

Navigate late-stage competitor pushback and pricing friction following a software demo.

Use this template when an enterprise buyer raises competitor alternatives or pricing discrepancies during late-stage evaluation stages. It provides sales reps with structured talk tracks to defend value differentiators and regain deal momentum.

Template

Role: Lead Solutions Consultant & Competitive Deal Desk Strategist specializing in mid-to-late stage enterprise software sales.

Context

  • Competitor alternative: {{competitor_name}}
  • Core platform differentiator: {{solution_differentiator}}
  • Pricing friction point: {{pricing_objection_detail}}
  • Buyer champion: {{buyer_champion_title}}
  • Required security standard: {{security_compliance_requirement}}
  • Targeted rollout schedule: {{implementation_timeline}}

Task

Produce an objection handling talk track and verbal battlecard script that equips a software sales rep to counter a late-stage pushback favoring {{competitor_name}}, reframing the conversation around total value and execution risk.

Method

  1. Analyze the risk profile presented by {{pricing_objection_detail}} to identify hidden costs in competitor offerings.
  2. Script an empathetic acknowledgment statement that validates the concern of {{buyer_champion_title}} without conceding ground.
  3. Formulate a reframing question that shifts evaluation criteria from upfront license price to {{solution_differentiator}}.
  4. Draft a competitive positioning narrative highlighting known trade-offs and hidden technical debt associated with {{competitor_name}}.
  5. Integrate {{security_compliance_requirement}} as a critical de-risking pillar that validates your higher baseline value.
  6. Structure a response protecting {{implementation_timeline}} by showing how delayed deployment cancels out short-term discounts.
  7. Write a mutual next-step agreement pitch to re-engage technical stakeholders in a proof-of-value summary.

Constraints

  • MUST use the "Acknowledge, Reframe, Differentiate, Advance" conversation framework.
  • MUST NOT disparage {{competitor_name}} with subjective slurs; stick strictly to architectural, security, and TCO facts.
  • MUST keep the total spoken script under 650 words.
  • Provide exact verbatim wording for the sales representative.

Output format

  • Step 1: Empathetic Acknowledgment & Pivot Hook (Spoken verbatim script, under 60 words)
  • Step 2: The Differentiator Reframe (Verbatim script highlighting {{solution_differentiator}} vs {{competitor_name}})
  • Step 3: Risk & Compliance Defense (Verbatim script anchoring {{security_compliance_requirement}} and {{implementation_timeline}})
  • Step 4: Next Action Lock-in (Verbatim closing question to secure buyer champion alignment)

Self-review

  1. Did I directly counter {{pricing_objection_detail}} using total cost of ownership rather than defensive discounting?
  2. Is {{competitor_name}} handled professionally using architectural contrast rather than badmouthing?
  3. Does the script give {{buyer_champion_title}} internal talking points to defend the decision to their procurement team?
AuraScore breakdown
79/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification6/14 · Thin

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency5/10 · Thin

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

sales
sales-general
technology-software
objection-handling
competitive-sales
deal-desk