Who do you work with as an AI automation consultant?

Operations-heavy teams of roughly 10–50 people — agencies, professional services firms, and growing startups. The common thread is a team losing real hours every week to repetitive work that a system could handle.

How long does an automation project take?

A single automation is usually one to two weeks. A connected system across a few tools is more like three to four. Scope is agreed before any work starts.

Do you work hourly or fixed price?

Fixed-scope, fixed-price only. No hourly billing. We agree what's being built and what it costs, then I build it.

What tools do you use to build automations?

Usually n8n for workflow automation, APIs for system integration, and LLM-powered agents (often with RAG) where reasoning is needed. No custom software is built unless off-the-shelf tools can't do the job.

Do we own the automation you build?

Yes. When it's done, it's yours — running in your tools, on your accounts, with documentation so you or another developer can maintain it without me.

Field Notes

Writing on AI, automation, and shipping real things.

Build logs, strategy, and industry breakdowns. Specific over conceptual — written to be useful, not to fill a calendar.

StrategyAugust 12, 2026

AI Readiness: 5 Questions to Ask Before Automating Anything

Most automation projects don't fail at the build. They fail before it starts, because no one checked whether the work underneath was ready to be automated. Five questions I run through with every client.

Read

Build LogAugust 5, 2026

How I Built a Slack Agent That Answers Team Questions From Internal Docs

A walkthrough of the RAG assistant I built for an ops-heavy team — what it does, the stack, where it nearly broke, and what I'd do differently. Concrete, not conceptual.

Read