Win/Loss Analysis
Short answer: Win/loss analysis is the practice of reviewing why bids were won or lost, using buyer debriefs, evaluator feedback and your own bid data, so you bid on better opportunities and write better responses. For RFPs, it works best as a routine: capture the same fields on every bid, ask for a debrief every time (win or lose), and review patterns quarterly rather than reacting to single losses.
In Iris: a win/loss dashboard (beta) tracks deal status synced from Salesforce or HubSpot, or set manually, and Insights (beta) shows which topics show up in wins vs losses.
Who this is for: proposal leads, sales leaders and RevOps teams who want to raise win rates with evidence.
What should you track on every bid?
Consistency matters more than volume. Record these on every RFP, ideally in the CRM:
| Field | Example values | Why it matters |
|---|---|---|
| Outcome | Won, lost, no decision, no-bid | The basis of every rate |
| Bid decision score | Your go/no-go score or Pwin at the time | Tests whether qualification works |
| Relationship before RFP | None, some, strong | Often the biggest driver |
| Competitors | Known bidders, incumbent | Patterns by competitor |
| Deal size and segment | Value band; industry; region | Where you win |
| Price position | Lowest, mid, highest (if known) | Was price the deciding factor? |
| Buyer's stated reason | From the debrief | The buyer's view, in their words |
| Evaluator scores | Per criterion, if shared | Where points were lost |
| Effort | Rough hours, SMEs involved | Cost of the bid |
How do you get a useful debrief?
Ask within days of the award notice, and ask the same questions every time. Public buyers often must offer a debrief; in US federal negotiated procurements, offerors can request one in many cases (FAR 15.505, 15.506).
Debrief question bank:
- How did our response score against each evaluation criterion?
- What were the strongest and weakest parts of our response?
- Where did the winning response score better than ours?
- How did our price compare (if you can share it)?
- Was anything unclear or missing?
- Did anything in our presentation or demo change your view?
- What would make our next response stronger?
Listen and record; don't argue the decision.
How do you run a win/loss review?
A quarterly review template:
WIN/LOSS REVIEW: [Quarter] · Bids reviewed: [n] · Attendees: [roles]
1. Outcomes: won [n], lost [n], no decision [n], no-bid [n]
2. Win rate by: segment · deal size · relationship-before-RFP · competitor
3. Qualification check: did higher go/no-go scores win more often?
4. Top 3 loss reasons (from debriefs, in buyers' words)
5. Top 3 win reasons
6. Content gaps: questions we answered weakly or couldn't answer
7. Actions: owner · due (e.g. new approved answer, change go/no-go threshold)
Worked example (fictional numbers)
A team reviews 20 RFPs from one quarter: 6 won, 11 lost, 3 no decision. Splitting by relationship: of 8 bids where the team had met the buyer before the RFP, it won 5; of 12 cold bids, it won 1. Debriefs on the cold losses mention generic answers twice. Actions: raise the go/no-go threshold for cold RFPs, and have the AE add buyer-specific context to the executive summary on every bid.
The lesson isn't the numbers; it's that one consistent field (relationship before RFP) made the pattern visible.
What are common win/loss mistakes?
| Mistake | Better |
|---|---|
| Only reviewing losses | Wins tell you what to repeat |
| Blaming price by default | Check the debrief; price is often not the deciding factor |
| Inconsistent data | Same fields, every bid |
| Reviewing one bid at a time | Look for patterns across a quarter |
| No actions | Every review ends with owners and dates |
How Iris supports win/loss analysis (beta)
- Win/Loss dashboard (beta): deal status synced daily from Salesforce, by webhook from HubSpot (HubSpot integration is limited beta), or set manually, shown alongside your response projects.
- Insights (beta): clusters your approved Q&A into topics and shows trends, win/loss by topic, deal size and owner, and capability gaps, so you can see which topics show up in wins vs losses.
- Content gaps you can act on: answers Iris couldn't draft from your content are flagged "There is not enough information to answer the question", which points to where your library needs work.
Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.
FAQ
What is win/loss analysis?
A structured review of why you won or lost deals, used to improve qualification, strategy and content.
How do you calculate an RFP win rate?
Wins ÷ (wins + losses) for submitted bids. Track no-decisions and no-bids separately so they don't distort the rate.
How often should we do win/loss analysis?
Capture data on every bid; review patterns quarterly.
Who should run it?
Usually the proposal lead or RevOps, with sales leadership in the review.
See it live
Respond to 50 RFPs a year
without the grind.
Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.
