I built the thing
I now help people
take apart.
I ran a network engineering practice with 150+ employees and eight-figure revenue. The outside story was complete. The inside story was the same as most of yours.
A house
with no doors.
"I had built something substantial and I had built it so that it could not operate without my attention."
I ran a network engineering practice with 150+ employees and eight-figure revenue. From the outside it was the whole picture — the contracts, the headcount, the growth curve.
From the inside, every meaningful decision in that company still ran through me. I had built something substantial and I had built it so that it could not operate without my attention. I've called it a house with no doors: strong foundation, real square footage, and no way to move between the rooms without me walking someone through.
That cost me more than I'd planned on paying. Not in money — in the years I was present for and not actually in.
Enterprise logic
in a 40-person room.
I've spent the four decades since on the other side of that problem, including Fortune 500 transformation work — among it the Wells Fargo/Wachovia merger, transitioning roughly 6,600 branches.
That work taught me something owner-led businesses almost never get access to: enterprise infrastructure is not a matter of scale or budget. It's a matter of design sequence. The same structural logic that lets 6,600 branches operate on a common system will let a forty-person company operate without its founder in the room.
What I do now is architecture, not coaching. I don't help you work smarter inside a structure that was never going to release you. I redesign the structure — starting with what you actually want your life to look like, then building the business model that funds that life instead of consuming it.
By the Numbers
6,600
Branches transitioned — Wells Fargo / Wachovia merger
40+
Years in enterprise infrastructure and business transformation
150+
Employees in his own network engineering practice
Purpose first.
Structure second.
That order matters, and it's why the methodology is called Soul-First. Purpose, vision, and mission first. Structure second. Reverse it and you'll build an efficient machine pointed somewhere you never wanted to go.
On the technology: we build on enterprise platforms already proven in market rather than prototyping on your business. What we design is the architecture — which capability goes where, in what order, reporting what to whom. The tools are replaceable. The sequence is the work.
Not everyone is a fit, and I'd rather say so early. I work with owners oriented toward what they're building for others — clients, teams, families, a legacy that outlasts them. If the honest answer to "who is this for" is "me," we won't work well together, and that's not judgment. It's a compatibility question, and it's cheaper to answer now than eight weeks in.
Soul-First
Business Architecture™
Four phases. In this order. The sequence is the method.
Most firms sell you the last phase first. They arrive with automation, AI, and a platform before anyone has established what the business is supposed to produce or who it's supposed to produce it for. Layer technology onto an undefined structure and you have bought expensive automation of a broken system — faster, more scalable, more permanent. We go in order.
Phase 1
Assess
We establish what you actually want, then measure what the business currently does. Where revenue leaks. Where the company waits on you. Which hours produce nothing. Whether the foundation can carry the technology you've been pitched. This is where the Blind Spot Audit and AI Readiness Assessment live — findings, not opinions, before anyone proposes anything.
Phase 2
Learn
We determine what kind of builder you are and what the business is structurally capable of next. There are four types, and each one has a different correct next move. Attempting a Type 4 build on a Type 2 foundation doesn't accelerate anything — it's the reason most transformation spending fails. You get told the truth here even when it's "not yet."
Phase 3
Connect
We design the load transfer. Every approval, decision, and handoff that currently routes through you gets an owner, a rule, a threshold, and an instrument. In larger companies this is where the Operating Model Map is built, department by department. This is where the business stops being a set of habits and starts being a system — documented, measurable, and capable of being handed to someone else.
Phase 4
Grow
Now the technology goes in, on both halves at once. On the demand side: visibility where buyers ask their questions, capture of the intent already on your site, and outbound that starts conversations on a schedule. On the operations side: agent employees running the documented workflows, automation on process that exists on paper first, and instrumentation that reports the whole thing back to you without anyone assembling it.
Because we sequenced correctly, this phase compounds instead of collapsing.
The output isn't a strategy deck. It's a business that runs, reports, and improves without you standing in the middle of it — which is also, not coincidentally, the only version a buyer will pay a premium for.
Start with the Blind Spot Audit