Do I need to automate all ten?

No. Pick the chore you did twice this week and resented. One workflow that runs is worth more than a catalogue of ideas. Come back for a second only after the first has failed in a way you noticed and fixed.

Which tool should I use?

Use the automation already included in a product you pay for, if it covers the job. Otherwise Zapier or Make for a cloud start, or n8n if you are hosting it. The comparison guide explains that choice. AI features inside those tools change, so check the current plan.

Will this replace a member of staff?

It will remove repeated formatting, filing and first drafts. It will not replace someone who knows the customer, the price, or the exception. If a task needs that knowledge, the automation should prepare the work and stop.

What if the model invents a fact?

Do not let that output reach a customer without a person. Drafts, summaries and internal notes are the right altitude for a first week. Sending, posting and issuing credit are not.

How do I avoid a mess of half-finished Zaps?

Write the task in a sentence, name the owner, and keep one workflow per job. If you cannot describe the failure ("I will notice because the Slack message did not arrive"), do not turn it on.

10 business tasks you can automate with AI this week

“Automate your business with AI” is usually a list of fantasies. The version that helps a small team is a list of chores with a clear input, a clear output, and a person who still checks the result. Here are ten you can set up this week without pretending you have a department. Do one.

Prices and AI feature names move. I am not quoting them. Where a product is named, open its site and confirm the feature still exists on the plan you have. The tool decision between Zapier, Make and n8n is covered in the comparison.

1. Sort new enquiries

The chore. A form or inbox mixes sales, support, suppliers and spam.

A sensible automation. Classify into a few buckets you defined, then notify the right person or apply a label. File the record.

The check. You glance at the bucket. You do not let the bucket email the customer yet.

This is the whole of the lead capture guide. If you only do one item from this list and you have a website form, do this one.

2. Turn a call into tasks, with permission

The chore. After a client call, the actions live in someone’s memory.

A sensible automation. Use the transcript your meeting tool already offers, or a transcription product you have a contract with, and ask a model for a list of actions, owners and dates that were actually said. Otter is one known option. Your existing Zoom or Google Meet transcript may be enough. Check what your plan includes.

The check. You edit the list before it becomes tickets. Tell the other people on the call that it is being transcribed. In the UK, do not quietly record people.

3. Draft replies to the emails you always write

The chore. The same five answers, typed again.

A sensible automation. A label or folder feeds a workflow that drafts a reply from a short brief and your own snippets. The draft waits in the mailbox.

The check. You send it. The n8n and OpenAI email guide is the step-by-step. The rule that matters: the draft may not invent prices, refunds or delivery dates.

4. Chase unpaid invoices, politely

The chore. You notice a late invoice when you do the accounts, which is too late.

A sensible automation. Your accounting tool’s own reminder if it has one. If it does not, a workflow that emails a short, pre-written note a set number of days after the due date, then stops for you to take over.

The check. You read anything that got a reply. Do not threaten interest or legal action from a template unless you have checked the current rules. The invoicing guide has a sequence you can adapt and the UK points to verify.

5. File receipts without a shoebox

The chore. Photos of receipts live in a chat thread.

A sensible automation. A dedicated email address or a phone upload drops the file into a folder named by month, with the supplier and amount in the filename if your tool can read them reliably. Many accounting products already do this. Use theirs if you have one. FreeAgent, Xero and QuickFile are the names UK freelancers already meet. Confirm the current capture feature rather than building a worse copy.

The check. You still code the expense. A filename is not bookkeeping.

6. A Monday numbers note

The chore. You open four tabs to remember what happened last week.

A sensible automation. A scheduled workflow pulls the few figures you already trust (new enquiries, unpaid invoices, support waiting) into a five-line note in your inbox. No narrative. No “insights” paragraph from a model unless you enjoy deleting it.

The check. If a number looks wrong, you fix the source, not the prose. A model must not be the thing that adds up money.

7. Repurpose one long piece into a draft, not a publishing machine

The chore. A blog post, a talk or a newsletter could become a shorter note, and never does.

A sensible automation. Paste the finished piece, or point a workflow at the URL you own, and ask for one newsletter draft and three social posts in your voice. Edit all of them.

The check. You publish. The model does not get the keys to the social accounts in week one. Nothing here should invent a customer quote. If you need tool ideas for the writing itself, the freelancer stack separates drafting from design.

8. Answer from your own docs, on the website, with a handoff

The chore. People ask the same questions in the chat widget that are already on the FAQ page.

A sensible automation. A chatbot limited to pages you wrote, which hands off to email or a shared inbox when it is unsure.

The check. Read the transcripts twice a week. If it improvises, narrow the sources or turn it off. The chatbot guide and the support tools guide split the widget from the queue behind it. Do not buy both on the same afternoon.

9. A new-client checklist that moves itself

The chore. Onboarding is a list in your head: contract, access, kickoff, first invoice.

A sensible automation. When a deal is marked won, create the tasks in the tool you already use, assign them, and send yourself the email you always send, as a draft.

The check. You confirm the tasks match this client. A checklist that assumes every job is identical will eventually skip a step that mattered.

10. Ask for a review after the work is finished

The chore. Happy clients never get the review link, because you moved on.

A sensible automation. A set number of days after you mark a job complete, send a short note you wrote, with one link, to people who have not already been asked. Stop if they did not reply. Stop if the job was difficult.

The check. You do not automate a second and third nag. You do not offer a reward the platform’s rules forbid. Read the review site’s current rules before you send the first one.

What I would not automate this week

Posting to clients without a draft. Anything that moves money, including refunds and “apply a discount if they sound annoyed”. Hiring decisions. Scraping other people’s sites because a model said the data would be useful. A chatbot that pretends to be a named colleague.

Those are not caution for its own sake. They are the automations that create apologies, which take longer than the original chore.

Pros

Each task has a small input and a visible output
You can use tools you already pay for
Drafts and labels teach you what is safe to send later

Cons

Ten half-built workflows are worse than none
AI output still needs a reader when a customer will see it
Native features are easy to miss and then rebuild badly

If the circled item is email, go straight to the email assistant tutorial. If it is money in, use the invoicing sequence. If it is “we should have a bot on the site”, read the chatbot piece before you install a widget, and the freelancer tools guide if the real gap is your own weekly stack rather than a customer-facing one.