Short answer: Prioritise construction sales opportunities on five dimensions: product relevance, project stage (can you still influence the specification?), commercial size, access to the deciding role, and existing relationship advantage. Score each project on all five, weight them for your business, and enforce hard disqualification rules so reps spend their capacity on projects that are actually winnable — not on the ones that happen to be familiar.
Why prioritisation is the real bottleneck
Most construction sales teams do not have a lead shortage. They have a capacity problem dressed up as a lead problem.
A building product manufacturer operating in four countries may have several thousand potentially relevant projects per year. A rep can meaningfully work perhaps forty to eighty at a time. Which means well over 90% of projects will not be worked — and the only question that matters is whether the 3% that get attention are the right 3%.
Without an explicit framework, that selection happens by default: reps work the projects they already know, in the regions they visit, with the customers they like. That is not a bad heuristic, but it systematically ignores new opportunities and unfamiliar markets.
The five scoring dimensions
1. Product relevance
Does this project actually need what we sell? Not "is it a commercial building" — does it require our product category, at a scale that matters?
This is where generic filtering fails. Two acoustic manufacturers with different portfolios should score the same school project differently. Scoring at product level requires the system to know the portfolio. Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets in order to score relevance against what you actually sell rather than against a project category.
2. Project stage — the influence window
Can we still shape the specification? A project at early design is worth far more than the same project at published tender, where the requirements are fixed and you compete on price.
Score stage against your own influence window, which differs by product category:
Specification-driven products: early and detailed design
Systems selected by MEP planners: detailed design
Commodity and fixing products: procurement, much later
3. Commercial size
Estimated value of your product on this project, not the total project value. A €200 million hospital may represent €30,000 of your product; a €12 million logistics centre may represent €400,000. Total project value is a widely used and consistently misleading proxy.
4. Access to the deciding role
Can we reach the person who decides on our category? A project with high relevance and perfect timing is worth little if the specifier is unreachable or the practice has a standing relationship with a competitor.
Score access on: named contact available, contact reachable, role confirmed as the decision-maker for your category, and prior engagement history.
5. Relationship advantage
Have we worked with any of the parties before? An architect who has specified you three times is a materially different prospect from a new practice. This is the dimension most tools ignore, because it requires reading the CRM and email history rather than the project data.
Weighting the model
Weights should reflect where your deals are actually won. Two common patterns:
Dimension | Specification-driven manufacturer | Contractor-driven / commodity product |
|---|---|---|
Product relevance | 30% | 30% |
Project stage | 30% | 10% |
Commercial size | 15% | 25% |
Access to deciding role | 15% | 25% |
Relationship advantage | 10% | 10% |
Do not over-engineer this. Any explicit, consistently applied weighting outperforms implicit prioritisation. Refine it after a quarter of real data, not in a workshop.
Hard disqualification rules
Weighted scores handle relative priority. Some conditions should remove a project entirely, regardless of score:
Below minimum order volume for your business
Project stage past the influence window for the category
Region you cannot commercially service
Competitor holds an exclusive or framework agreement on this account
No route to any role that influences your category
Disqualification is a performance signal, not a failure. A rep rejecting 60% of assigned projects in week one is doing the job properly — and every rejection reason is training data that sharpens the scoring model.
Running it weekly
A prioritisation framework only works if it survives contact with a Monday morning.
New projects arrive scored and ranked, not as a search interface. If a rep has to build the list, they will use last week's list.
Top of list is assigned with an owner and a next step. Unowned projects do not move.
Rejections are captured with a reason, in one click, from a phone.
Score changes trigger review. A project that moves from design to tender should drop; a project where a specifier finally responds should rise.
Weekly review looks at the list, not the individual deals. Are we working the top of the list, or the comfortable middle?
What to measure
Share of worked projects from the top scoring quartile — the direct measure of whether prioritisation is real
Average project stage at first contact — should move earlier over time
Disqualification rate and reasons — tells you whether the scoring model is calibrated
Specification rate by score band — validates the model; if high-scoring projects do not convert better, the weights are wrong
Time from project identification to decision-maker contact
That third-to-last point is the honest test of any scoring model. If your top quartile does not convert better than your bottom quartile, you are ranking projects on the wrong dimensions.
Frequently asked questions
How do you prioritise construction projects for sales? Score each project on product relevance, project stage, the value of your product on that project, access to the deciding role, and existing relationship advantage. Weight the dimensions for your business, apply hard disqualification rules, and work the list from the top.
Is total project value a good prioritisation criterion? No. What matters is the value of your own product on the project, which correlates weakly with total project value.
How many projects should a rep work at once? Typically forty to eighty active projects, depending on cycle length and product complexity. Beyond that, follow-up quality degrades.
Should reps be able to override the score? Yes, with a recorded reason. Reps hold context the system does not, and their overrides are the most valuable input for improving the model.
How Building Radar applies these five dimensions
Building Radar scores every project on the five dimensions above and delivers a ranked list rather than a search interface.
Product relevance comes from Jeane reading your website, product catalogues and technical data sheets, which is why two manufacturers with different portfolios correctly receive different scores on the same project. Project stage comes from continuous monitoring across more than 50 countries, including at planning and design stage. Access comes from identifying the deciding role per project with reachable contacts. Relationship advantage comes from Jeane reading your CRM and email history, so a project where a colleague already has a contact is not treated as cold.
Rejections feed back into the model, so the reasons your reps give in week one sharpen the scoring in week ten. Everything is written into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C with an owner and a next step.
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 prioritise on data instead of habit?
Find out how Building Radar's revenue engineering solution scores every project against your portfolio and delivers a ranked list your team will actually work.
Schedule an initial consultation