The Monday Morning Building Product Advisor
​Issue #117

Do you know the most “dangerous” moment between an architect and a sales rep?

It’s not during the first cold call, the first handshake, or even when the project goes out to bid.

It happens while you’re still talking about product features and performance numbers. Somewhere in the middle of that, up inside my architect-shaped melon, I’m thinking about something very different from what you might expect.

I’m not asking myself, “Is this product good?” I usually know that already.

Instead, I’m wondering, “Can I defend my choice if something goes wrong?”

Most reps don’t realize I’m asking that question. But it’s the one that decides if your great presentation leads to a real project, or just a polite “I’ll keep it in mind” and a brochure that never gets opened.

This is what’s called your “Why True?” problem.

This is also your biggest opportunity, if you’re willing to think it through. Today, I’ll show you what this silent evaluation looks like from my side, and how you can pass it.

Let’s get rockin’.

Architects aren’t skeptical to be difficult. It’s because our license is at stake.

When architects specify a product, it’s more than a purchasing recommendation.

When I specify a product, I’m putting my professional credentials and often my firm’s E&O liability on the line, promising the product will work as described. If it fails, I’m not just embarrassed… I could face contractor disputes, client complaints, insurance claims, or worse.

My license is attached to every decision I put in a set of construction documents.

So when you tell me your product is better than the competition, I want to believe you. But part of my mind is always focused on whether I can defend this decision.

I’m not asking, “Is this chucklehead telling the truth?” [That’s a bit harsh…]

Instead, I’m thinking, “If I had to explain this choice to my client, contractor, or insurance carrier, what would I say?” I’m making this judgment even while you’re presenting.

Most reps don’t even realize this is happening.

But since you’re reading this and now know it exists, you’ve taken the first step toward passing it.

There’s a big difference between proof that sounds like marketing and proof that feels like evidence.

It’s easy to agree with this idea, then go back to your usual approach.

So let’s make sure it’s clear…

Here’s what “marketing proof” sounds like:

“Our system has been tested to exceed ASTM standards.”

But, evidence sounds more like:

“Here’s the third-party lab report from SGS showing our system tested at 1.8x the required load. I’d be happy to send you the full document.”

It’s the same claim, but it carries a completely different weight.

Marketing proof sounds like:

“We’ve been specified on hundreds of projects.”

Evidence sounds like:

“There’s a completed aquatic center about 40 minutes from here that’s been running our waterproofing system for 6 years through freeze-thaw cycles. I can get you the project architect’s contact information if you want to call them.”

Again, it’s the same idea. One is just a talking point, while the other is something an architect can actually act on.

Hopefully, you can see the pattern: Proof that comes from you feels like marketing. Proof from an independent source (a lab, a third-party certifier, another architect, or a completed building they can visit) feels like evidence.

Architects are trained to evaluate evidence on every project. When you bring us real evidence, you’re speaking our language. If you only bring talking points and call them proof, we notice even if we don’t always say so.

The good news is that most reps don’t bring real evidence. So when you do, you’ll stand out right away.

Your most powerful proof is the one you use least.

I mentioned this briefly last week, but let’s go into more detail.

Nothing answers “Why True?” better than showing an architect a completed installation of your product. I don’t mean a showroom or factory [though those are nice to see too]. I mean a real building, in use, under conditions like the ones I’m designing for.

Here’s why it works so well.

When I can stand in a space and see your product performing…

• See the flooring holding up under real traffic
• Feel the curtain wall handling a real weather exposure
• Hear the acoustic system doing its job in a live environment

The question of believability answers itself. There’s no claim to judge. It’s just the product, working right in front of me.

It also does something more subtle.

It shows me that other architects (my peers with the same responsibilities) made this decision before me, and it worked. That’s a kind of social proof a brochure can’t match.

If you can say, “I’d love to show you a project we did with a firm like yours, about 20 minutes from here,” you’ll have a much better conversation than if you just hand over a spec sheet. One approach leads to your brochure being ignored; the other leads to a productive follow-up.

If you’re not already keeping track of completed local installations to show architects, start now. It’s one of the most valuable things you can do, and very few reps do it regularly.

Your own background can also be proof… if you use it the right way.

If you have experience in architecture, construction, or building systems (even if it was years ago), that matters to architects. It’s not that it makes you more likable (though it might). It changes how we receive your claims.

If a rep without technical experience says, “This product performs better in high-humidity applications,” architects hear a sales pitch. But if you’ve worked on buildings and say the same thing, we hear a professional opinion. The words are the same, but the second version has real credibility.

But this only works if you use your background the right way.

If you mention your background as a credential, like saying, “I’m actually a trained architect myself,” it can feel forced. But if you show your experience through how you talk, it becomes real proof.

So, what’s that look like?

• Understanding design intent
• Knowing where a product sits in the construction document sequence
• Anticipating the contractor interface questions before the architect has to ask them

Show your understanding, don’t just say it. If I feel like you understand my challenges, I’ll trust your product claims more.

That’s because you proved it through your actions.

When architects trust you, the rest of the conversation becomes much easier.

That’s the real benefit of getting the “Why True?” question right.

Once an architect truly trusts that your claims are defensible…

And once I have evidence I can share with a client, contractor, or colleague…

The “Why You?” conversation gets much shorter, and the “Why Now?” conversation can actually happen. Skepticism is costly. Every minute you spend addressing doubt is a minute you’re not helping the architect make a decision.

Next week, we’ll wrap up the series with “Why Now?” and why this part is often mishandled. Most urgency in product sales isn’t real… Architects know it, and it undermines everything else. I’ll show you what real urgency looks like and how to use the project timeline to close it out.

​
​That's it for this week!

Here's to building more than just buildings, and see you next week,

Neil "Danger" Sutton
​Architect | Speaker | The Product Rep Coach

=======

P.S. Do you really want inside an architect's head?

When you’re ready, there are 3 ways you can start working with me:

• Product reps: If you want to be better at connecting with architects, reply, and let's chat.
• Business owners or Team Leaders: You can book an Architect Connections Training for your team. Reply, and I'll send you the details.
• Speaking: If you need me to present at an upcoming group meeting, get in touch, and let’s talk!

=======
​If this was forwarded to you, go to → mmbpa-newsletter(dot)carrd(dot)co ← so you don’t miss the next lesson.
​=======