The Monday Morning Building Product Advisor
​Issue #102

If I had a nickel for every time a rep sat across from me and said their product was “high quality”…

…I’d have retired from architecture years ago.

Instead, I’ve spent 28+ years in that chair. I’ve usually got a deadline hanging over my head, and I’m only half-listening to another “pitch” that sounds like the last three.

Not because I’m rude. [At least I TRY not to be.]

It’s because when you’ve heard 5 versions of “great service and unmatched quality” in one week… it becomes white noise.

You’ve GOT to realize: You’re not just competing with other products. You’re competing with the architect’s exhaustion. And unless you give us something specific and memorable, you will NOT be the product we defend when things hit the fan.

So today, I’ll show you exactly how to fix this.

It’s a dead-simple framework to go from “sounds like everyone else” to “holy crap, this rep actually gets us.”

No fluff. No buzzwords. Just one clear reason we should bother specifying you.

What a USP actually is (and what it isn’t)

A USP (or Unique Selling Proposition) is the clearest reason someone should choose you instead of your competitors.

It’s not a catchy slogan you slap on a trucker hat. It’s not your mission statement. It’s definitely not the features list in your spec sheet.

Think of it this way. If an architect is looking for a window, they have a thousand choices. But if they’re looking for a window that can handle Category 5 hurricane winds without looking like a heavy industrial porthole, and you’re the only person who can deliver that… suddenly, the other 999 options don’t matter.

A strong USP lives where these 3 things meet:

• Who you’re talking to (architects designing a specific project type)
• What problem you solve better than alternatives […not just differently, better]
• Why that difference actually matters to them [reduced risk, easier specs, happier clients, fewer Friday afternoon phone calls during CA]

Your USP is the key point you want architects to remember. It’s what they’ll say when your name comes up in a project meeting. If they can’t remember it or wouldn’t bother repeating it, you don’t have a USP yet.

It’s still just a sales pitch that sounds like everyone else’s.

Why USPs matter

In most industries, price and availability drive decisions.

You already know architectural sales don’t work that way. We specify products before pricing gets involved. We’re selecting you because we trust you. We want to reduce risk and make sure you solve a problem we care about.

By the time your product shows up in a bid, the decision is already half-made.

A strong USP is a risk reduction strategy.

When you have a clear USP, you aren’t just selling “stuff.” You’re selling a shortcut. You’re giving that architect a reason to tell the General Contractor, “No, we aren’t accepting a substitution for this, and here is exactly why.”

You’re giving us the ammo to defend you.

The traps most reps fall into (the “Empty Word” Graveyard)

Here’s what doesn’t work.

I’ve heard these claims 1,000 times from my desk, and every architect you’re calling on has heard them too.

“We offer high quality.” (Everything should be high quality. That’s the baseline.)

It means nothing. Quality compared to what? Measured how? Proven where? I’ve had reps tell me their product was “high quality,” only to watch it fail in the field 6 months later.

“We provide great service.”

This one’s especially common. And we’ve heard it from every rep who later disappeared when problems showed up during construction. Or the ones who ghost us when we need a quick answer for an RFI.

Service is table stakes. That’s not a USP unless you can point to something specific and provable. Like… “We respond to all RFIs within four hours during business days” is specific. “Great service” is not.

Feature-only differentiation.

“Our panel system has a proprietary locking mechanism with a 17-point engagement system and thermally broken aluminum extrusions.”

Great. But do I care right now? Does it solve a problem I’m actually facing on this project?

Features matter, but only when they’re tied to outcomes we value. Otherwise, it’s just technical noise.

Here’s the pattern you hopefully noticed:

All these claims are either too vague to be believable or too product-focused to be relevant to what we’re actually trying to accomplish. We don’t care about your features. Not really. We care about OUR problems. Or our CLIENT’S problems.

Your USP MUST connect those dots.

The simple USP Builder (your new framework)

Most reps think their product is a commodity.

They stare at the same specs their competitors have… same R-values, same ratings… and think:

“There’s nothing special here. It’s all the same.”

Wrong. You’re just talking about it the same way.

Here’s the fix: Use this fill-in-the-blank formula before your next meeting.

We help [specific audience] achieve [specific outcome] by doing [distinct approach]. That matters because [risk reduced or value created].

Let’s break it down:

[Specific audience]: Who exactly are you serving?

Not just “architects.” Pick a team & context:

• healthcare teams trying to avoid late compliance surprises
• K-12 teams racing a bid date
• multifamily teams avoiding acoustic complaints

Focus question: Who feels this pain the most in your territory?

[Specific outcome]: What does success look like for your audience?

“Better performance” is still vague. Instead, try:

• fewer RFIs (less time drain)
• fewer substitutions (design stays intact)
• smoother install (less jobsite drama)

Focus question: What gets easier, safer, or more predictable when your system is on the job?

[Distinct approach]: This is where you name what you do differently.

Don’t just say, “we care.” Tell me what you do.

Examples:

• You provide a project-specific detail package that prevents common failures
• You run a pre-submittal review so the team doesn’t get trapped in resubmittals
• You give vetted alternates upfront (with documentation) so VE doesn’t wreck the design

Focus question: What do you do consistently that competitors don’t, won’t, or can’t?

[Why it matters]: Connect your approach to something painful we’d rather avoid:

• late redesign during DD or CD
• coordination conflicts between trades
• value engineering that changes the design intent
• change orders and finger-pointing

Focus question: What bad thing are you helping them not experience?

You probably already do something worth specifying. You just haven’t learned how to say it yet.

Still not sure? Here are a few Before & After examples…

Here’s the difference between a generic pitch and a strong USP…

Example 1: Exterior Insulation System

Generic version: “We manufacture a high-performance continuous insulation system with excellent R-values and third-party tested fire ratings.”

USP version: “We help architects on multifamily projects meet energy code without adding wall thickness, using a compressed mineral wool system that stays within standard framing depths. That matters because you avoid costly redesigns and keep the envelope on schedule.”

See the difference? The second version clearly states who it’s for, what issue it addresses, and why that issue matters.

And it tells me you understand the actual constraints I’m dealing with. Adding thickness to a wall assembly on a multifamily project is a nightmare. It affects everything from property lines to unit layouts to window details.

Example 2: Acoustic Ceiling Tile

Generic version: “Our ceiling tile offers superior acoustics, Class A fire rating, and multiple sizes and finishes.”

USP version: “We help architects designing open-office spaces meet acoustical targets without sacrificing daylighting, using a tile that absorbs sound and maintains reflectance values above 0.85. This matters because you don’t have to compromise energy performance for comfort.”

Again, same product, but now I know exactly when to think of you.

If you give us something we can repeat in a project meeting, you get specified.

If not, you’re just another product waiting to get VE’d off the job.

A little secret from my side of the desk…

…Most architects want you to be the expert.

We can’t possibly know everything about every material. We’re looking for someone to grab us by the shoulder and say, “Hey, for this type of building, don’t do that… Do this instead. Here’s why.”

That’s what a USP does. It’s a sentence that positions you as the expert who “gets it.”

Homework (the easy kind)

Before your next meeting, I want you to try this. Forget the “about us” slides for a minute. Think about the last time an architect or contractor thanked you because you saved their skin.

• What happened?
• What was the specific mess you cleaned up?

That “mess” could be where your USP is hiding. Write it down using that framework above. It’ll feel a little clunky at first. That’s okay. Real conversations are a little messy.

Then send me your draft USP, and I’ll send you my quick feedback. (Seriously… I will.)

And if you want my help really digging into your product or business to help you extract a great USP, HIT REPLY and I’ll send you details. You’ll even get a roadmap to help you put that USP into place in your business.

​
That's it for this week!

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

Neil "Spillin’ Secrets" 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, hit reply, and let's chat.
• 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.
​=======