Writing
64 pieces on AI employees, one-process builds, and the parts that still need a person. Written for operators, not for a prompt.

Foundations · 5 Sept 2026 · 8 min
The words people use for this work, written so a founder and an engineer can mean the same thing in a meeting.
Read the piece

Foundations · 4 Sept 2026 · 7 min
The questions people actually type, answered the way I answer them on a thirty-minute call.

Foundations · 1 Sept 2026 · 7 min
An AI employee is a named worker for one written process, not a chat box with a job title.

Foundations · 18 Aug 2026 · 6 min
A chatbot answers. An AI employee finishes a job and leaves a record you can audit.

Foundations · 4 Aug 2026 · 6 min
More agents sat in real workflows in 2026. Governance did not catch up. Owners still matter.

Foundations · 14 Jul 2026 · 6 min
It cannot invent policy, close harm alone, or sit outside the law. Drafting is not deciding.

Foundations · 23 Jun 2026 · 6 min
If the process is folklore, the stakes have no gate, or nobody owns misses, do not hire yet.

Foundations · 19 May 2026 · 6 min
Hire one written process. A platform is a year. A queue is a week.

Foundations · 21 Apr 2026 · 6 min
The person on the gate is not a fallback. They are the job you actually hired.

Foundations · 24 Mar 2026 · 6 min
A copilot sits next to a person. An AI employee owns the queue when the person is not there.

Foundations · 17 Feb 2026 · 6 min
RPA repeats a click path. An AI employee reads messy input and still has to stop at a gate.

Foundations · 8 Jan 2026 · 6 min
Tell the board it is one worker, one process, a cost, an owner, and a gate. Not a platform.