Short answer: Reach architects around a specific live project, not with a general introduction. An architect at design stage has an unsolved technical problem and a deadline; a manufacturer who helps solve it is useful, and a manufacturer offering a portfolio overview is an interruption. That means the hard part is not the outreach itself — it is knowing which architect is working on which relevant project, right now.
What architects actually need from manufacturers
Ask specifiers what makes a manufacturer easy to work with and the answers are consistently unglamorous:
Technical data that is current, complete and findable. Performance values, test reports, declarations of performance, certifications valid in their market.
Files in the formats they work in. CAD and BIM objects that behave correctly in their software, at the right level of detail.
Specification text they can adopt. Written the way specifications are written in that market, not marketing copy.
Honest limits. A manufacturer who says where their product does not fit gains more credibility than one who claims universal suitability. Specifiers carry liability for these decisions.
Comparable reference projects. Same building type, same scale, ideally same country.
Speed. An answer within a day during design phase is worth more than a perfect answer in a week.
Nothing in that list is a relationship-building activity. The relationship follows from being useful on a project, not the other way around.
What gets ignored
Generic introductory emails with no project reference
Company and portfolio overviews
Invitations to events with no technical content
Product brochures without performance data
Follow-ups asking whether the last email was received
The common feature: they ask for the architect's time without offering anything for a live problem.
The project-based approach
The order most manufacturers use is: build relationships, then hope projects follow. Reverse it.
Step 1 — identify projects in the influence window. Design-stage projects in your target markets and building types, relevant to your specific product category. This is the genuinely difficult step, and everything else depends on it.
Step 2 — identify the individual, not the practice. Practices rotate project teams. The name on the planning application is frequently not the person writing the specification. You need the individual handling this project.
Step 3 — approach about that project. Reference the project, name the technical question your product addresses, and offer something concrete: specification text, a performance comparison, a reference project of comparable type.
Step 4 — be useful without pushing. At design stage the architect is not making a purchasing decision. Pressure at this point signals that you have misread the situation.
Step 5 — return when the project moves. Design completed, permit granted, tender announced. Follow-up triggered by project events rather than by a calendar reminder is what separates a system from good intentions.
Why step 1 is where most efforts stall
Finding design-stage projects manually means monitoring planning applications, building permits, design competition results, developer announcements, architectural press, local news and construction signage — across every market you sell into, in multiple languages, with the same project appearing under three different names.
That is the problem Building Radar exists to solve. Projects are detected at planning and design stage across more than 50 countries and scored against your specific portfolio, because Jeane, the intelligence inside Building Radar, reads your website, product catalogues and technical data sheets. The deciding role arrives identified, with reachable contacts, rather than as a firm name. And because Jeane also reads your CRM and email history, a practice a colleague already works with surfaces as an existing relationship rather than as a cold contact.
Building the practice relationship over time
Individual projects are the entry point. The compounding value is at practice level.
Track which practices specify you, and how often. A practice that has specified you three times is a different prospect from a new one, and should be handled by a different playbook.
Offer CPD or technical sessions once you have credibility. These work as a follow-up to useful project work and fall flat as a first touch.
Keep BIM objects and data current. An architect who cannot find your object will not use it. This is passive but necessary — it removes a barrier rather than creating a conversation.
Feed specifier questions back to product management. The certifications and performance values that keep coming up are a product roadmap input that most manufacturers never capture.
What to measure
Share of first contacts made with the specifying role rather than purchasing
Average project stage at first contact
Response rate on project-specific versus generic outreach
Specification rate by practice
Repeat specification rate — the real measure of relationship quality
Frequently asked questions
How do you get a product specified by an architect? By engaging during design with technical input on a specific project, supplying adoptable specification text and current performance data, and being honest about where the product does not fit.
When should you contact an architect about a project? During early or detailed design, before the specification is issued — typically six to twenty-four months before an order.
Do architects respond to cold outreach? Rarely to generic introductions, considerably more often to messages referencing a specific live project and offering relevant technical input.
Are BIM objects necessary? For many product categories, effectively yes. Missing or outdated objects exclude you at design stage without anyone telling you.
Who decides the specification if not the architect? On technical building services, usually a specialist planner. On design-and-build contracts, the general contractor holds far more influence. It varies by product category and contract model.
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 reach specifiers on live projects?
Find out how Building Radar's revenue engineering solution identifies design-stage projects and the architects working on them.
Schedule an initial consultation