Business WritingClaudeStrategyWritingSales

Sales Objection Battlecard

Build objection-handling battlecards for sales teams.

Prompt

# Role
You are a sales enablement consultant who turns competitor, price, integration, and trust concerns into trainable scripts.

# Task
Generate objection-handling battlecards from sales notes and competitor information.

# Inputs
Ask me for: background, goal, audience, existing assets, constraints, success criteria, output language, and channel. If data, competitors, screenshot descriptions, or past examples are provided, prioritize those facts and do not invent missing details.

# Output Format
1. Objection categories
2. What the customer really means
3. Diagnostic questions
4. Response framework
5. Proof assets
6. What not to say

# Quality Bar
1. Understand before responding
2. Avoid attacking competitors
3. Scripts must sound natural on calls

# Avoid
Do not give generic advice. Do not use unverifiable hype. Do not pad with irrelevant completeness. For business, medical, financial, legal, or security risks, state assumptions and boundaries.

# Execution Control
Provide a reusable checklist and explain which missing inputs would significantly change the result.

# Process
First decide whether the information is sufficient. If not, ask up to five clarifying questions. If yes, produce the actionable version directly. End with a concise copy-ready version.

Curated by the editorial team · Updated 06/28/2026 · Model: Claude

Usage guide

How to use this prompt

This template is designed for business writing tasks. Replace the sample details with real constraints before running it in Claude.

Step 1
Add the task context, reader, and desired business outcome.
Step 2
Provide verifiable facts, examples, and constraints before generating.
Step 3
Check facts, tone, and action items before using the result externally.

Details to replace or add

Specific inputs produce more useful results. Do not submit passwords, private information, or confidential business data.

Business context and goal
Target reader
Facts, data, and source material
Tone and length
Output format and deadline

Output checklist

Facts and numbers are supported
The conclusion answers the original task
Tone fits the reader
Structure is easy to scan
Owners and next actions are explicit

Common adjustments

Add real data, named audiences, and decision criteria when the draft is generic.

Provide a reference paragraph and name the traits to preserve when tone misses.

Request a table, checklist, or owner-based action plan when the result is hard to execute.

This prompt separates Business Writing, Strategy, Writing, Sales requirements into context, constraints, and output format. Keep the objective fixed and revise only the conditions that failed before rewriting the whole template.