Competitive analysis
AuraScore 83/100

Merchant Acquiring Competitive Counter-Pitch Script

Draft a live phone sales script to win merchant acquiring deals against low-cost fintech processors.

Use this template when commercial payments sales teams face prospects considering alternative fintech payment processors. It delivers an objection-handling dialogue that exposes hidden processing fees and proves settlement reliability.

Template

Role: Global Head of Commercial Merchant Services and Payments Competitive Strategy.

Context

  • Merchant acquirer: {{acquiring_firm}}
  • Fintech challenger: {{fintech_disruptor}}
  • Industry vertical: {{merchant_category}}
  • Challenger hook: {{competitor_pricing_gimmick}}
  • Cost blind spot: {{hidden_fee_angle}}
  • Core operational advantage: {{settlement_advantage}}

Task

Author a conversational, scenario-based outbound and discovery call script that sales representatives at {{acquiring_firm}} can use to pivot prospects away from {{fintech_disruptor}} in the {{merchant_category}} space.

Method

  1. Dissect the promotional claims in {{competitor_pricing_gimmick}} commonly marketed by {{fintech_disruptor}}.
  2. Map the operational pain points and processing overhead specific to {{merchant_category}}.
  3. Script a low-friction opening question that prompts the merchant to scrutinize their true effective rate.
  4. Design a structured dialogue exposing the financial downside of {{hidden_fee_angle}}.
  5. Build a clear value contrast highlighting the revenue impact of {{settlement_advantage}}.
  6. Write branching responses for common merchant pushbacks: price fixation, switching friction, and contract terms.
  7. Establish a closing commitment ask for an interchange-plus statement audit.

Constraints

  • Dialogue MUST sound natural, inquisitive, and consultative rather than aggressive.
  • You MUST NOT make unverified legal claims regarding competitor contract terms.
  • Script must contain clearly designated speaker roles: [Sales Rep] and [Merchant Prospect].
  • Must provide at least two alternative branching paths for distinct merchant reactions.

Output format

  • Pre-Call Intelligence Checklist: 3 critical items to confirm before dialing.
  • Scene 1: Pattern-Interrupt Opener & Diagnostic Question (100 words)
  • Scene 2: The Transparency Pivot on {{hidden_fee_angle}} (150 words)
  • Scene 3: Operational Value Delivery with {{settlement_advantage}} (150 words)
  • Scene 4: Branching Objection Handling & Close (200 words)

Self-review

  • Ensure [Sales Rep] lines sound conversational and ask open-ended diagnostic questions.
  • Verify that {{competitor_pricing_gimmick}} is reframed using specific payments arithmetic.
  • Confirm the closing ask focuses strictly on obtaining a statement for a side-by-side audit.
AuraScore breakdown
83/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 efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness5/5 · Strong

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

research-analysis
research-competitive
financial-services
merchant-acquiring
payments
sales-script