How we work · Adopt

We set up Claude and train your team.

Claude set up with your IT team, training on your own documents and tasks in your office, then weekly office hours until your team is writing and sharing its own skills.

Who it's for

Leadership has decided AI matters, a few people have tried Claude on their own, and nobody's sure what to do next. The training answers that with your actual work, not a generic course.

What's included

Training on your own work.One or two days in your office on your team's documents and tasks.At IMRIS that was three days on site in Chaska, training the teams on their own work.
Setup with your IT team.One workspace, your domains verified, seats and admin settings in place.At Icelandic Glacial that meant one Team workspace with both domains verified and the separate Iceland plan retired.
Connecting your systems.NetSuite, Microsoft 365 and the other systems Claude connects to, with the permissions that make them work.When a NetSuite permissions rule stopped several finance users at Icelandic Glacial, we traced it and wrote the setup guide the rest of the company used.
Weekly office hours.An hour a week by video for questions on real work.At Icelandic Glacial, group sessions gave way to one-on-one time by mid-August.
Skills written with your team.Built in a session with the person who owns the work, then shared across seats. The skill libraries are yours outright.The NetSuite accuracy skill we wrote with Icelandic Glacial's VP of Finance & Controller went to every seat on August 13.
Scheduled tasks.Claude working through a set list every morning without being asked.Lone Star's legal assistant has two running every weekday, set up in one working session.
Usage reviews.We go through your Claude admin analytics with you: who's using it, on what, and where to train next.

What a session looks like

A call before. We confirm the agenda, who attends and the examples from each team, so the exercises on the day are your own work.
One or two days in your office. A three-hour morning and a two-hour afternoon, with the whole team in the room. We start with the basics: asking clearly, checking what comes back, and what confidential data stays out. Then your own work, team by team, in Claude. Then, for anyone who wants to go further, Claude Code: small tools for the work your team repeats. Remote or hybrid when that works better.
The deck, yours to keep. Written for your office, with the prompts and skills built on the day.
Office hours after. An hour a week by video for the questions that come up on real work, while people start writing and sharing their own skills.

What it produces

A team that uses Claude on its own work. At Icelandic Glacial, finance and production went from first use to writing and sharing their own skills in weekly sessions.

Where it leads

Often the training turns up a problem worth building for. When it does, we build it with the same team, and the training continues around what gets built. Lone Star trained every role first, then got the app. At IMRIS, an engineer in the pilot group went on to build the extraction tools himself.