Where this comes from
A decade building brands and launches. Then three years building the AI underneath them. Turns out it was always one job.
The Pattern
Every founder I’ve worked with built their business the same way: one decision at a time, in response to what was actually in front of them. That’s how every good business gets built. The brand voice was a real answer to a real question two years ago. The CRM workflows made sense when the team was three people. The offer structure was perfect for the audience you had when you had three thousand subscribers.
Then you grew. And the things that worked kept working, mostly. Until they didn’t. The brand started feeling a little off, even though no one could say exactly what changed. The reporting started telling you less than it used to. New hires kept asking the same questions about how things actually work, and the answers all started with “well, originally...”
Most growth-stage businesses have a perfectly good strategy and a wildly out-of-date architecture. They’ve spent the last year or two optimizing the strategy when the architecture is the thing that actually needs the work. So the strategy keeps almost-working, the team keeps almost-aligning, the systems keep almost-holding, and the founder keeps being the load-bearing wall.
I want to be clear about this part: nothing about that is a failure of judgment. It’s what happens when a business outgrows its own scaffolding. The kind of attention it needs now is just a different kind than the kind that got it here.
How I work
Before I form a strong opinion, I want to see what’s already there — the brand, the numbers, the workflows, how the team actually gets things done. A lot of that comes from talking to the people who don’t usually get asked, because they’re the ones who know where things stick. None of it slows the work down; we’re already moving. What I hand back first isn’t really a deliverable. It’s an honest read on what’s working, what isn’t, and where I’d start.
I spent a decade in brand and launch work before I spent three years building AI systems, and somewhere in there I stopped seeing them as separate jobs. How you talk to your customers shows up in how your team runs, and in your tech stack, and in whether any of your reporting actually means something. When those stop lining up, work that should be simple turns into a daily fight. Most of what I do is get them back in sync.
Some of this needs someone in the building for the long haul, which is what I did for years inside a coaching company that was scaling fast. Some of it just needs someone to come in, build the thing properly, write it down, and hand it over. I’m good with either. The two things that don’t change are that I take on very few clients at once, and what I build is meant to run on its own.
Why I work this way
I don’t advise from the outside. I work inside the business, and across all of it.
When you hire a brand strategist, you get brand work. An ops consultant, ops work. An AI implementer, AI work. Each one is excellent inside their lane, and each one designs around the assumption that the other two will agree with them. They almost never do, because they were never in the same room.
I think of brand as the contract you’ve made with your customer, operations as the system that delivers on the contract, and the tech stack as the infrastructure underneath both. Built in conversation, the three hold together. Built in isolation, you end up being the only thing holding them together.
So I’m not the person across the table with a set of recommendations. I’m in it — building the systems, running them, fixing them when they break, working next to your team instead of around them. It’s how I worked embedded inside a company that was scaling fast, and there’s really one test I hold the work to, which is whether it holds up on its own once it’s built.
That’s the part that never quite fit the word “consultant.” I’m not handing you a deck and wishing you luck. I show up, do the actual work, and build things that keep standing on their own.