Win/Loss Analyzer
win_loss_analyzerAnalyze why a deal was won or lost and what to change, turning deal details or patterns into buyer-reason insights, review questions, and sector notes.
Instructions
Helps you decide why you won or lost and what to change. You give the details of one deal, a competitor pattern or a set of deals. You get a short write up that names the outcome, the stated reason in the buyer's words, what the reason points to and what the buyer weighed, then questions for the review call and sector notes. It adds no figure or reason you did not give, and says what a missing outcome or reason would add. Read-only for business data. It needs no sign-in and stores no inputs or outputs. Hosted usage metadata is recorded. Missing required fields or invalid values return an error naming what to supply or correct. Use this instead of deal_strategy_coach when you need to learn from completed outcomes and stated buyer reasons.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"analysis_type": "<analysis_type>"
},
"name": "win_loss_analyzer"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| deal_value | No | Deal value. Format is a JSON number. For example, 12. | |
| loss_reason | No | Stated loss reason (for lost deals). Format is text. For example, "two deals paused after budget review". | |
| your_sector | No | Optional: your company's own industry (not your customers'). When given, it decides the sector notes; when left out, the tool reads it from your words and stays neutral if they are unclear. Format is text using one of the listed labels. For example, "logistics_tech". | |
| deal_details | No | Deal details, can be rough notes, CRM export, or structured data. Format is text. For example, "renewal was paused because budget approval was delayed". | |
| deal_outcome | No | Deal outcome for single deal analysis. Format is text using one of the listed labels. For example, "won". | |
| analysis_type | Yes | Type of analysis. Format is text using one of the listed labels. For example, "single_deal". | |
| your_solution | No | What you were selling. Format is text. For example, "invoice review service". | |
| competitor_won | No | Competitor who won (if applicable). Format is text. For example, "the current manual review process". | |
| multiple_deals | No | For portfolio analysis: summary of multiple deals. Format is text. For example, "renewal was paused because budget approval was delayed". | |
| sales_cycle_days | No | Length of sales cycle. Format is a JSON number. For example, 12. | |
| stakeholders_involved | No | Key stakeholders and their positions. Format is text. For example, "procurement lead and security reviewer". |