Consulting
Helping teams run coding agents in production.
I help teams run coding agents in production — past the demo, at the point where dispatch, verification, cost, and infrastructure discipline start to decide whether the fleet ships software or generates noise.
The practice behind this is documented in public: the workflow manual describes the full seven-stage method, and the notes record what breaks and what holds. Engagements apply that material to your stack.
What I work on
Agent-fleet operations. Taking a team from one interactive assistant to a supervised fleet of headless workers: task decomposition, atomic claims, dispatch policy, and the failure modes that only appear past a handful of concurrent agents.
Verification and guardrails. Review gates that don't rely on the agent grading its own homework; reversibility rules for what agents may do without a human; GitOps boundaries so fleet activity stays declarative and revertible.
Cost accounting. Measuring cost per closed task rather than cost per token, model-mix decisions grounded in your own numbers, and the instrumentation to keep those numbers current.
Infrastructure for fleets. CI that agents can drive, spot-instance clusters that survive preemption, and self-hosted pipelines where the economics or the data demand it.
What an engagement looks like
Assessment (1–2 weeks). I read your setup — repos, pipelines, how work reaches agents and how it comes back — and deliver a written report: where the fleet leaks time or money, what to change, in what order, and what to measure to know it worked.
Implementation sprint (2–6 weeks). We pick one bounded outcome from the assessment and ship it together: a dispatch pipeline, a verification gate, a cost dashboard, a CI migration. Done means running in your environment, documented, and owned by your team.
Advisory (ongoing). A standing block of time each month for design reviews, incident postmortems, and decisions as your fleet grows.
If the shape you need isn't listed, describe the problem — the categories bend.
How to start
Email [email protected] with:
- what you're running today (tools, team size, where agents fit),
- what's not working or what you want to be true in three months,
- any constraints worth knowing up front (compliance, stack, budget shape).
You'll get a reply within two business days — either a call proposal or a pointer to published material if that already answers the question. No newsletter, no funnel; the write-ups are free either way.