How do I get my product specified by architects?
Get your product data in front of them before design decisions are made, in the format their software uses, and be a name they already recognise when the question comes up. Specification is largely settled between RIBA Stages 2 and 4, which is months before anyone orders anything, and it's decided by people who choose from what they know and trust.
Two things go wrong for manufacturers trying to get specified, and they are opposite problems.
The first is turning up too late, at the point where someone is pricing a job, when the specification has already been written and the only conversation available is about price against a product that's already named.
The second is treating it as purely a data exercise. Getting your product sheets onto the right platforms matters, and plenty of firms stop there, then wonder why nothing changed.
When specification actually happens
The RIBA Plan of Work is the frame most practices work to, and it's worth knowing where you fit:
- Stages 0 to 2. Early thinking. Designers look at what has been done elsewhere, which is why your case studies and your CPD matter more here than your technical data.
- Stage 3. The design develops and product data becomes critical. Declarations of performance, certification and sustainability data need to be available digitally, or you are simply harder to include than the alternative.
- Stage 4. The specification is written. Your data gets aligned to specification clauses, or it does not.
- Stages 5 to 7. Installation, warranty and maintenance information. Product queries, proposed alternatives and delivery decisions may still need your support.
Most manufacturers put their effort into Stage 4 and later. The firms that get specified consistently are present at Stages 0 to 2, when nobody is asking them for anything. NBS sets this out from the specifier's side and it's worth reading in full if you sell into practices.
A stage-by-stage checklist
It's worth running through this for each application you sell into. The evidence a hotel refurbishment needs is rarely the same as a school or a warehouse, so a checklist per application tends to be more useful than one for the whole range.
| Stage | Have ready | A useful action |
|---|---|---|
| Stages 0 to 2 | Two or three completed projects in the sectors the practice works in, with the application named and photographs you have permission to use. A CPD session or short technical guide that teaches something. | Get to know the practices working in your sectors and offer a relevant case study or CPD before any project needs you. |
| Stage 3 | Complete product data on the platforms specifiers use. Declarations of performance, test reports and certificates for the application in question. Sustainability information, such as an EPD, where you have one. BIM objects where they're relevant. | Answer technical questions quickly, with evidence that matches the use the design team has in mind. |
| Stage 4 | A specification clause in the format the practice works in, with options and limitations stated plainly. Installation details and the junctions the team will need to draw. | Check with the specification writer that the clause covers the performance they need, and flag anything that needs technical review. |
| Stages 5 to 7 | Installation guidance, warranty terms, maintenance and replacement information, and a clear response ready for proposed alternatives. | Support the contractor and installer on site, and gather feedback and photographs for your next case study. |
Technical evidence that matches the application
"Available on request" tends to slow a design team down. What helps is evidence that answers the question for the use they have in mind. A few examples of how that looks:
- Wall panels in a hotel corridor. Reaction to fire classification for that location, cleaning guidance for heavy use, impact resistance, and how a damaged panel is replaced without disturbing its neighbours.
- Flooring in a care home. Slip resistance test data in wet and dry conditions, cleaning and infection control guidance, and impact sound performance between rooms.
- A roofing system on a refurbishment. Compatibility with the existing deck, wind uplift calculations for the site, the warranty conditions, and who inspects the installation.
- Balustrading on a residential block. Test evidence for the loads involved, fire performance where it applies, and the fixing details the design team will need.
Keep each piece of evidence tied to the product, the test standard and the conditions it covers. If something hasn't been tested for that use, say so and offer a route to find out. Design teams remember the manufacturers who were straight with them.
The four things that make a product easy to specify
- Data where they already work. Product information on the platforms specifiers use, with the certification and performance data complete rather than "available on request". An incomplete entry is a reason to choose someone else.
- BIM content. Where relevant, usable BIM content can help a design team assess and coordinate your product. Inclusion in a model does not guarantee a specification or an order.
- A specification clause they can drop in. Make writing you into the spec a two-minute job, not a research project.
- CPD. A session that teaches something useful can help a technical team understand your expertise. Its value depends on the topic, audience and quality of the learning, alongside responsive support afterwards.
The part nobody writes about
All of that makes you specifiable. It doesn't make you the one specified.
An architect writing a specification is choosing from a shortlist in their head, and that shortlist is made of people and products they already know.
Which is why the manufacturers who do well here tend to be visible to specifiers continuously, not in bursts. They know which practices work in their sector and their region. They know who the technical lead and the specification writer are at each one. They turn up with something relevant about a scheme that practice is working on rather than a product brochure.
It's slow, and it has very little to do with marketing in the usual sense. It's closer to how a good rep worked twenty years ago, done at the scale a small team can manage.
What about the contractor?
Worth saying plainly: being specified isn't the end of it. On most projects the contractor can propose an alternative, and value engineering removes specified products regularly. So the relationship with the main contractor, the QS and the subcontractor who installs your product matters as much as the one with the architect. Firms that only court specifiers get written in and then swapped out.
Where this doesn't apply
If your product is a commodity bought on price from a merchant, none of this is your route. Specification work suits products where performance, certification, warranty or appearance genuinely differ. If yours does not, the honest answer is that distribution and price will decide it, and your money is better spent there.
The questions that come with it
At what stage should I approach an architect about my product?
Early, at RIBA Stages 0 to 2, when the practice is still looking at precedents. By Stage 4 the specification is being written and the decision is largely made.
Does getting my product on a specification platform mean architects will use it?
It makes you findable, which is necessary but not enough. Specifiers tend to choose from products and manufacturers they already know, so visibility with the practice matters alongside the data.
Who actually writes the specification?
Usually the architect or a specification writer within the practice, sometimes with input from a specialist consultant. On larger schemes a dedicated specifier may own it.
Can a contractor substitute a specified product?
Often, yes. Alternatives get proposed at tender and during value engineering, which is why relationships with the contractor, the QS and the installing subcontractor matter as well as with the architect.
Is CPD still worth doing?
Yes, when it teaches something useful rather than pitching a product. It remains one of the few ways a technical team gets to know a manufacturer properly.
Being known to the practices that specify your sector
That's the work we do. We'll show you which practices we would target, who we would be talking to there, and the messages we would send.