The Monday Morning Building Product Advisor
​Issue #88

​

You could see it in her body language.

She wasn’t typing. Wasn’t taking notes. Wasn’t even pretending to care. Just that glazed-over stare architects reserve for presentations that feel like code compliance checklists.

This first product rep had been talking for 6 minutes.

Still no mention of the project. No hint he understood the design intent. Just kinda’ stuck on thermal bridging coefficients. So I leaned back and watched the inevitable play out …

The next day, I watched another rep do something different.

She didn’t start with performance data or even open a slide deck. She just said:

“This building is going to change how this thinks about mixed-use development. I’ve worked on three mixed-use towers where the developer was trying to attract Class A tenants outside the core. Here’s what worked… and what didn’t.”

And just like that… the architect leaned forward.

​

The hidden cost of spec-first selling

Look, I’m not suggesting you ignore technical requirements.

• Building codes exist
• Structural loads are real
• Engineers have to sign off on performance data

I think most reps think they’re being helpful by leading with technical specs. But to an architect, you’re teaching them to see you as just a commodity supplier, not a strategic partner.

Consider what happens in a typical presentation:

• You open with test results → The architect thinks: “This is a compliance discussion.”
• You compare thermal values → The architect thinks: “This is a performance comparison.”
• You discuss installation methods → The architect thinks: “This is an execution decision.”

And when the room shifts from design partner to vendor, you’ve already lost the job.

​

Here’s what to do instead…

The best reps I’ve worked with do one thing consistently. They know how to put the specs into context for the architect or their client.

​

Don’t say: “Our curtain wall delivers superior thermal performance with U-values of 0.28 BTU/hr-sf-°F.” [That’s what they all say!]

Try this: “Are you targeting LEED Platinum certification? In a competitive rental market, energy efficiency stands out. It impacts operating costs and attracts tenants. Our curtain wall technology is how we deliver the performance numbers your energy consultant needs to hit those targets…”

​

Don’t say: “Our modular installation reduces field labor by 40%.” [This is where most architects start to glaze over!]

Try this: “Right now, skilled curtain wall installers are booking six months out. And weather delays are adding weeks to project schedules. Our installation methodology reduces both labor dependency and weather exposure, giving you schedule control that most contractors can’t promise…”

​

Don’t say: “We provide comprehensive technical support throughout the project.” [What’s that even mean?!?]

Try this: “Complex facades create coordination challenges that can derail budgets and schedules. Our technical team acts like an extension of your project management. We spot possible conflicts before they become field problems. It’s the difference between managing a crisis and preventing it…”

You’re promoting the same product and technical specs. But you’re creating a very different conversation.

​

You don’t need to be an architect, but…

You do need to sound like someone who’s been in their meetings.

Align your words with their priorities. You know… like design intent, approval timelines, and reputational risk. The more you can do that, the more they trust that you “get it.”

And that trust can help buy you permission to guide the conversation.

​

Your Next Move: The Context Audit

Pull out your standard presentation and run it through this filter:

The Technical Translation Test:

• For each technical spec, can you explain the business problem it solves?
• For each test result you show, can you explain the competitive advantage it creates?
• For each compliance requirement you meet, can you describe the risk it eliminates?
• For each feature you mention, can you quantify the schedule or cost benefit?

Architects don’t just want your specs. They want some perspective. Start there.

​

P.S. I’m putting together a step-by-step workbook. With it, you’ll be able to turn your product features into a compelling story. One that hits your audience’s pain points. Whether it’s an architect, engineer, builder, or developer.

It’s called “The Story Advantage: 30-Day Playbook.”

If you’re interested, REPLY to this email saying “Story Advantage,” and I’ll add you to the waitlist. And when I release it, you’ll be one of the first to know.

​
That's it for this week!

Cheers to building more than just buildings, and see you next week,

​

Neil "Tell-Me-A-Story" Sutton
​Architect | Speaker | The Product Rep Coach

=======

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, hit reply, and let's chat about how I can help.
• Business owners or Team Leaders: You can book an Architect Connections Training for your team. Hit reply, and I'll send you the details.
• Speaking: If you’d like me to present at an upcoming group meeting, reach out, 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.
​=======