Before you start

What you need

One real, repetitive task that you have already decided is worth automating — frequent, stable, and consequential. If you have not made that decision yet, do Robot Readiness first; choosing badly is the expensive mistake, and no amount of good building fixes it.

You also need somewhere to run things: a computer that stays on, a server, a hosting account, or an automation platform. Any of these work.

The five moves

1. Pin the task down — one trigger, one outcome, written on one line.
2. Build the smallest useful version — and resist everything else.
3. Add the guard rails — safe to repeat, safe to interrupt, safe when the input is wrong.
4. Give it a heartbeat — so its silence is detectable.
5. Watch it for a week — then decide what it still needs.

Why tool-agnostic

I could teach you one platform, and in two years the platform would have changed its pricing, its interface, or its owner. The five moves above have not changed for me in twenty years and they transfer to whatever you end up using. Where I need to be concrete I will describe the shape of the thing, not the buttons.