OctiAI

Categories

Competitive Battlecard Template — One-Page Prompt

Generate a concise, sales-ready one-page battlecard with differentiation, rebuttals, feature gaps, pricing delta and frontline scripts.

What You'll Get

How to Use

Collect three concrete proof points before running

Ask product/marketing for: 1) one case-study stat or outcome (e.g., retention or time saved), 2) a customer quote or testimonial you can cite, and 3) current list pricing or common discount ranges. Exact phrasing to request: 'Please provide one metric we can cite, one short customer quote, and any public list price or typical discount %.'

Works Best With

Produces the best battlecards when you supply:

Prompt Template


## Goal
- Produce a one-page competitor battlecard that equips frontline reps to win or gracefully walk away vs a named competitor and to advance deals (request demo/close next step) at the current {{funnel_stage}}.

## Inputs
- Offer: {{offer}}
- Target audience / ICP: {{target_audience}}
- Funnel stage: {{funnel_stage}}
- Channel: {{channel}}
- Primary benefit to emphasize: {{primary_benefit}}
- Proof points (case studies, metrics, testimonials): {{proof_points}}
- Typical objections to overcome: {{objections}}
- Primary CTA (single next-step for reps to push): {{cta}}

If any of the above are missing or the user has not specified the competitor to compare against, the model must ask exactly these targeted clarifying questions before producing the battlecard:
1. "Which competitor (name + one-sentence positioning) should I compare against?"
2. "List up to 3 competitor claims or messaging points you most often hear from prospects about that competitor."

Do not proceed until a competitor name and at least one competitor claim are provided.

## Prompt
You are a senior sales strategist writing a one-page competitive battlecard for reps. Using the provided inputs ({{offer}}, {{target_audience}}, {{funnel_stage}}, {{channel}}, {{primary_benefit}}, {{proof_points}}, {{objections}}, {{cta}}) and the competitor name + claims the user provides, produce the battlecard in the exact order and format specified in "Output Format" below.

Requirements — be precise and actionable:
- Use the competitor name the user supplies. If competitor details are missing, stop and ask the two clarifying questions listed in Inputs.
- For every differentiation point and rebuttal provide a single-line evidence note that references an item from {{proof_points}} or specify exactly what proof is needed (e.g., "need a 30% retention stat or customer quote").
- When stating a pricing delta, use exact numbers if the user supplies them; otherwise give a clear scripting template reps can use (e.g., "competitor lists at $X; you position at $Y with Z included").
- For feature gaps, list concrete feature names and the observed customer impact of the gap.
- Create rebuttals as short scripts (1-2 sentences) that end with a question or next-step prompt pushing to the {{cta}}.
- Include one primary CTA only — the {{cta}} — and integrate it into the closing "Win" script.
- Language must be short, direct, and usable verbatim by a rep in a call, DM, or email. All copy should be measurable by the funnel stage (e.g., "advance to demo", "secure PO", "get commitment to pilot").

Deliverables — produce the following items in this exact order and with these headings:
1. Competitor Quick Positioning (1 line)
2. Top 5 Differentiation Points (each with 1-line evidence)
3. 3 Battle-Tested Rebuttals (scripted 1-2 sentences + evidence + next-step CTA)
4. Feature Gaps (3-6 bullets: competitor feature → impact → our advantage)
5. Pricing Delta (one concise comparison; if numbers missing, provide a script template)
6. Ideal-use Objections & Short Scripts for Wins/Losses (3 objections with two short scripts each: "Win" script to advance, "Loss" script to disengage)
7. 3 Frontline Messaging Lines (one-liners reps can use immediately)
8. When to Walk Away (2-3 crisp criteria)
9. Single Primary CTA usage (exact phrasing integrating {{cta}})

Be conservative on claims: do not invent metrics. If proof is missing, list the exact proof required.

## Output Format
Output the battlecard as a single page using the exact headings below (in this order). Use short bullets and bold key phrases. Include an "Assumptions" block only if any required input or competitor detail was not supplied; in that case list the missing items as questions. Otherwise omit "Assumptions."

Required headings and ordering:
- Competitor Quick Positioning
- Top 5 Differentiation Points
- 3 Battle-Tested Rebuttals
- Feature Gaps
- Pricing Delta
- Ideal-use Objections & Short Scripts for Wins/Losses
- 3 Frontline Messaging Lines
- When to Walk Away
- Single Primary CTA usage
- Assumptions (only if inputs/competitor details missing)

Make outcomes measurable: append a one-line "Objective" under the main title stating the measurable next-step (e.g., "Objective: Secure a demo within 7 days" or "Objective: Move to commercial evaluation").

## Guardrails
- Ban cliches and hypey phrases (no "industry-leading", "best-in-class", "game-changer"). Use specific differentiators only.
- Claim hygiene: do not fabricate results or guarantees. If a metric is stated, cite which {{proof_points}} entry supports it or state "proof required: [what to collect]."
- One primary CTA only: {{cta}}. Do not scatter multiple CTAs.
- Keep scripts <20 words where possible and end with a question or clear next step.
- Do not include long narrative; use bullets and verb-level scripts that reps can say or paste.
- If the competitor's public claims contradict your proof, note the contradiction and advise an evidence request (e.g., "ask for contract term or user metric").

## Examples
Tiny excerpt demonstrating style:

Competitor Quick Positioning
- AcmeCloud: low-price, templated workflows that trade flexibility for faster setup.

Top 5 Differentiation Points
- Custom integration depth — supports bi-directional API vs Acme's one-way sync. Evidence: customer case study in {{proof_points}} showing two-week integration time reduced.

Variables

Usage Notes

Not for

Do not include

Competitive Battlecard Template — One-Page Prompt

Create a one-page competitor battlecard tailored to a named competitor and funnel stage, producing measurable next-step scripts, evidence notes, and A/B-ready variants for frontline reps.

Turn this into a working asset in minutes.

Import into Workspace to auto-fill variables, adapt output style, and iterate with OctiAI's prompt editor.

What you'll get

Output format

Markdown

Best used when

Avoid when

Sign in to save, like, or rate this prompt.

Made for

What to fill in

Use the guidance below to complete each placeholder with the right level of detail.

Funnel Stage

Provide the key details needed for this variable.

Offer

Provide the key details needed for this variable.

Target Audience

Provide the key details needed for this variable.

Channel

Provide the key details needed for this variable.

Primary Benefit

Provide the key details needed for this variable.

Proof Points

Provide the key details needed for this variable.

Objections

Provide the key details needed for this variable.

Cta

Provide the key details needed for this variable.

Rules

Canonical Examples

Input: Offer: RevOpsFlow (sales workflow automation for mid-market SaaS). Target: Head of Sales / SDR teams. Funnel stage: Qualification -> Demo. Channel: Call/Email/LinkedIn. Primary benefit: Cut manual CRM work and shorten sales cycles. Proof points: FinTechCo pilot cut sales cycle from 42 to 28 days (33% reduction); Integration delivered two-way Salesforce sync in 7 days; Customer quote: 'reduced follow-up work by half.' Objections: 'We already have a CRM workflow', 'Too disruptive', 'Security/compliance'. CTA: 'Schedule a 30-minute demo'. Competitor: PaceCRM — positions as 'all-in-one CRM with built-in workflows'. Competitor claims: 1) 'Simpler to set up with prebuilt templates.' 2) 'Lower price per user.' Competitor price: $25/user/mo; Our price: $45/user/mo (includes onboarding).

Loading result...

Failed to load output.


Competitor Quick Positioning: PaceCRM — all-in-one CRM + templates. Objective: Secure a demo within 7 days.
Top 5 Differentiation Points: ...
3 Battle-Tested Rebuttals: ...
Pricing Delta: PaceCRM $25/user/mo vs RevOpsFlow $45/user/mo (onboarding incl.).

Why it works: This example supplies a full set of inputs including competitor name+claims and proof points with concrete metrics and pricing—allowing the battlecard to produce specific evidence notes, an exact pricing delta, and short scripts that push the specified CTA.

Input: Offer: ContractQuick (contract lifecycle automation for mid-market legal & sales teams). Target: GC/Head of Legal and Sales Ops. Funnel stage: Demo -> Commercial evaluation. Channel: Email/Call. Primary benefit: Accelerate contract turnaround times and centralize approvals. Proof points: Beta pilot at RetailCo reduced approval time from 14 to 5 days; API connectors to DocStore and HRIS; Security: SOC2 Type II in vendor pack. Objections: 'We use manual Word+SharePoint', 'Integration complexity', 'Legal will not change process'. CTA: 'Start a 14-day pilot'. Competitor: SignFlow CLM — claims: 'Already integrated with e-sign and easy templates', 'Lower per-contract cost.' Competitor price: per-contract pricing unknown (not supplied).

Loading result...

Failed to load output.


Competitor Quick Positioning: SignFlow CLM — integrated e-sign + templates. Objective: Move to a 14-day pilot.
Top 5 Differentiation Points: measurable approval time reduction; modular integrations; security certs.
Pricing Delta: competitor price missing — provide script template to discuss per-contract delta.
Assumptions: missing competitor pricing info (asks for exact number).

Why it works: This example demonstrates behavior when some competitor details (pricing) are missing: the card uses supplied proof points for evidence, provides a pricing script template, and lists exact proof required where needed (e.g., contract cost data). It shows full rebuttals, feature gaps, and a single pilot-focused CTA.

Works Best With

Produces the best battlecards when you supply: