Skip to content

What is win/loss analysis?

Win/loss analysis is a bid team's review of finished bids, won and lost, to learn why each was decided as it was and to change the next bid. The bid manager runs it at closeout from the buyer's feedback, the team's own review and the scores, then reads the pattern across bids.

Win/loss analysis works by recording each finished bid's result with the reasons behind it, then comparing those records over time to find patterns. In bid and tender work, those patterns feed the next bid/no-bid decision and the answers kept in the content library. In sales and product marketing, the same name covers interviews with buyers after any closed deal, which is a separate exercise from reviewing scored bids.

How win/loss analysis works on a bid team

Win/loss analysis, also written win-loss analysis, rests on one record per finished bid. That record holds the result, the score against each award criterion, the price and how it compared, the winner where the buyer names one, and the reasons for the outcome. Read across bids, the records show win rate by buyer, sector or bid type, the criteria where marks keep being lost, and the reasons behind each decision not to bid.

The record only works if every bid is logged the same way. The Association of Proposal Management Professionals (APMP) calls for objective measures of capture success in its certification syllabus. Consistent fields are what make one bid comparable with the next. A reason recorded as "price" on one bid and "too expensive" on another splits a single pattern in two.

The pattern then tests the bid/no-bid criteria. APMP's Winning Business Ecosystem frames that decision around ROI, win probability and risk. The win/loss record holds the past results behind each of those judgements. It shows how bids like the one in front of the team actually fared, and on which criteria they gained or lost marks.

An illustrative case shows the mechanism. A team reviewing several lost bids for one buyer type finds the same comment in each piece of feedback: the transition plan was generic and cited no comparable reference. Its win rate with that buyer type had already dropped, but the count alone never said why.

The team acts on two fronts. It rewrites the library answer on transition around its own method, milestones and named references, so the next bid starts from the stronger version. It also adds a question to its bid/no-bid test, asking whether the team can cite a comparable transition reference for this buyer. A tender that fails that question goes to the head of bids before any writing starts.

Where win/loss analysis sits in the bid process

Win/loss analysis comes at closeout, once the result and the buyer's feedback are in. In APMP's lifecycle, the debrief belongs to the contract award step, and win/loss analysis follows at closeout for awarded and unsuccessful bids alike.

The order matters because the debrief supplies one input. The analysis turns that input into a recorded reason, set beside the scores and the team's own view of the bid. A debrief heard and never recorded leaves nothing for the next bid to draw on.

From closeout, the recorded reasons travel forward in two directions. They go into the next bid/no-bid decision, where a weak pattern on a buyer type or a criterion becomes a question at the gate. They also go into library upkeep, where answers that kept losing marks are rewritten before anyone reuses them.

This makes closeout the step that feeds the next pursuit in the wider bid management cycle.

Where the reasons for a result come from

Reasons come from the buyer's feedback after the award, the team's own review of the bid and the outcome record. What a buyer must provide depends on the rules its procurement follows.

In the UK, for public procurements begun since 24 February 2025, a buyer running a competitive tendering procedure must give each supplier whose bid it assessed an assessment summary explaining why the bid won or lost, before it publishes the contract award notice (UK government guidance). Elsewhere, a debriefing meeting cannot be assumed. Across the countries surveyed in the OECD's review of its Recommendation on Public Procurement, only 18% regularly provide debriefings to unsuccessful bidders. On private RFPs, feedback depends entirely on the buyer.

Where a debrief does happen, its points can be turned into recorded reasons with a debrief analysis prompt.

The team's own review adds what the buyer never says. Writers, reviewers and the account lead record their reading of the bid: which answers were weak, whether the solution fitted, and what was known about the buyer before submission.

The outcome record holds the hard facts: scores against each criterion, the price position and the winner where known. Scores show where marks were lost even when nobody explains them. Where the buyer says little, the team's review and the outcome record carry the reasons on their own.

How it differs from the debrief, lessons learned and win rate

Three terms sit close to win/loss analysis.

The debrief

A debrief is one buyer's account of one bid, given at the award. It feeds win/loss analysis but is not the analysis itself. It explains a single result from the buyer's side, and only the record across bids shows whether that reason recurs or was a one-off.

The lessons-learned review

APMP lists a documented lessons-learned exercise as its own closeout item, next to win/loss analysis. Its certification syllabus has the lessons-learned review determine how the process, strategies and talent can be improved. That review looks inward, at how the team ran the bid, covering the plan, the reviews, the hand-offs and who was staffed on it. Win/loss analysis looks outward, at why the buyer decided as it did.

The win rate

The win rate is one output of win/loss analysis: a count without reasons. It shows that results with a buyer type have fallen. It never shows which criterion lost the marks, or whether price decided the award. Win/loss analysis supplies the reasons behind the number, and the number shows where to look first.

Win/loss analysis in SEQUESTO

In SEQUESTO's agentic operating system (aOS), the team works from standard dashboards for win rate, by number of deals and by contract value. They are built on the team's own bid fields, so whatever the team records for each bid, such as buyer type or sector, can shape what the charts show. Every chart clicks through to the bids behind it, and the bid manager can open the bids behind a figure rather than read the number alone.

When a new tender arrives, Agent Force, the specialist agents, extracts its evaluation criteria and requirements. James, SEQUESTO's AI bid agent, reads the whole tender pack and checks it against the company's references, certificates and past bids. He then writes the bid/no-bid brief following the team's own workflow. The brief sets out which requirements the company clearly meets, where it is weak, and the risks.

The bid manager takes the bid/no-bid decision and records it on the bid, where the next review can read it. Answers the team approves during a bid can go back into the Knowledge Hub for the next bid.

Frequently Asked Questions

Further Reading

Put the terminology to work

Now you know the language, see how SEQUESTO automates the process. Book a demo and see how SEQUESTO runs your bids, first-hand.