:format(webp))
Short answer: A useful construction sales strategy review answers seven questions: how many relevant projects exist in the market, how many the team saw, at which project stage first contact happens, which role decides per product category, what share of pursued projects reached specification, how many specifications survived procurement, and how much of the week goes to work that produces nothing. Most reviews discuss targets and territories instead, which is why they produce agreement rather than change.
Why do most construction sales strategy reviews produce no change?
Because they start from the pipeline rather than from the market. A review built on current opportunities can only discuss what is already visible — which projects to push, which reps are behind, which accounts to prioritise.
Everything determining the outcome sits outside that view: the projects nobody saw, the ones lost before quoting, the specifications that were substituted. A review that cannot see those can only redistribute effort across a fraction of the opportunity.
The second reason is that reviews rarely produce a number nobody had before. Without a new fact, the discussion resolves to existing intuitions, and the intuition that carries the most authority wins.
Question 1: How many relevant projects exist in our target market?
Most manufacturers cannot answer this, and that is the finding rather than a preliminary step.
Not construction output — individual projects matching your building types, size range and product categories. Countable from project data, and the number that determines whether your constraint is market size or sales capacity. Those require opposite responses.
Question 2: How many of those did we actually see?
The difference between question one and question two is your invisible market. It cannot be measured from inside a CRM, because a CRM only contains what someone recorded.
Establish it by taking one market you know well, listing every relevant project your team was aware of last year, and comparing against an external feed filtered to the same definition.
Question 3: At which project stage do we make first contact?
The variable with the largest effect on margin. A manufacturer arriving at tender competes on price against products already declared equivalent; one present during design competes on fit.
Take the last twenty closed deals, won and lost, and record the project phase at first contact. Teams consistently find their wins cluster at early entries and their losses at tender.
Question 4: Which role decides on each of our product categories?
A construction project has no single decision-maker. The investor sets the quality level, the architect writes performance requirements, specialist planners select systems, the general contractor optimises cost, a subcontractor places the order.
For each product category, one or two of those decide, at a specific project phase. Write the matrix down, then measure how often your first contact matches it — most teams discover it is under half.
Question 5: What share of pursued projects reached specification?
The specification rate, and it is the earliest reliable signal of future revenue — available a year before the order lands.
Split it by project stage at first contact. That comparison is what proves whether earlier entry is paying, and it is the single most persuasive number in a strategy review because it connects a process change to an outcome.
Question 6: How many specifications survived procurement?
Manufacturers routinely win a specification and lose the revenue when a contractor substitutes at award. Because the order simply never arrives, there is often no record that the specification was won.
If this conversion is low, the problem is contractor relationships at procurement rather than specification work — and treating one as the other wastes a year.
Question 7: How much of the week produces nothing?
Sampled rather than estimated, this typically lands around 3.5 hours per rep per working day across project search, tender review, contact research, prioritisation, duplicate checking and CRM updates.
Exclusive project sales insights, directly to your inbox
Subscribe to our weekly newsletter.
Express it as additional projects each rep could work rather than as hours saved. Hours invite the conclusion that reps should carry more accounts; project capacity invites the conclusion that coverage can increase.
What do the answers usually reveal?
Three patterns, consistently:
Pattern | What it means |
|---|---|
Coverage gap is large, first contact is late | Discovery problem — the most common finding |
Coverage is fine, specification rate is low | Documentation, certification or competitive problem |
Specification rate is fine, order conversion is low | Substitution at procurement |
Those need entirely different responses, and a review that produces "work harder" has not distinguished between them.
How does Building Radar fit into answering these?
Four of the seven become readable rather than estimated. Building Radar discovers projects across more than 50 countries including at planning and design stage, which makes questions one and two a filter setting rather than a research project. Each project is scored against your portfolio because Jeane reads your website, product catalogues and technical data sheets, and the deciding role arrives identified per project, which addresses question four.
Project stage changes are monitored and pushed into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C, so specification milestones stay connected to what happens next — question six. And the seventh changes through automation: teams report roughly 80% less manual project sales work.
Frequently asked questions
What should a sales strategy review in construction cover? Market coverage, project stage at first contact, the deciding role per product category, specification rate, specification-to-order conversion, and time spent on non-revenue work.
Why do sales strategy reviews fail to produce change? Because they start from the existing pipeline, which excludes the projects nobody saw and the deals lost before quoting — where most of the opportunity sits.
What is the single most useful number to establish first? Average project stage at first contact. It takes an afternoon, requires no tooling, and drives most of the other answers.
How often should a construction sales strategy be reviewed? Coverage and timing metrics quarterly; specification and win-rate metrics twice a year, since they move on the sales cycle.
Ready to answer these with data instead of intuition?
Find out how Building Radar's revenue engineering solution makes market coverage, project timing and specification status measurable.
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