New bookThe Bid Director: Win the Deals That Matter. Read a free chapter
Win strategy · Whitepaper

Lessons From the Losses: How to Run a Loss Review That Wins the Next Bid

A lost bid is the most expensive research you will ever buy. Most teams file the letter and move on. Here is how to hear what the buyer saw, trace the loss to where it was really decided, and fix it before the next pursuit.

A large SAP or ERP pursuit can absorb months of senior time. When it is lost, most teams get back a letter, a score and a few quiet days. Then the next RFP lands, and the lesson goes unlearned.

The usual post-mortem doesn’t help much. It is run by the people who wrote the bid, about the bid they wrote, before anyone has asked the buyer. So it explains the loss in the team’s own terms (price, the incumbent, politics) and changes nothing. Win-loss researchers at Corporate Visions report that the reason sellers give for a lost deal differs from the buyer’s reason up to 70% of the time, and that 53% of buyers in lost deals say the losing vendor could have won by doing something differently.

Most losses are known before they happen

Our new book, The Bid Director: Win the Deals That Matter, tells the story of Kestrel, a €200 million outsourcing re-compete that ran for most of a year. Before bidding, the team took it through a full qualification session. By the end of the day the wall showed friends high up in the client and very few further down, incumbents who had been there for years and employed some of the client’s own former staff, and some history at the account that nobody wanted to talk about. In the end the client kept its incumbents. All of them.

None of it was a surprise. As the book puts it, “every red flag on that wall deserved a name next to it and a decision: fix it, price it, or accept it, out loud.” A loss review’s job is not to discover the reasons. It is to find out why known reasons weren’t acted on.

Five steps, from the letter to the next bid

  1. Within 48 hours: the hot wash. Thirty minutes with the core team to capture facts, not verdicts: what we knew, when we knew it, what we decided, and every assumption the bid relied on.
  2. In the first week: ask for the debrief, in writing. For a private buyer, ask the sponsor for thirty minutes. Ask for the conversation, not a justification.
  3. Within three weeks: listen, don’t defend. Send one senior person and one note-taker. A buyer’s misunderstanding of your bid is itself a finding about your bid.
  4. Within four weeks: trace the loss. With a chair from outside the pursuit, map the evidence onto the eight battles every ERP bid has to win (below).
  5. Before the next bid: three actions, three owners. Each with a date and the next pursuit it will be tested on. Then thank the buyer: a good debrief is the start of the next pursuit with that client.

Which battle did we lose?

BattleThe questionWhat it sounds like in a debrief
1. ShapeDid we help shape the requirement before the RFP?“The winner understood what we were really trying to do.”
2. QualifyShould we have bid, and did we act on the red flags?“It was always going to be hard to move away from our current supplier.”
3. DecodeDid we know how we’d be scored, and by whom?“Your technical answer was strong, but the value case was less clear.”
4. AssembleWere we one team across partners?“It felt like several companies presenting together.”
5. StoryWould our story survive being read aloud?“We weren’t sure what made you different.”
6. Draw the lineCould our price and scope be read only one way?“We couldn’t compare your price with the others.”
7. Win the roomWho answered the hardest question, and how?“The orals didn’t match the written proposal.”
8. LandDid they believe we’d deliver what we sold?“We weren’t confident about the transition.”

Five debrief questions worth asking

  • What problem were you most trying to solve when you went to market?
  • At what point did the winner pull ahead?
  • In one sentence, what did you understand we were offering?
  • Was our price unclear, high, or high for what you believed you would get?
  • If we could have changed one thing, what should it have been?

The whitepaper has all twelve, with a note on what each one tests.

Public tenders: your right to reasons

Above the EU thresholds, a debrief isn’t a favour. In Ireland the award notice that starts the standstill period must include a summary of the reasons your tender was rejected, and the standstill runs for at least 14 calendar days when the notice is sent electronically (S.I. No. 130 of 2010). On written request, the authority must tell you within 15 days why you lost and, if your tender was admissible, the characteristics and relative advantages of the winning tender and the winner’s name (Directive 2014/24/EU, Article 55, Regulation 55 of S.I. No. 284 of 2016). The Irish High Court has held that those reasons must be specific to your tender, not generic. Ask early: a debrief doesn’t pause the standstill period or the time limits for a challenge. This is general information, not legal advice.

Free whitepaper · PDF

Lessons From the Losses

10 pages: the five-step method, the twelve-question debrief bank, the one-page loss review template and the public-tender rules. No sign-up, no email required.

Download the whitepaper

Just lost one that matters? An outside chair is the difference between a review that protects the team and one that changes the next bid. We can run the hot wash and root-cause session and prepare your debrief, scoped as a fixed-fee project. Book a free discovery call or email sales@dealcraftadvisory.ie.

Planning an ERP procurement, or a live pursuit?

A short conversation is enough to work out whether the gap is strategy, staffing or story — and what would fix it before submission.

Book a free discovery call