šŸ›ļø PRODUCT REPS: What have you done for me lately...?


The Monday Morning Building Product Advisor
​
Issue #109

About 6 years ago, this newsletter was in its wee early stages.

I had a whopping 10 people signed up.

[And 1 of them was me!]

Back then, I wasn’t active on LinkedIn or any social media, so I was depending on someone stumbling across my website and signing up.

[In other words, I didn’t know WTH I was doing.]

And I eventually gave up and stopped writing those emails.

But then, in early 2023, I took several courses and learned how to write for online audiences. And in April of that year, I got brave enough to actually write my first LinkedIn post. [I’ve written another 500 posts since then…]

And in December of 2023, I finally resurrected this newsletter and have been sending it out (almost) every Monday since.

ā€œThat’s nice, Neil… Why you telling me this?ā€

Well, I was just going through some of those old original emails, and stumbled across one that I think is very relevant today.

In fact, I’ve shared this example as recently as last week.

Today’s email is an updated version of the one I originally sent on June 30, 2020. It was the second-to-last email I’d sent before quitting.

I hope it’s helpful…

What have you done for me lately…?

There’s a rep I work with regularly.

Good product. I specify them on almost every project.

Anyway! They call me every few months to check in, ask what’s on my boards, and close every conversation the same way:

ā€œLet us know when you’ve got something going out to bid.ā€

Do I call them when I do?

Honestly? Na-a-h-h-h.

Not because I don’t like them. It’s because they haven’t really done anything for me. If anything, I’m the one doing them a favor by specifying their product.

So when I’m juggling 1,000 things as a project goes out the door, that call doesn’t make the list.

Now compare that to what happened a few weeks ago…

I had a hospital project CD deadline coming in hot, and a hardware schedule that [no matter how hard I clicked my heels & wished] just wouldn't write itself.

If you’ve never had to spec door hardware for a healthcare facility, count yourself lucky! Security requirements, automation, code compliance, infection control… It’s one of those tasks architects dread and put off until the last possible moment.

But then, out of the blue, a knight on a white steed galloped up to save my bacon!

A rep, I’d never met before, stepped in and did the whole thing. He gathered the information. He sorted out the complex door types. And put together complete hardware sets for every opening on the project.

When we finished going through everything, he said, ā€œHey, would you mind giving me a heads-up when this goes out to bid? I’d love to make sure my team gets a shot at it.ā€

I was like, ā€œAbso-freakin’-lutely.ā€

And I meant it. Two months ago, I didn’t ā€œknow this guy from Adam.ā€ Now I’m ready to go out of my way to make sure he gets a fair shot at the project.

That’s the difference between being present and being indispensable.

So here’s the question: which one are you?

If you offer something that saves an architect real time or headache…

  • Help with specifications
  • Code compliance help
  • Design Assist
  • Takeoffs
  • …Anything

… Are you making sure they actually know you offer it?

Don’t assume!

Many architects, especially younger ones without mentors, don’t know these services exist. They think they have to figure it out on their own.

Tell them.

In your presentations. On your website. And in a one-pager that exists for no other reason than to explain what you’ll do for them and what it’ll save them.

Because that’s how you get the phone call.

​
That's it for this week!

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

Neil "Keep-on-doing" Sutton
​
Architect | The Product Rep Coach

=======

P.S. This is exactly the kind of thing I dig into with the reps I work with. Figuring out where the "indispensable" opportunity is hiding in what you already offer. And how to make sure the right architects know about it.

If that's something you'd want to think through, reply to this email, and I can share more.

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

Monday Morning Building Product Advisor

Connecting with architects should be simple. I'm a veteran architect (28+ years) who's been helping architectural product reps get even better at it for 11 years. So we're all working toward a stronger industry. Get the weekly insights by signing up here.

Read more from Monday Morning Building Product Advisor

The Monday Morning Building Product AdvisorIssue #112 Let me describe someone on your call list right now. You’ve been visiting this architect for a while. The relationship feels warm. They let you buy them lunch, attend your CEU presentations, and ask good questions. Every time you leave their office, you feel pretty dang good about things. But wait… should you? I mean, when was the last time they specified your product? If you had to think about that for more than 5 seconds, you might be...

The Monday Morning Building Product AdvisorIssue #111 Most reps I work with are busy. And as someone who’s spent decades on both sides of that relationship (as an architect and as a coach), I can tell you the busyness isn’t the issue. Tell me if this sounds about right: You take long drives each week to cover your territory. Your calendar is full. You’ve got CEU presentations scheduled 3 weeks out. But if we look closely at your territory, the same uncomfortable image would likely show up…...

The Monday Morning Building Product AdvisorIssue #110 While I was talking with a client last week, I shared this story. As I explored better ways to solve it, I found a pretty sweet framework to address it. Unfortunately, it’s stuck in my head, and I keep thinking about it, so I thought I oughta’ share it with you, too. Anyway! Let’s go to the background story… A rep I know [we’ll say he’s called ā€œJohnā€] lost a specification on a very nicely sized project last year. And it wasn’t because his...