The Monday Morning Building Product Advisor
|
She just used a better system. You donât need anything complicated. In fact, the simpler the system, the more likely youâll stick with it.
Here are the two routinesâŚ
This routine happens before you start the car.
After every meeting with an architect, spend 60 to 90 seconds recording a voice memo on your phone. Donât overthink it. Just talk about what happened while itâs still fresh in your mind.
[Unless it went like hot garbage⌠then maybe itâs best to wipe it from your memoâ No! Nope⌠Never mind. I guess you still need to capture what went wrong and why. Letâs keep going.]
Your recording could be something like:
âGood meeting with Bob at ABC Architects. He mentioned theyâve got a healthcare project coming up in Q3. Itâs still early, but itâs worth watching. Heâs been dealing with acoustic complaints between exam rooms on his last two projects. Clients keep getting complaints about it after occupancy. He lit up a bit when I mentioned weâd solved that for another firm. Worth following up in about 6 weeks.â
Thatâs 90 seconds. Done before youâve even buckled your seatbelt.
The voice memo does two things for you.
This helps you catch important details while theyâre still fresh. Talking about the meeting out loud also helps you spot small but important points. If you wait, youâll only remember the simple stuff.
You might think you can skip this step because the meeting is still fresh and you believe youâll remember everything.
Spoiler: You wonât. I wonât. Even Megamind wonât.
We wonât remember the specifics. Not the details that matter.
Spending 90 seconds in the parking lot recording a voice memo can really help. With those details, you can come back in six weeks with a useful question or solution. If you skip it, youâll just show up next time with a smile and maybe some donuts.
Which one do you think will work out better for you?
Spend 20 minutes every Thursday afternoon turning your voice memos into a short note for each architect you visited.
You only need 4 fields. Thatâs it.
The âNext questionâ field is the one most reps skip, but itâs the most important!
Hereâs why: It turns your notes from a simple record into a plan for your next visit. Donât just write down what happened. Prepare for your next conversation before you even leave the parking lot.
If you do this consistently for 6 months, youâll have something no competitor can buy or borrow. Youâll know exactly what matters most to each of your top architect relationships. Not just in general, but for each current project and client.
Thatâs what makes it possible to ask the right, problem-focused question. Itâs not intuition or charm. Itâs having a written record of what matters to each person.
1) 90-second voice memo in the parking lot
2) 4-field note on Thursday afternoon
Thatâs the whole system.
Over time, this system leads to results that are hard to match. Youâll be the rep who walks back into a conversation six weeks later and says:
âLast time we talked, you mentioned acoustic issues between exam rooms. Did you ever get that resolved?â
To an architect, that question feels like magic.
But it's not magic. Itâs that voice memo and the 4-field note. Thatâs all.
If you do this consistently, you'll become someone different in your territory. Not just more organized, but more worth calling. And architects can feel that difference the moment you walk back in.
Next week, weâll wrap up this series with the question that youâve probably been asking yourself along the way.
You now know how to score your territory. You can sort your relationships and document what matters. And you can also invest your energy where it really counts.
But what about the other 80%? The architects who arenât ready yet. The ones on the low-cost track.
Do you just let them go cold and hope they get in touch when the time is right?
No, thereâs a better answer. Itâs simpler and much more valuable than most reps expect.
More on that next week.
â
That's it for this week!
Here's to building more than just buildings, and see you next week,
Neil "mind like a steel trap" 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:
=======
âIf this was forwarded to you, go to â mmbpa-newsletter(dot)carrd(dot)co â so you donât miss the next lesson.
â=======
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.
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...