A domain track
Non-technical professionals in any role who have tried Claude for a one-off email or summary but never made it part of the actual job. This track turns the files, reports and decks you touch every week into work Claude does with you, and settles what's actually safe to share with it.
24 topics
You asked Claude to tidy an email once. It was fine, and the following week you opened a blank document anyway. That is a normal place to be. In a mixed room, people from finance, HR, operations and support each bring one chore that comes back every week: the report rebuilt by hand every Sunday, the inbox folder full of PDFs, the Excel file with the tab nobody dares touch. Nobody ever wrote that chore down, and it is what the day is built on.
What stops most people is not the tool but one question: what am I allowed to paste in? Without an answer, not trying is the sensible choice. So the session starts by writing the answer down together, on a single page. Which files can go in as they are, which get masked first, which never go in, and who rules on the odd case. It is worded the way your organization talks, and it can go straight to the next person who joins.
The rest of the day runs on real material. Several long documents shrink to one page with their contradictions marked. A first draft of an email or deck comes out in your tone and your template. A static spreadsheet answers questions asked in plain language, no formula needed. A weekly routine runs from raw files to the summary email on its own. Each participant leaves having run one of these on their own file, and knowing how to run it again on Monday.
A live opening session built to shift the room, not lecture it: real demos of what Claude can already do inside your workflows, run in front of the group. Participants leave with a working sense of where AI helps and where it doesn't, and enough curiosity to start using it that afternoon.
What tokens, context windows and hallucinations mean, explained without the math and without the hand-waving. Once a team understands why a model sometimes gets things wrong, it stops either trusting it blindly or dismissing it after one bad answer. Every other module in the program builds on this one.
Before the work starts, we walk the Claude screen together: a new conversation, uploading files, choosing a model, and where Projects, Artifacts and Skills live. Face to face it is a live demo; in the online course it is a recorded tour. Ten minutes that save weeks of fumbling.
Claude Skills turn a procedure your team already does well into something Claude can repeat on its own: the same checklist, the same tone, the same edge cases covered every time. You build it once with the person who actually knows the process, and from then on every teammate gets that expertise on demand. For teams where quality depends on one or two people, this is how that stops being a bottleneck.
Structure, context and role framing: the craft of asking in a way that gets a usable result on the first try instead of the fifth. Participants practice on real prompts from their own work, not toy examples, so what they take home already fits the job. Every other module assumes this fluency, which is why it comes early.
Claude Projects hold your documents and instructions in one persistent workspace, so every conversation starts already knowing your company, your terminology and your rules. Teams that set this up once save the ten minutes of re-explaining context at the start of every session, every day. For anyone running the same kind of task repeatedly, this alone changes the math.
Artifacts are documents, dashboards and small interactive tools Claude builds live inside the conversation, editable on the spot instead of copied out and reformatted. The session covers static outputs and interactive artifacts alike, with an eye on what a non-technical teammate can actually ship without engineering help. It's the module that convinces people Claude is a builder, not just a chatbot.
The shift from asking Claude a question to handing it a multi-step task it completes on its own, checking in only where it matters. Participants learn what actually counts as an agent, when handing over work beats doing it turn by turn, and how supervision needs to change once Claude is running unattended. Get this wrong and you either babysit an agent that didn't need it or trust one that did.
In the Claude chat you can hand over a whole job instead of asking a question. Claude plans the steps, searches the web, reads your files, runs code and hands back a finished document, spreadsheet or deck. On a big task it can split the work between several sub-agents running at once. Participants learn which work is worth handing over and how to brief it the way they'd brief a colleague, then practice staying in control while Claude works. They finish by turning a weekly chore into a scheduled task that runs on its own.
A full pass across the Office suite: drafting and redlining in Word, tables and analysis in Excel, decks in PowerPoint, and inbox triage in Outlook, taught as one connected workflow rather than four separate tricks. Every exercise uses documents close to what participants actually produce at work. It's the broadest module in the program, and the one most teams come back to most after training.
Tasks Claude runs on its own, on a schedule: a morning brief from your calendar and inbox, a weekly report, a competitor watch. Participants learn to tell a routine from its schedule, connect only the connectors it needs, and test every routine before it runs alone. They leave with one routine that works from the next morning.
Connecting Claude to the systems your team actually runs on: drives, CRMs, databases, through connectors and MCP, with the permission boundaries covered before the connection ever gets made. Participants leave knowing exactly what to expose and what to keep out of reach. This is the module that turns Claude from a smart typewriter into something acting on real, current data.
CLAUDE.md is a plain text file Claude Code reads at the start of every session, so whatever you'd explain to a new hire on day one, you write there once. Participants learn what goes in it and what stays out, when it's read, and where it lives: the organization, you, the project and a subfolder, all loading together. They leave with a draft from /init and one rule for growing it: what you corrected twice goes in the file.
How to build an agent without writing code: it gets a job description, a badge that limits what it can touch, and a bottom line it hands back. Participants see why the work goes to a separate room, take an agent file apart, and fill in the one-page charter that turns into the agent's file. They learn to hire for a role, not a task, and to tell when a job needs an agent rather than a skill. They leave knowing the hard part is the charter, and that the charter is their own expertise, written down.
A plugin carries the agents, skills and hooks a team built, so another team installs the same department instead of rebuilding it. Participants see what goes in the box and what stays home: CLAUDE.md and the permission rules belong to each team. Then they ask Claude to build one, try it in a fresh session, and share it through a marketplace.
How context windows, memory and cost interact, and what to do about it before a long working session starts drifting or the bill surprises someone. Participants learn to spot when Claude is still hauling a task that should have been closed an hour ago, and how to reset without losing what mattered. A short module with an outsized effect on both output quality and the invoice.
The rules every employee needs before their first real session: what data is safe to share, what isn't, and what org-level guardrails should exist so individual judgment isn't the only safeguard. This module is usually the one legal and IT ask for by name. It replaces vague anxiety about compliance with a clear, specific policy people can actually follow.
Where people belong in an AI-assisted workflow: which steps need a review gate, which need an approval, and how to calibrate trust so oversight isn't either everywhere or nowhere. This pilot module gives teams a concrete framework instead of a gut feeling about what to check. Get the calibration right and quality goes up without slowing anything down.
Permissions, prompt injection and data boundaries: what makes an agent that can act also one that can go wrong, and how to run it anyway without carrying the risk. This pilot module is built for organizations moving agents past read-only demos into things that write, send and change data. It's the module security teams should sit in on.
Extending Claude with plugins: how to evaluate one before installing it, what to trust, and when the right move is building the one your team is missing instead. This pilot module keeps the scope practical rather than a tour of everything that exists. Teams leave able to tell a useful plugin from a risky one.
Claude inside Word for text-heavy roles: drafting from a brief, redlining a contract, controlling tone across a document, and automating the parts of writing that are really just formatting. This pilot module is aimed at HR, legal, marketing and sales, where documents are the daily output. It's the module that turns a quick-draft request into a five-minute job.
Coming soon: turning a rough brief into a board-ready deck, structure, story and design covered as one process instead of a slide-by-slide grind. This syllabus item targets teams currently spending a disproportionate share of their week formatting instead of thinking. Expect deck time to drop to a fraction, not just get a bit more polished.
Coming soon: bringing Claude into Slack and Teams so summaries, answers and actions happen where the team already talks, instead of a separate tool people forget to open. This syllabus item covers both the setup and the etiquette of an agent inside a shared channel. Built for teams whose real workflow lives in chat, not in a dedicated app.
Coming soon: writing the AI policy an organization actually needs, usage rules, risk tiers and rollout governance, instead of a generic template nobody follows. This syllabus item is for leadership and compliance stakeholders shaping how AI gets adopted company-wide. Built to produce a document teams can point to, not a discussion that goes nowhere.
Four outputs that work as well for a payroll lead as for a support manager, because each one is built around the task that person brought.
A written list of file types, each sorted into go in, mask first, or stay out. When someone on the team hesitates, they have a page to check instead of a guess. The call on borderline cases stays with the person you name.
Five long documents become a single page, with a list beside it of where they contradict each other. You read the conflicts and decide which version is right. Claude only shows you where to look.
Ask the sheet in plain words which supplier got the most expensive this quarter, and get an answer with the range it came from. Every figure can be checked against the sheet, and the original file stays untouched.
The report you build by hand each week becomes a fixed routine: files go in, a draft summary email comes out. You read it, fix it and send it yourself, but you no longer start from a blank page.
Everyone's own chore
Before the session, each participant names one task that comes back every week, and the exercises are prepared around it, on their own files, once the upload rule is settled. In one room with people from several departments, everyone practices next week's actual work.