How to approach architects on LinkedIn as a building product manufacturer

The short answer

Approach an architect on LinkedIn with a clear reason your product category relates to their work. Refer to a real project or design question, offer one useful piece of information, and make the next step easy to answer. Use the conversation to establish relevance before asking for a meeting or discussing a specification.

An architect does not need your complete product range in the first message. They need to understand why you have contacted them and whether you can help with something they actually work on.

If you have not yet chosen the practices to approach, use our guide to building an architect target list first. The quality of the message depends on the quality of that research.

Make your profile useful before you reach out

Give the person who visits your profile a clear explanation of the product, its applications and your role. Show relevant project examples and provide a straightforward route to technical information or the colleague who can answer detailed questions.

A manufacturer’s representative might explain which sectors they support and how they help design teams assess suitability. If your role is commercial rather than technical, make the handover to your technical team clear.

Check any performance, environmental or certification claims before publishing them. Use evidence that applies to the product and application being discussed. A confident headline should not leave an architect with a misleading impression of what has been tested or verified.

Find a reason that belongs in their working day

A useful reason for contact could be a recently published project, a sector the practice works in regularly, a material the team is exploring or a design issue they have discussed publicly.

The connection to your product needs to make sense. Congratulating someone on an award and immediately sending an unrelated catalogue does not explain why the two businesses should know each other.

For example, a wall-panel manufacturer could refer to a hospitality refurbishment the practice has published, then offer a short case study explaining how panels were maintained in a comparable setting. That gives the architect enough context to decide whether the information is relevant.

Keep the first message focused

The following examples illustrate the approach. Use them only when the project reference and the resource you offer are real.

For a manufacturer supplying hospitality interiors:

I saw the restaurant refurbishment your team shared recently. We manufacture wall panels for hospitality projects, and have a short case study covering cleaning and replacement access in a similar setting. Would that be useful for your materials library?

For a manufacturer offering technical support:

Your recent post about refurbishment constraints caught my eye. Our technical team has put together a guide to the fixing details for our panel system in retrofit applications. Would you like me to send it across?

Both messages give a specific reason for contact and offer something the person can accept or decline. Neither assumes that the architect has a live requirement or that the product is suitable before the technical work has been done.

Send the resource you offered

When someone says yes, send the relevant case study or guide with a short explanation of what it covers. Use one clear link where possible, so they can get to the information without sorting through a collection of attachments.

Make sure the page identifies the application, the product used and any important limitations. If they ask a technical question, involve the colleague best placed to answer it. NBS’s discussion of supporting specifiers highlights the value of responsive technical help alongside the product data.

A useful follow-up question might be: “Is this the sort of application your team handles, or is there a colleague who looks after that package?” That helps establish the right contact without pushing for a meeting before there is a reason for one.

When the right person is a colleague

Often the person you've reached isn't the one who handles your application, or their question needs your technical team rather than you. Both are good outcomes if the handover is clean.

If the architect points you to a colleague:

Thanks, that's really helpful. I'll get in touch with Sarah and mention you pointed me her way, so my message doesn't arrive out of the blue.

Then to the colleague:

Hi Sarah, Tom mentioned you look after the interiors packages on the practice's hotel work. We manufacture wall panels for hospitality projects, and I'd sent him a case study on cleaning and replacement access. Would it be useful if I sent it your way too?

If the question needs your technical team:

That's a good question, and I'd rather you heard the answer from someone who works on it every week. Our technical lead, James, handles fixing details for retrofit projects. Would a short call with him suit, or would you prefer the answer in writing first?

Introduce the colleague by name, explain why they're the right person, and stay in the conversation so the architect isn't passed around. Update your record with the new contact rather than starting them on the same sequence as everyone else.

Let the conversation determine the next step

The appropriate next step depends on what the architect needs. It may be a sample, a technical discussion, a visit to an installation or a CPD session. Continuing professional development, or CPD, should teach something relevant to the audience rather than turn into a product presentation with an educational title.

NBS’s guidance on engaging specifiers discusses education, product information and collaboration as complementary ways manufacturers can support design teams.

If you offer a CPD, explain its learning objectives, intended audience and format. Describe accreditation accurately. A useful technical conversation can also happen without a formal session.

Follow up when you have a reason

A follow-up should help the architect move the discussion forward. You might answer the question raised in their reply, send the promised detail or share a newly completed example relevant to their sector.

If someone has not replied, one brief reminder can be reasonable. If there is still no response, give them space. Return when there is useful new context rather than repeating the same request every few days.

Keep a record of what was offered and any commitment you made. Promising a sample or a technical answer and failing to deliver it undermines the relationship you are trying to build.

Following up after a sample or a CPD session

A sample or a CPD session gives you a natural reason to check in, as long as the follow-up is about their project rather than your product.

After sending samples:

Hope the samples arrived safely. Once the team has had a chance to look at them alongside the other finishes, I'd be glad to hear what worked and what didn't. If the colour or the edge detail needs to change for the scheme, our technical team can look at that.

After a CPD session:

Thanks for having us in on Thursday. A couple of your team asked about fire performance in refurbishment work, so here's the test summary we mentioned. If it would help to talk through a live project, Emma from our technical team is happy to join a call.

Give a sample a week or two before checking in, and follow up a CPD within a few days while the session is still fresh. If nothing is live yet, note when the next project might start and come back then with something useful.

Support the specification conversation properly

Once a live application comes up, establish the project requirements with the relevant team. Provide the product information and evidence they need to assess suitability, and be clear about questions that need further technical review.

That work continues beyond an initial introduction. A positive reply is not a specification, and being named in a specification does not guarantee an order. Project roles, procurement, technical requirements and proposed alternatives can affect what is ultimately purchased.

Our guide to getting your product specified by architects explains the wider relationship between product information, timing and the people involved.

Measure progress towards a genuine requirement

Track the stages separately: a relevant conversation, confirmation of the right contact, a sample request, a technical review, a specification discussion and an eventual order. Only mark a stage as confirmed when you have evidence for it.

This makes it easier to see whether your activity is reaching the right people. It also gives your commercial and technical teams a shared record of what the architect needs next.

Want more useful conversations with architects?

Tell us who you want to reach and what your product helps them achieve. We can discuss a personal LinkedIn approach your commercial and technical teams can support.