Collaborations
I take on a small number of collaborations a year, in the places where my actual work lives: AI systems, tracking and visibility, automation, agent workflows, and operational measurement.
The best fit isn’t a generic AI idea. It’s a system where something real breaks — attribution that won’t reconcile, dashboards that disagree, agents that need to touch live tools, context lost between steps, or a business that can’t tell whether it’s still visible where decisions now happen. I work full-time at Bobdo, so I’m selective; the boundaries are spelled out below.
What I can help think through
I’m most useful around:
- how visibility and discovery shift as AI answers, summarizes, and routes
- measurement and tracking without third-party cookies or guaranteed referrals
- agentic workflow design and orchestration
- persistent memory and context systems
- MCP and tool boundaries
- human-agent handoff and review loops
- internal automation systems
- operational reliability for agent and data workflows
- local-first AI tooling
- technical diagnosis of fragile automation, tracking, or AI systems
The common thread is the layer around the model and around the click: state, context, measurement, recovery, and control.
Good fit
A good fit usually looks like this:
- there is a real operational or measurement problem, not just an abstract AI idea
- discovery, tracking, or attribution is actually broken and it costs money
- multiple tools, APIs, or people are involved
- context or data needs to persist and stay trustworthy across work
- humans need inspection, approval, or override points
- reliability matters more than a polished demo
I’m especially interested where the hard part is coordination, measurement, memory, handoff, recovery, or knowing whether any of it actually worked.
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
- ten-steps-to-beat-Google growth promises
- work that competes with or creates ambiguity around my full-time role
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.
Commercial work
For commercial work, I start with the boundary: whether it conflicts with Bobdo, whether the problem is narrow enough, and whether the hard part is real.
If the work belongs closer to Bobdo’s domain, I’ll say so. If it’s independent, technical, and bounded, I may be able to help directly. If the boundary is unclear, I’d rather not take it.
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.