Engagement Models
Three ways to work together.
The Approach
How I operate.
Every engagement follows the same discipline, regardless of scale.
Listen
I listen before I prescribe. No frameworks imposed before understanding your specific constraints, history, and goals.
Diagnose
Root causes, not symptoms. I map the system — people, processes, technology — and find where it actually breaks.
Design
Solutions that fit your reality. Not textbook architectures, but pragmatic systems designed for your team, budget, and timeline.
Execute
I don’t leave you with a slide deck. I stay until the system works — or hand off with enough clarity that your team can finish.
Expertise
Where I operate.
Domains where I have deep operational experience \u2014 not just advisory knowledge.
Digital Transformation
End-to-end modernization of legacy systems, processes, and team structures
Read related essayseCommerce Operations
Scaling multi-channel commerce from $1M to $50M+ with operational discipline
See related work Flagship domainPMO & Governance
Program management offices, delivery governance, and execution frameworks
See related workAI & Automation
Strategic AI adoption, workflow automation, and intelligent systems design
Read related essaysSystems Architecture
Designing resilient systems that scale without breaking under complexity
See related workAgricultural Technology
Applying modern systems thinking to uplift farming communities and supply chains
See related workPrinciples
What I believe.
Common Questions
Before you reach out.
Questions I get from founders and executives weighing an engagement.
How is this different from traditional consulting?
Traditional consulting delivers a deck and exits. I stay until the system works. Every engagement is structured around delivered outcomes, not delivered slides. If a roadmap can't be executed by your team after I leave, the work isn't done.
How do you decide whether to take an engagement?
Two filters. The problem must be a systems problem, not a tactical fix; and the leadership team must be willing to see root causes. If either is missing, I decline. I'd rather refer you elsewhere than take work I can't make stick.
What happens in the first two weeks?
Listening before prescribing. I map your operating system — people, processes, technology, history — and identify where it actually breaks versus where the symptoms appear. By week two you have a written diagnosis and a prioritized roadmap your team can review and challenge.
Can you embed if we already have a PMO or delivery function?
Yes. Most engagements coexist with an existing PMO. I work alongside, not over. The goal is to upgrade your system without replacing the people running it. Where I add capacity, that's by agreement; where I add governance, I document it for handoff.
How do you handle confidentiality given your other ventures?
Every engagement is exclusive within its sector for the duration of the work. Sensitive material stays within scope. Where there's any potential conflict — including ventures I'm involved in — I disclose before signing. Trust is the foundation; I don't optimize around it.