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.

What I shipped, how, and what broke. Specificity = credibility.

Build LogSeepient

August 13, 2026

Enforcing Architecture in the Age of AI Code: Taming the Slop

AI development tools offer unprecedented speed, but unguided code generation introduces hidden operational risks. Here is how I enforce strict governance over AI-built code.

Read

Build LogSeepient

August 13, 2026

Inside Seepient's Permission System: Policy, Approval, Execution, Audit

Why simple yes/no approval prompts fail when automating business tasks, and how my 4-stage governance pipeline makes autonomous AI execution safe and fully auditable.

Read

Build LogSeepient

August 13, 2026

Foundational Architecture: Designing for Evolution, Scale, and Zero Redundancy

How a disciplined, six-layer modular architecture protects Seepient from technical debt, isolates system failures, and guarantees zero vendor lock-in.

Read

Build LogSeepient

August 13, 2026

Seepient: Engineering an AI Person, Not Just Another Chatbot

Why single-prompt chatbots fail for busy teams, and how Seepient operates as a persistent, secure digital colleague across desktop and cloud environments.

Read

Build Log

August 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