Revenue Enablement report
Win/Loss Analyzer: your result
This answer uses a made up example company. Change the details above and press Run to see your own result.
Win/Loss Analyzer
Structure a win/loss review of your deals
For sales and revenue leads. The decision: why did we win or lose, and what do we change?
Give it the type of review, plus the deal outcome and details, and get the likely reasons you won or lost, questions for the review, a stakeholder analysis and action items.
What you get
This sample is a made up example, built from the inputs behind Fill in an example. It shows part of one section of the answer.
Write-up
The product lost this deal to your first competitor. The deal was worth $36,000 and ran 75 days.
What was sold: our product.
What the buyer weighed. The buyer weighed the product against your first competitor.
- your first competitor is another option the buyer used or considered. One of them is the option you named as the winner. Ask the buyer what it did well, and what it failed to give them.
The stated reason. The reason the buyer gave, in the words you recorded: "price".
What the reason points to.
See the full example answer or run it with your own details.
Result
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
What next? Work with Shashwat Try another tool See all 85 tools and skills
Example answer
Generated on 2 November 2026 from this branch, with the inputs behind Fill in an example. Your own inputs give a different result.
Revenue Enablement report
Example: Win/Loss Analyzer
Show the full result
Win/Loss Analysis: Single Deal: our product
Sector: not clear from your inputs (name the industry for sector notes). Business model: not stated. Tell us how you charge and the plan will adjust.
Billing dependent steps are conditional: trials, seats and recurring renewals require a subscription; a statement of work requires a services contract; site or link commitments require connectivity billing. Confirm the applicable choice before using those steps.
Write-up
The product lost this deal to your first competitor. The deal was worth $36,000 and ran 75 days.
What was sold: our product.
What the buyer weighed. The buyer weighed the product against your first competitor.
- your first competitor is another option the buyer used or considered. One of them is the option you named as the winner. Ask the buyer what it did well, and what it failed to give them.
The stated reason. The reason the buyer gave, in the words you recorded: "price".
What the reason points to.
- Price or budget: at $36,000 the account owner needs the buyer’s approved cost case against your first competitor. Check whether the value case was agreed in the buyer's own numbers before price came up.
Questions for the review call
- What did the buyer say about your first competitor, and at which point did it become the real comparison?
- The deal ran 75 days: which stage took longest, and was that the buyer's process or a stall you could have moved?
- The deal was worth $36,000: did the price or the size of the commitment come up as a reason, and who raised it?
- Was the reason you recorded the real reason or the polite one, and who inside the buyer first said it?
Inputs as you gave them
| Item | Value |
|---|---|
| Solution | our product |
| Deal Value | $36,000 |
| Sales Cycle | 75 days |
| Outcome | Lost |
| Stated reason | Price |
| Competitor who won | Your first competitor |
To sharpen this, give:
What was not given, and what each input would change:
stakeholders involved: it would change the people section from a list of sector roles to the real buying group, with a question for each person.deal details: it would add the buyer, the alternatives and the notes to the write-up.
How the answer is laid out, using the sections the tool prints. Each branch is a hypothesis to check.
When a tool is not enough: if the decision needs more than one answer, talk it through in a call. Book 45 minutes with Shashwat.
How to read the answer
The analyzer summarizes the deal facts you entered into a Write-up (What was sold, What the buyer weighed, The stated reason, and What the reason points to) and generates specific Questions for the review call based on your outcome, deal value, sales cycle length, stated reason, and winning competitor. It treats the stated loss reason (such as "price") as a hypothesis to check: for example, asking whether the value case was agreed in the buyer's own numbers before price came up, and whether the recorded reason was the real reason or the polite one.
What to do next
- Founder: Call the buyer contact yourself using the Questions for the review call to find out at which point the winning alternative became the real comparison and whether your stated reason was the real reason.
- CEO: Compare Sales Cycle length and Deal Value across your won and lost deals this quarter to see whether stalls happen in the buyer's process or because the economic buyer was never reached.
- CMO: Feed the verified win and loss reasons into ICP Evolution Tracker and Competitive Intel so your positioning and battle cards reflect why buyers actually chose or rejected you.
- CRO: Require reps to enter Stakeholders involved and Deal details (as listed under To sharpen this) before every post-deal debrief, and check whether an approved cost case existed before pricing was shared.
- Demand generation head: Review lost-deal patterns (Several deals or Loss pattern mode) to stop spending budget on segments or triggers that consistently lose on the same structural gap.
Why come back
Run the analyzer after every closed-won or closed-lost deal in Single deal mode, and come back at the end of the quarter in Several deals, Competitor analysis, or Loss pattern mode with a portfolio summary of your deals. The tool applies the same fixed rules every time. It does not call an AI model, and this site does not keep what you enter.
Who is the Win/Loss Analyzer tool not ideal for?
- Anyone who cannot give the inputs listed above, because the answer is built only from them.
- Teams that want the tool to read their CRM, email or call notes: it works only from what you type.
- Anyone who wants to send the output straight to a buyer: every output is a draft for a person to review first.
How do I use the Win/Loss Analyzer tool with an AI assistant?
Add Revenue Enablement once (see Use it in Claude, ChatGPT or Gemini), then ask in plain words. Here is a prompt built from the tested example:
My role is not stated. Ask me for my role first. Use Revenue Enablement's Win/Loss Analyzer tool. analysis type: Single deal; deal outcome: Lost; loss reason: price; competitor won: your first competitor; deal value: 36000; your solution: our product; sales cycle days: 75. If this tool is unavailable, ask me to open its web page; do not invent its output. In Gemini CLI or Antigravity, use the Helix GTM Suite skills package for related guidance, without claiming to run this connector.
How does the Win/Loss Analyzer tool work?
You do not need to sign in. A web browser is enough, and the answer comes back in a second or two.
- Fill in the form above, or press Fill in an example.
- Press Run Win/Loss Analyzer.
- Read the result on this page, then copy it and edit it before you use it.
It applies fixed rules in the Revenue Enablement code to the inputs above and returns text. It does not call an AI model, does not look anything up, and does not store what you type. The web form and the AI assistant connector run the same tool code, so the same input gives the same answer in both.
Previous: Mutual Action Plan GeneratorNext: Proposal Section Writer
For developers
MCP tool name: win_loss_analyzer. REST: POST https://revenue-enablement.gtmhelix.com/api/tools/win_loss_analyzer with this JSON body (see How it works):
{
"input": {
"analysis_type": "single_deal",
"deal_outcome": "lost",
"loss_reason": "price",
"competitor_won": "your first competitor",
"deal_value": 36000,
"your_solution": "our product",
"sales_cycle_days": 75
}
}
Choose your app
Run a Helix tool in your browser, then take the result to ChatGPT, Claude or Gemini. Connectors work with supported plans in Claude, ChatGPT, Cursor, VS Code and Windsurf. The Helix GTM Suite skills package supports Claude Code, Gemini CLI, Antigravity, Cursor and VS Code, and is available through skills.sh. Each plugin has its own installation steps, below or on its own page.
Connector setup guides · Skills package setup guide · Find the skills on skills.sh