Automation · February 2, 2026 · 6 min read
Automation people trust is boring on purpose
The automations that survive are predictable, visible, and easy to stop. Notes on human-in-the-loop design from building follow-up and invoicing flows.
Nobody trusts a workflow they can't see, stop, or correct. The most common reason automations get switched off isn't failure — it's mystery. Someone receives a message they didn't expect, asks who sent it, and the answer is a shrug.
Draft, don't send
For anything client-facing — invoices, follow-ups, outreach — the automation should draft and schedule, and a human should approve. The approval step looks like friction. It is actually the feature that lets the owner sleep.
- One source of truth (a board or sheet) showing draft → scheduled → sent → paid
- Idempotency: the same trigger twice must never send twice
- Every automated message labeled internally with which flow sent it
- A single off-switch per flow, not per message
Fail safe, not loud
When data is missing, the flow should pause and flag — never guess and send. A stuck item in a visible queue is a minor chore. A wrong invoice sent confidently is a trust incident.
duplicate check → required fields present? → draft first → human approves → send → log everything
Placeholder series — swap in your real voice and stories as you publish.