SearchQuestionnaire & RFP Response

Win-Loss Analysis

Win loss analysis that counts every reason and shows the buyer saying it

Turn every loss into a specific fix, in the buyer's own words.

See one case, screen by screen ↓
demo86sourcesread for 14 lost deals in the sample half-year — bids, debriefs, interviews, call notes and CRM records
demo4of 14closed-lost reasons in the CRM that the buyer's own words contradict, found on the sample data
target100%of losses with the CRM reason checked against the buyer's words
target2daysfrom half-year close to an approved readout
In short

What is Win-Loss Analysis?

Win-Loss Analysis reads your bids, buyer debriefs, interviews, call notes and CRM records to explain why deals were won or lost. Seven agents group the reasons into themes with their deal counts and the buyers' own words, test each theme against CRM data and the deals you won, and check every quote. The VP Sales approves each finding with a reason code and signs before anything is shared.

How to choose AI solutions for back-office and enterprise work →

Updated

The problem

Why nobody can say, with evidence, why the deal was lost

The reason in the CRM is one pick-list word, typed by the seller on the day the deal closed — usually “Price”. The real reasons sit where nobody reads them together: the proposal you submitted, the buyer's debrief (a formal score sheet in the public sector), interview notes, call notes and the CRM's own numbers. Without reading them together, nobody can count how many deals a reason really cost.

So the win-loss readout is built by hand. The product marketer chases interviews, codes notes and writes it up over weeks; it rests on whichever deals got an interview, and no reader can check a quote. Nobody tests “we lost on price” against the deals you won at a higher price — so the fix is often the wrong one, and it rarely gets an owner or a measure.

typical39%average RFP win rate, so most of the evidence a team pays for comes from losses
typical166RFPs a yearanswered by the average proposal team
typical33hoursspent on each RFP response
Where a win-loss readout's working days goestimated
By hand31 days
With the solution1.8 days
  • Gathering bids, debriefs, call notes and CRM records per deal3 → 0.1 d
  • Scheduling and running buyer interviews12 → 0.5 d
  • Coding notes into themes and counting deals10 → 0.1 d
  • Checking quotes and testing themes against CRM data and wins1 → 0.1 d
  • Writing, reviewing and approving the readout5 → 1 d

Estimated split of the six or so weeks a win-loss readout takes by hand, and with the solution.

How it works

How a question becomes signed findings

Seven agents read every bid, debrief and interview, test each theme against CRM data and the deals you won, and check every quote; the VP Sales approves and signs.

What comes in
Evidence in5 sources · bids, debriefs, interviews, notes, CRM
Agents at work
Intake agentreads every source
Interview agentfills thin themes
Then
Theme agentthemes, deal counts
CRM check agentnumbers, loss reasons
Then
Quote checkerverbatim, in context
Challenger agenttested against wins
Readout agentdrafts, fixes
A person decides
VP Salesapprove, edit, reject or hold
What comes out
Signed readout
CRM corrections
Owned fixes
One case, step by step

One question, from “why did we lose?” to a signed readout

Kestrel & Vane's Technology Services business sells KV Assure, licensed per seat, to hospitals and health systems. The first half of FY27 closed with 14 healthcare deals lost, $18.6M of contract value. Here is what happens when the VP Sales asks why, screen by screen, in the working solution.

  1. 01Thursday morning

    The half-year, and what needs her

    Dana Whitcombe · VP Sales, Health Systems

    The H1 analysis finished overnight. Dana's home screen shows the healthcare win rate at 55% — 17 of 31, down from 64% in H2 FY26 — $18.6M of contract value lost across 14 deals, and 4 of 14 CRM loss reasons the buyer contradicts. Needs you lists four items: approve the H1 findings, due 21 Oct; one quote the checker removed; 4 CRM corrections; 4 interview proposals.

    “9 of 14 losses partly on price per seat — mostly shared workstations billed as named seats.”

  2. 02One question

    “Why did we lose healthcare deals in H1?”

    The agents

    She asks in plain words. The theme agent sets the scope — healthcare, KV Assure, April to September 2026, lost: 14 deals, $18.60M. The intake agent reads 14 bids and 11 debriefs, two of them formal public-sector debriefs read as score sheets, then 9 interviews with consent checked on each, 38 call notes and 14 CRM records. Each agent's step shows as it runs, through to her review.

    “Only deals you are allowed to see are read.”

  3. 03The answer

    Each reason a column, headed by its deal count

    Theme agent

    Four themes, every loss under at least one: price per seat, 9 of 14 deals; integration took too long, 5; no reference our size, 4; security review late, 3 — marked Emerging, below the 4-deal minimum. Under each column are the buyers' own words, with the role, the deal, the source and the date. Of 19 quotes, 18 are verified and 1 removed.

    “Your rate per seat was fine. What killed it was paying a full seat for every shared workstation on the floor.” — Director of Clinical Engineering, St. Brennan Health System

  4. 04One click

    Every quote opens the passage it came from

    Dana Whitcombe · VP Sales

    She opens the Northgate University Health quote. It comes from the written post-award debriefing, requested on 4 June within 3 days of the award notice: “Offeror's price score: 22 of 30. The successful offeror's evaluated price was 18% lower over five years.” The passage sits in its context, marked Verbatim match and In context, with the $3.2M deal beside it.

  5. 05Working with the agents

    The agents report, ask, and answer back

    Quote checker and challenger agent

    Under the answer, each agent reports what it did and asks for a decision. The quote checker removed Fairhaven Health's “Honestly, price was what decided it”: the sentence goes on to say the four-month go-live came first. It suggests moving the quote to integration, which would then rest on 6 deals; Dana moves it. She asks whether the seat tier would have saved St. Brennan. The challenger: closer, not certain — about 21% lower, within 3% of the winner, and the 16-week plan was the other reason.

    The quote checker can remove a quote, never rewrite one. A person decides where it belongs.

  6. 06Argued against

    Price holds — but it is the seat count, not the rate

    Challenger agent

    The CRM check agent puts numbers on the price theme: 18–24% above the winner per seat, median 23%, deal by deal — $41 against $33 a seat a month at St. Brennan. The challenger tests it against the 17 wins: we were dearer than the runner-up in 6, and 5 of those 6 offered the shared-device seat tier. Verdict: holds, refined. The fix becomes a seat tier, not a discount.

    “The rate alone does not lose deals; the seat model does.”

  7. 07The CRM check

    Four loss reasons the buyer contradicts

    CRM check agent

    The CRM says Price for 12 of 14 losses; buyers named price in 9. At Penrose Regional, Westbrook Senior Living and Thornbury Medical Alliance the buyer named the integration plan; at Oakmere Cancer Institute it was the security review, not Timing. Dana asks the agent to select the four and sends them. Each now sits with its account owner to confirm.

    “Corrections go to the account owner; nothing is written to the CRM until they confirm.”

  8. 08A thin theme

    Four interviews proposed, none sent without a yes

    Interview agent

    Security review late rests on 3 deals: questionnaires went back after 19, 23 and 26 days against 10-day deadlines. To confirm or drop it, the interview agent proposes security questions for the two pending interviews at Oakmere and Kingsreach, and two wins for contrast — Cedarline Health Network, where security cleared in 6 days, and Bellhaven University Hospital. The questions are drafted; each account owner approves outreach first.

    The interview agent never contacts a buyer without the account owner's approval.

  9. 09Her decision

    Approve, edit, reject or hold — each with a reason code

    Dana Whitcombe · VP Sales

    Review and approve lists each finding with the agents' recommendation. With the open quote question answered, she applies them: price per seat, integration (now 6 of 14) and references approved with A1, Evidence sufficient; security review late held with W1, Await interviews. Any finding can be changed, edited with a reason such as E2, Narrow to a segment, or rejected with one such as R1, Too few deals.

  10. 10Signed and shared

    She signs; each finding becomes an owned fix

    Dana Whitcombe · VP Sales

    She picks the audiences — sales leadership and product and pricing with names shown, the proposal team and enablement with names hidden — confirms she has read the findings and the quotes behind them, and signs. Held and rejected findings are not shared. Each approved finding becomes a fix with an owner and a measure: a shared-device seat tier (Leo Marchetti, 30 Nov), an 8-week integration plan with a named engineer (Hannah Brooks, 13 Nov), a reference bench of three systems over 800 beds (Tomasz Wilk, 15 Dec).

    “Pilot since 1 Sep: 3 won, 1 lost, 2 open — 4 decided, too few to call.”

Who it’s for

Built for everyone who owns a win rate.

The same half-year of lost deals, seen by the four people who act on it — what their quarter looked like, and what it looks like now.

DW
Dana WhitcombeVP Sales, Health Systems · approves and signs the findings
VP Sales
Before
Watches the win rate fall from 64% to 55% with a CRM that says “Price” and a readout still weeks away.
Now
Asks why in plain words, sees each reason's deal count and the buyer saying it, and signs only the findings she stands behind.
LM
Leo MarchettiProduct marketing · runs the win-loss programme
Product marketing manager
Before
Spends about six weeks a quarter chasing interviews and coding notes; by the time the readout is done, the next quarter's deals are already lost.
Now
Starts the analysis on the theme codebook, finds themes counted, quotes checked and tested overnight, and owns the seat-tier fix and its pilot.
HB
Hannah BrooksProposal manager · 11 live bids, owns the bid templates
Proposal manager
Before
Hears that the integration plan loses deals, but not which paragraph.
Now
Sees section 6.2 of the bid — 16 weeks — beside the winners' 6–8, and owns the 8-week plan in the bid template, due 13 Nov.
SL
Sofia LindgrenAccount owner · approves outreach and CRM corrections
Account owner
Before
The loss reason she typed on the day a deal closed is the one the business reports on, and nobody checks it.
Now
Confirms each correction to her own records, and approves or declines outreach to her buyers before anyone is contacted.
Built on the engine

7 agents. Each with one job, and hard limits.

Seven agents read every bid, debrief and interview, test each theme against CRM data and the deals you won, and check every quote; the VP Sales approves and signs.

Intake agent

Gathers every source for each closed deal — the bid, the debrief, interviews, call notes and the CRM record — reads it, links it to the deal and checks consent. A password-protected file is not dropped: it stops and drafts a request for a person to send.

  • Never stores an interview without recorded consent
  • Never reads a deal the person asking may not see
Interview agent

Sees which themes rest on too few deals and proposes exactly whom to interview, wins included for contrast; drafts the questions and runs async AI-led interviews with follow-up questions once the buyer consents.

  • Never contacts a buyer without the account owner's approval
  • Never mentions another bidder's price
Theme agent

Reads all the sources, groups the reasons into themes from your codebook, counts the deals behind each and picks the buyers' quotes.

  • A finding needs 4 or more deals; fewer is Emerging
  • Never states a reason without a passage
CRM check agent

Tests each theme against the numbers — price per seat, seat counts, plan weeks, reference sizes, questionnaire dates — and compares every closed-lost reason with the buyer's words, proposing corrections.

  • Never writes to the CRM
  • Every correction needs the account owner
Quote checker

Confirms every quote is word for word, in context and allowed for each audience. A quote out of context is removed with the full passage shown.

  • Can remove a quote, never rewrite one
  • A person decides where a removed quote belongs
Challenger agent

Argues against every theme: looks for the counter-case in the deals you won and in the CRM data, and marks each theme holds, refined or weak.

  • Independent of the theme agent
  • Cannot delete a theme
Readout agent

Drafts the readout for each audience, proposes a fix for each finding with an owner and a measure, and tracks results with the number of deals they rest on.

  • Never shares before the VP Sales signs
  • Never claims a result on fewer than 10 decided deals
VP Sales

Approves each finding with a reason code and signs before it is shared. The agents propose; a named person decides.

Ask in plain words

Ask why, in plain words

Ask about any theme, deal, quote or competitor — or tell the agents what to do. Every answer carries its sources and can open the screen it is about.

Summarise H1 in three sentences for the CRO

Healthcare win rate fell from 64% to 55% in H1; we lost 14 deals worth $18.6M. The biggest reason is how we count seats, not our rate: 9 losses, 7 of them over shared workstations. The fixes are a shared-device tier, an 8-week integration plan and a larger reference bench — the findings need approval before they go out.

Is the price problem getting worse?

Yes. Price-per-seat losses went from 2 of 6 losses in Q3 FY26 to 5 of 8 in Q2 FY27, while the win rate fell every quarter.

Would the seat tier have saved St. Brennan?

Closer, not certain. St. Brennan has about 600 shared workstations; billing them as devices at the tier rate takes the bid about 21% lower, within 3% of the winner. Integration was the other reason there: our plan said 16 weeks.

Which losses have no interview yet?

Five. Ashgrove, Calloway and Larkspur declined; Oakmere and Kingsreach are pending. Three of the five sit under price per seat, which already rests on 6 interviews and debriefs, so the gap that matters is security review late.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

TodayThe win rate, contract value lost, the CRM reasons buyers contradict, what needs the VP Sales and what the agents found overnight.
Agents at workA plain-words question, its scope, and each agent's step as it runs — 86 sources read, by type.
Themes and the buyers' wordsEach reason as a column with its deal count, the challenger's verdict, a CRM figure and verified buyer quotes; a removed quote stays visible with the reason.
Working with the agentsEach agent reports and asks for a decision — the removed quote, here moved by the VP Sales — and her follow-up question is answered with its sources.
The passage behind a quoteA formal post-award debriefing with the quoted passage in context, its checks, the deal, and questions to ask about the source.
One theme, testedThe deals behind price per seat, our rate against the winner's, the challenger's counter-case from the wins, and every quote.
CRM checkThe reason the seller entered beside what the buyer said, the four contradictions, and corrections waiting for each account owner.
InterviewsInterviews the agent proposes for a thin theme, approved in bulk by account owners, and every requested interview with its status and format.
Review and approveEach finding with the agents' recommendation, its evidence and a reason code; the open question answered before signing.
Sign and shareAudiences with names shown or hidden, the attestation, and the signature recorded with the reason codes.
The readoutThe signed readout as all of sales sees it: findings with deal counts, buyer quotes with names hidden, and the fix for each.
FixesEvery approved finding as a fix with an owner, a due date and a measure, and results reported with the deals they rest on.
Your rulesMinimum deals for a finding, deals before a result is reported, quote verification and the rules every analysis follows — changes go for approval.
Governance

Built for findings you can defend: cited, checked, signed.

Every count and quote cites its passageEach theme count, buyer quote, CRM figure and agent answer links to the passage it came from. A seller's call note can support a theme but is never shown as the buyer's words.
Quotes checked, never rewrittenEvery quote must match its passage word for word and be in context. The quote checker can remove one, never rewrite it, and a removed quote needs a person's decision before the readout is signed.
Every theme argued againstAn independent challenger tests each theme against the deals you won and the CRM data. A finding needs 4 or more deals, and a fix result is reported only from 10 decided deals.
Owners say yes before anything changesAgents never contact a buyer, write to the CRM or share a readout. Account owners approve outreach and confirm CRM corrections; the VP Sales approves the threshold and codebook changes.
Signed, with names hidden where buyers askedEach finding is approved, edited, rejected or held with a reason code, and the VP Sales signs. Buyer anonymity holds per audience, and a public debrief keeps only what the buyer disclosed about you.
Every step on the audit trailEvery action by a person or an agent is recorded with what it relied on. Nothing can be edited or deleted, entries are kept for 7 years, and internal audit can export the evidence for any readout.
Configuration

Your thresholds, your consent rules

How themes are judged, who sees buyer names and the clocks the work runs to are settings. Threshold changes are proposed, approved and apply to the next analysis.

SettingDefaultChoose from
Minimum deals for a finding4Any number; below it a theme shows as Emerging
Minimum decided deals before a fix result is reported10Any number; fewer is reported as too few to call
Quotes verified before sharing100%Fixed
Default when a buyer gives no choiceRole onlyRole only · Not quoted
Keep recordings for24 months24 months · 12 months
Buyer names shown toSales leadership, Product and pricingSales leadership, Product and pricing · Sales leadership only
Request a public debrief within3 days of the award noticeSet in days; the default follows FAR 15.506
Approve a half-year readout within15 business days of closeSet in business days, with an approver reminder after 2 days
Connections

Works with the systems your deals already run on

CRMopportunities, closed-lost reasons and call notes; a reason is written only after the owner confirms
Proposal librarysubmitted bids and pricing, final versions
Debrief inbox and buyer portalsdebrief calls, formal evaluation debriefs and assessment summaries
Interview recorderscheduling, recording and transcription, with consent
Public noticesaward notices and debrief letters
E-signaturereadout signatures
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
+5pts
win rate in the segment analysed, within two quarters
H1 healthcare55%
Target60%
target
100%
of losses with the CRM reason checked against the buyer's words
14 of 14 checked
4 were wrong
target
2days
from half-year close to an approved readout
By hand≈ 6 weeks
With agents2 days

“demo” = seen in the working solution, on its sample data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures (a 2026 RFP benchmark survey of 1,500+ teams, run by an RFP software vendor — 39% average win rate, 166 RFPs a year, 33 hours each; FAR 15.506 on post-award debriefings). People, companies, competitors and deals named on this page, including Kestrel & Vane Group, are fictional — characters and sample data in the working solution.

Questions

What sales and proposal leaders ask us.

What is Win-Loss Analysis?

Win-Loss Analysis reads your bids, buyer debriefs, interviews, call notes and CRM records to explain why deals were won or lost. Seven agents group the reasons into themes with their deal counts and the buyers' own words, test each theme against CRM data and the deals you won, and check every quote. The VP Sales approves each finding with a reason code and signs before anything is shared.

How is it different from a win loss analysis built on interviews alone?

It reads every source for every deal in scope, not only the deals that got an interview, so each theme shows how many deals it rests on. A challenger agent argues against each theme using the deals you won — in the sample, “price” became “shared workstations billed as named seats”, which changes the fix from a discount to a seat tier.

Does it check the closed-lost reasons in our CRM?

Yes. The CRM check agent compares every closed-lost reason with what the buyer said and cites both. In the sample half-year, 4 of 14 reasons were contradicted. Corrections go to the account owner, and nothing is written to the CRM until they confirm.

Can it read public-sector debriefs and evaluation scores?

Yes. Formal written debriefings and assessment summaries are read as score sheets, so “we lost on price” is backed by the evaluator's own marks — in the sample, 22 of 30 on price, with the winner's evaluated price 18% lower over five years. Only what the buyer disclosed about you is kept, and a clock prompts the debrief request within 3 days of an award notice.

Does it interview buyers?

Where a theme rests on too few deals, the interview agent proposes whom to interview, drafts the questions and can run an async AI-led interview with follow-up questions once the buyer consents; human-led interviews are read the same way. No buyer is contacted until the account owner approves, and buyers choose whether they are quoted by name, by role only or not at all.

Can a quote be taken out of context?

The quote checker matches every quote word for word to its passage and reads it in context. A quote out of context is removed, never rewritten, with the full passage shown, and a person decides whether to move it, keep it removed or restore it.

Do people stay in control of what is shared?

Yes. Agents never contact a buyer, write to the CRM, rewrite a quote or share a readout. The VP Sales approves, edits, rejects or holds each finding with a reason code and signs; buyer names are hidden for the audiences you choose; and every step is on an audit trail that cannot be edited.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your loss-reason pick-list, a sample of past bids and debriefs, your CRM fields and consent rules — and it goes live once every quality gate has passed. We will walk you through it on your own closed deals first.

See it on
your lost deals.

We'll run Win-Loss Analysis on a sample of your own closed deals, bids and debriefs.