Competitor Loss Counter-Strategy
Turn a competitor loss into a practical counter-strategy and future win plan.
Customise & copy
Add the context you have. The prompt updates as you work.
Enter the competitor that won the deal.
Describe the product, capability, or positioning that influenced the decision.
Paste or summarize the customer’s stated reason for choosing the competitor.
State the specific advantage our product or approach has for this account.
Choose the stage that should guide the future win plan.
Live prompt
5 fieldsCreate a competitor-loss counter-strategy using only the information provided. Do not invent competitor claims, customer facts, metrics, testimonials, or social proof. Clearly distinguish known information from reasonable inference, and do not ask follow-up questions. Use exactly this four-section format: 1. Positioning summary Write exactly one sentence explaining why the competitor won and how we should position against that outcome. 2. Counter-strategy Give 2–3 specific points covering how to reframe the customer’s stated reason, use our differentiator, and address the competitor’s winning feature without bashing them. 3. Diplomatic mention script Write a concise, customer-ready script that mentions {{competitor_name}} respectfully, acknowledges the appeal of {{competitor_feature}}, and explains where our approach may be a better fit. Do not make unsupported claims. 4. Future win plan Give 3 actionable steps appropriate to the Closed-lost follow-up stage, including what to validate, who to engage or influence, and what proof or comparison to prepare. Keep the plan practical and usable after one light edit. Inputs: - Competitor name: {{competitor_name}} - Product or feature they won with: {{competitor_feature}} - Customer’s stated reason for the loss: {{loss_reason}} - Our key differentiator: {{our_differentiator}} - Target account stage: Closed-lost follow-up
Proof before you use it
A real example
Tested on gpt-5.6-luna on 2026-09-10
{
"loss_reason": "The CFO selected Northstar because the finance team needed a familiar reporting format before the next quarterly board meeting",
"competitor_name": "Northstar Analytics",
"competitor_feature": "Executive dashboards with prebuilt board-reporting templates",
"our_differentiator": "Deeper scenario modeling and permissioned data access for regional healthcare administrators",
"target_account_stage": "Renewal or expansion window"
}A small ritual that works
How to use it
- 01Enter the competitor name.
- 02Describe the feature they won with and the customer's stated reason for the loss.
- 03State your key differentiator.
- 04Select the target account stage.
Why it works
The prompt creates a disciplined four-part response: it first states a positioning direction, then turns that direction into counter-strategy points, a respectful customer-ready script, and stage-specific next steps. Its evidence rules keep the analysis grounded in the five supplied inputs, distinguish inference from known information, and prevent unsupported competitor claims or social proof. The required mention of validation, stakeholder engagement, and comparison preparation makes the plan more actionable without allowing the writer to invent account facts.
Where it fails
The prompt is constrained by the information supplied in its five inputs. When those inputs are vague, incomplete, or do not identify the customer’s actual priorities, the response must remain general and label important conclusions as matters to validate rather than presenting them as established facts. Its instruction not to ask follow-up questions also limits how much missing context can be clarified within the response.
Customisation tips
Make the inputs specific enough to support a useful commercial conversation. Describe the competitor feature in concrete terms, separate the customer’s stated loss reason from internal assumptions, and express the differentiator as an account-relevant advantage rather than a broad slogan. Choose the account stage carefully because it determines the emphasis of the future win plan. If the prompt is adapted, preserve the four-section structure while adjusting the stakeholder, proof, or comparison requirements to match the sales process.
Watch-outs
- Keep known customer statements separate from reasonable inferences; the prompt explicitly requires uncertain priorities to be validated.
- Do not turn the competitor feature into an unsupported weakness claim. The required script is designed to acknowledge its appeal and compare fit respectfully.
- The phrase "one light edit" does not remove the need to verify account-specific details before external use.
- The comparison should include only capabilities that are confirmed or clearly marked for validation, especially for competitor functionality.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Want to make AI useful across your team? Explore Atul's training.