🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.
Sales enablement managers, Account executives, Sales leaders, Product marketers, SDR 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 enablement and competitive positioning specialist. Your task is to create a sales battlecard reps can use during competitive conversations.
### Required Input
- Company or Offer: [Describe what is being sold. Example: "B2B payroll platform for distributed teams"]
- Competitor: [Name or describe the competitor. Example: "large legacy payroll provider"]
- Target Buyer: [Example: "HR leaders at 100-500 employee companies"]
- Deal Context: [Where competition appears. Example: "late-stage evaluation after demo"]
- Buyer Priorities: [What buyers care about. Example: "accuracy, compliance, employee experience, implementation speed"]
- Your Strengths: [Known advantages. Example: "faster onboarding, stronger support, modern employee portal"]
- Competitor Strengths: [Be honest. Example: "brand recognition, broad integrations, procurement approval"]
- Competitor Weaknesses: [Known gaps or perceived issues]
- Proof Points: [Case studies, metrics, testimonials, implementation examples]
- Claims to Avoid: [Legal, compliance, or positioning limits]
### Input Validation
Check that the competitor, buyer, deal context, strengths, weaknesses, and proof points are specific enough to support a useful battlecard. If the user only provides general statements like "we are better" or "they are expensive," ask for clarification and pause.
### Instructions
Create a battlecard that helps reps sell with confidence and accuracy. Avoid aggressive or unsupported claims. Focus on how to guide the buyer toward the right evaluation criteria.
Start by summarising the competitive situation: why the competitor is considered, what they may appear strong at, and where the buyer may need a clearer comparison. Identify the moments in the sales process where the battlecard is most useful.
Develop positioning that is respectful, credible, and buyer-centred. Show reps how to reframe the comparison around business outcomes, risk, speed, adoption, service quality, cost of ownership, or strategic fit depending on the context.
Include a competitive talk track that reps can say naturally. Provide discovery questions that reveal whether the competitor is a real threat, a procurement benchmark, or simply part of the buyer's research. Include traps to avoid, especially unsupported criticism or feature-by-feature arguments that weaken credibility.
For each likely competitor claim, provide a measured response, a question to ask, and a proof point to support the response. Finish with practical guidance on when to escalate, when to bring in leadership, and what assets to send after the conversation.
### Output
Produce the battlecard with these sections:
- Competitive Snapshot
- When This Battlecard Applies
- Buyer Evaluation Criteria
- Positioning Summary
- Your Advantages
- Competitor Advantages to Respect
- Competitive Risk Areas
- Discovery Questions
- Competitor Claim Response Table
- Talk Track
- Proof Points and Assets to Use
- Traps to Avoid
- Recommended Follow-Up Actions
Create a one-page rep version with only the talk track, claims, responses, and proof points.
Our Offer: Apex Automated Logistics Suite (Cloud-Native Route Optimization & Cross-Border Hub).
The Competitor: Titan Logistics Software (Large Legacy Enterprise Provider).
Target Buyer: VP of Global Logistics, Director of Supply Chain, and Chief Information Officer (CIO) at mid-to-large freight forwarding and shipping enterprises ($100M–$500M in revenue).
The Battle Dynamics: Titan is the entrenched, heavily recognized legacy standard. They typically enter deals backed by historical executive alignment, broad monolithic suite capability, and a “safe choice” procurement reputation. However, their architecture is rigid, requiring custom coding for integrations, expensive professional services for workflow changes, and manual spreadsheet workarounds for modern cross-border data compliance.
Deploy this battlecard during Mid-to-Late Stage Evaluations (immediately following the technical demonstration or sandbox phase). This is the critical window where the buyer is actively comparing Titan’s expansive, check-the-box feature list against Apex’s agile, automated, and deployment-friendly architecture.
Do not attempt to match Titan feature-for-feature across their 20-year-old monolithic product catalog; that plays directly into their trap. Instead, reframe the conversation around Agility vs. Architecture Rigidness. Position Titan as an expensive, slow-moving IT project that requires your business to adapt to their software. Position Apex as a modern, high-velocity infrastructure engine that deploys in weeks, automates manual workflows natively, and adapts instantly to changing supply chain environments.
| What Titan Claims | The Hidden Reality | Recommended Rep Response Track | The Pivot Question |
|---|---|---|---|
| “We offer a complete, unified all-in-one logistics suite.” | Their suite is a collection of acquired point solutions stitched together with messy backend code databases. | “Titan does offer an expansive module catalog. However, many enterprise operations find that these legacy modules require massive custom middleware code to actually communicate with each other in real-time.” | “Do you prefer a wide checklist of separate modules that require manual data synchronization, or a single, modern engine built natively for high-velocity route automation?” |
| “We are the safest choice with 20 years of enterprise compliance.” | Their core database architecture was built before cloud computing and modern cross-border API systems. | “Titan is a well-established brand. But their underlying tech stack was built 20 years ago, which is why modifying simple workflows often requires hiring their internal software consulting army.” | “Does choosing a ‘traditional’ vendor mitigate your operational risk if their deployment rigidity keeps your field dispatchers stuck in manual Excel spreadsheets for another 6 months?” |
“Titan is an excellent, expansive enterprise suite if you are looking for a multi-year IT consulting project to centralize historical databases. But if your immediate corporate priority is scaling your cross-border throughput next quarter by 30% without ballooning your operational staff budget, you need execution velocity, not legacy architecture code. Apex is built to ingest your live data fields, automate manifest preparation in weeks rather than fiscal quarters, and drive immediate dispatcher adoption without requiring custom professional services budgets.”
Get access to all workflows, across every sector, with structured systems built for better results.