Short answer: Win/loss analysis in construction sales usually examines deals lost at proposal or tender stage. That is the wrong sample. The projects that reveal the most are the ones where your name never came up at all — where a competitor was specified during design and you never entered the process. Those projects almost never get tracked, because they either never reached the CRM or were dropped so early that nobody remembers them.
The sample problem
A standard win/loss review takes the deals in your CRM with a closed-lost status and looks for patterns. Price, timing, competitor, product fit.
The problem is what is in that sample. If your team starts tracking a project when a proposal goes out, then every project you lost *before* that point is absent — and in construction, that is where most losses happen. The specification was written around a competitor's product six months earlier. You never quoted, so there is no lost deal to analyse.
The result is a win/loss picture built entirely from the subset of projects you were competitive in. It will tell you about pricing and product details. It cannot tell you about the losses that mattered.
A reasonable estimate is that most teams have a clear view of perhaps 20% of their actual win/loss reality. The rest is inference.
The three categories of loss, and which one gets examined
Loss type | When it happens | Usually tracked? |
|---|---|---|
Never entered the process | Design phase; competitor specified | No |
Entered too late | Tender stage; specification fixed | Partly |
Lost on price or terms | Bid evaluation | Yes |
Specified, then substituted | Procurement, after award | Rarely |
The bottom row deserves particular attention. Manufacturers routinely win a specification and lose the revenue when a contractor substitutes at procurement — and because the order simply never arrives, there is often no record that the specification was won in the first place.
Two of the four categories are essentially invisible in a typical setup. Both are the ones you could most readily fix.
What the invisible categories would tell you
If you could see them, three patterns emerge that price analysis never reveals.
Where you are consistently too late. Not on average — by segment. You may be reaching hospital projects at design stage and industrial projects only at tender. That is a coverage problem in one segment, not a product problem overall.
Which segments you are quietly losing. A segment where you never appear at design stage will show a declining share over years, with no single loss to point at. It looks like market softness.
Where your value proposition actually lands. The projects where you were specified without a fight tell you where your technical argument is strongest — which is a portfolio and messaging input, not just a sales one.
Why this is a tracking problem, not an analysis problem
The root cause is simple. If tracking starts at proposal, everything before is invisible, and there is no data to learn from. No amount of analytical rigour recovers information that was never captured.
Exclusive project sales insights, directly to your inbox
Subscribe to our weekly newsletter.
Which means the fix is upstream: capture project activity from the earliest signal, whether or not the project ever becomes a quote.
That has a second-order benefit worth noting. Disqualification reasons become data. A rep who rejects a project because the specification is already locked to a competitor is recording a market fact. Aggregated over a year, those rejections describe exactly where you are structurally late — and that is a better strategic input than any lost-deal review.
How Building Radar makes the invisible sample visible
Building Radar captures project activity from the first signal, long before a proposal is anywhere near the table.
Projects are discovered across more than 50 countries, including at planning and design stage, and recorded whether or not anyone eventually quotes. Each carries a relevance score against your portfolio, because Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets. Disqualification reasons are captured as part of the workflow rather than as an extra step.
Project stage changes are then monitored continuously and pushed into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C — which is what makes the fourth category visible. Jeane flags when a specified project enters procurement, so substitution becomes something you can intervene in rather than something you discover from a missing order.
Over time this produces the picture that price-based win/loss analysis cannot: where you are consistently too late, which segments you are losing without noticing, and where your value proposition genuinely lands. None of it requires anyone to fill in a spreadsheet.
What to do this quarter
You do not need a platform to start. Three steps:
Reconstruct twenty projects you never quoted on. Ask two reps to name relevant projects in their region from last year where your company never entered the process. Establish why for each.
Add a disqualification reason field, with five options. Below minimum volume, outside influence window, no route to decision-maker, competitor framework, wrong region. Require it on rejection.
Record specification as a milestone, separate from the order. Without this, category four stays invisible permanently.
Those three make the next win/loss review considerably more useful than the last one.
Frequently asked questions
What is win/loss analysis in construction sales? A structured review of why projects were won or lost. In construction it is frequently misleading, because the sample only includes projects that reached proposal stage.
Why are early-stage losses not tracked? Because most teams create a CRM record at proposal stage. Projects lost during design were never recorded, so there is nothing to analyse.
What is the most common invisible loss? A competitor being specified during the design phase, before you entered the process at all. The second most common is substitution at procurement after you were specified.
How do you track losses you never knew about? By capturing project activity from the first signal rather than from the proposal, and by recording disqualification reasons systematically.
What should a good win/loss review reveal? Where you are consistently too late by segment, which segments you are losing without a visible cause, and where your value proposition wins without a fight.
Ready to see your real win/loss picture?
Find out how Building Radar's revenue engineering solution records project activity from the earliest signal — including the projects you never quoted.
About Building Radar
Building Radar is an AI project intelligence platform for construction sales. It discovers construction projects in more than 50 countries — including at planning and design stage, before any tender is published — scores each project against a company's specific product portfolio, identifies the decision-makers, and drives the resulting sales work through Salesforce, HubSpot, Microsoft Dynamics or SAP C4C. Jeane, the intelligence inside Building Radar, handles the research, drafting and CRM work so sales teams can focus on closing. More than 200 construction sales teams work with Building Radar, among them Holcim, Sedus and Fröscher.
Schedule an initial consultation