Why I Go Deep, Not Wide

Most consultants spread across 5-10 clients at once. Most agencies juggle multiple projects. The Sovereign Architect model is different: one client, one transformation, complete focus.

This isn't a business strategy. It's how my brain works — and it turns out, it's how the best transformations happen.

"I am a better sniper than machine gunner."

Sniper vs machine gunner. That's the mental model. Let me explain what it means for you.

"It's almost as though I could choose exactly the place where I would like to work. I just need to go in and speak to the people and start to work for them. The problem is I'm terrible at using a machine gun. Everything I do is like a sniper and a rifle. That is how I think."

Machine gunner mode: parallel threads, broad outreach, context switching, many shallow hits. Juggle 10 clients. Spread thin. Give everyone 10% of your attention.

Sniper mode: single thread, targeted precision, deep immersion. One client. One problem. 100% focus until it's solved.

Traditional consulting rewards machine gunners. More clients = more revenue. But more clients also = more context-switching = shallower work = slower transformation.

"As you know I like using a sniper rifle not a machine gun."

When I try to spread across multiple engagements, quality drops. I've tried. It doesn't work. My brain refuses to operate in machine gunner mode.

But give me one problem? One company? One transformation to own completely? That's where the magic happens.

Here's what sniper mode means for you as a client:

DURING EMBEDDING — You get 100% of my attention. Not 10% while I juggle other clients. Not 'I'll get back to you tomorrow.' Full immersion in your problem.

TRANSFORMATION SPEED — What takes spread-thin consultants 6 months happens in 2-4 weeks. Because I'm not context-switching. Because your problem is the only thing in my tunnel.

DEPTH OF SOLUTION — Surface-level fixes come from shallow engagement. The insights that create real transformation — like 'the bottleneck is comprehension, not code' — come from going deep enough to see what others miss.

The tradeoff is real: I can only work with one client at a time. There's a waitlist. The engagement has a defined end (I exit when the transformation is complete).

But the result is different. Not 'advice delivered, good luck implementing.' Instead: 'transformation complete, new system outperforms old, here's the documentation, you're independent now.'

"My biggest problem is that since the object of my focus becomes all encompassing I feel I get pulled around and move from one major hyperfocus to another."

I wrote that in 2023 as a description of a problem. Now I understand it as a description of an architecture. The all-encompassing focus isn't a bug to fix. It's the feature that enables deep transformation.

If you want someone on retainer for ongoing check-ins, I'm not your person. If you want someone who will disappear into your problem and emerge with a complete transformation, let's talk.