Zero to VA 0%

Module 5 • The Automator

Automation — the skill that changes your rate

Highest-value module

0 of 14 done

Goal
Learn the automation stack clients pay a premium for, and build three working automations you can show.
Roughly
12 hours. This is the highest-value module in the plan.

Part 1 — Zapier, Make and n8n

Watch first

Lessons

  1. Why this module exists. A general admin VA with no experience starts around $3 to $5 an hour. Automation VAs in Make, Zapier, or n8n are quoted at $12 to $20 an hour in 2026 niche surveys. Same person, different skill — which is why this sits before the portfolio, not after it.
  2. Learn one platform properly instead of three badly. Zapier is the easiest start and the most common in job posts; Make is cheaper at volume; n8n is the most powerful and what newer AI-automation posts ask for. Pick one — the concepts transfer.
  3. Every automation has the same shape: a trigger, actions, and conditions in between. Learn to describe a manual task in those terms before building it. "When a form is submitted, add a row, then email the owner only if the budget is over X" is the whole job.
  4. Build three automations for your invented business. One: a form or new email creates a spreadsheet row and sends a notification. Two: a weekly digest that assembles itself every Monday. Three: one with an AI step inside it, such as summarising enquiries or drafting a first-pass reply.
  5. Test each one end to end with realistic data, then deliberately break it and add the error handling. Clients notice the VA who thought about what happens when it fails.
  6. Write the one thing that sells this work: a one-page before-and-after — manual process, automated process, hours saved per month. That beats any certificate, because it is priced in the client's own currency.

Checklist — click each box to tick it

0 of 7 done

Part 2 — Automation inside AI tools

Goal
Turn the AI tools clients already pay for into repeatable, checkable workflows — saved prompts, projects, skills and agents — instead of one-off chats.
Roughly
10 hours. Do it after Part 1; both parts use the same trigger-and-steps thinking.

Watch first

Lessons

  1. Why this part exists. Many small businesses already pay for ChatGPT, Claude or Gemini and use it like a search box. A VA who turns that subscription into reliable, repeatable workflows adds value with no new software to buy — which is what the AI operations roles in the Rates section are paying for.
  2. Prompting comes first. A work prompt that holds up has five parts: who the assistant is working for and why, the task, the material to work on, the exact output format, and the rules — length, tone, and what it must never do. Test each prompt on three real-looking examples and keep the ones that work in one prompt library document. A tested prompt is an asset; a clever one-off is not.
  3. Projects give the assistant a standing brief. A project holds instructions and reference files — the client's tone of voice, services and prices, FAQs, email templates — so every chat inside it starts already briefed. Claude Projects are available on the free plan (up to five projects), and ChatGPT has Projects too. Build one for your invented business and notice how much shorter your prompts become.
  4. Skills turn a procedure into a tool. A skill is a folder with a SKILL.md file — a name, a one-line description of when to use it, and the steps and rules — plus any templates or examples. The assistant loads it when a matching task comes up, so the work is done the same way every time. As of October 2026, Claude Skills are available on every plan including Free (code execution must be switched on): zip the folder and upload it under Customize, then Skills. Gemini is replacing Gems with skills, and Gems on personal accounts convert automatically from 17 November 2026. ChatGPT skills are on business plans so far, and use the same open format as Claude's, so a well-written skill can move between them. Building a custom GPT needs a paid ChatGPT plan.
  5. NotebookLM holds the client's knowledge. Upload SOPs, policies, call transcripts or product sheets and ask questions; every answer points back to its source. It is free with a Google account, and it is the fastest way to become the person who knows where everything is.
  6. Connect the AI tools to the platforms from Part 1. The pattern clients pay for: an automation catches the trigger, an AI step drafts or sorts, and a person approves before anything goes out. Zapier and n8n also offer AI agents that choose their own next step. Build one only after a fixed workflow works, and keep a human approval for anything sent to a customer.
  7. Rules for AI on client work. Never paste passwords, card or bank details, government IDs or health information into an AI tool. Use client data only in the tools and plans the client has approved. Check every output before it reaches anyone — AI is confidently wrong often enough that checking is part of the job. Tell the client which tasks use AI; being open about it builds trust.
  8. Price it in the client's currency. Add each AI build to the before-and-after from Part 1: minutes per task by hand, minutes with the workflow, and the plan it needs. A client cares that inbox triage dropped from 40 minutes a day to 10, not which model did it.

Prompt library — copy, paste, adapt

Replace everything in [square brackets], then test each prompt on real-looking material before you save it.

Inbox triage
You are triaging email for [client name], who runs [type of business].

Sort each email below into one of three groups:
- Urgent: needs [client name] today (money, a deadline, an unhappy customer)
- Waiting: needs a reply this week, or I can reply myself
- Reference: no reply needed

For each email give: the group, the sender, a one-line summary, and the next action.
Put Urgent first. If you are unsure, put it in Urgent and say why.
Do not draft any replies.

Emails:
[paste emails]
Summarise a long thread
Summarise this email thread for [client name], who has not read it.

Give me:
1. What was decided, in three bullet points or fewer
2. What is still open, and who is waiting on whom
3. Any dates, amounts or commitments, quoted exactly
4. The one thing [client name] needs to do next

Keep it under 150 words. If the thread contradicts itself, point it out instead of guessing.

Thread:
[paste thread]
Meeting notes to action list
Turn these meeting notes into an action list.

For each action: the task, the owner, and the due date if one was mentioned. Write "no date set" if none was.
Then list any decisions made, and any questions nobody answered.
Use only what is in the notes. Do not invent owners or dates.

Notes:
[paste notes or transcript]
Reply in the client's voice
Draft a reply to the email below as [client name].

Tone: [warm and brief / formal / friendly but firm]
Goal of the reply: [for example, decline politely and offer an alternative]
Facts to use: [prices, dates, policy lines]
Keep it under [120] words, no exclamation marks, and sign off as "[sign-off]".

If the email asks something the facts above do not cover, write [CHECK WITH CLIENT] in the draft instead of answering.

Email:
[paste email]
Write an SOP from rough notes
Write a standard operating procedure from my notes below.

Format:
- Title and one-line purpose
- When to use it
- Tools and access needed
- Numbered steps, one action each, each starting with a verb
- Common mistakes and how to fix them

Write for someone doing this task for the first time. Mark any step where my notes are unclear with [UNCLEAR].

Notes:
[paste notes or a screen-recording transcript]
End-of-shift update
Turn my task log into an end-of-shift update for [client name].

Sections: Done today, In progress, Blocked or waiting (with who I am waiting on), Tomorrow.
Use short bullet points. Put anything that needs a decision from [client name] at the top.
Do not make the day sound bigger than it was.

Task log:
[paste notes]
Example skill — a SKILL.md for inbox triage
---
name: client-inbox-triage
description: Sorts a batch of client emails into Urgent, Waiting and Reference, with a one-line summary and next action for each. Use when asked to triage, sort or summarise an inbox.
---

# Client inbox triage

## Steps
1. Read every email before sorting any of them.
2. Put each email in one group:
   - Urgent: money, a deadline within 48 hours, or an unhappy customer
   - Waiting: needs a reply this week
   - Reference: no reply needed
3. For each email write: group, sender, one-line summary, next action.
4. List Urgent first, then Waiting, then Reference.

## Rules
- Never draft or send replies in this skill.
- If unsure between two groups, choose the more urgent one and say why.
- Copy amounts and dates exactly as written.

Checklist — click each box to tick it

0 of 7 done

Module 5 complete

Milestone reached: The Automator

You can build automations in Zapier, Make, or n8n — the skill that lifts your rate

Reset all progress?

This clears every ticked box, tracker row and note saved on this device. It can’t be undone — export your progress first if you might want it back.