The first automation often sets the tone for what follows. Chosen well, the team sees the gain at once and starts asking for more. Chosen poorly, it feels like a project for nothing.
Three criteria are enough. The task must be frequent, at least once a week. It must be predictable — a rule you can state in one sentence. And the result must be checkable at a glance, so trust builds quickly.
In practice, that almost always points to the same family of tasks: follow-ups, document filing, and sorting incoming requests. That is exactly why our standard packages exist.