Short answer: In construction project sales, a field rep typically loses around 3.5 hours per working day to manual tasks that have no direct effect on revenue — duplicate checks, contact research, project searching, gut-feel prioritisation, tender review and CRM updates. At a fully loaded hourly rate of €30, that is roughly €23,000 per rep per year. Building Radar reduces those tasks to about one hour per day, which puts the recoverable amount near €17,000 per rep annually.
The calculation, spelled out
Most claims about efficiency in sales software are unfalsifiable. This one is worth stating with its assumptions visible, so you can substitute your own numbers.
Task | Typical time per day |
|---|---|
Searching for new projects manually | ~60 min |
Reviewing and evaluating tenders | ~45 min |
Finding the right contacts | ~30 min |
Prioritising opportunities by gut feeling | ~30 min |
Updating CRM records | ~30 min |
Checking for duplicate leads | ~15 min |
Total | ~3.5 hours |
At €30 per hour and roughly 220 working days, that is about €23,000 per rep per year spent on work with no direct pipeline effect.
Two things to note about this table. First, none of it is optional — all of it has to happen before selling can start. Second, none of it requires the experience of the person doing it.
Why the number is larger than it looks
The euro figure understates the problem, for three reasons.
Opportunity cost, not just labour cost. The alternative to three and a half hours of admin is not three and a half hours of idleness. It is time with a specifier. The value of the lost hour is closer to the margin on a specification than to €30.
Capacity limits, not just efficiency. A rep can meaningfully carry 40 to 80 active projects. That ceiling is set largely by how much context work each project requires. Reduce the per-project overhead and the ceiling rises — which means more of the market gets touched, not just the same market faster.
The tasks that do not happen at all. Follow-ups that were never triggered because nobody noticed a project moved. Contacts never researched because there was no time. Those losses do not appear in a time audit because the work was skipped, not slowed.
Where the time actually goes wrong
It is worth separating two different failure modes, because they need different fixes.
Duplicated effort. The same project arrives from a data provider, an inbound enquiry and a rep's site visit — three records, three research efforts, sometimes two reps calling the same architect. This is a data problem, and it compounds across a team.
Low-information decisions. A rep with 40 projects and no scoring has to decide every morning where to start. Without a system telling them, the projects that get worked are the ones making noise — the ones where someone just called. High-potential projects that are quiet go dormant. Lower-value projects that generate inbound get disproportionate attention.
The second is more expensive than the first and much harder to see in a time audit, because deciding badly takes no longer than deciding well.
Exclusive project sales insights, directly to your inbox
Subscribe to our weekly newsletter.
What a rep should and should not be doing
The clarifying question is not "how do we make these tasks faster" but "which of these tasks require a person at all".
Replaceable:
Searching for new projects in a region
Determining which phase a project is in
Finding the right contact at the right company
Checking whether a colleague already worked that contact
Reading 80 pages of tender documents for two relevant paragraphs
Deciding which of 40 leads to call first
Updating the CRM after a site visit
Monitoring key accounts for new project activity
Tracking which projects need follow-up this week
Qualifying inbound requests before passing them on
Not replaceable:
Building trust over years
Sitting across from the customer
Handling the conversation nobody else could have
Judging when to walk away from a difficult account
Every item on the first list is on the €23,000 bill. Nothing on the second list is.
How Building Radar changes the arithmetic
Building Radar takes the first list off the plate rather than making it faster.
Projects are discovered across more than 50 countries, deduplicated and enriched, and scored against your portfolio — because Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets. Tender documents are read and matched against your value proposition, with the scope, requirements and deadlines extracted; teams report roughly 83% faster processing of service specifications. The deciding role arrives identified with reachable contacts. Follow-ups are triggered when a project changes stage. Records stay current in Salesforce, HubSpot, Microsoft Dynamics or SAP C4C without a rep typing.
And it works away from the desk. Jeane is reachable by web app, email, WhatsApp, phone and API — a rep between site visits can request a meeting brief and report the outcome as a voice message, and the CRM updates from that.
Teams working this way report roughly 80% less manual project sales work, which brings the 3.5 hours down to about one. Whether that is worth €17,000 in your case depends on your hourly rates and volumes, and the Revenue Potential Calculator will run the arithmetic on your own numbers rather than these.
Frequently asked questions
How much time do construction sales reps lose to manual work? Typically around 3.5 hours per working day, spread across project search, tender review, contact research, prioritisation, CRM updates and duplicate checks.
What does that cost per rep? At a fully loaded rate of €30 per hour and roughly 220 working days, about €23,000 per rep per year. The recoverable share is around €17,000 when the tasks drop to about one hour daily.
Is the real cost just the labour hours? No. The larger cost is opportunity — the specifier conversations that did not happen, and the follow-ups nobody triggered because a project change went unnoticed.
Which manual tasks should be automated first? Project search and duplicate resolution, because they compound across a team, and tender document review, because it consumes the largest single block of time.
Does automation reduce headcount? In practice it raises the number of projects each rep can work, which increases coverage rather than reducing team size.
Ready to calculate this for your own team?
Find out how Building Radar's revenue engineering solution removes the work that competes with selling.
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