Short answer: By the time a project reaches the bid stage, most of the decisions that determine who wins have already been made — the requirements are written, the acceptable products are defined, and the remaining variable is price. Winning before the bid means finding projects during planning and design, reaching the person who writes the requirements, and getting your solution embedded in the criteria while they are still being drafted.
What is already decided when the bid goes out
A bid document is the end of a decision process, not the beginning. By the time it is published:
The performance requirements are fixed, and they were written with specific products in mind.
The system approach is chosen — which construction method, which product families are in scope.
The acceptable alternatives are defined, explicitly or by the tightness of the criteria.
The budget has been allocated on the basis of assumptions about which products will be used.
If your product was not part of those assumptions, you are bidding into a specification written around a competitor. You can still win on price, but you will win at the margin the specification allows, not the margin you wanted.
Where the influence window actually sits
For most building products, the sequence looks like this:
Phase | Who is deciding | Your leverage |
|---|---|---|
Feasibility / concept | Owner, developer | High, but requirements too vague to specify |
Early design | Architect, lead planner | Highest — requirements being written |
Detailed design | Specialist planners | High — system selection, criteria refinement |
Tender preparation | Planner, cost consultant | Moderate — criteria largely fixed |
Bid / tender published | Contractors bidding | Low — price competition |
Award and procurement | Contractor, purchasing | Substitution risk on your specification |
The window is early design to detailed design. In calendar terms, that is typically six to twenty-four months before the order. Which means the projects you need to be working on now will not produce revenue this year — and the projects producing revenue this year were won by someone during a period when your team was probably looking at tenders.
A pre-bid playbook
1. Build a source of design-stage project information
You cannot work early-stage projects if you cannot see them. Tender portals are structurally too late. Early signals come from planning applications and building permits, design competition results, architectural press and local news, developer and investor announcements, and construction signage.
The practical problem is volume and noise. This is what AI project intelligence is for: consolidating those sources, deduplicating the same project appearing under different names, and scoring each one against what you actually sell. Building Radar detects projects at planning and design stage across more than 50 countries and scores them against your product portfolio.
2. Identify the requirement writer, per product category
The person who writes the requirements for your product category is specific and not always obvious. For façade systems it is usually the architect and the façade planner. For technical building services it is the MEP planner. For fixings and fastening it is often a specialist subcontractor much later in the chain.
Write this down as a matrix: product category × project phase × deciding role. Then measure how often your first contact matches the matrix. Most teams discover they are contacting purchasing departments on projects where purchasing has no influence.
3. Arrive with something the specifier can use
An early-stage conversation with an architect is not a sales call. The architect has an unsolved design problem and a deadline. What is useful:
Ready-to-use specification text for your product
Current technical data, in the formats and file types they work in
Reference projects comparable in type and scale
A clear statement of what your product does *not* do, which buys more credibility than a feature list
4. Track the project between contacts
Early-stage projects go quiet for months and then move quickly. The follow-up that matters is the one triggered when the project changes stage — design completed, planning permission granted, tender announced — not the one scheduled six months earlier in a calendar.
Automating this is the difference between a pre-bid strategy that works and one that exists in a slide. Jeane monitors project stage changes and drafts the follow-up when a project moves, so the timing comes from the project rather than the rep's memory.
5. Defend the specification at procurement
Winning the specification is not winning the order. At procurement, contractors substitute — on price, on availability, on habit. Your specified projects need to be monitored through award, with contact established with the winning contractor before purchasing decisions are made.
6. Measure the pre-bid funnel separately
Pre-bid work looks like inactivity in a standard pipeline, because nothing closes for a year. Give it its own metrics:
Share of pipeline sourced at design stage versus tender stage
Average project stage at first contact
Specification rate on early-entry projects versus late-entry projects
Time from project identification to specifier contact
Without these, the first budget review will cut the activity that produces next year's revenue.
What the outcome looks like
Teams that make this shift report the pattern rather than a single metric: more meetings, because more projects are reachable while they are still open; higher win rates, because fewer deals are decided on price; and better margins on the deals that close. Holcim measures a 400% increase in sales meetings after moving specification work earlier; Fröscher measures a 4.1x increase in win rate from project found to closed.
Frequently asked questions
Why is it easier to win before the bid stage? Because the requirements that determine which products are acceptable are written before the bid is published. Influencing those requirements creates an advantage that price competition cannot easily overturn.
How far before the bid should you engage? Typically at early or detailed design, which is usually six to twenty-four months before the order is placed.
How do you find construction projects before they go to tender? Through planning applications, building permits, design competition results, developer announcements, trade and local press, and construction signage — consolidated and scored, because the raw volume is unmanageable manually.
What if our product category is only decided at procurement? Then your influence window is later, and your effort should concentrate on contractor and subcontractor relationships rather than specifiers. The matrix of category, phase and deciding role is what tells you which case you are in.
How Building Radar supports the pre-bid motion
Every step in the playbook above depends on seeing projects before the bid, which is what Building Radar is built for.
Projects are detected at planning and design stage across more than 50 countries and scored against your specific portfolio, because Jeane reads your website, product catalogues and technical data sheets. Each project arrives with the deciding role identified — architect, specialist planner, general contractor or subcontractor, depending on your product category — and reachable contacts.
Between contacts, Jeane monitors project stage changes and drafts the follow-up when the project moves, including when a specified project enters procurement and substitution risk begins. That is the step manufacturers most often lose invisibly.
Everything lands in Salesforce, HubSpot, Microsoft Dynamics or SAP C4C, so pre-bid work is visible in the pipeline instead of looking like inactivity.
Holcim reports a 400% increase in sales meetings after moving specification work earlier.
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 work projects before the bid?
Find out how Building Radar's revenue engineering solution surfaces design-stage projects and helps you influence the specification early.
Schedule an initial consultation