Training · Claude

Claude, learned on your own files.

Writing, long-document analysis, structuring work with Projects and Artifacts, producing mockups and decks with Claude Design, delegating with Cowork. Your teams work on what they actually have to deal with — never on exercises.

Formats

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.

Delivered by · Jonathan Delmas or a trainer from the team, same programme
Webinar · 1 to 1.5 hrs

Reach everyone

A remote session to set the basics, show what the tool actually does and clear the first questions. No cap on attendees.

Leadership team, a whole department,
or the entire company
Half-day · 3.5 hrs

Start a practice

The most requested format. Fundamentals plus two or three use cases worked directly on the participants' own files.

8 to 15 people
from the same function
Full day · 7 hrs

Build autonomy

The full programme, with time to practise, get it wrong and build your own working methods.

8 to 12 people
at a similar level
Ongoing support · 4 to 12 weeks

Make it stick

Short sessions spread out, with real work in between. The only format that lets you measure how practice actually evolves.

A full team
or internal champions
Programme

What your teams can do when they walk out.

The outline below is the full-day format. Shorter formats cover points 1 to 3; Cowork belongs to the ongoing-support track.

01

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
02

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
03

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
04

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 in a dedicated pane, 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
05

Delegating a whole task 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
06

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
Discuss this format — 30 min, free →
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.

Pharma · Regulatory affairs

Cross-reading documentation

Compare several versions of a regulatory framework, spot the differences and prepare a reasoned position note.

Outcome · Hours of reading reduced to a guided pass, with verifiable citations
Real estate · Property management

Lease and contract analysis

Extract deadlines, review clauses and obligations across a lease portfolio, then produce a summary per asset.

Outcome · Systematic reading where a quick skim used to do
Manufacturing · Quality

Audit reports

Turn field notes into a structured report, compliant with the internal template, with an action plan.

Outcome · A report written the same day rather than the following week
Marketing · Communications

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.

Outcome · Presentable assets without going through a studio for every iteration
HR · Internal training

Interactive modules and gamification

Build interactive artifacts — quizzes, simulators, practice paths — to train teams internally, from your existing procedures.

Outcome · Internal modules built in hours, and updatable by the HR team itself
Leadership · Strategy

Board and committee prep

Condense a set of heterogeneous documents into a two-page note, with decision points isolated.

Outcome · Better-prepared committees for the same time spent
“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!”
Jules Fakhoury · Senior Digital Transformation and AI Manager, Novo Nordisk France
Discuss this format — 30 min, free →
Get in touch

Let's talk about your teams and their files.

The direct route

Book 30 minutes

A scoping call: your context, your teams, the format that fits best.

Book 30 minFree · No commitment
In person or remoteEnglish · French · SpanishFrance & internationalIn-house
In writing

Describe your need

Three lines is enough: reply within 24 h.