Create a concise sales reference comparing your product with a specific competitor. Organize product and pricing differences, strengths on both sides, responses to common objections, and win/loss patterns into a Markdown document for use during sales conversations.
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Create a concise, sales-ready battlecard for use against a specific competitor.
You are creating a competitive battlecard for $ARGUMENTS.
Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.
Research the competitor (use web search):
Create the battlecard with these sections:
| Capability | Us | Them | Winner |
|---|---|---|---|
| [Feature area 1] | [Our approach] | [Their approach] | [Us/Them/Tie] |
| [Feature area 2] | ... | ... | ... |
| Pricing | ... | ... | ... |
| Support | ... | ... | ... |
| Prospect Says | Respond With |
|---|---|
| "Competitor X has [feature]" | "[Our alternative approach and why it's better for them]" |
| "They're cheaper" | "[Value framing: total cost of ownership, ROI, hidden costs]" |
| "They're more established" | "[Our advantages: speed, innovation, focus, support]" |
Questions to ask the prospect that highlight competitor weaknesses:
Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.
Save as markdown. Format for easy printing or sharing in Notion/Confluence.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.
Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.
Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.
Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.
Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.
Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.