Short answer: Five things stay consistently invisible in construction project sales: how much of your market you never see, at which project stage you actually make first contact, which projects you lost before quoting, whether your specifications survive procurement, and how much of your team's week goes to work that produces nothing. Each is measurable. None appears in a standard pipeline report, which is why the same five recur across manufacturers.
1. How much of your market you never see
The question: How many projects in your target market required your product category last year, and how many did your team know about?
Most manufacturers cannot answer the first half. That is the blind spot — not a low number, but an unknown one.
It stays hidden because a CRM only contains what someone put there. If nobody knew about a hospital project in Lyon, there is no record of its absence. No report will ever reveal it.
How to measure it: Take one market you know well. List every relevant project your team was aware of last year. Compare against an external feed filtered to the same countries, building types and size range. The delta is your invisible market, and for most manufacturers it is uncomfortably large.
2. At which project stage you actually make first contact
The question: In your last twenty closed deals, what was the project phase when someone first made contact?
Teams have an intuition about this and it is usually optimistic. The intuition comes from the deals they remember, which skew toward the ones that went well — which skew toward early contact.
It matters because this single variable drives most of the outcome. A manufacturer arriving at tender stage is competing on price against products already declared equivalent. One that was present during design is competing on fit.
How to measure it: Reconstruct twenty deals from memory and email. Record the phase at first contact. If most cluster at tender, you have found your largest available improvement.
3. Which projects you lost before quoting
The question: How many relevant projects last year did your company never enter at all?
This is the largest category of loss and the one almost never examined. A standard win/loss review looks at deals with a closed-lost status — which requires a CRM record, which requires a proposal. Projects where a competitor was specified during design produce no lost deal to analyse.
Realistically, most teams see perhaps a fifth of their actual win/loss picture.
How to measure it: Ask two reps to name relevant projects in their region from last year where your company never entered the process, and establish why for each. Then add a disqualification reason field with five options and require it on rejection. Within a quarter the pattern is visible.
4. Whether your specifications survive procurement
The question: Of the projects where your product was specified, what share converted to an order?
Manufacturers routinely win a specification and lose the revenue when a contractor substitutes at procurement. Because the order simply never arrives, there is often no record that the specification was won in the first place.
How to measure it: Record specification as an explicit CRM milestone, separate from and earlier than the order. Then monitor those projects through award. If the conversion is low, your problem is contractor relationships at procurement, not specification work — and those need entirely different responses.
5. How much of the week produces nothing
The question: How many hours per rep per week go to project search, tender review, contact research, prioritisation, duplicate checking and CRM updates?
Estimates here are unreliable in both directions. Sampled properly it typically lands around 3.5 hours per working day — roughly €23,000 per rep per year at a fully loaded rate of €30 per hour.
How to measure it: Have three reps log their week in half-hour blocks for two weeks, categorised into specifier contact, travel, research and list building, CRM and admin, internal meetings.
Why these five stay hidden together
They share one cause: the pipeline starts too late. When records are created at proposal stage, everything before is invisible — coverage, timing, early losses, specification milestones, and the research effort that preceded all of it.
That also means they can be fixed together. Moving the tracking start point earlier makes four of the five measurable in a single change.
What closes them
Building Radar captures project activity from the first signal rather than from the proposal. Projects are discovered across more than 50 countries, including at planning and design stage, which makes coverage a number you can read rather than a gap you cannot see. Each is scored against your specific 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, which addresses the third blind spot without an extra process. Project stage changes are monitored continuously and pushed into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C, so specification-stage records stay connected to what happens next — and Jeane flags when a specified project enters procurement, which is the fourth.
The fifth changes through automation rather than measurement: teams report roughly 80% less manual project sales work.
Where to start
Pick the second one. Average project stage at first contact takes an afternoon to establish, requires no tooling, and it is the variable with the largest effect on margin. Everything else follows more easily once that number exists.
Frequently asked questions
What is the biggest blind spot in construction sales? Market coverage — how many relevant projects exist versus how many the team knew about. It stays hidden because a CRM cannot report the absence of something nobody recorded.
Why does win/loss analysis miss most losses in construction? Because it examines deals that reached proposal stage. Projects lost during design, before any quote, produce no record to analyse.
How do you track whether a specification survives procurement? Record specification as an explicit milestone separate from the order, then monitor those projects through contract award and intervene with the winning contractor before purchasing decisions are made.
How much time do construction sales reps lose to non-revenue work? Typically around 3.5 hours per working day when sampled rather than estimated, across project search, tender review, contact research, prioritisation and CRM updates.
Ready to make the five measurable?
Find out how Building Radar's revenue engineering solution records project activity from the earliest signal.
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.
Schedule an initial consultation