W E S S T R U E B I N G
Founder. Operator.
Systems Architect.
I grew up inside systems under pressure.
Three Generations in Moving and Logistics
I am a third-generation operator in moving and logistics, and that inheritance started in 1934 with Westlake Moving Systems.
I grew up inside systems under pressure.
Not theoretical systems. Real ones.
Warehouses. Trucks. Customers. Claims. Payroll. Dispatch. Breakdowns. The phone ringing at dinner. The balance sheet that did not balance. The driver who did not show. The client who did.
My grandfather founded Westlake Moving Systems in 1934. My father carried it forward. He turned down Stanford Law to do it. He believed the company his father built was worth more than any career he could have chosen instead.
I am third generation. This industry is not my market. It is my inheritance.
I learned systems physically. Not in a classroom. On a dock. In a warehouse. On the phone with a customer who was angry about something that broke because the process behind it was held together by one person's memory.
I watched businesses survive because good people compensated for broken architecture. And I watched other businesses collapse because the founder became the system without realizing it.
That pattern stayed with me.
It became the lens I see everything through.
40 Years Inside Founder-Led Companies
After 40 years inside founder-led companies, I know most of them do not break from lack of effort. They break from invisible dependency.
Over 40 years inside logistics, freight, operations, and founder-led companies, I realized something most people do not say out loud:
Most companies do not fail because people are lazy.They fail because dependency becomes invisible.
The founder compensates. The team adapts. The culture normalizes it. And eventually the business becomes structurally dependent on exhaustion.
Not on systems. On exhaustion.
I have seen this pattern hundreds of times. In moving companies. In freight operations. In healthcare platforms. In PE-backed portfolios. In SaaS companies. In service businesses. In every industry where a founder built something real and then became trapped inside it.
The pattern does not care about the industry. It cares about the architecture.
I have also been that founder.
I took someone's word for it. They said the system would scale. I did not understand the architecture deeply enough to challenge them. So I trusted the builder and signed the checks.
When the business pivoted, the system could not follow. I spent two years apologizing. To clients. To my team. To myself. I was trapped inside someone else's design decisions and did not know how to get out.
I got out when AI gave me the tools to rebuild the entire system for one percent of what the original cost. Not because AI is magic. Because a founder who understands their own business deeply enough can finally build the architecture themselves.
I built my way out of it.
That is the experience I bring.
The Work I Do Today
The work I do today runs through three logistics platforms: NexMuv, CRST Specialized Transportation, and GlobalTranz (WWEX Group).
I played football at BYU under LaVell Edwards. Twenty-nine years, one offense, 19 conference titles. He never chased trends. He trusted the architecture and let it compound.
That changed how I think about everything.
Today I run three logistics platforms. I serve as Co-Chair of MovingIQ Group. I advise founder-led companies between $5M and $100M. I host a podcast called Move or Be Moved. I wrote a book called The Moron Test. I built the Founder Dependency Index.
All of it comes from the same place: 40 years of watching what happens when complexity creates dependency, and dependency becomes invisible, and invisible dependency breaks companies that looked strong from the outside.
I am not interested in strategy that dies in the conference room.
If the system only works when the founder is awake, it is not a system. It is a dependency wearing a process label. And most operational problems are dependency problems wearing different clothes.
Why This Matters to Me
Why I Build Differently
I build differently because I have paid what founder dependency costs, and I design systems so the next founder does not have to.
I care about this work because I know what dependency costs.
I know what it feels like when the phone never really stops. When every exception routes back to the founder. When the team depends on your memory instead of the system. When growth becomes heavier instead of stronger. And when success quietly turns into operational exhaustion.
I have lived inside that pressure.
I have been the founder who built load and called it growth. I have been the operator who could not take a week off. I have been the guy who checked email from the parking lot of his daughter's school play because the company needed him for everything, and honestly, it felt good to be needed.
It was not leadership. It was dependency. And I did not see it until it almost broke me.
That is why I build differently now.
Because the founder should not be the operating system.
Who I Work With
I work with founder-led companies where growth has started to depend on the founder, and every engagement starts with a 30-minute discovery call.
If you have read this far, you are probably the kind of founder I work with.
Not because you are struggling. Because you are succeeding in a way that has started to depend on you for everything. And you are starting to wonder whether the company can survive the next phase without something changing structurally.
I have been where you are.
30 minutes. No pitch. No deck. Just an honest conversation about what is broken and whether I can help fix it.
If it is not a fit, I will tell you.
Three questions. Sixty seconds. One number.
Or read Chapter 1 of The Moron Test free →By Wes Struebing · Last updated
