Short answer: In standard B2B sales there is one cycle — how far along your sales process you are. Construction project sales has two that move independently: your sales cycle, and the timeline of the physical building project. A deal can be at proposal stage in your CRM while the building permit has not been granted. You can be fully specified and still lose, because the general contractor does not break ground for another eighteen months. Any forecast that tracks only the first cycle is measuring half the situation.
What the two cycles are
Your sales cycle. How close you are to a signed contract. Project identified, specifier contacted, requirement understood, specification submitted, product approved, order placed. This is the dimension every CRM is built to track.
The project timeline. How far along the actual construction project is. Concept, planning application, design, permit, tender, contract award, construction. This dimension is set by the owner, the planning authority, the financing and the contractor — none of whom consult you.
The two are related but not synchronised. Progress in one does not imply progress in the other, and this is the single most consequential structural fact about selling into construction.
Why this makes construction the hardest B2B sale
Most people outside the industry do not believe this until they see it. Four consequences follow directly.
Your deal does not become more likely just because your sales process advanced. In software sales, moving from demo to proposal genuinely improves the odds. In construction, moving to proposal while the permit is still pending changes nothing about the outcome. The project has to progress too.
The buying centre spans companies, not departments. Standard sales training assumes an economic buyer, a champion and procurement inside one organisation. Here it is the investor, the architect, the specialist planner, the general contractor and a subcontractor — each with different incentives, different timelines, and a different definition of what makes your product worth specifying.
Cycles run 18 to 36 months. Long enough that no individual can hold a portfolio of 30 to 50 projects in their head reliably, and long enough that a project can go quiet for six months and then move in a week.
The same project appears under different names. Across planning databases, tender portals, press coverage and a rep's notes, one development can exist as four records with different spellings and addresses.
What this breaks
Weighted pipeline forecasting. Multiplying deal value by a probability percentage assumes the close date is knowable and that probability rises monotonically. Neither holds. A specified product can drop to zero probability in a week through substitution at procurement, with no signal in the CRM.
Standard pipeline stages. Stages defined by rep activity — called, offer sent, negotiating — say nothing about when revenue arrives. A project at "offer sent" might be two months or two years from award.
Follow-up by calendar reminder. A reminder set eight months ago is not a system. The moment that matters is when the project moves, and that moment is unpredictable.
Sales training. Teaching objection handling does not help if the rep is talking to the wrong person three months too late. The skills that matter here are different: knowing where a project sits in its lifecycle, navigating stakeholders across companies, maintaining momentum over multi-year cycles, and recognising when the specification is still open versus already decided.
Exclusive project sales insights, directly to your inbox
Subscribe to our weekly newsletter.
How to work with two cycles instead of against them
Stage the pipeline on project reality. Replace activity-based stages with verifiable project milestones — specification submitted, product approved, tender listed, order placed. Then the stage tells you something about timing.
Forecast the two risks separately. Win risk is determined by specification status and competitive position; you influence it. Timing risk is determined by the construction schedule; you influence almost none of it. Collapsing both into one percentage is why forecasts miss in both directions.
Trigger action on project events, not sales events. Permit granted, design completed, tender announced, contract awarded. These are the moments when your next step becomes relevant.
Report two horizons. Near-term revenue from projects past specification and approaching procurement. Influenced pipeline from design-stage projects, which is next year's revenue and should never be mixed into this quarter's number.
Why this is a data problem
None of the above is possible if your record of project stage is whatever someone typed when the record was created. A project that said "design stage" in March and still says it in November makes any stage-based approach fiction.
This is where Building Radar fits. Projects are monitored continuously across more than 50 countries, from planning and design stage onwards, and stage changes are pushed into Salesforce, HubSpot, Microsoft Dynamics or SAP C4C as they happen. Jeane, the intelligence inside Building Radar, holds both dimensions — where your sales process stands and where the project stands — and derives the next best step from the combination rather than from the sales stage alone.
That last point is the practical difference. Knowing the right next move across 40 projects with two independent clocks is difficult for an experienced rep and close to impossible for a junior one. Fröscher measures a 4.1x increase in win rate from project found to closed on this basis.
Frequently asked questions
Why is construction project sales more complex than other B2B sales? Because two cycles run in parallel — the sales process and the physical project timeline — and they move independently. Progress in one does not imply progress in the other.
How long is the construction project sales cycle? Typically 18 to 36 months from first project signal to order, depending on project type and when you engaged.
Why does weighted pipeline forecasting fail here? It assumes a knowable close date and steadily rising probability. In construction the close date is set by the construction schedule, and probability can collapse at procurement through substitution.
What should pipeline stages be based on? Verifiable project milestones — specification submitted, product approved, tender listed — rather than rep activity, because milestones carry timing information and activities do not.
Can a deal be lost after the product is specified? Yes. Contractors substitute at procurement on price, availability or habit. Specified projects need monitoring through award.
Ready to track both cycles?
Find out how Building Radar's revenue engineering solution holds the project timeline and your sales process in one view.
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