contact / technical intake

Let's talk about the system, not just the feature.

If your team is evaluating agents, automation, internal tooling, or an applied AI layer, this is the best place to start turning it into something real.

Start with email Open LinkedIn

channels

Pick the channel based on how fast you need to move.

Best for scope, context, and technical decisions.

[email protected] LinkedIn

Useful for intros, quick messages, and professional context.

Open profile GitHub

If you want to review technical tone, code, and experiments.

See repos

where I add the most

I do my best work when the problem needs both judgment and execution.

Agents and internal tools that need observability and clear boundaries.

Operations automation where the current workflow already feels expensive.

Context, RAG, or knowledge systems where information is still scattered.

Products that need a fast technical prototype before scaling the team.

process

This is how an initial conversation usually turns into a real plan.

Problem read

I review the context and separate symptom, constraint, and actual bottleneck.

Diagnostic call

We align on goals, risks, dependencies, and the real level of complexity.

Technical direction

I propose a concrete route: experiment, focused implementation, or broader system work.

first brief

If you already have context, even better.

You can share stack details, constraints, examples, or simply the part of the system that feels stuck right now.

Send project context