Claude, learned on your own files.
Writing, analysing long documents, structuring recurring work, producing materials and handing complete tasks over to Claude. Your teams work on what they actually have to deal with — never on exercises.
Four ways in, depending on where you stand.
The format is chosen in a scoping call, based on how many people are involved, their level and what you want to achieve.
Reach everyone
A remote session to set the basics, show what the tool actually does and clear the first questions. No cap on attendees.
or the entire company
Start a practice
The most requested format. Fundamentals plus two or three use cases worked directly on the participants' own files.
from the same function
Build autonomy
The full programme, with time to practise, get it wrong and build your own working methods.
at a similar level
Make it stick
Short sessions spread out, with real work in between. The only format that lets you measure how practice actually evolves.
or internal champions
What your teams can do when they walk out.
The outline below is the full-day format. Shorter formats cover points 1 to 3; delegating complete tasks belongs to the ongoing-support track. Feature names are given as examples: the content is adjusted before each session to the features available in your environment and the way your teams work.
Understanding how Claude reasons
A handful of operating principles change the quality of the output entirely. This is the foundation for everything else — and what most training rushes through.
- Context window — what Claude reads at once, and why a 400-page document isn't handled like a memo
- No memory between conversations — when to open a new thread, when to stay in the current one
- Where errors come from — why a reference is sometimes invented, and the three checks that prevent it
- Anatomy of a good prompt — role, context, task, expected format, example: the difference between a generic answer and a usable one
Writing and rewriting
The most immediate gain for most functions. We work on documents the participants bring, within the confidentiality boundaries agreed with you.
- Meeting minutes from raw notes
- Sensitive letters and emails: several versions, several tones
- Briefing notes and arguments built from multiple sources
- Passing on your style — supplying examples so output reads like what your organisation actually writes
Analysing long documents
The highest-return skill of the day. Contracts, reports, tenders, regulatory texts: extract, compare, interrogate.
- Targeted extraction: clauses, deadlines, quantified commitments
- Comparing several documents and spotting the gaps
- Verification method — demand citations and locate them in the source
- Known limits: complex tables, scanned documents, multi-column layouts
Structuring the work: Projects, Artifacts, Skills
What turns individual experiments into team practice. Three complementary mechanisms, usually discovered too late.
- Projects — standing instructions and shared reference documents: tone, format, business constraints, internal vocabulary, approved templates
- Artifacts — produce a document, a table or a tool, then refine it through the conversation instead of copying everything out
- Skills — package a recurring procedure of yours so it is applied the same way every time, by everyone
- Claude Design — produce a deck, a screen mockup or a visual asset already on brand: the design system (colours, type, templates) is loaded once, and every output comes out compliant
- Organise by use case rather than by person, so one person's work serves the rest
Delegating a whole task, for example with Cowork
The step beyond conversation: hand over a multi-step piece of work instead of steering every answer. It is the most important shift in posture to support.
- What changes — you describe an expected result and a scope, not a sequence of instructions
- What suits it — processing a batch of documents, producing a multi-part deliverable, research and formatting work
- What doesn't — tasks where every decision needs your call
- Staying in the loop — checkpoints, source verification, sign-off before anything goes out
Embedding the habits
A use case that doesn't fit into a routine disappears within three weeks. The closing session exists precisely to prevent that.
- Each participant names two or three use cases applicable the very next day
- Identifying the moments in the week where those use cases fit
- What stays out of scope: tasks where the tool saves no time
- A method for improving alone and spotting new use cases
What it looks like, function by function.
A first selection of cases seen in training. Yours will differ — the scoping session is what brings them out.
Cross-reading documentation
Compare several versions of a regulatory framework, spot the differences and prepare a reasoned position note.
Lease and contract analysis
Extract deadlines, review clauses and obligations across a lease portfolio, then produce a summary per asset.
Audit reports
Turn field notes into a structured report, compliant with the internal template, with an action plan.
On-brand decks and mockups
Client decks, page mockups, campaign visuals: the brand design system is given to Claude once, and every output comes out on brand.
Interactive modules and gamification
Build interactive artifacts — quizzes, simulators, practice paths — to train teams internally, from your existing procedures.
Board and committee prep
Condense a set of heterogeneous documents into a two-page note, with decision points isolated.
“Jonathan was able to adapt his workshop to my specific in-house need. I appreciated the thorough preparation and the teaching quality throughout. It all went very smoothly and the participants came out very satisfied!”
Frequently asked questions
The training is for employees who want to use Claude practically in their work, whether they are beginners or already use the tool. The programme is adapted to the participants’ roles, experience level and the real files they handle.
Yes. Participants work on their own documents, presentations, analyses, files and business cases to develop methods and uses they can apply directly after the session.
Projects creates workspaces with their own context, documents and instructions. Skills provides Claude with reusable instructions, scripts and resources for specialised tasks with greater consistency. Cowork lets users delegate complex, multi-step tasks to Claude, including agentic work and scheduled tasks, according to the features available.
No. The main Claude uses intended for business teams do not require programming skills. The training focuses on providing the right context, structuring requests, checking outputs and building reusable working methods.
Let's talk about your teams and their files.
Book 30 minutes
A scoping call: your context, your teams, the format that fits best.
Describe your need
Three lines is enough: reply within 24 h.