If the work feels relevant, the next move should be simple.

Email is the fastest way to reach me for conversations around LiveOps, production systems, and team coordination.

Good fit

The best conversations usually start with a real problem.

If you already know the friction point, we can get to a useful conversation quickly.

Advisory or consulting conversations around LiveOps, delivery systems, and production operating models
Game-team problem solving around execution, planning, workflow design, and cross-functional alignment
A direct note when something important is blocked, drifting, or getting more expensive than it should be

Other channels

If email is not the best fit, these channels are also open.

LINK_00::LINKEDIN

Best if you want the quick professional overview before moving the conversation somewhere more direct.

LINK_01::GITHUB

Best if you want the code-side portfolio, repos, and project history after the first hello.

LINK_02::DISCORD

Best if you want a more gaming-native, informal channel after the first hello.

LINK_03::STEAM

Best if you want a direct window into the games, history, and player identity behind the work after the main conversation is already clear.

LINK_04::RESUME

Best if you want the concise version of my experience, leadership scope, and production background.

Next step

Clear enough to act on, direct enough to mean it.

If you’re working through a delivery problem, a LiveOps decision, or a team-shape question, send an email. The best conversations start early.