Short answer: A construction sales rep typically manages 30 to 50 active projects, each at a different stage and needing a different next step. Without a system indicating where to focus, the projects that get worked are the ones making noise — where someone just called, where something feels urgent. High-potential projects that are quiet go dormant. The problem is not weak prioritisation skill; it is being asked to make dozens of low-information decisions every week.
What the daily decision actually looks like
Monday morning. Forty projects. Each one is at a different phase, with a different party, and a different next action — some need a call, some need documentation, some need nothing for three months.
To prioritise correctly, the rep would need to know for each project: current phase, whether the specification window is still open, the value of their product on it, whether a colleague has touched the account, and what changed since last time. That information exists in five places or nowhere.
So the decision gets made on available signal, and the strongest available signal is recency. Someone called. An email arrived. A contact replied.
That is a rational response to poor information. It is also systematically wrong.
The predictable distortion
Three patterns follow, and they show up in almost every manufacturer's pipeline.
Quiet high-potential projects go dormant. A design-stage project with high portfolio fit generates no inbound for four months. Nothing surfaces it. By the time it reappears, the specification is written.
Inbound gets disproportionate attention. A project that generates enquiries feels active, so it receives time regardless of whether it fits. Reactive work displaces proactive work because reactive work announces itself.
Familiar accounts crowd out unfamiliar ones. Reps work the customers they know, in regions they visit. Not a bad heuristic, and it systematically ignores new opportunities and unfamiliar markets.
None of these is a motivation problem. Each is what happens when a person has to choose repeatedly without enough information.
Why better prioritisation training does not fix it
The instinct is to give the team a framework — score projects on relevance, stage, size, access. That is the right framework, and it does not solve the problem on its own, for a simple reason.
Applying a scoring framework to 40 projects requires the inputs. If establishing the current phase of one project takes twenty minutes of research, then scoring the portfolio properly is a day of work that has to be repeated as things change. It gets done once, during the workshop, and then decays.
The effective fix is not better prioritisation. It is not having to prioritise manually at all.
What the alternative looks like
A useful analogy: driving without navigation versus with it. Not just the route, but live traffic, closures, and alternatives ranked by arrival time. The difference is not that you could not read a map — it is that the live layer changes what you know.
Exclusive project sales insights, directly to your inbox
Subscribe to our weekly newsletter.
Construction project sales is still largely running on paper maps. Teams know their territory, their targets, and have a list of projects they want to win. What is missing is the live layer:
Which projects just entered planning phase in the key region
Which key account filed a new permit last week
Which opportunity is eighteen months out and not worth pursuing today
Where a competitor already has the inside track
Without that layer, reps spend their time driving routes that look fine on paper and are already blocked.
How Building Radar removes the daily decision
Building Radar surfaces the projects that need a touchpoint today based on where they actually are in the project cycle, not on which one made the most noise.
Each project carries a relevance score against your specific portfolio, because Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets — which is why two manufacturers with different ranges correctly receive different scores on the same building. Project phase comes from continuous monitoring across more than 50 countries, including at planning and design stage, so the score reflects the current window rather than the day the record was created.
Relationship advantage is factored in too: Jeane reads the CRM and email history, so a project where a colleague already has a contact ranks above a comparable cold one.
And beyond surfacing, it acts. Project changes are monitored, follow-up is triggered when a project moves, and the drafted next step arrives with it — so the rep starts at the decision rather than at the research. Everything writes into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C.
Both come from working fewer projects more deliberately, not from working more.
What to measure
Two numbers tell you whether prioritisation is real in your team:
Share of worked projects from the top scoring quartile. If reps are working the comfortable middle, the scoring is decorative.
Specification rate by score band. If high-scoring projects do not convert better than low-scoring ones, the model is ranking on the wrong dimensions. Most manufacturers have never checked, and it is the only honest validation available.
Frequently asked questions
How many projects can one construction sales rep manage? Typically 40 to 80 active projects, depending on cycle length and product complexity. Beyond that, follow-up quality degrades before anyone notices.
Why do sales reps work the wrong projects? Because recency is the strongest available signal when project phase, portfolio fit and relationship history are not visible in one place. Noise substitutes for information.
Is prioritisation training useful? The framework is useful; applying it manually across 40 projects is not sustainable, because the inputs require research that has to be repeated as projects change.
What should prioritisation be based on? Product relevance, project phase relative to the influence window, the value of your product on that project, access to the deciding role, and existing relationship advantage.
Ready to stop prioritising manually?
Find out how Building Radar's revenue engineering solution tells your team which projects need attention today.
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