Collaborations
I work full-time at Bobdo, where I build agentic systems for marketing operations, analytics, SEO, reporting, and automation across real client workflows.
This page is for conversations around the same class of problems I write about here: agent-native software, orchestration, memory, human-agent workflows, operational reliability, and local-first tooling.
I’m open to selected collaborations where there is a clear overlap between the problem and my interests.
That usually means systems where AI agents interact with real tools, APIs, dashboards, files, browsers, terminals, or humans over time — and where reliability matters after the demo.
What I can help think through
I’m most useful around:
- agentic workflow design
- orchestration and execution models
- persistent memory and context systems
- MCP and tool boundaries
- human-agent handoff and review loops
- internal automation systems
- operational reliability for agent workflows
- local-first AI tooling
- technical diagnosis of fragile automation or AI systems
The layer I care about is not only the model call. It is everything around it: state, context, tools, recovery, observability, and control.
Boundaries
I work full-time at Bobdo, so I do not take on work that conflicts with my role there.
If a project overlaps with Bobdo’s domain — marketing operations, SEO, paid ads, analytics, reporting, or client-facing automation — I handle that openly. Depending on the project, the right path may be through Bobdo, through a clearly agreed collaboration, or not at all.
I also do not use Bobdo client data, internal systems, or company time for independent work.
The goal is to keep the boundary explicit.
Good fit
A good fit usually looks like this:
- there is a real operational workflow, not just an abstract AI idea
- multiple tools, APIs, or people are involved
- context needs to persist across work
- humans need inspection, approval, or override points
- reliability matters more than a polished demo
- the project sits near agent infrastructure, automation, internal tools, developer tooling, or operational systems
I’m especially interested in problems where the hard part is coordination, memory, handoff, recovery, or control.
Not a fit
I’m probably not the right person for:
- generic chatbot projects
- prompt packs
- thin AI wrappers
- AI strategy decks with no implementation reality
- one-off automation with no deeper systems problem
- work that competes with or creates ambiguity around my full-time role
Commercial work
For commercial work, I prefer to start with a short conversation about scope, overlap, and fit.
If the project is outside any conflict and narrow enough, I may be able to help directly.
If the project belongs closer to Bobdo’s domain or needs broader execution capacity, I’ll say that clearly and route the conversation appropriately.
If the boundary is unclear, I’d rather not take the work.
Contact
Send a short note with:
- what system or workflow you are trying to improve
- what tools or platforms are involved
- what currently breaks, slows down, or requires manual work
- whether this is a technical discussion, a possible collaboration, or commercial work
Telegram is fastest. Email also works.