Short answer: It depends almost entirely on when you enter the project. Engage at design stage and expect twelve to twenty-four months to order. Enter at tender and it is one to four months — but you are competing on price against products already declared equivalent. The long cycle is not a problem to be shortened; it is where the margin is created. What needs fixing is the reporting, which usually cannot handle a pipeline that runs for years.
Cycle length by entry point
Entry stage | Typical time to order | What you are competing on |
|---|---|---|
Idea / feasibility | 24–48 months | Standards and quality level |
Early design | 12–24 months | Requirements definition |
Detailed design | 9–18 months | System and product selection |
Tender preparation | 3–9 months | Equivalence criteria |
Tender published | 1–4 months | Price |
Procurement / substitution | Weeks | Price, availability, habit |
Two things follow from this table.
The projects producing revenue this quarter were won by someone during a period when your team was probably looking at tenders. That lag is the whole reason early engagement is hard to sustain organisationally.
A "shorter sales cycle" usually means a worse one. Teams reporting fast cycles are often reporting that they only engage at tender — which is a margin problem disguised as an efficiency metric.
Why the cycle is usually measured wrong
Most manufacturers measure from "opportunity created in CRM" to "order booked". That produces a number that says almost nothing, for three reasons.
The clock starts arbitrarily. A rep creates the CRM record when they feel like it — sometimes at first contact, sometimes when a quote is requested. Two reps working identically produce different cycle lengths.
The specification decision is invisible. The moment that actually determines the outcome sits months before the order and is usually not recorded at all. So the metric measures the gap between an administrative act and an invoice.
Project delays are counted as sales delays. A project postponed for eighteen months because of financing appears as a stalled deal. Nothing about your sales process caused it, and nothing about your sales process will fix it.
What to measure instead
Three cleaner metrics:
Time from project identification to first decision-maker contact. Short and controllable. The best leading indicator in project sales, and the one your team can actually influence week to week.
Time from first contact to specification. Measures the effectiveness of the specification motion itself.
Time from specification to order. Largely determined by the project schedule, not by you. Useful for forecasting, not for performance management.
Splitting the cycle at the specification milestone separates what you control from what you do not. A team whose first metric is deteriorating has a real problem. A team whose third metric is deteriorating probably has a market where projects are being delayed.
Managing a pipeline that runs for years
Stage the pipeline on project reality, not rep activity. "Offer sent" tells you nothing about when the order comes. "Specification submitted" and "product approved" do.
Expect and plan for silence. A design-stage project will go quiet for months. That is normal, not a sign of a lost deal. The failure mode is not the silence — it is having no mechanism to notice when the project moves again.
Trigger follow-up on project events. Permit granted, design completed, tender announced, contract awarded. Jeane, the intelligence inside Building Radar, monitors project stage changes and drafts the follow-up when a project actually moves, so timing comes from the project rather than a reminder set eight months earlier. This is the single biggest source of quietly lost deals in long-cycle sales.
Forecast on project stage, not on rep confidence. In a two-year cycle, a rep's gut feeling from month four has little predictive value. Where the project sits, and whether you are in the specification, has a lot.
Report early-stage work separately. Otherwise the activity that produces next year's revenue looks like inactivity this quarter and gets cut.
The capacity question this raises
A long cycle means a rep carries many projects simultaneously — typically forty to eighty active. Each needs periodic touch, and each touch needs context: what was discussed, what stage the project is at, what changed.
That context work is where long-cycle sales quietly consumes capacity. Research, re-reading old notes, checking whether anything moved, updating records. It is also the part that can be removed: Building Radar handles project monitoring, meeting preparation and CRM maintenance, with Jeane reachable by web app, email, WhatsApp, phone and API so a rep can get a project brief before walking into a meeting.
Fröscher measures a 4.1x increase in win rate from project found to closed on this basis — not by shortening the cycle, but by managing more of it properly.
Frequently asked questions
How long is the average building product sales cycle? There is no single figure. Design-stage entry typically runs twelve to twenty-four months to order; tender-stage entry runs one to four months. The difference reflects when you engaged, not how efficiently you sold.
Can you shorten the construction sales cycle? The portion you control — from project identification to specifier contact — can be shortened significantly. The portion determined by the construction schedule cannot, and trying to compress it usually means engaging later, which costs margin.
Why do construction deals go quiet for months? Because the project does. Design phases, permitting and financing run on their own timelines, independent of your sales activity.
How do you forecast with a two-year cycle? Forecast on project stage and specification status rather than on rep confidence, and report early-stage pipeline separately from near-term revenue.
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 manage a long-cycle pipeline properly?
Find out how Building Radar's revenue engineering solution tracks projects through their full lifecycle and triggers follow-up when they move.
Schedule an initial consultation