I build and lead businesses, growth systems and modern operating capabilities.
Over 25+ years, I’ve built and operated companies, managed P&Ls and capital, led organizations, built customer-acquisition systems, helped transform a traditional media business into a digital-first company, and now lead growth and modernization across a national portfolio.
A few numbers that put the work in context.
Operating decisions with business consequences.
A few examples of the work behind the titles: decisions about capability ownership, growth architecture and how a business needs to operate when the model changes.
Bringing a critical growth capability in-house.
The decision was not agency versus in-house. It was whether a core acquisition capability still belonged outside once speed, data, economics and institutional learning became strategic.
Connecting demand to capacity, conversion and revenue.
Reframing growth around the full operating chain so more demand was not automatically treated as the answer to every revenue gap.
Building the capabilities required for a digital-first business.
Moving beyond isolated digital initiatives to build acquisition, CRM, analytics, product, technology and revenue capabilities across functions.
Growth is a connected operating system, not a stack of departments.
The forward-looking model underneath much of the work: market signal to durable customer value, with data, economics, technology and operating design supporting the whole chain.
See the change.
Create interest.
Focus attention.
Move toward a decision.
Create value.
Compound value.
Growth Plan Check
A small public model built around a practical planning question: what has to be true for a revenue target to work?
Pressure-test the plan before you add more demand.
Enter the target, conversion assumptions, acquisition cost and selling capacity. The model works backward to show the customers, opportunities, leads, acquisition spend and sales capacity required.
The point is not the sample result. The point is to make the assumptions visible enough to challenge them.
Ideas shaped by operating work.
The future executive needs to know how things are built.
Not how to become an engineer. How to inspect the logic, understand where the data came from, and know whether a system is actually useful.
When more marketing stops being the answer.
I’ve learned to slow down whenever a revenue gap gets translated immediately into “we need more leads.” Sometimes that is the answer. Sometimes it feeds the wrong constraint.
If we built the company from zero today, would we create the same departments?
I do not think departments are going away. I do think technology has changed enough of the old coordination costs that some inherited boundaries deserve another look.
The arc matters more than the titles.
I’ve spent my career close to the point where strategy has to become something real: a budget, a team, a customer journey, a piece of technology, a workflow, a product or a measurable business result.
That range has made me less interested in defending departmental boundaries and more interested in whether the pieces work together. This site is where I document selected work, build useful models and work through ideas about growth, technology and how organizations should operate next.