Background

The rare combination.

What makes this unusual is that I run large-scale marketing and I write the software underneath it: the connectors that unify every data source, the AI agents that do the analyst work, the audit systems that catch what platforms miss. Most operators do one or the other. I do both, which means the infrastructure I build isn't a vendor dependency. It belongs to you.

That combination is the whole story. The marketer who can't build waits in a vendor's queue. The engineer who can't market builds the wrong thing. Doing both collapses the distance between "we should know this" and "we know this" from a quarter to an afternoon, and at scale, that speed is the multiple.

I work this way because I've watched the alternative fail: strategy decks nobody executes, dashboards nobody trusts, pilots nobody has the nerve to kill. The fix was to become the person who does the whole job, and to leave behind systems that keep working after I'm gone.

The record itself lives on the Evidence page. This page is just the why.

How I work

The operating principles.


Operator, not advisor

I launch things, run spend, build infrastructure, and scale what earns it. I don't hand you a strategy deck and leave.


Numbers first

Kill criteria before a dollar is spent. Real numbers every week. No zombie projects.


Few clients

I take on a small number of engagements so the work gets my full attention, not a junior team member's.


The truth

If I don't see a multiple in your business, I'll say so. That honesty is the job.

PF  //  Field Doctrine The Art of War

Victorious warriors win first and then go to war; defeated warriors go to war first and then seek to win.

— Sun Tzu 01 / 09
↳  In practice

The pilot discipline. Kill criteria written before the first dollar moves.

Tell me what you're building.

Work Together Read My Writing