Tuesday Email: From Advisor to Architect

Happy Tuesday!

Every Tuesday I'd like to offer strategies for the week ahead and a thought to fuel your action.

The skills that got us to our first $125 million will cap us from getting beyond $200 million.

When we build something that works, produces, and creates without us being involved, we've built a business. When our presence is the linchpin that keeps everything running, we've built a job. A job is right for many people. But those who want to grow at scale need to build a business instead.

As advisors, our identity is stuck in the work — building the portfolio, determining the holdings, running the financial plan. We don't consciously choose this. It just becomes our reality.

We believe clients hire us for all the "how" we provide. In reality, what they want is the outcome we deliver. This is something I struggle with, have struggled with, and continue to struggle with. In a desire to be accepted and valued, I believe that everything I do needs tangibility to drive my worth. Thinking strategically has no tangibility. Building a financial plan has tangibility.

To build something lasting and scalable, we have to shift from the value being the work we do to the value being the processes and systems we build to enable consistent, valuable output by others.

When you think about this evolution, there are three distinct phases which apply both personally and professionally.

The Ending. The moment we decide to relinquish the idea that our identity is tied to being the expert practitioner. We let go of the need to always be client-facing, of that being our primary signal of worth.

The Neutral Zone. This is where we regress. It's the uncomfortable gap between what worked and what's unknown, between familiar and uncertain. The feedback loops disappear. The visible wins vanish. Confidence erodes. Internal doubt sets in. And we're supposed to sit here, in this uncertainty, with an unwavering belief in an uncertain outcome.

But we can’t just sit there. We don’t just sit there. We go back to what we know. We micro-manage. We cling to our expertise. We avoid the things we aren't good at. I have failed here multiple times. Not because I lack the ability, but because I'm human.

Here’s the thing: you act your way into a new identity. You don't think your way into it. And learning by doing is a humbling experience.

The final phase is the new beginning. After navigating through the uncertainty and finding a new way of being and doing, that's where you become enlightened of what’s possible. You see the other side.

But it's not just about navigating phases. There are external and internal legitimacy cues that drive every decision we make.

There's an internal legitimacy crisis in this industry (and within all of us as humans). If we're no longer making the investment decisions, managing the client relationship, or dealing with the fires, we feel like we've lost the right to be in the room. Our legitimacy came from those actions. When we step back, it feels like our legitimacy steps back with us. I've struggled with this directly: what is my value if I'm not deep in it, not doing it alongside the team?

Then you add the external layer. Partners, peers, and team members are socialized to respect rainmakers and technical experts. Building a system is less tangible. Running a process is less tangible. Tangibility drives social validation. And deep down, we all still care about social validation, at least a little.

There's an architect named Eric Reinhold who ran a boutique residential architecture firm. Like advisors, his work was bespoke and expertise-driven. He was capped by his own hours.

So he stopped custom drafting every home. Instead, he created standardized plan sets. He took the inputs behind every great design he'd built, standardized them, and used the time freed up to build a content engine that drove people to his productionized plans. Theis created a transparent process with transparent pricing. The flywheel worked. And it wasn't capped by his personal hours.

We have the same opportunity. Our planning philosophy, discovery framework, and portfolio construction logic are intellectual assets we can productionalize. If we do, more people on our team can execute them consistently. The value we were delivering to 100 families can now reach thousands, without us being the bottleneck.

The pushback is always the same: productionization eliminates personalization. It doesn't.

Productionization means defining the desired output, the desired feeling, and the desired deliverable for every process and workflow, clearly and separately. When you do that, you free up the human element. You elevate how you connect, explain, and relate to the person in front of you. Productionization allows for more human, not less.

Clients don't care about the process you used. They care about the outcome you delivered. If you can productionize the ability to deliver a great outcome consistently, that's what matters, whether it's model portfolios or individual holdings.

In the world of AI, a sub-10-person firm can now deliver value like a hundred-person firm. That's the opportunity.

But there's a U-curve to be aware of.

When you start using AI, it actually creates more strain on your senior people before it creates less. Junior team members produce more content, more research, more code — but it still needs review by a senior person.

I see this on our transformation team every day. We have two senior developers. We brought in three junior developers using AI-assisted coding. More code ships more frequently, which means more review for the senior developers. Over time the junior developers get better and the review load lightens. But the immediate reality is that AI amplifies output before it lightens senior load.

The key is not to avoid adopting AI because of the additional work load. Rather, it’s to enter with eyes wide open and an understanding, especially as we shift from being the doer to being the builder.

To start, go pick one phase of your client lifecycle — onboarding, annual review, tax planning. Map every step. For each step, ask: does this require my judgment, or does it require my methodology? If it only requires methodology, or if you could build a methodology for it, that's a productionization target. Systematize it. Make the output consistent.

Most advisors I talk with say they want to scale but don't actually want to stop being the best advisor in the room.

They want the growth and revenue of scale while keeping the identity of being indispensable.

I relate to this completely. It's not a strategy problem. It's an honesty problem, honesty with self. I wrestle with it every single day. And I haven't solved it.

The reason I write this isn't to provide the solution. There is no book that gives you the answer. There is only action. This is me taking a step, learning about myself and learning by doing, and sharing that journey with you.

The transition from advisor to architect is uncertain. It's uncomfortable. It's not a straight line. But I hope you'll come with me.

The best is ahead!

-Matt