Most email gets an answer. Generic outreach does not.

Channels

• Email [email protected] Fastest. Best for anything substantive.
• LinkedIn in/kembec Professional context and background.
• GitHub @Kembec Code, issues, and pull requests on any of the open-source work.
• X @kembec Shorter thoughts, occasional replies.

What I am a good fit for

• Conversations about product and technology leadership, particularly where both are genuinely in scope.
• Advisory or consulting on product operating models, platform strategy, or technical organizations.
• Podcasts, panels and events on the topics in the media kit.
• Collaboration on Model Context Protocol tooling and agent-facing developer products.
• Questions or corrections about anything published here — including disagreement with the arguments.

What I am not

• Generic recruitment outreach with no role context.
• Requests to review or promote products I have no relationship with.
• Unpaid speculative work, or "quick calls" with no stated subject.

Saying this plainly saves us both time, and it is the same discipline I argue for in product work.

Before you write

If you are evaluating me for a role, about me covers the current scope and trajectory, product covers how I think, and work covers what that produced. If you are writing about me, the media kit has the correct name, role, biographies and photograph.