Sales reps closing deals this week against specific competitors. These 25 prompts generate finished battlecard sections you can review, edit, and distribute to your team immediately.
These prompts pair well with Jasper AI for Sales-specific tone control, or Copy.ai for fast iteration.
Competitor Feature Comparisons
You are a sales enablement manager creating a feature comparison section for a competitive battlecard.
Our product: {product_name} Competitor: {competitor_name} Key differentiators: {three_main_advantages} Competitor strengths: {two_areas_they_win} Target audience: {buyer_persona} Deal size: {typical_deal_value} Sales cycle: {length_in_weeks} Tone: {confident / neutral / data_driven}
Write a 400-500 word feature comparison section using a three-column format: Feature Category, Us, Them. Focus on business outcomes, not technical specs. Lead with our strongest differentiators. Acknowledge their strengths honestly but frame around fit for our target buyer. Include specific metrics where possible.
When to use it: Your team keeps losing deals to one specific competitor and you need a clear feature breakdown that reps can reference during discovery calls.
Pro tip: Always include at least one area where the competitor is genuinely stronger. Reps who acknowledge competitor strengths early build more credibility than those who pretend every feature comparison favours you.
You are a sales engineer writing a technical battlecard section for enterprise deals.
Integration focus: {primary_integration_challenge} Our solution approach: {how_we_solve_it} Competitor approach: {their_method} Customer environment: {existing_tech_stack} Implementation timeline: {weeks_or_months} Resource requirements: {team_size_needed} Risk factors: {main_technical_concerns} Success metrics: {how_customer_measures_win}
Write a 300-400 word technical comparison that a non-technical buyer can understand. Start with the business problem, not the technical solution. Use analogies for complex concepts. End with three questions reps should ask to expose the competitor’s technical limitations.
When to use it: You’re competing in technical evaluations where the buyer’s IT team influences the decision but the economic buyer isn’t technical.
Pro tip: Frame technical advantages as risk reduction, not feature superiority. CFOs care more about implementation risk than architectural elegance.
You are a sales manager creating a pricing battlecard for deals where prospects mention competitor pricing.
Our pricing model: {how_we_charge} Competitor pricing: {their_model} Total cost difference: {percentage_higher_or_lower} Value differentiators: {why_price_difference_exists} ROI timeframe: {months_to_payback} Hidden costs in their solution: {what_they_miss} Discount authority: {maximum_flex_available} Champion strength: {strong / moderate / weak}
Write a 250-300 word pricing positioning script that reframes the conversation from cost to value. Include specific ROI calculations. Give reps language to handle the “you’re more expensive” objection without immediately discounting. End with a discovery question that exposes hidden costs in the competitor’s approach.
When to use it: Your solution carries a price premium and reps need confident language to justify the investment without sounding defensive.
Pro tip: Never lead with “we’re not actually more expensive when you consider…” Instead, agree that investment matters, then ask what outcome would make the difference in price irrelevant.
You are a competitive intelligence analyst writing a marketplace positioning battlecard.
Market category: {software_category} Our market position: {leader / challenger / niche} Competitor position: {their_market_stance} Analyst reports: {recent_gartner_forrester_mentions} Customer base size: {our_vs_their_customer_count} Geographic strength: {regions_where_each_wins} Industry focus: {verticals_each_targets} Recent news: {funding_acquisitions_partnerships}
Write a 350-450 word market positioning section that sales reps can reference when prospects ask “how do you compare to [competitor]?” Focus on market momentum, customer traction, and strategic direction. Include specific data points that support our positioning. Address any recent competitor wins or announcements that prospects might mention.
When to use it: Large prospects want to understand market dynamics and vendor viability before committing to a significant purchase.
Pro tip: If the competitor recently raised funding or made acquisitions, position it as instability rather than strength. Growth-stage companies often struggle with integration and customer service during rapid expansion.
You are a sales enablement specialist creating a use case battlecard for a specific industry.
Industry: {target_vertical} Common use case: {primary_business_problem} Our approach: {how_we_solve_it} Competitor approach: {their_solution_method} Regulatory requirements: {compliance_considerations} Implementation complexity: {simple / moderate / complex} Typical buyer: {job_title_and_concerns} Success story: {customer_name_and_outcome}
Write a 300-350 word industry-specific battlecard that positions our solution for this vertical. Start with industry challenges the buyer recognizes. Explain why our approach fits their operating environment better than the competitor’s. Include one specific customer example with measurable outcomes. End with industry-specific questions that reveal fit.
When to use it: You’re competing for deals in a vertical where industry expertise matters more than generic functionality.
Pro tip: Use industry-specific language and reference regulatory requirements even if both solutions meet them. Buyers want vendors who understand their world, not generic software companies.
Objection Handling Scripts
You are a sales trainer writing objection handling scripts for the “we’re happy with [competitor]” response.
Competitor name: {current_vendor} Length of relationship: {years_with_them} Known pain points: {issues_they_likely_face} Our key advantage: {primary_differentiator} Switching cost concern: {implementation_effort} Decision timeline: {urgent / exploring / future} Stakeholder sentiment: {satisfied / frustrated / mixed} Trigger event: {why_they_took_meeting}
Write a 200-250 word script that acknowledges their satisfaction while opening conversation about improvement opportunities. Don’t attack the competitor directly. Focus on evolving business needs they might not be addressing. Include three discovery questions that reveal gaps in their current solution.
When to use it: Prospects take the meeting but claim they’re satisfied with the incumbent vendor and aren’t actively looking to switch.
Pro tip: Ask about their experience during the last major business change (growth, acquisition, new regulations). Incumbent solutions often break down during scaling or transformation.
You are a sales manager creating scripts for the “we need to include [competitor] in our evaluation” objection.
Competitor: {name_they_mentioned} Our relationship stage: {early / advanced / final_stages} Their evaluation process: {formal_rfp / informal / undefined} Key stakeholders: {who_drives_decision} Timeline pressure: {deadline_constraints} Budget approved: {yes / no / unknown} Our unique value: {what_only_we_offer} Competitive weakness: {their_known_limitation}
Write a 250-300 word response script that positions inclusion of competitors as positive while steering the evaluation criteria toward our strengths. Include language that helps the prospect design a fair evaluation process. Give reps questions to ask that expose areas where the competitor typically struggles.
When to use it: You’ve built momentum with a prospect but they want to run a competitive process before deciding.
Pro tip: Help them design the evaluation criteria rather than resisting the competitive process. Prospects who feel you’re trying to avoid competition assume you’re afraid of losing.
You are a sales enablement manager writing scripts for price objections specific to competing against lower-cost alternatives.
Price gap: {percentage_difference} Competitor positioning: {how_they_justify_lower_price} Value at risk: {what_prospect_loses_with_cheap_option} Implementation risk: {likelihood_of_problems} Total cost factors: {hidden_expenses_in_their_solution} Prospect budget: {confirmed / estimated / unknown} Decision criteria: {cost_vs_features_vs_risk} Timeline sensitivity: {rushed / normal / flexible}
Write a 300-350 word script that reframes the price conversation around total cost of ownership and risk mitigation. Include specific examples of what goes wrong with low-cost solutions. Give reps language to calculate the true cost difference when factoring in implementation time, training, and ongoing support.
When to use it: You’re losing deals to competitors who win primarily on price rather than functionality or service.
Pro tip: Ask what happens if the implementation fails or takes twice as long as planned. Low-cost vendors rarely have the resources to fix problems quickly.
You are a sales coach writing scripts for handling the “we want to build this internally” objection.
Prospect company size: {employee_count} Technical team capacity: {engineering_resources} Build vs buy history: {past_decisions} Time to market pressure: {urgency_level} Core business focus: {what_they_should_focus_on} Estimated build cost: {internal_development_expense} Maintenance burden: {ongoing_resource_needs} Competitive pressure: {market_timing_factors}
Write a 250-300 word script that respectfully challenges the build decision without dismissing their technical capabilities. Focus on opportunity cost and time to market. Include questions about ongoing maintenance, feature development, and resource allocation that reveal the true cost of building internally.
When to use it: Technical prospects believe they can build a solution faster or cheaper than buying your product.
Pro tip: Don’t argue about their ability to build it. Instead, ask about the cost of maintaining and evolving it while their competitors are advancing their core business.
You are a sales director writing scripts for the “we need more time to decide” stall.
Evaluation length: {how_long_they_have_been_looking} Stakeholders involved: {who_needs_to_approve} Stated concerns: {reasons_for_delay} Competitor status: {where_others_stand} Budget cycle: {when_money_becomes_available} Current pain level: {how_urgent_the_problem} Implementation timeline: {when_they_need_solution_live} Risk of status quo: {cost_of_waiting}
Write a 200-250 word script that creates appropriate urgency without being pushy. Help them understand the cost of delay in business terms. Include questions that reveal whether this is a real timing issue or a polite way of saying no. Give reps language to offer interim solutions or phased approaches that reduce decision risk.
When to use it: Qualified prospects go silent or keep pushing decision timelines despite having budget and apparent need.
Pro tip: Ask what would need to change for them to feel comfortable deciding today. Often the delay is about one specific concern they haven’t voiced directly.
Win/Loss Story Templates
You are a sales enablement manager documenting a competitive win for future battlecards.
Customer: {company_name_and_industry} Deal size: {contract_value} Competitors involved: {who_else_they_evaluated} Decision timeline: {length_of_sales_cycle} Key stakeholders: {titles_of_decision_makers} Winning differentiators: {why_they_chose_us} Competitor weaknesses exposed: {where_others_fell_short} Turning point moment: {when_momentum_shifted}
Write a 400-500 word win story that sales reps can reference in similar competitive situations. Structure it as: situation, competitors involved, evaluation process, key decision factors, why we won, and specific outcomes achieved. Include direct quotes from the customer about what mattered most. Make it credible and specific enough to reference in proposals.
When to use it: You won a competitive deal and need to capture the story while it’s fresh for use in future similar situations.
Pro tip: Get the customer’s permission to use their story by positioning it as helping other companies make better decisions. Most customers will agree if you offer to share insights about the vendor evaluation process.
You are a competitive intelligence analyst writing a loss analysis for sales team learning.
Lost deal: {customer_and_deal_size} Winning competitor: {who_beat_us} Stated reason for loss: {what_they_told_us} Likely real reason: {actual_decision_factors} Our mistakes: {what_we_could_have_done_differently} Competitor advantages: {where_they_legitimately_won} Warning signs missed: {early_indicators_we_ignored} Process lessons: {sales_methodology_improvements}
Write a 350-400 word loss analysis that helps reps recognize and avoid similar losses. Be honest about our mistakes without making excuses. Identify specific moments where different actions might have changed the outcome. Include questions reps should ask earlier in similar deals to qualify properly or disqualify faster.
When to use it: You lost a significant competitive deal and need to extract lessons for the broader team without assigning blame.
Pro tip: Interview someone on the prospect side if possible. Sales reps often get polite reasons for losses rather than the real decision factors.
You are a sales manager creating a case study from a customer who switched from a major competitor.
Customer: {company_name} Previous solution: {competitor_they_left} Reason for switch: {primary_pain_points} Implementation experience: {how_smooth_the_transition} Time to value: {how_quickly_they_saw_results} Measurable outcomes: {specific_improvements} Switching costs: {what_they_had_to_invest} Unexpected benefits: {positive_surprises}
Write a 300-400 word switching story that addresses concerns prospects have about leaving incumbent vendors. Focus on the business case for change, implementation experience, and measurable outcomes. Include specific metrics that justify the switching cost. Address common fears about disruption during transition.
When to use it: Prospects are interested but worried about the risk and effort of switching from their current solution.
Pro tip: Include details about what the customer wishes they had known earlier and how much faster they wish they had made the switch. FOMO is powerful when it comes from a peer.
You are a sales enablement specialist creating a David vs Goliath win story against a much larger competitor.
Customer size: {employee_count_or_revenue} Large competitor: {big_vendor_we_beat} Their advantages: {resources_brand_features_they_had} Our advantages: {agility_service_focus_areas} Decision factors: {what_mattered_most_to_customer} Implementation difference: {how_our_approach_differed} Ongoing relationship: {service_level_differences} Customer quote: {what_they_said_about_choosing_us}
Write a 250-350 word underdog win story that helps prospects see advantages of working with smaller vendors. Position our size as an asset, not a limitation. Include specific examples of how we moved faster, customized more, or provided better service than the larger alternative. Make it relevant for prospects comparing us to market leaders.
When to use it: Prospects worry that you’re too small or lack the resources of bigger competitors they’re evaluating.
Pro tip: Emphasize the customer’s access to senior team members and decision-makers. Large vendors often assign junior resources to all but their biggest deals.
You are a sales director documenting a win in a crowded competitive evaluation with multiple vendors.
Evaluation size: {number_of_vendors_considered} Evaluation process: {how_they_narrowed_down_options} Final competitors: {who_made_the_shortlist} Evaluation criteria: {how_they_scored_vendors} Our differentiator: {what_separated_us_from_pack} Proof point: {demo_trial_reference_that_sealed_it} Decision timeline: {how_long_evaluation_took} Implementation priority: {what_they_needed_first}
Write a 350-450 word story about succeeding in a formal RFP or multi-vendor evaluation. Explain how we positioned against multiple competitors simultaneously. Include details about the evaluation process that help reps understand how to succeed in similar formal procurements. Focus on what made us stand out in a crowded field.
When to use it: You’re entering a formal procurement process with multiple competitors and need to understand how to differentiate effectively.
Pro tip: Large evaluations often come down to who best understands the customer’s unique requirements. Generic responses that work for any buyer usually lose to customized approaches.
Territory Planning
You are a sales manager creating a competitive landscape analysis for a new territory.
Territory: {geographic_region_or_market_segment} Primary competitors: {top_three_vendors_in_area} Market share distribution: {rough_percentage_breakdown} Customer concentration: {where_prospects_are_located} Competitive strengths: {what_each_competitor_does_well} Market trends: {industry_direction_regulatory_changes} Partner ecosystem: {resellers_consultants_influencers} Win conditions: {what_it_takes_to_succeed_here}
Write a 400-500 word competitive territory analysis that helps new reps understand the local competitive dynamics. Include specific companies or deals to target, competitors to watch, and strategies that work in this market. Identify any unique regional factors that affect competitive positioning.
When to use it: You’re assigning a rep to a new territory or market segment and need them to understand competitive dynamics quickly.
Pro tip: Include names of specific prospects who have expressed dissatisfaction with current vendors or are approaching renewal dates. Timing matters more than perfect fit in territory development.
You are a competitive intelligence manager creating quarterly battlecard updates based on recent competitive activity.
Reporting period: {quarter_and_year} Competitor focus: {vendor_with_most_activity} Product updates: {new_features_or_releases} Pricing changes: {adjustments_to_their_model} Partnership announcements: {new_integrations_or_channels} Customer wins/losses: {notable_deals_they_won} Market positioning shifts: {messaging_or_strategy_changes} Team changes: {new_hires_departures_leadership}
Write a 300-400 word competitive update that sales reps can read in two minutes. Focus on what changed that affects active deals. Include specific talking points for common questions prospects ask about recent competitor news. Highlight any new vulnerabilities or strengths the team should know about.
When to use it: A major competitor makes significant announcements or changes that affect your competitive positioning.
Pro tip: Focus on what matters for deals closing in the next 90 days. Reps don’t need comprehensive analysis; they need specific talking points for conversations happening this week.
You are a sales enablement director creating account-specific competitive intelligence for a major deal.
Target account: {company_name} Account size: {employee_count_and_revenue} Current vendor: {incumbent_solution_provider} Relationship length: {years_with_current_vendor} Known pain points: {issues_driving_evaluation} Stakeholder map: {key_people_and_their_preferences} Evaluation trigger: {what_started_this_process} Competitive threats: {other_vendors_they_are_considering}
Write a 350-450 word account-specific competitive brief that prepares the sales team for this particular deal. Include background on existing vendor relationships, likely objections, and stakeholder preferences. Provide specific strategies for this account rather than generic competitive positioning.
When to use it: You’re pursuing a strategic deal where account-specific competitive intelligence could make the difference between winning and losing.
Pro tip: Research the decision-makers’ backgrounds and previous vendor selections. People often have patterns in how they evaluate and choose solutions.
You are a sales operations manager analyzing competitive win/loss patterns to identify strategic gaps.
Analysis period: {time_range_reviewed} Total competitive deals: {number_analyzed} Win rate vs each competitor: {percentage_breakdown} Common loss reasons: {top_three_factors} Common win factors: {what_drives_success} Deal size patterns: {where_we_win_vs_lose_by_size} Industry patterns: {verticals_where_we_struggle} Sales cycle differences: {length_variations_by_competitor}
Write a 400-500 word strategic competitive analysis that identifies where to focus battlecard improvements and sales training. Include specific recommendations for addressing competitive weaknesses. Identify market segments or deal types where competitive positioning needs adjustment.
When to use it: You need data-driven insights about competitive performance to guide sales strategy and enablement investments.
Pro tip: Separate what sales reps say about why they lose from what customers actually say. The gap between these perspectives reveals training opportunities.
You are a channel manager creating competitive guidance for partner sales teams.
Partner type: {reseller_system_integrator_consultant} Partner expertise: {their_technical_and_industry_focus} Common competitive situations: {competitors_they_face_regularly} Partner advantages: {unique_value_they_bring} Support available: {resources_we_provide} Co-selling situations: {when_we_engage_directly} Margin considerations: {how_pricing_affects_their_business} Training provided: {competitive_education_available}
Write a 300-400 word partner-focused competitive guide that helps channel partners position against competitors effectively. Include language they can use with their customers and guidance on when to engage direct sales support. Focus on competitive situations where partners have advantages over direct sales.
When to use it: Channel partners need competitive guidance that’s different from what works for direct sales teams.
Pro tip: Partners often compete on relationships and local presence rather than product features. Give them ammunition that plays to their strengths, not just product advantages.
Frequently Asked Questions
How often should I update sales battlecards with new competitive intelligence?
Update battlecards monthly for active competitors and quarterly for secondary players. Set up Google alerts for competitor news and update immediately when they announce major product changes, pricing adjustments, or leadership shifts that affect your positioning.
What’s the most effective way to get reps to actually use competitive battlecards?
Make them searchable by situation rather than organized by competitor. Reps don’t think “I’m competing against Competitor X today.” They think “The prospect just said they’re happy with their current solution” and need the right script immediately.
Should battlecards include information about competitors’ weaknesses or focus on our strengths?
Include both, but frame competitor weaknesses as “areas to explore” rather than direct attacks. Reps who trash competitors lose credibility. Instead, give them questions that help prospects discover limitations on their own through the evaluation process.