AI That Does Your Work

The course

About this course

Not AI literacy and not a demo. A half day in which each person takes one recurring piece of their own work, a reconciliation, a lead sheet, a forecast tab, a report pack, a vendor tracker, and turns it into a process that runs the same way every time: input, transformation, output, human check. We teach on a shared practice dataset so the room stays together, then each person applies it to their own file. By the end, every table has ranked its recurring processes by hours, frequency, and how rule-bound they are, and picked the first two. Runs on Claude or Copilot, whichever your organization allows; the pattern is what you keep when the tools change.

Who it is for

Finance and operations staff: accounting, FP&A, AP and AR, finance systems, and the ops, HR, and procurement teams around them

Format

Hands-on half day. Everyone brings one recurring task and one file, and leaves with it running.

What the team leaves with

Outcomes

• One of your own recurring processes running through the tool, with a one-page process card: input, what I do to it, output, who checks it, how often, how long.
• The trust model in plain terms: what these systems are and are not, why the ERP stays and the spreadsheet layer shrinks, and what never goes in.
• A first-pass sub-ledger to GL reconciliation, or a lead-sheet flux commentary, or a forecast workbook refresh, done on practice data and then on yours.
• A ranked roadmap of the team's recurring processes, with the first two chosen and an owner for each, in the sponsor's hands before the room empties.

Outline · 2.5 hours

How the session runs.

Usually 9:30 to 12:00 or 2:00 to 4:30. Other times are fine.

1. 0120 min

   What this is, and what it is not

   • What these systems do reliably and where they guess. The ERP stays; the spreadsheet layer shrinks.
   • The pattern: input, transformation, output, human check. Deterministic where it must be, AI where it helps.
   • The data question, answered from the guide we sent ahead.
2. 0230 min

   One process, together, on practice data

   • The AP sub-ledger to GL reconciliation: the tie stays in the query, the tool drafts the timing-versus-error explanations and the approval email.
   • Writing the process card that becomes the instruction.
   • The ten-second check that catches a wrong number.
3. 0350 min

   Your process, on your file

   • Each person builds their own card and runs it: lead sheet commentary, forecast tab, report pack, vendor expiry tracker, close checklist.
   • Pairs swap: you run your neighbour's process on their data. If a second person can reproduce it, it is a process.
   • Six starter tasks on the shared data for anyone who brought nothing.
4. 0420 min

   The control layer

   • What never goes in, and how you tell.
   • Who approves, where the log lives, and how you would defend the output to an auditor.
   • The harvest: one that worked, one that half-worked, one that was the wrong job for AI.
5. 0530 min

   The roadmap

   • Each table lists its recurring processes and ranks them by hours, frequency, and how rule-bound they are.
   • Pick two. Name an owner. First ones should be high volume, rule-bound, and something the auditor will not ask about.
   • The sponsor leaves with the company's list.

Bring

What to bring

• A laptop and a Claude or Copilot login your organization allows for work. Setup instructions come ahead of the course.
• One recurring task and one file it uses. A sanitized or practice version is fine.

If IT blocks the tool, tell us on the call and we plan around it.