← Back to blog
Sales

9 KPIs for Construction Sales Performance

25 Aug 2026
9 KPIs for Construction Sales Performance

Short answer: Revenue tells you what happened eighteen months ago. The nine KPIs that explain and predict construction sales performance are: relevant projects identified, average project stage at first contact, time from identification to decision-maker contact, disqualification rate, specification rate, sole-versus-equivalent split, specification-to-order conversion, win rate from project found to closed, and weekly active tool usage. Together they tell you which part of the system is limiting output.

Why revenue is a lagging indicator here

In building product sales, the decision that produces revenue happens six to twenty-four months before the invoice, is made by a party you do not invoice, and is recorded nowhere unless you record it deliberately.

So a quarter of disappointing revenue tells you that something went wrong during a period you can no longer influence, and gives you no information about which thing. Every KPI below exists to make one specific part of that period visible.

The nine

1. Relevant projects identified per quarter

Diagnoses: market coverage. Why: you cannot pursue what you never saw. Most manufacturers cannot state this number, which is itself the finding. Watch for: coverage that tracks rep headcount rather than market size — a sign that discovery depends on personal networks.

2. Average project stage at first contact

Diagnoses: timing, and therefore margin. Why: the single strongest predictor of win rate. A team entering at tender is competing on price by definition. Target: moving earlier quarter over quarter. Building Radar's own illustration puts the win-probability difference between early planning and tender engagement at up to fourfold.

3. Time from project identification to decision-maker contact

Diagnoses: operational speed. Why: the most controllable metric in the set. Days, not months. Deteriorating numbers usually mean reps are drowning in research rather than losing motivation.

4. Disqualification rate, with reasons

Diagnoses: qualification discipline and scoring calibration. Why: a rep rejecting 60% of assigned projects in week one is working correctly. A rep rejecting 5% is not qualifying at all. The real value is the reasons. If "specification already locked" dominates, your problem is upstream timing, not tender qualification.

5. Specification rate

Diagnoses: effectiveness of the specification motion. Formula: projects where your product is named or approved ÷ projects actively pursued. Why: the earliest reliable signal of future revenue, available a year before the order. Segment it by project stage at first contact — that comparison is what proves whether early engagement is paying.

6. Sole versus "or equal" split

Diagnoses: quality, not just quantity, of specifications won. Why: sole specification converts to order at a far higher rate. A rising specification rate composed entirely of "or equal" entries is a weaker result than it looks.

7. Specification-to-order conversion

Diagnoses: substitution risk at procurement. Why: manufacturers routinely win specifications and lose the revenue without recording why. If this number is low, your problem is contractor relationships at award, not specification work.

8. Win rate from project found to closed

Diagnoses: the whole system, end to end. Why: the only number that captures discovery, qualification, specification and procurement defence together. Fröscher measures a 4.1x improvement on this metric. Caveat: it moves slowly, on the sales cycle's own schedule. Use it to validate direction, not to manage weekly.

9. Weekly active users as a share of licences

Diagnoses: whether any of the above is actually happening. Why: the metric nobody puts in a KPI deck and the one that most often explains a failed initiative. A tool used by three of twenty reps produces roughly none of the modelled return. Measure at six months, not at onboarding.

Reading them together

Individually these are interesting. Together they diagnose:

Symptom

Likely cause

Low win rate, late first contact

Discovery problem — you are not seeing projects early

Low win rate, early first contact

Product, documentation or competitive problem

High specification rate, low order conversion

Substitution at procurement

Low disqualification rate

No qualification discipline; capacity spread thin

Good metrics, low tool usage

The numbers reflect two power users, not the team

Coverage flat despite headcount growth

Discovery bound by personal networks

That table is the actual point of the exercise. A disappointing quarter should produce a specific diagnosis rather than a generalised instruction to work harder.

Making them measurable

Most manufacturers cannot report five of these nine, because the underlying data does not exist. Three prerequisites:

The project is the CRM object, not the company. Specification happens at project level, and company-centric records duplicate the same project across firms.

Specification is an explicit pipeline stage, recorded when it happens, separate from the order.

Project stage updates automatically. A stage set at record creation and never refreshed makes metrics 2, 5 and 7 meaningless. Building Radar monitors project stage changes and pushes them into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C for this reason.

Where to start

Do not instrument all nine at once. Start with three: relevant projects identified, average project stage at first contact, and specification rate. Those three cover coverage, timing and effectiveness — the parts of the system where most manufacturers are actually losing.

Add the rest once the first three have a baseline worth comparing against.

Frequently asked questions

What is the most important construction sales KPI? Average project stage at first contact, because it determines whether you are competing on fit or on price, and it drives most of the others.

How is specification rate calculated? Projects where your product is named or approved, divided by projects actively pursued, expressed as a percentage. Count only projects where a rep took a substantive step.

Why measure tool adoption as a sales KPI? Because a process that only two people follow produces the results of two people. Adoption is the difference between a metric describing your team and one describing your power users.

How often should these be reviewed? Metrics 1–4 weekly or monthly; 5–7 quarterly; 8 and 9 twice a year. The fast ones are for management, the slow ones for direction.

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.

Ready to make these measurable?

Find out how Building Radar's revenue engineering solution captures project and specification data so these KPIs become reportable.

Schedule an initial consultation

Relevant resources