Short answer: Construction sales teams are frequently organised as internal competitions — leaderboards, individual quotas, territory ownership. That works when deals are independent. In project sales they are not: one building involves several parties, practices work across regions, and the same architect can appear in three reps' territories. When information does not circulate because circulating it costs someone credit, the company loses deals that nobody is accountable for losing.
Where the model breaks
Individual quotas assume deals are separable. In construction they overlap in three specific ways.
Practices work across territories. An architecture practice in Munich designs projects in Hamburg and Stuttgart. Under geographic ownership, the relationship sits with whoever covers the postcode of each building — so three reps hold fragments of one relationship, and none holds the whole.
One project involves several buying roles. The specifier and the buyer are different companies. If specification work is credited to one rep and the order to another, the incentive to do the earlier, harder work weakens.
Key accounts start projects everywhere. An existing customer's new development appears in a region the account owner does not cover. Whether that surfaces depends on whether someone volunteers it.
What actually gets lost
Three concrete losses, in order of size.
Duplicate outreach. Two reps contact the same planner about different projects at the same practice, unaware of each other. That is not just wasted effort; it damages credibility with exactly the person whose opinion matters most.
Unshared context. A rep learns that a developer has a three-project pipeline. Under a competitive model, mentioning it means handing two projects to colleagues. Most people are decent enough to share anyway — but the system is asking them not to, and at the margin that shows.
Specification work that goes uncredited. The most expensive of the three. If a rep spends six months getting a product specified and the order lands in another territory, the recognition follows the invoice. Do that twice and reps rationally stop doing specification work outside their own postcodes.
The uncomfortable part
None of this requires anyone to behave badly. It happens through ordinary self-interest inside a structure that rewards individual attribution in a business where outcomes are collective.
Which means it is not fixed by asking people to collaborate more. It is fixed by changing what gets measured.
What to change
1. Credit the specification, not only the order. Add specification as an explicit milestone in the CRM, attributable to whoever achieved it, separate from and earlier than the purchase order. Without this, the work that determines outcomes is structurally invisible — and unrewarded work stops happening.
2. Own practices, not postcodes. For specification work specifically, assign the relationship with an architecture practice or planning office to one person regardless of where the buildings are. Geographic ownership is right for closing and wrong for specifying.
3. Make shared knowledge the default rather than a favour. If the system shows who spoke to whom, sharing costs nothing because the information was already visible. If it does not, sharing is an act of generosity and will be inconsistent.
This is a data problem more than a culture problem. Jeane, the intelligence inside Building Radar, reads the CRM and email history, so a practice a colleague already works with surfaces as an existing relationship rather than being rediscovered — or contacted twice. The duplicate outreach problem disappears because the duplicate is visible before the call.
4. Measure team coverage alongside individual performance. What share of relevant projects in the market did the team touch? That number cannot be improved by one person outperforming another, which is exactly why it is worth having.
What replaces the leaderboard
Competition is not the enemy of performance, and removing all of it produces its own problems. The distinction worth drawing is between competing on effort and competing on information.
Fine: who reached the most specifiers, who moved the most projects into specification, who improved their average project stage at first contact.
Costly: who found the project first, who owns the account, who gets credit for the order.
The first set rewards behaviour you want repeated. The second rewards withholding.
What it looks like when it works
Teams that make this shift report the same thing: top-performer insight stops disappearing into personal notes. Everyone can see who spoke to whom and build on it, so success becomes repeatable rather than individual.
That has a second effect worth mentioning. When market knowledge lives in a shared system, a rep leaving becomes a handover rather than a loss — which is the same argument as the one for reducing key-person risk, arrived at from a different direction.
Companies such as Schindler, Heidelberg Materials, Hochtief and Saint-Gobain Switzerland already use Building Radar to their advantage.
Frequently asked questions
Is internal sales competition always harmful? No. It works where deals are independent. In construction project sales, deals overlap across territories and buying roles, which turns competition into an incentive to withhold information.
How should territories be organised in construction sales? Geographic ownership works for closing. For specification work, assigning practices and planning offices to one owner regardless of building location prevents fragmented relationships.
Why does specification work need separate credit? Because the order frequently lands in a different territory and through a different company. Without separate attribution, the work that determines the outcome goes unrewarded and gradually stops.
What should be measured instead of individual deal credit? Specifications won, average project stage at first contact, and team-level market coverage — metrics that reward the behaviour rather than the attribution.
Ready to make market knowledge shared?
Find out how Building Radar's revenue engineering solution gives your whole team visibility of who spoke to whom.
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