Your team, fluent in AI.
Hands-on training for teams that want real work out of Claude, ChatGPT, Gemini, and the tools around them. Half day or full day, in person or remote, built from the work your team already does.
Book a training callDear valued customer, I hope this email finds you well. I am reaching out to touch base regarding our previous correspondence...
no context · no constraints · sounds like everyone
Dana, good news on the onboarding worry: setup is 45 minutes with your team on the call, not the weeks you were quoted. Free Thursday to walk through it?
context · constraint · clear ask
The tools your team already has. The fluency it doesn't.
Most companies bought the licenses before anyone learned the tools. We close that gap.
Everyone has AI. Why is nobody faster?
Because a license is not a skill. A few people on every team get good on their own. Everyone else types a sentence into a chat window, gets a mediocre answer, and quietly goes back to doing it the old way. The distance between what these tools can do and what most teams get out of them is enormous, and it does not close by itself. Training closes it: your people, on their own work, with someone in the room who does this every day.
What we cover
A working understanding of AI, taught in plain language through the work your team already does.
Prompting that holds up on real work
How to ask so the answer is useful the first time: context, constraints, examples, and how to push back when the output is almost right. The gap between a chat toy and a work tool is mostly in how you talk to it.
The tools, side by side
Claude, Cowork, ChatGPT, Gemini, Copilot. What each one is genuinely good at, where each falls down, and which to reach for in a given job, so your team stops guessing.
The everyday workload
Drafting, summarizing, research, analysis, meeting notes, first passes at anything. The unglamorous daily work where these tools quietly return hours to your week.
Judgment, not just usage
Where AI gets things wrong with total confidence, and how to verify before you rely on it. Knowing when not to trust the output is half of being good at this.
Agents, in plain language
What tools like Claude Code and Cowork actually do: AI that takes a goal and works through the steps itself. What that makes possible for a team, explained without the jargon.
A practice that sticks
A shared prompt library, working habits, and a way to keep learning after we leave. The session is the start of a team practice, not a one-day event.
What does a session look like?
A scoping call
We learn what your team does all day, which tools you already pay for, and where the hours go. That call shapes everything that follows.
A curriculum from your work
The exercises come out of your documents and your workflows, not a canned demo. Nobody has to translate a generic example into their own job.
The session
Half day or full day, in person or remote. Everyone works on their own machine, on their own tasks, and leaves having done real work a new way.
What you keep
A recording of the session, the prompt library the room built together, and a written Q&A answering everything that came up.
Our team ranges from power users to people who avoid it. Does that work?
That is the normal room, and the session is built for it. Everything is taught in plain language, grounded in examples from your own company, and nobody gets left behind for not knowing a term. The power users leave with sharper technique and the skeptics leave having watched AI do an hour of their own week in minutes. Skepticism usually survives a demo. It rarely survives that.
Common questions
How long is a training session?
Half day or full day. The scoping call decides which fits: a half day covers the core working skills, a full day adds deeper practice on your own workflows and a segment on agents. Both end with a prompt library your team built itself.
Remote or in person?
Both. In person around Los Angeles and the Bay Area, remote anywhere. The session is hands-on either way: everyone works on their own machine, on their own tasks.
Do our people need to be technical?
No. Everything is taught in plain language and grounded in examples from your own company. Mixed rooms are the normal case: power users leave with sharper technique, and beginners leave past the blank-page problem.
Which tools do you cover?
Claude, Claude Code, Cowork, ChatGPT, Gemini, and Copilot, weighted toward whatever your team already pays for. Tool choice is part of the scoping call.
How many people can join?
It works best between five and twenty-five. Larger groups split into two sessions, so everyone gets hands-on time instead of watching.
What do we keep afterward?
A recording of the session, the prompt library the room built, and a written Q&A document answering everything that came up, including the questions we went away to check.
Want a team that actually knows these tools?
Tell us what your team does all day, and we build the session around it.
Or send us a note at [email protected]