Conversation Types

Use this page as context, then reach out for the right reason.

The best conversations are specific. If you are reaching out about a leadership role, advisory work, AI implementation, product strategy, speaking, or thoughtful collaboration, say which one it is and what context matters.

Good Reasons To Reach Out

Leadership roles

CTO, VP Engineering, Head of Technology, or senior operating roles where execution systems, product leadership, and AI capability matter.

Advisory and consulting

Product, architecture, delivery, AI adoption, execution quality, or operating-model questions where you need a technical operator, not generic advice.

Speaking and mentoring

Talks, workshops, panels, mentoring, or educational conversations around software, AI, systems thinking, and leadership execution.

Thoughtful collaboration

Writing, product thinking, research, or serious conversation where clarity, systems, and implementation matter more than noise.

Highest-Value Engagement Paths

Advisory retainer

For founders or leadership teams who need ongoing thinking across AI direction, platform shape, and execution-system design.

Strategy sprint

For focused architecture, AI-adoption, or delivery reviews where you need clarity quickly and want concrete decisions, not abstract decks.

Workshop or keynote

For organizations and events that want technology leadership, AI implementation, and systems thinking translated into a room well.

Best Ways To Reach Me

Useful Context To Include

The fastest way to get to a useful conversation is to include role or engagement type, current context, what problem you are trying to solve, and why you think I may be a fit.