Claude training

Your team does not need a Claude demo. It needs to be independent.

Most Claude training stops at prompt tips. Ours ends when your people build with it unsupervised, inside your own stack, with governance your compliance team can defend.

Where you are

If any of this sounds familiar.

You have licences, and usage that has plateaued with a handful of enthusiasts.

Different teams need different things, and one generic session serves none of them well.

Someone in legal or compliance has asked what gets logged, and nobody has a clean answer.

The tracks

Different people need different things.

Claude Code

For engineers. Hands-on in your own codebase, CI and secrets management.

See the track

Claude Cowork

For teams doing document and analysis work, in their own files.

See the track

Claude Chat

For the wider organization, with a governed usage policy behind it.

See the track

Who it’s for

Built for the people who do the work.

Engineering leaders whose teams have Claude Code and no structured way to adopt it
Operations and analysis teams who would get more from Cowork than from a chat window
Enterprises that need a usage policy and an audit trail before rollout, not after

What you get

What your team keeps afterwards.

Hands-on sessions in your own repositories, documents and workflows, not a sandbox

Role-specific starter kits tuned to your actual stack, so people begin from a working setup

The governance module every Kriv engagement includes: who owns which automated action, what gets logged, and what an auditor sees.

A team playbook and reference materials your organization keeps

A leadership readout with an honest view of where adoption will and will not pay off

How it runs

Scoped to your week, not ours.

Discovery workshopHalf day, virtualFind out where Claude fits before committing a budget.

Team enablementOne to three days, on-site or virtualOne or more tracks, delivered to a named team.

Enterprise programMulti-month, hybridAll tracks, multi-department, with implementation support.

Training pricing

Straight answers

The questions that actually come up.

Is this different from the Claude Code training page?

Claude Code is one track under this program, and it has its own page because it is the one most teams arrive looking for. This page is the umbrella: the same delivery model applied to Cowork, Chat and the Agent SDK, so a mixed organization is not forced into a developer-shaped course.

Do you train on the whole Claude surface or just Claude Code?

The whole surface. Claude Code for engineers, Cowork for document and analysis work, Chat for the wider organization, and the Agent SDK where a team is building something durable. Which tracks you take is a scoping decision, not a fixed package.

Who delivers the training?

A senior practitioner who delivers Kriv's commercial engagements, not a trainer reading someone else's deck. There is no junior bench. The person who scopes the program is the person in the room.

What does the governance module actually cover?

Who owns each automated action, what is logged and where, how a decision gets reviewed, and what an auditor is shown. It is in every engagement because a rollout that cannot answer those questions gets stopped later by someone who can.