Do I need to know how to code to attend?
The name is misleading. Claude Code works on the folder you point it at and the files inside it: the documents, spreadsheets and decks your team opens every morning. In the first session everyone in the room learns to run the tool on their own tasks, and in the second we build the workflows chosen during discovery.
What is Claude Code?
An Anthropic tool that lives in the Claude desktop app, under the Code tab. It sees one folder you choose, then reads → plans → executes → checks itself → and repeats until the result matches the request. Permissions are set in advance: when it asks, when it acts on its own, and what it must never touch.
How long is the workshop and how is it structured?
Two in-person sessions, four hours each, one to two weeks apart. The first covers the fundamentals, the second builds the workflows chosen during discovery. The gap is long enough for people to experiment on their own, short enough that they do not forget.
Why is there a discovery phase before the workshop?
Because a general AI talk has already been through your organization, and few people can open the tool on a Monday morning and do something that relates to their actual work. In discovery I learn what the team opens every morning, which recurring tasks eat the most hours, who already works with AI and who is touching it for the first time, and what management wants to see a month later. The examples, exercises and integrations for both sessions are built from that.
What do participants need to bring?
A laptop with the Claude desktop app installed and an active account. The install guide goes out a few days before the first session, and in the first few minutes I check that everyone has the tool open and connected.
What happens with sensitive data?
Claude Code sees only the folder you selected, which is both the protection and the limitation. What can be connected and what stays out is decided during discovery, together with whoever owns IT on your side.
Who handles licensing and permissions?
The organization. Tool licensing and IT permissions sit on your side, and I walk the process through with whoever owns it. Start early, it is usually the slow part.
How many people can attend?
One instructor per five participants. Up to five I run the workshop alone, and at ten I bring an additional instructor, so everyone gets attention during practice. The workshop is in person only, for exactly that reason.
How is this different from a regular AI workshop?
A regular AI workshop shows you tools and you leave with a list. Here participants work on their own real tasks and on the organization's own files, and leave with a workflow that runs. That is also why discovery comes first: without knowing what the team opens every morning, every example in the room is somebody else's example.
Is this vibe coding?
Vibe coding means describing what you want in plain language and letting the tool build it. That is what happens in the workshop, except the output is not an app: it is the process you run every week, the report you used to assemble by hand, the connection between two systems that do not talk. Most of the first session is about exactly that, how to phrase a request so what comes back is what you wanted.
How is this different from the ChatGPT we already have?
ChatGPT answers you in a window, and you copy that answer over to where the work actually lives. Claude Code sees the folder you selected, opens the files inside it, works on them and hands back a result. What changes is who does the work between the answer and the file.
