- Some advisory work does not senior-associate. It requires operator judgment that has to sit in one head from first call to last review.
- The two founder-led pillars at Magicworks are AI Consultation (Pillar 03) and Marketplace & Platform Consultation (Pillar 04).
- The constraint limits growth of these two lines. That is the point, not the problem.
- Founder-led is what makes the work useful. Remove the constraint and the work becomes a deck rather than a decision.
Every founder who runs an advisory practice eventually faces the same question. How do we scale this? The instinctive answer is to hire smart people, train them, systemise the frameworks, and put a senior name on the door of engagements without the founder in the room.
For most advisory work, that answer is right.
For some advisory work, it is exactly wrong.
The two advisory pillars at Magicworks, AI Consultation and Marketplace & Platform Consultation, are the second kind. They are founder-led by design, not by resourcing constraint. I still take the first call, run the working sessions, and sign off on every recommendation myself. That decision is deliberate, and it is the thing I want to explain here, because founders keep asking why and clients keep asking whether it will change.
The short answer is no. The longer answer is what follows.
I · What "does not senior-associate" means
Consulting has a phrase for the work that senior associates do well: leverage. The partner makes the sale, sets the frame, reviews the deliverable, and holds the client relationship. Everything in between is done by capable people who follow a well-designed process. When it works, the model is beautiful: one partner can hold ten engagements at once because the process is doing most of the thinking.
That model breaks in specific categories. It breaks when the work requires judgment that cannot be trained fast enough. Judgment about which category to enter. Judgment about which reader to serve. Judgment about which decision the site is actually helping the reader make. Judgment about when the paid economics are lying to you. Judgment about which piece of AI tooling is genuinely useful today versus which is a demo pretending to be a product.
None of that is proceduralisable. It is pattern recognition earned by doing the work personally over a long time. When you take it out of the partner's head and put it into a senior associate's briefing document, the recommendations start to look right on paper and fail on contact with the actual market.
Which is a polite way of saying: the client pays for the deck and does not get the decision.
II · The two pillars this applies to
At Magicworks I run five service pillars. Three of them are properly team-led: Digital Marketing (Pillar 01), Web Development (Pillar 02), and Brand, Research & Publishing (Pillar 05). These are engagements where excellent teams can and do produce excellent work at scale, with me in an oversight role and out of the day-to-day.
Two of them are not.
Pillar 03 · AI Consultation. This is advisory on how a mid-market business should actually adopt AI across marketing, operations, and product. The category is a year old at most, changing every quarter, full of demos that look like products and products that turn out to be demos. Any recommendation I make today will be re-examined in six months. That review has to be done by someone who has been personally paying attention across the whole horizon, not by someone reading a summary of it.
Pillar 04 · Marketplace & Platform Consultation. This is advisory for founders building portals and platforms. The work draws on the portal thesis I proved at Ideovate and on the operator scars that came from running simplidistance.com for six years. The engagement covers category economics, information architecture, editorial governance, and paid economics that all have to be judged together. You cannot senior-associate that judgment without losing what makes it worth paying for.
Both pillars are engagements where I sit in the first call, the working sessions, the mid-project reviews, and the final handover. That is not a marketing claim. It is the specification.
III · Why the constraint is a feature
The obvious cost of founder-led work is that these two pillars cannot grow the way the other three can. There are only so many hours in the week and so many months in the year. Any strategy that requires scaling founder attention hits a ceiling that no amount of process design can move.
I have thought about that trade carefully. The constraint is the point, and here is why.
It keeps the quality honest. When my name is on every recommendation, I cannot ship work I would not defend at a whiteboard. That constraint sharpens every deliverable in ways that a review layer over someone else's work never quite does.
It keeps the pricing honest. Founder-led work costs more than team-led work, and it should. Clients who want the price of team-led work should hire team-led providers. The mismatch of expectations gets sorted at the sales call rather than at the halfway review.
It keeps me in the work. The main reason I still find these two pillars interesting after seventeen years is that they are where the practice actually happens. If I hand them off, I stop learning, and if I stop learning, the practice becomes something I can look up rather than something I can do.
It keeps the practice small on purpose. A big consulting shop has its own incentives that eventually override client outcomes. A small founder-led practice does not. That is a real difference, and it is one of the things that makes clients repeat.
IV · What this means for a prospective client
If you are considering an engagement with either of these two pillars, three things follow from the founder-led design.
Lead time is longer than for team-led work. I take on a limited number of engagements at a time. The waitlist is real. Plan accordingly.
Scope is narrower and deeper than a typical advisory brief. I would rather do the important half of what you want, done properly, than the surface of the whole thing.
Handover is real. When the engagement ends, your team has to be able to run the recommendations without me. So the working sessions are as much about capability transfer as they are about the deliverable.
Everything else is negotiable. The founder-led constraint is not.