Architects research products to reduce uncertainty. They are trying to understand whether a product fits the design intent, performance need, budget, programme, sustainability requirement and client expectation.
For manufacturers, the lesson is clear: product information must be easy to find, easy to compare and credible enough to support a project decision.
Watch: why practices cannot ignore better research tools
This Architecture Social conversation is useful because product research is changing. Architects still need judgement, but better tools can change how quickly they compare information.
Product research usually starts with a problem
Architects rarely research products in isolation. They usually have a project question: how to achieve a finish, meet a performance requirement, solve a detail, satisfy a client or compare options before a specification conversation.
- What product type could solve this design or technical problem?
- Which manufacturers have credible evidence?
- Is the product suitable for the project stage, budget and location?
- Can the team access drawings, samples, data or technical support quickly?
- What are the risks, limitations and alternatives?
Go deeper with Architecture Social
These related Architecture Social episodes add more context once you have the practical framework.
Listen: AI, practice change and better information
This episode adds a broader view on how technology and information habits are changing inside architecture practice.
What architects look for first
The first scan is often practical. Architects want to know whether the product is relevant enough to investigate further.
- Clear product category and use case.
- Performance data and compliance information.
- Sustainability, warranty and maintenance context.
- Good photography, details, drawings or BIM resources where useful.
- A fast route to technical support or samples.
If that information is hidden, outdated or too sales-led, architects may move on before anyone in the business knows they were interested.
For architects: keep a decision trail
Product research is stronger when the decision trail is visible. Keep short notes on why a product was considered, why it was rejected or why it should be discussed with the client or consultant team.
- Project requirement or design problem.
- Product options compared.
- Key performance, cost or sustainability evidence.
- Questions still needing technical confirmation.
- Who needs to approve or comment next.
This is useful for students and early-career staff too. It shows that product choices are not random finishes, they are design and technical decisions with consequences.
How practices compare products
Product comparison is not only about price. It is about fit. Practices compare evidence, confidence, availability, risk, aesthetics, support and whether the product can survive scrutiny from clients, consultants and contractors.
- Does it support the design intent?
- Can it be detailed properly?
- Is the information current and specific?
- Can the manufacturer support the project quickly?
- Is there a credible precedent or case study?
Where manufacturers lose attention
Many manufacturers lose architects at the information stage. The product may be good, but the research journey makes it hard to trust.
- Important downloads are hidden behind forms.
- Technical claims are broad but not evidenced.
- Case studies do not explain why the product was chosen.
- The website is organised around internal product names rather than architect problems.
- Support is slow or too sales-led.
Make research easier for architects
Better product content should answer the questions architects actually ask. It should help them compare, rule in, rule out and take the next step with confidence.
- Structure pages around use cases and project problems.
- Keep technical files up to date and easy to find.
- Explain limitations honestly.
- Use case studies that show decision-making, not only imagery.
- Make the next step clear: sample, CPD, technical call, directory profile or enquiry.
Common mistakes
- Writing for buyers but not specifiers.
- Assuming architects know the product category already.
- Making every product sound suitable for every project.
- Treating sustainability as a claim rather than evidence.
- Forgetting that architects may research quietly long before they contact sales.
Architecture Social view
Stephen’s industry view is that product research is a trust journey. The easier a manufacturer makes it for architects to understand the product properly, the better chance it has of being remembered when the right project appears.
Next step
Compare your product information with the questions above. Then read how architects engage with manufacturers, review the Architecture Social directory and consider promoting a directory listing if architects need an easier route to discover your offer.
Add a comment