AI product strategy
Choose a workflow worth solving.
Clarify the user decision, source data and acceptable failure modes. Define which work belongs to a model, a deterministic system or a human reviewer.
AI advisory and technical strategy
I bring the perspective of an engineering leader, independent AI builder and technical author. I help frame the architecture, evaluation and operating choices that determine whether an AI product deserves its users’ trust.
Where I can contribute
My advisory interests center on AI products, developer tools, workflow automation, consumer commerce and privacy-aware software.
AI product strategy
Clarify the user decision, source data and acceptable failure modes. Define which work belongs to a model, a deterministic system or a human reviewer.
Agent architecture and evaluation
Review tool permissions, context and memory, orchestration, evaluation scenarios, observability and recovery. Define evidence for a release decision.
Engineering adoption
Connect AI-assisted development to code review, automated checks, engineering standards and manager accountability. Draw on platform adoption and organizational change experience.
Privacy and governance
Identify sensitive data, model access boundaries, approval points and audit needs. Examine whether the architecture supports the product’s promises.
Why this perspective
At PayPal, I lead 50 people through three engineering managers and own production Shopping AI/ML integration and operations. Independently, I build the controls, evaluations and product workflows I write about.
PayPal UI adopted by 2,000+ engineers across 100+ teams, alongside shared infrastructure handling 50M+ daily requests.
KaiInbox source validation, Sanctuary privacy controls, agent-workflow experiments and educational evaluation tooling.
20+ AI books and field guides within a broader 25+ book catalog, covering agents, context, AI-native delivery and governance.
Start with the problem
I welcome selective advisory, technical diligence and engineering-leadership conversations. Share the product context, the engineering decision and the outcome you want to improve.