Book a demo
A commuter rushing past people standing still in a concrete building

Learn AI by building with it.

A live class every week. A coach who marks what you build.

Book a 15‑minute demoSee the 17 courses

Everyone says use AI.
Nobody shows you how.

"I've watched the videos." Then you open the tool and stare at a blank box.

"I only use it for emails." You know there's more in it, and don't know what to try next.

"My team is behind." Competitors automate the admin you still do by hand.

How a course runs

01

Your whole kit, and a first build in week one

A cyclist in motion 02

A real build every week, on your own work

A crowd moving through a city, one person in a red jacket 03

A live class with your coach, every week

04

Every build marked by a person

Works with what you already use.

Seventeen courses.

  • AI for you6 weeksUnits and assessment
    • Course code AIY-06
    • 6 weeks
    • 6 to 8 hours a week
    • 14 assessed build tasks
    • Certificate of completion

    6 dense weeks: a learn pack, an Explore block and two or three build tasks every week, a core security and governance week, a live build every Thursday at 6pm, and a coach who marks every task.

    Week 01Your whole kit, and your first build3 assessed tasks

    Everything in one week: how AI is used and how people make money from it in 2026, where this course can take you, Claude with your context, the brief method, Claude Code, your first skills, and a personal page running on your own computer.

    By the end of the week you can

    • Describe how AI is used at work, at home and in business in 2026
    • Name the real AI business models, and which fit you
    • Set up Claude with projects, memory and an about-me file
    • Write four-part briefs, install Claude Code and skills, and run the learning loop

    Lessons · 3 h 39 min

    1. How to learn AI: the trial-and-error loopReading · 10 min
    2. How AI is used in 2026: at work, at home, in businessVideo · 14 min
    3. How AI makes money in 2026: the business modelsReading · 15 min
    4. Where this course can take youVideo · 10 min
    5. What AI is good at, and what it isn'tVideo · 10 min
    6. The four-part briefVideo · 10 min
    7. Install everything, gentlyLab · 60 min
    8. Live build: your first page, on your computerLive class · 90 min

    Assessment

    1. 1.1
      Your personal setup

      An about-me file and three projects (work, money, home), each used for a real job this week.

      You submitYour file and one result from each project.

    2. 1.2
      Your AI map

      Pick the two business models that fit you best and the three jobs in your own week AI should take over first. This is your plan for the course.

      You submitOne page.

    3. 1.3
      Your first page

      Have Claude Code build a one-page personal site and run it at localhost.

      You submitA screenshot and the folder on GitHub.

    Explore

    Open the skills library and install two skills that look fun. Use them on something real from your week. Log what happened.

    Knowledge check

    • Name three AI business models and who each suits.
    • What are the four parts of a brief?
    • What is localhost?
    Week 02Make it look designed, and put it online2 assessed tasks

    Why AI work looks like AI, the three decisions that fix it, and your site live on the internet.

    By the end of the week you can

    • Spot the tells of AI design and fix them
    • Use design skills and screenshots
    • Deploy a site to a live URL

    Lessons · 2 h 8 min

    1. Why it looks like AI, and how to fix itReading · 14 min
    2. Design skills and the screenshot loopVideo · 12 min
    3. From localhost to liveVideo · 12 min
    4. Live build: launch your siteLive class · 90 min

    Assessment

    1. 2.1
      Your website, live

      Your site with one direction, two typefaces and one colour, deployed.

      You submitThe live URL and before-and-after screenshots.

    2. 2.2
      Three directions

      Three versions from three direction sentences, and why the winner won.

      You submitThree screenshots.

    Explore

    Build your page in three different directions and keep the best. Find one design skill on your own.

    Knowledge check

    • Name three tells of AI design.
    • What does deploying do?
    • Why screenshot before finishing?
    Week 03Connect it to your life2 assessed tasks

    Connect email, calendar and files, run research that cites its sources, and build a daily brief that tells you what matters.

    By the end of the week you can

    • Connect Gmail, Calendar and Drive
    • Explain MCP in two sentences
    • Run research with real sources

    Lessons · 1 h 43 min

    1. Connectors and MCP in plain EnglishVideo · 10 min
    2. Research that shows its workingReading · 12 min
    3. Prompt injection, simplyReading · 6 min
    4. Live build: your morning briefLive class · 75 min

    Assessment

    1. 3.1
      Your morning brief

      A daily brief from your calendar and inbox: the three things that matter today. Run it for five days.

      You submitFive briefs and one change you made because of them.

    2. 3.2
      A decision, researched

      A real decision you face, researched with sources and both sides argued.

      You submitThe one-page brief.

    Explore

    Find one MCP server or connector for an app you use every day and try it. Try to trick it with a sneaky email.

    Knowledge check

    • What does a connector let AI do?
    • How do you check a source is real?
    • What should a brief never do on its own?
    Week 04AI security, safety and governanceCore unit2 assessed tasks

    A core module in every course. Keep your own data and accounts safe, spot AI scams and deepfakes, understand the rules, and know how workplaces govern AI so you can be the person who uses it responsibly.

    By the end of the week you can

    • Keep personal data, passwords and keys out of AI tools
    • Check and change the privacy settings of every tool you use
    • Spot AI scams, deepfakes and prompt injection
    • Explain the Privacy Act, copyright and disclosure basics
    • Write a personal AI policy, and know how workplaces govern AI

    Lessons · 2 h 23 min

    1. The personal AI security checklistReading · 12 min
    2. Privacy settings, retention and training, tool by toolVideo · 12 min
    3. Scams, deepfakes and voice clones: how to spot themVideo · 12 min
    4. Prompt injection and connected accountsReading · 8 min
    5. The rules: privacy, copyright, disclosure and Australia's AI guardrailsVideo · 14 min
    6. How workplaces govern AI, and why that's a career skillReading · 10 min
    7. Live build: lock down your setupLive class · 75 min

    Assessment

    1. 4.1
      Your security audit

      Every tool and connector you use: its privacy setting, what data it can reach, two-factor on, anything you don't need switched off.

      You submitThe audit checklist, with changes made.

    2. 4.2
      Your personal AI policy

      One page: what you'll never put into AI, which tools you trust for what, and how you check anything that matters.

      You submitThe policy.

    Explore

    Open the privacy settings of every AI tool and connector you've set up. Change at least one. Then find a real AI scam reported in Australia this year and work out how you'd have spotted it.

    Knowledge check

    • Name three things that never go into an AI tool.
    • How would you spot a voice-clone scam call?
    • What does Australia's Voluntary AI Safety Standard ask of organisations?
    Week 05Make it run on its own, and build your own tool3 assessed tasks

    A heavy week. Scheduled tasks, documents that build themselves, a skill you write yourself, and a small app of your own with real data.

    By the end of the week you can

    • Schedule a recurring AI task
    • Write and test your own skill
    • Plan and build a small app with saved data

    Lessons · 2 h 28 min

    1. Scheduled tasks and routinesVideo · 10 min
    2. Documents, PDFs and spreadsheets on autopilotReading · 14 min
    3. Writing your own skillVideo · 12 min
    4. Plan a small app in ten minutesVideo · 10 min
    5. APIs and data, simplyReading · 12 min
    6. Live build: one automation and one tool eachLive class · 90 min

    Assessment

    1. 5.1
      An automation that saves an hour

      Automate one weekly job: a budget, a meal plan, a report, job applications. Time it before and after.

      You submitThe automation and both times.

    2. 5.2
      Your own skill

      A skill that does one thing exactly your way, tested on three inputs.

      You submitThe skill folder and three outputs.

    3. 5.3
      Your own tool

      A small app that solves one of your own problems, with saved data: a budget tracker, a habit tracker, a job-hunt board.

      You submitA walkthrough recording and your trial-and-error log.

    Explore

    Time three jobs you do every week and automate the longest. Then find an app you pay for that you only use one feature of, and build that feature.

    Knowledge check

    • What makes a task worth automating?
    • What is a skill?
    • Where does your tool's data live?
    Week 06Take it to the world, honestly2 assessed tasks

    No get-rich-quick promises. Pick the business model that fits you now: AI in your job, builds for local businesses, a productised offer or content. Then price it, publish it and pitch it.

    By the end of the week you can

    • Pick an offer that matches your skills
    • Price it and publish an offer page
    • Make your first ten approaches

    Lessons · 2 h 36 min

    1. The business models, revisited: which one is yours nowVideo · 12 min
    2. Selling builds to local businesses: sites, automations, assistantsReading · 14 min
    3. Productised offers: build once, sell many timesVideo · 10 min
    4. AI in your job: becoming the person your team asksVideo · 10 min
    5. Pricing, scoping and saying noReading · 10 min
    6. The basics before you charge: an ABN, a simple agreement, the rules on claimsReading · 10 min
    7. Showcase: pitch it liveLive class · 90 min

    Assessment

    1. 6.1
      Your offer page

      One thing you can now do for other people, priced and published on your site.

      You submitThe URL.

    2. 6.2
      Capstone: ten approaches and a pitch

      Ten real approaches and a two-minute pitch to the cohort.

      You submitYour outreach log and the recording.

    Explore

    Find five people offering something like your offer. What do they charge, and what would you do better?

    Knowledge check

    • Why avoid income claims?
    • What makes an offer specific?
    • What will you build for your first client?

    How you're assessed

    Every build task is marked Satisfactory or Not Yet Satisfactory by a coach, with written feedback within three working days and unlimited resubmissions. Each week also has a short knowledge check. The next week opens when this week's tasks are marked Satisfactory.

    What you receive

    A certificate of completion and a verifiable digital badge listing the skills you showed, linked to your builds. This is a short course. It isn't nationally recognised training and doesn't lead to a qualification.

    Book a demo of AI for you
  • AI for business12 weeksUnits and assessment
    • Course code AIB-12
    • 12 weeks
    • 8 to 10 hours a week
    • 36 assessed build tasks
    • Certificate of completion

    12 weeks: a dense learn pack, an Explore block and three build tasks every week, a core security and governance week, two build-sprint weeks, a live build every Tuesday at 6pm, and a coach who marks every task.

    Week 01Your whole kit, and your first build3 assessed tasks

    No easing in. By Friday you have every tool installed, a business brain the AI reads first, three skills plugged in and a script running on your own computer.

    By the end of the week you can

    • Set up Claude, Claude Code, git and GitHub
    • Write briefs with context, task, format and a check
    • Install skills and connectors, and know when each one fires
    • Run the learning loop on your own: search, try, break, fix, log

    Lessons · 3 h 34 min

    1. How to learn AI: the trial-and-error loopReading · 10 min
    2. Where this course takes you, and your businessVideo · 10 min
    3. What's really happening when you type a messageVideo · 12 min
    4. The four-part brief, and making AI check itselfVideo · 12 min
    5. Your data rule: what goes in, what never doesReading · 10 min
    6. Install everything: Claude, Claude Code, git, GitHubLab · 60 min
    7. Skills and connectors in ten minutesVideo · 10 min
    8. Live build: your kit, working, by 7pmLive class · 90 min

    Assessment

    1. 1.1
      Your business brain

      A one-page context file: what you sell, who buys, your prices, your tone, your data rule. Every later task feeds it to the AI first.

      You submitThe file, plus one before-and-after answer showing the difference it makes.

    2. 1.2
      A script that saves an hour

      Pick a boring computer job (renaming files, merging spreadsheets, turning a list into a CSV) and have Claude Code build a script that does it in one command. Put it on GitHub.

      You submitThe GitHub repo and a 60-second recording of it running.

    3. 1.3
      Three skills, tried and logged

      Install three skills from the library and use each on a real job. Log what worked, what broke, and what you asked the AI when it broke.

      You submitYour trial-and-error log with three entries.

    Explore

    Open the skills library, read the names of every skill in it, and install three that look useful for your business. Try each on real work. Write down one that surprised you and one that did nothing.

    Knowledge check

    • Why does a long conversation get worse over time?
    • What are the four parts of a brief?
    • Name two things that never go into an AI tool.
    Week 02Your website, designed and live3 assessed tasks

    Why AI work looks like AI, the design process that fixes it, and your website on your own domain by the end of the week.

    By the end of the week you can

    • Name the ten tells of AI-made design and ban them
    • Run the process: direction, references, type, colour, build, screenshot, fix
    • Run a site locally, deploy it and connect a domain

    Lessons · 2 h 37 min

    1. The slop list: ten things that scream AIVideo · 12 min
    2. Pick a direction before you touch anythingReading · 14 min
    3. Design skills and the screenshot loopReading · 12 min
    4. Hosting locally: localhost, ports and dev serversReading · 15 min
    5. Deploying and domains without the jargonVideo · 14 min
    6. Live build: launch nightLive class · 90 min

    Assessment

    1. 2.1
      Your website, live

      Build your business site with Claude Code from a one-sentence direction. Run it locally, deploy it, point your domain at it and make the contact form reach your inbox.

      You submitThe live URL, the repo and a test enquiry arriving.

    2. 2.2
      Three directions, one winner

      Build your homepage three ways from three different direction sentences. Screenshot all three and say why the winner won.

      You submitThree screenshots and three sentences.

    3. 2.3
      One asset redesigned

      Take a flyer, menu or quote template you already use and redesign it with your direction and a design skill.

      You submitBefore and after images.

    Explore

    Find two design skills and one font pairing you'd never have picked yourself. Build the same page three ways with three different directions, and keep the best one.

    Knowledge check

    • Name four tells of AI-made design.
    • What is localhost?
    • What does a DNS record do?
    Week 03Explore week: skills, plugins and hooks3 assessed tasks

    A week of deliberate play. Hunt down skills, break them, write your own, and set rules the AI can't forget.

    By the end of the week you can

    • Find, judge and install skills without a guide
    • Write and test skills of your own
    • Use hooks so the AI follows rules every time

    Lessons · 3 h 50 min

    1. What a skill is, and how the AI decides to use oneVideo · 11 min
    2. Writing a skill with the skill creatorVideo · 14 min
    3. Hooks: rules the AI can't forgetReading · 10 min
    4. Explore: ten skills in one afternoonExplore · 120 min
    5. Live build: a skill for every person in your teamLive class · 75 min

    Assessment

    1. 3.1
      Ten skills, logged

      Your trial-and-error log for ten skills, including three you found yourself.

      You submitThe log.

    2. 3.2
      Two skills of your own

      Write two skills that do recurring jobs exactly the way your business would, such as a quote and a follow-up. Test each on three different inputs.

      You submitBoth skill folders and three outputs from each.

    3. 3.3
      One hook

      Add one hook that enforces a rule: never use a banned word, always run the tests, always screenshot before finishing.

      You submitThe hook and a recording of it catching a mistake.

    Explore

    Try ten skills this week, at least three you found by searching rather than from our list. For each, one line: what it does, whether you'd keep it, and what broke.

    Knowledge check

    • What is the difference between a prompt and a skill?
    • How do you know a skill was actually used?
    • When would you use a hook instead of a skill?
    Week 04Connect your tools: APIs and MCP3 assessed tasks

    Give the AI hands. Connect email, calendar, files and the apps you pay for, move data between them, and learn where the risks are.

    By the end of the week you can

    • Explain an API, a key, a webhook and an MCP server
    • Keep secrets out of code
    • Spot prompt injection and keep a human on anything that sends

    Lessons · 2 h 20 min

    1. APIs explained with a restaurantVideo · 9 min
    2. Keys, secrets and .env filesReading · 12 min
    3. What MCP is, and why it changed everythingVideo · 11 min
    4. Prompt injection: when an email gives your AI ordersReading · 10 min
    5. Rate limits and credits: the timer that burnt a month of creditsReading · 8 min
    6. Live build: connect three of your toolsLive class · 90 min

    Assessment

    1. 4.1
      Your inbox assistant

      Connect email and calendar. Build an assistant that sorts today's inbox into reply, delegate and ignore, and drafts replies for you to approve. It never sends on its own.

      You submitA recording of a morning run and three drafts.

    2. 4.2
      Pull your data out

      Use one tool's API to pull last month's bookings, invoices or leads into a spreadsheet with one command. Keys stay in .env.

      You submitThe repo, with no keys in it, and the spreadsheet.

    3. 4.3
      One MCP server you found yourself

      Install an MCP server from the directory for an app you use and do one real job with it.

      You submitYour log entry and the result.

    Explore

    Browse the MCP servers directory and find one server for an app your business uses. Install it, ask the AI what it can now do, and try to make it do something it shouldn't.

    Knowledge check

    • What is the difference between an API call and a webhook?
    • Where should an API key live?
    • Give an example of prompt injection.
    Week 05Automate the admin3 assessed tasks

    Scheduled tasks, triggers and no-code tools: the jobs that happen every morning without anyone remembering.

    By the end of the week you can

    • Schedule tasks and trigger them from events
    • Choose between no-code tools and code
    • Build in a human check where money or people are involved

    Lessons · 2 h 16 min

    1. Three ways to make something run on its ownVideo · 12 min
    2. Scheduled tasks, cron and cloud routinesReading · 14 min
    3. Zapier, Make, n8n or code?Video · 10 min
    4. Logs, alerts and the human checkReading · 10 min
    5. Live build: follow-up on autopilotLive class · 90 min

    Assessment

    1. 5.1
      A morning automation

      Every weekday morning: yesterday's sales, overdue invoices, missed enquiries. It logs what it did and asks before anything reaches a customer.

      You submitA week of logs and one output.

    2. 5.2
      Follow-up on autopilot

      Automate one follow-up your business forgets: a quote not answered, a booking reminder, a review request.

      You submitThe automation and three messages it drafted.

    3. 5.3
      No-code versus code

      The same automation built both ways, with your verdict.

      You submitBoth versions and a paragraph.

    Explore

    Build the same small automation twice: once in a no-code tool and once with Claude Code. Note which was faster, which broke, and which you'd trust.

    Knowledge check

    • What is a cron schedule?
    • When would you pick no-code over code?
    • Where should a human check sit?
    Week 06AI security and governanceCore unit3 assessed tasks

    A core module in every course. Everything you've connected so far can leak data, spend money or say the wrong thing to a customer. This week you lock it down and write the rules your business will run AI by.

    By the end of the week you can

    • Classify your business data and decide what AI may touch
    • Know your obligations under the Privacy Act and the Notifiable Data Breaches scheme
    • Write an AI use policy and a register of every AI tool you run
    • Lock down keys, permissions, connectors and data retention
    • Apply Australia's Voluntary AI Safety Standard and the AI Ethics Principles to a small business

    Lessons · 3 h 2 min

    1. The AI security checklist for a small businessReading · 15 min
    2. Your data: what's personal, what's sensitive, what's yoursVideo · 12 min
    3. Privacy Act, APPs and data breaches, in plain EnglishVideo · 14 min
    4. Vendor settings: retention, training, connectors and who can see whatReading · 12 min
    5. Prompt injection, permissions and least privilegeVideo · 12 min
    6. Governance that fits a small business: policy, register, risk, human reviewReading · 15 min
    7. Copyright, accuracy, bias and telling customers it's AIVideo · 12 min
    8. Live build: audit your own setupLive class · 90 min

    Assessment

    1. 6.1
      Your AI use policy

      One to two pages: which tools are approved, what data may go into each, who reviews AI output before customers see it, and what happens when something goes wrong.

      You submitThe policy.

    2. 6.2
      Your AI register

      Every AI tool and automation you run: what it does, what data it touches, its risk level, who owns it and when it was last reviewed.

      You submitThe register.

    3. 6.3
      A security audit of everything you've built

      Keys out of code, least-privilege permissions, retention settings checked, connectors you don't need switched off, a backup restored.

      You submitThe audit checklist, with fixes.

    Explore

    Read the privacy and data-retention settings of every AI tool you've connected so far. Find one setting that surprised you and change it. Then try to get your own inbox assistant to leak something, and fix what you find.

    Knowledge check

    • What counts as personal information under the Privacy Act?
    • When does a data breach have to be reported?
    • Name three guardrails from the Voluntary AI Safety Standard.
    • Where does a human have to stay in the loop in your business?
    Week 07Build sprint 1: solve a real problem3 assessed tasks

    No new content. Pick the most annoying problem in your business and solve it end to end with everything from weeks 1 to 5. Your coach reviews your plan on Tuesday and your build on Friday.

    By the end of the week you can

    • Plan a build before starting it
    • Combine skills, connectors, APIs and automations in one tool
    • Ship something a real person uses

    Lessons · 3 h 10 min

    1. Shape it first: who it's for and what done looks likeVideo · 10 min
    2. Live build: plan reviewLive class · 60 min
    3. Live build: open build nightLive class · 120 min

    Assessment

    1. 7.1
      Your build plan

      One page: the problem, who uses the fix, what done looks like, which pieces you'll combine.

      You submitThe plan, marked by Tuesday.

    2. 7.2
      The build, shipped

      Build it, use it for real for three days, and fix what breaks.

      You submitA two-minute walkthrough video and the repo.

    3. 7.3
      Your sprint log

      Everything that broke and how you fixed it.

      You submitThe log.

    Explore

    Before you build, search for three people who've solved a similar problem with AI. Steal the best idea from each.

    Knowledge check

    • What made your plan change once you started building?
    • Which piece broke most, and why?
    • Who uses it now?
    Week 08Dashboards and data3 assessed tasks

    Get your real numbers out of five apps and onto one page that tells you what to do next.

    By the end of the week you can

    • Store data in a simple database
    • Choose honest charts
    • Build a dashboard that answers questions

    Lessons · 2 h 8 min

    1. From spreadsheet to databaseVideo · 12 min
    2. Charts that tell the truthReading · 15 min
    3. Servers, static pages and when you need eachVideo · 11 min
    4. Live build: a dashboard on your dataLive class · 90 min

    Assessment

    1. 8.1
      Your dashboard

      The three numbers that matter most, a trend, and what needs action today. It refreshes on its own.

      You submitA screenshot, the URL and one decision it helped you make.

    2. 8.2
      Your data in a database

      Move one spreadsheet you rely on into a database the dashboard reads.

      You submitThe schema and the import script.

    3. 8.3
      A weekly report that writes itself

      A PDF or email report built from the same data every Monday.

      You submitTwo weeks of reports.

    Explore

    Find three dashboards you admire (any business, any app) and work out what question each one answers first.

    Knowledge check

    • When does a spreadsheet stop being enough?
    • Name a chart that misleads and why.
    • What makes a dashboard more than a list?
    Week 09Your own tool, part 1: build it3 assessed tasks

    The small piece of software you keep paying too much for: a CRM, a booking app, a quote builder or a client portal. This week it works on your laptop.

    By the end of the week you can

    • Design the screens and data before building
    • Add logins and roles
    • Build with tests from the start

    Lessons · 2 h 12 min

    1. Screens and data firstVideo · 12 min
    2. Logins, roles and databasesReading · 18 min
    3. Tests first: proving it works before you trust itVideo · 12 min
    4. Live build: your tool, running locallyLive class · 90 min

    Assessment

    1. 9.1
      The spec

      Screens, data and the annoyances list.

      You submitThe spec.

    2. 9.2
      It runs locally

      Logins, the main screen and real data, running on localhost.

      You submitA walkthrough recording.

    3. 9.3
      Tests passing

      At least ten tests that prove the important parts work.

      You submitThe test run.

    Explore

    Use the tool you're replacing for an hour and write down every click that annoys you. That list is your spec.

    Knowledge check

    • Why write tests before trusting a tool?
    • What's the difference between a login and a role?
    • What did the annoyances list change?
    Week 10Your own tool, part 2: ship it3 assessed tasks

    Put it on a server, lock it down, back it up and hand it to the people who'll use it.

    By the end of the week you can

    • Deploy to a server with a database
    • Keep personal data and keys safe
    • Back up and restore for real

    Lessons · 2 h 6 min

    1. Servers you can actually affordVideo · 12 min
    2. Security basics: personal data, keys and backupsReading · 14 min
    3. Handing it over: training the people who'll use itVideo · 10 min
    4. Live build: ship nightLive class · 90 min

    Assessment

    1. 10.1
      Deployed

      Live on a server with a demo login.

      You submitThe URL and a demo login.

    2. 10.2
      A backup you restored

      Back it up, wipe a copy, restore it.

      You submitA recording of the restore.

    3. 10.3
      First real users

      Two people use it for a week. Fix what they hit.

      You submitTheir feedback and your fixes.

    Explore

    Try to break into your own tool: wrong passwords, someone else's record, a huge upload. Fix what you find.

    Knowledge check

    • What personal data should a small tool avoid storing?
    • What is a backup you have actually tested?
    • What did your users hit first?
    Week 11Agents, voice and documents3 assessed tasks

    Sub-agents that work in parallel, AI voice for receptionists and video guides, and documents that build themselves.

    By the end of the week you can

    • Use sub-agents for research and review
    • Add voice, with honest disclosure
    • Generate documents and PDFs from data

    Lessons · 2 h 7 min

    1. Agents and sub-agents: many hands, one bossVideo · 12 min
    2. Voice: receptionists, voice-overs and video guidesReading · 15 min
    3. Documents and PDFs that build themselvesVideo · 10 min
    4. Live build: an agent teamLive class · 90 min

    Assessment

    1. 11.1
      An agent workflow

      Research or review work split across sub-agents, with one agent checking the others.

      You submitThe run and its output.

    2. 11.2
      A document generator

      Proposals, quotes or reports generated from your data in your design.

      You submitThree generated documents.

    3. 11.3
      A video guide

      A two-minute guide to your own tool.

      You submitThe video.

    Explore

    Record a two-minute video guide for your own tool with an AI voice-over. Then record it in your own voice. Ask three people which they trust more.

    Knowledge check

    • When is a sub-agent worth it?
    • What must a voice agent always disclose?
    • What makes a generated document trustworthy?
    Week 12Build for someone else, then show it3 assessed tasks

    No new content until showcase night. Build a tool for another business, cost everything you've built, and demo your toolkit. Building for someone else is how you find out you're competent, and it's where this course can take you next.

    By the end of the week you can

    • Take a brief from someone else and build to their needs
    • Cost and maintain every tool you've built
    • Know the paths from here: running your business on AI, building for others, or an AI role

    Lessons · 3 h 44 min

    1. Taking a brief like a builderVideo · 10 min
    2. What it costs to run, and how to keep it runningReading · 10 min
    3. Where you can go from here: your business, other businesses, AI rolesVideo · 12 min
    4. Selling what you can build, honestlyReading · 12 min
    5. Live build: brief swapLive class · 60 min
    6. Showcase night: demo your toolkitLive class · 120 min

    Assessment

    1. 12.1
      A tool for someone else

      Take their brief, build it, hand it over with a one-page guide, and have them use it for three days.

      You submitTheir brief, their feedback and your handover guide.

    2. 12.2
      Your running costs

      Every tool, what it costs a month and what it saves.

      You submitThe cost sheet.

    3. 12.3
      Capstone: your toolkit demo

      Ten minutes: each tool, the problem it solves, what it saves, what you'll build next.

      You submitThe recording and a one-page summary.

    Explore

    Interview another business for 30 minutes and find the job they hate most. Then look back at your week 1 log and pick the three biggest lessons.

    Knowledge check

    • What did they ask for that you'd never have built for yourself?
    • Which tool saves the most, and how do you know?
    • What will you build next?

    How you're assessed

    Every build task is marked Satisfactory or Not Yet Satisfactory by a coach, with written feedback within three working days and unlimited resubmissions. Each week also has a short knowledge check. The next week opens when this week's tasks are marked Satisfactory.

    What you receive

    A certificate of completion and a verifiable digital badge listing the skills you showed, linked to your builds. This is a short course. It isn't nationally recognised training and doesn't lead to a qualification.

    Book a demo of AI for business
  • AI for marketing6 weeks
  • AI for admin and the office6 weeks
People passing on a city street For RTOs and training providers

Sell all seventeen under your own name.

Nothing up front. A share of the fees you collect.

Talk about licensing

Questions

Do I need to know how to code?

No. Every course starts from zero. The AI writes the code; you learn to direct it, check it and fix it.

How much time does it take?

Six to ten hours a week, depending on the course: one live class, short lessons, and the week's build. Every class is recorded.

Is it nationally recognised training?

No. These are short courses. You finish with a certificate of completion and a digital badge that links to what you built.

Can I train my whole team?

Yes. Teams start together as their own group, with the live class at a time that suits them and builds on the business's own work.

What happens to my data?

Your builds are yours. We show you how to keep private and client information out of AI tools, and the course has a full week on AI security and safety.

Can my RTO or training provider offer these courses?

Yes. Training providers license any course and sell it under their own name: nothing up front, a share of the fees collected, with the marketing built and coaches available.

Book a 15‑minute demo.