The Monday Morning Building Product Advisor
|
The project isnāt dead, and it hasnāt been handed off to another architect. For now, itās just sitting on a shelf.
We finished the drawings months ago. Everything was specified, coordinated, and ready to bid. But the project went quiet because itās waiting for USDA funding approval before it can move forward.
Weāve seen that wait stretch to 6 months on past projects.
Iāve noticed that most product reps think a finished set of documents means the project is moving forward right away. Thatās not always true. Sometimes, itās just sitting on a shelf, and the reason isnāt about the design.
And itās usually completely out of the architectās hands. But it's helpful for you to understand that it does happen.
From what I hear from other architects, HUD approvals can work the same way for multifamily and public housing projects. Andā¦
Each agency has its own timeline, but the result is the same. The documents are finished, but the project isnāt moving forward right away.
Now, there are other situations where a project does actually die on the vine.
Recently, a rep reached out to ask about a project where he had helped me with some waterproofing details. I checked with the lead architect and found out the developer went out of business. Now weāre waiting to see if a new developer picks up the original plans.
In most cases, product reps donāt check in to find out why.
ā¦And most architects wonāt send an update to every rep who helped us. Weāve usually moved on to other projects to keep our time billable during the wait.
The waiting period isnāt wasted time. Itās actually an opportunity, but most product reps miss it.
Maybe your product has a few changes or updates. If itās the architectās Basis of Design, we would like to know whether we need to make a few quick fixes to the spec.
If there were a code change during the wait, weād really appreciate a heads-up on how it might affect our project.
If a productās lead times change and you have a simple fix for the specs, the waiting period is the perfect time to tell your architect. We arenāt under bid pressure, so we may have time to review and update things before the documents are finalized.
What you donāt want to do during this lull is pitch something new that wasnāt already part of the project.
Save that conversation for another time for the next project.
Once funding is approved and the project goes out to bid, simple changes can become more complicated.
A product update that could have been handled with a quick email during the waiting period now needs an addendum or a change order. That takes longer, creates more paperwork for us, and honestly, weāre much less likely to make the change once weāre busy with other bidding tasks.
So donāt wait for the RFP or a call from the contractor. If you know a project is delayed by USDA, a school bond, or something else, ask your architect directly if itās on hold.
Then make the most of that time.
The rep who called me last week will send me a product update before the project goes out to bid. And I can make a quick change to 2 or 3 lines in the spec. And itās not because heās lucky⦠Itās because he simply asked.
If you have a project that might be on hold right now, reply and let me know what funding source itās waiting on. Iāll let you know if thatās a normal delay or something you should ask about.
ā
That's it for this week!
Here's to building more than just buildings, and see you next week,
Neil 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 #137 Steadfast Steve, Part 2 We found ourselves 900 miles away in Wausau, Wisconsin, sitting at a table to review the shop drawings before they were officially submitted. If you missed last week, hereās a quick recap⦠Steadfast Steve spent around 3 years helping our teams solve curtain wall details, often on projects he wasnāt likely to win. When the research campus moved to phase two, he put in a substitution request for the new system he...
The Monday Morning Building Product AdvisorIssue #136 Steadfast Steve, Part 1 Our design team had a problem at the front door. We were working on a research tower for a big client in town, and our team wanted the main entrance to make a statement. They wanted the curtain wall to blend smoothly into the limestone. With no bulky frame where the glass met the stone. It looked great on paper, but it would be hard to make it happen during actual construction. āSteveā sat at the end of our...
The Monday Morning Building Product AdvisorIssue #135 Hereās what usually happens after a lunch-and-learn. The team eats⦠someone asks a question about your warranty or something⦠someone grabs the leftover sandwiches⦠people thank you as they leave⦠and the person who helped you set it up walks you to the elevator. Afterward, no one feels like they owe you. Youāve probably heard that bringing lunch helps build relationships and earns goodwill. Thatās true! Itās a good way to get your foot in...