When you need this

There is a task somebody does every day or every week that is nothing but moving information from one place to another. Exporting orders and emailing them. Chasing an enquiry nobody answered in three days. Updating prices from a supplier’s file. Posting the same news in three places.

The test: it happens on a schedule, the rules do not change, and getting it wrong costs money. If it takes five minutes a month, the automation costs more than it saves — I say so before we start.

What I actually build

A schedule that is kept. Left to itself, WordPress runs a scheduled task only when somebody visits the site, so on a quiet site “every night at two” becomes “whenever”. I set the clock on the server instead, so two means two.
Runs twice, sends once. An automation that fires twice by mistake must not send two invoices or create two records.
A message to you when a run fails. An automation that stops silently is worse than none, because you go on assuming it ran.
A history you can open — what ran, when, what it touched — so you check it rather than trust it.
A way for your staff to pause it or run it by hand, without calling me.

Where this shows up in my work

The nearest published piece is in A course catalogue that has to work in three languages: an enquiry reaches the sales team’s phone within seconds instead of waiting in an inbox. Scheduled work — reports, price updates, follow-ups — is not on a published case yet.

What you get

A task that no longer needs a person to remember it, a record you can point at when someone asks whether it ran, and a message instead of a discovery when it does not. Scope and price in writing before the work starts.