Short answer: Standard weighted-pipeline forecasting assumes deals close on a schedule your sales team controls. In construction project sales they do not — the order arrives when the project reaches procurement, which can be eighteen months later or never. A forecast that multiplies deal value by a rep's confidence percentage will be wrong in both directions. A workable model forecasts on project stage and specification status, and separates timing risk from win risk.
Why the standard model breaks
Weighted pipeline is: sum of (deal value × probability by stage). It assumes three things that hold in most B2B sales and none of which hold here.
Assumption 1: the close date is knowable. In construction, the order date is set by the construction schedule, not by your sales process. Financing delays, permitting, weather and contractor availability move it by quarters. Your rep's close date is a guess about someone else's project plan.
Assumption 2: probability rises monotonically through the stages. In project sales it does not. A product can be specified — very high probability — and then substituted at procurement, dropping to zero in a week without any warning signal in the CRM.
Assumption 3: the deal is with one party. The specification decision and the purchase order frequently involve different companies. The stage your CRM records may describe your progress with the architect while the risk sits entirely with a contractor you have never spoken to.
The result is familiar: a forecast that misses in both directions, quarter after quarter, with no pattern anyone can explain.
Separate the two risks
The core fix is recognising that a construction opportunity carries two independent risks.
Win risk: will we be the supplier? Determined by specification status, competitive position and relationships. You influence this.
Timing risk: when will the project reach procurement? Determined by the construction schedule. You influence almost none of it.
Standard weighted pipeline collapses both into one percentage, which is why it fails. Forecast them separately.
A stage-based model that works
Step 1 — forecast win probability from specification status, not rep confidence.
Status | Typical win probability |
|---|---|
Project identified, relevant | Low |
Specifier contacted, requirement understood | Low–moderate |
Specification submitted | Moderate |
Named with equivalents permitted | Moderate–high |
Sole specification, no equivalents | High |
Order placed | Certain |
Populate the actual percentages from your own history rather than from a template. The important part is that the driver is a verifiable project fact, not a feeling.
Step 2 — forecast timing from project stage, not from a rep-entered close date. Use the construction schedule where known, and typical stage durations for your building types where not. A project at detailed design will not produce an order next quarter regardless of what the CRM says.
Step 3 — apply substitution risk separately. Between specification and order, a share of specified projects are substituted. Measure your own rate. If 20% of your specifications are substituted at procurement, that is a discount to apply after the specification stage, not before.
Step 4 — report two horizons. Near-term revenue from projects past specification and approaching procurement. Influenced pipeline from projects at design stage, which is next year's revenue and should never be mixed into this quarter's number.
What this requires from your data
The model is not complicated. What defeats most manufacturers is that the inputs do not exist:
The project must be the CRM object, not the company, or the same project appears three times and the forecast double-counts.
Specification must be an explicit milestone, recorded when it happens, separately from the order.
Project stage must be current, which means it has to update automatically. A record that said "design stage" in March and still says it in November makes any stage-based forecast fiction.
That third point is where Building Radar fits: project stage changes are monitored continuously and pushed into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C, so the stage driving your forecast reflects the project rather than the date the record was created. Jeane also flags when a specified project enters procurement — which is precisely when substitution risk becomes live and a forecast most often breaks.
Three habits that improve accuracy quickly
Stop asking reps for close dates on design-stage projects. They cannot know. Derive the date from project stage and typical durations, and let the rep override with reasons.
Track forecast accuracy by stage. If projects at "specification submitted" convert at 40% rather than the 60% in your model, fix the model. Most manufacturers have never checked.
Review lost deals for the stage where they died. Consistent losses between "specification submitted" and "approved" indicate a documentation or sample problem. Losses between "approved" and "order" indicate substitution — a contractor relationship problem. Those need opposite responses, and an undifferentiated forecast hides which one you have.
Frequently asked questions
Why is construction sales forecasting so difficult? Because the order date is set by the construction schedule rather than the sales process, the specification decision and the purchase involve different parties, and win probability can collapse at procurement without warning.
Should we use weighted pipeline in construction sales? Only if the weights are driven by specification status rather than rep confidence, and timing is forecast separately from the construction schedule.
What is the best leading indicator? Time from project identification to first decision-maker contact, combined with specification rate. Both are current-quarter signals for revenue that arrives much later.
How do you forecast projects that are years out? Do not put them in the revenue forecast. Report them as influenced pipeline with project stage and specification status, on a separate horizon.
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 forecast on project reality?
Find out how Building Radar's revenue engineering solution keeps project stages current so your pipeline reflects what is actually happening.
Schedule an initial consultation