// page.contact

    

I am useful when a team needs someone customer-facing who can move between product context, ML systems, coding tools, and research judgement without losing the plot.

// direct.channels

     

Email is best for context. Calendar is best when the problem is already shaped enough for a working session.

// what.happens.next

  

01

Send context

Tell me what you are trying to build, where the AI system is stuck, and what a useful win would look like.

02

I map the problem

I look for the workflow, data boundary, evaluation loop, and the first thing worth shipping instead of a deck.

03

We decide the build path

If there is fit, we define a lean plan: prototype, production path, risks, and what not to spend time on.

// the.deal

Hover to find the fit.

You bring the domain and the customers. I bring the AI systems that ship.

I know the chemistry

You know the Business

// send.note

    

A good note has the business problem, the current system, the users affected, and the constraint that makes it hard.

See previous work

Get In Touch