What this prompt does
You hand it a list of the chores your team repeats every week. It comes back with a ranked plan: which tasks to automate first, which tool fits each one, how to set it up, and roughly how many hours you get back. It acts like an outside operations person who has seen this problem many times and knows where the easy wins hide.
The useful part is the ranking. Most people try to automate the biggest, messiest task first, stall halfway, and give up. This prompt pushes you toward the task with the best ratio of saved hours to setup effort.
When to reach for it
Use it when your team keeps saying "we are buried" but nobody can name the single worst offender. It also helps before a hiring decision: if automation can absorb ten hours a week, you may not need that extra person yet.
Skip it if you have already mapped your workflows. In that case, ask for setup guides for the specific tasks you have picked.
How to run it
- Write down five to eight tasks that eat time each week. Be concrete: "reply to order status emails" beats "customer service".
- Add your business type, team size, and the tools you already pay for. Existing tools are cheaper than new ones.
- Paste the prompt and fill the placeholders with that list.
- Ask it to justify each rating in one sentence. This exposes guesses.
- For the top two tasks, request the setup steps as a checklist with a time estimate per step.
- Try one task end to end before touching the rest.
A worked example of the list you might send:
- answering routine supplier questions by email
- writing the monthly newsletter
- turning call notes into CRM entries
- building the weekly sales summary
What a good answer looks like
Each task gets a rating, a named tool, honest setup steps, and an hours-saved figure. The top pick should be something you could start this week, not a six-month project.
Watch for three things. First, ratings with no reasoning. Second, tool suggestions you would have to buy and learn from scratch when a tool you own already covers it. Third, hour estimates that assume perfect adoption on day one. Cut them in half and see if the plan still makes sense.
If a setup guide names steps you cannot follow without technical help, say so and ask for a simpler route. The goal is a plan your team can actually run, not the most sophisticated one on paper.
A prompt that reviews your recurring work, rates each task for automation potential, and gives you a setup plan ranked by time saved. For small teams drowning in重复 work.
Read this page, then check whether AI assistants can read yours: one scan, six pillars, a score.