Write a response to [RECIPIENT] about a competitive analysis of [PRODUCT OR MARKET]. The response should help them make a decision, not read like a generic sales pitch. Use only the facts in [ANALYSIS NOTES], [OUR POSITION], and [RECIPIENT CONTEXT]. Do not invent competitor features, pricing, customer results, market share, quotes, weaknesses, or product-roadmap commitments. Start by identifying the recipient’s likely decision and the two or three criteria that matter most to them. Then write an email of 220 to 320 words with: 1. A direct opening that acknowledges the request and frames the decision. 2. A compact comparison of 2 to 4 options. Compare only criteria supported by my notes, such as target customer, workflow fit, implementation effort, integrations, control, service model, pricing structure, or known limitations. Use neutral language for competitors and name uncertainty where evidence is incomplete.
3. A recommendation that explains which option fits which circumstances. State where our offering is a poor fit if my notes support that conclusion. 4. A specific, low-pressure ask: a call, technical review, pilot discussion, or decision on the next artifact. Include a proposed agenda if asking for a meeting. Use short paragraphs or a simple labeled list, whichever makes the decision easiest to scan. Avoid unsupported superlatives, fear-based claims, and feature dumping. If the recipient is an internal stakeholder, prioritize decision criteria and tradeoffs; if external, keep confidential analysis out of the response. Before answering, verify every comparative statement against my notes and flag claims that need a source or approval. Ask up to 3 clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT] | Describe who will receive the response and their role in the decision. | Priya Shah, Director of Customer Support at a 150-person SaaS company |
| [PRODUCT OR MARKET] | Name the product category, purchase decision, or market being compared. | customer support platforms: HelpScout, Zendesk, and our service, Caseboard |
| [ANALYSIS NOTES] | Paste verified comparison facts, sources, caveats, and known competitor information. | Priya needs email and chat support for 25 agents. Zendesk has advanced workflow options but requires more administration. HelpScout has a simpler shared inbox. Caseboard supports email, chat, and HubSpot sync; its knowledge-base analytics are limited. |
| [OUR POSITION] | Describe your offering, its proven strengths, limitations, pricing context, and approved claims. | Caseboard offers assisted migration and a 14-day pilot. HubSpot sync and support setup are confirmed. Do not claim it is cheaper because pricing has not been approved. |
| [RECIPIENT CONTEXT] | Explain the recipient’s use case, priorities, stage of evaluation, and desired next step. | Priya asked after a demo for a candid comparison. Her priority is faster agent adoption and fewer manual CRM updates. Ask for a 30-minute workflow review. |
How to use
- Gather comparison facts from product documentation, approved pricing, test results, and notes from the recipient’s stated requirements.
- Separate verified facts from opinions before pasting them into the prompt; label any information that is uncertain or confidential.
- Check that the recommended option matches the recipient’s decision criteria rather than your preferred outcome.
- Follow up with: “Make this 150 words for an executive reader and retain only the comparisons that affect adoption, cost of change, and risk.”
Variations
Internal recommendation
Use this when advising colleagues or leadership on a vendor decision.
Write an internal recommendation memo about choosing between [OPTIONS] for [DECISION]. Use [EVALUATION EVIDENCE] and [STAKEHOLDER PRIORITIES]. Produce a 400-word memo with a decision summary, weighted criteria, factual tradeoffs, major risks, and a recommended next action. Separate verified evidence from assumptions. Do not hide weaknesses or claim a feature is available without evidence. Include a short list of questions that must be resolved before commitment. Ask up to 3 questions only if required input is missing.
Customer comparison
Use this after a prospect asks how you differ from a named competitor.
Draft a 180- to 240-word email to [PROSPECT] comparing [OUR PRODUCT] with [COMPETITOR] for [USE CASE]. Use only [APPROVED FACTS]. Open with the prospect’s stated priority, compare no more than three relevant capabilities, and explain the practical impact of each difference. State uncertainty plainly and avoid criticizing the competitor. End by offering [NEXT STEP]. Flag any statement that would require legal, product, or pricing approval. Ask up to 3 questions only if required input is missing.
Competitive rebuttal
Use this when you need to respond to a specific competitor claim.
Prepare a factual response to a competitor claim that [CLAIM]. Use [VERIFIED EVIDENCE], [AUDIENCE], and [DESIRED OUTCOME]. Write a brief response with the claim stated neutrally, the relevant facts, any qualifying conditions, and the action the reader should take. Do not repeat an allegation as fact, make legal conclusions, or speculate about competitor intent. Give two versions: a 90-word email paragraph and a 30-word sales-call answer. Ask up to 3 questions only if required input is missing.
Tips
- Compare the options against the buyer’s actual workflow; a long feature list hides the conditions under which a capability matters.
- Use sources for claims that can change, especially pricing, integrations, security posture, and product availability.
- A candid limitation increases credibility only when it is concrete and connected to fit, such as limited analytics for a team that needs advanced reporting.
- Do not forward internal competitive notes to an external recipient without removing confidential strategy, unverified claims, and vendor-negotiation details.
FAQ
Can AI compare competitors accurately?
It can organize evidence you provide, but product features and prices change. Confirm any current claim against official documentation or an approved internal source.
Should I name a competitor’s weaknesses?
Name relevant tradeoffs factually and without exaggeration. The useful question is which option fits the buyer’s situation, not which company is universally better.
What if the recipient has not shared decision criteria?
Ask a short question about the use case, constraints, and decision deadline. Do not guess what matters most and build a comparison around that guess.