Give your teams the skills to work with AI.
Most companies already pay for AI seats. We train leaders and teams on the tools you own, using their own documents and reports as the material, so good daily use becomes the habit.
Leadership briefing
Executive team · 2 hours
Week 1 · Briefing
BriefingTeam workshops
Four teams · 90-minute sessions
Weeks 2–5 · 4 sessions per team
4 sessions per teamBuilder track
Six internal builders
Weeks 5–7 · 3 sessions + office hours
3 sessions + office hoursAdoption review
Usage, playbooks, next workflows
Week 8 · Review
Review
Draft the September variance commentary from this month's close pack.
Bring
- Trial balance export
- Budget file, version 3
- Last month's commentary
Practice
- Explain each variance over 5%
- Tie every figure to a source line
- Keep what can go in the tool, and what cannot
The controller reviews and signs off before it is shared.
A better month-end report, in half a day.
Training works when people practice on the work they already do. Here, a finance analyst brings September's close pack to the workshop and leaves with a better draft and a repeatable way to produce it.
- Their own material
- Exercises use the documents, requests, and reports each team handles every week, not generic prompts.
- Review stays with people
- Every exercise ends with who checks the output and what can and cannot go into the tool.
- Adoption you can see
- We agree a measure up front, such as weekly active use, and review it with each team lead after the sessions.
Opex came in over budget this month, mainly due to various items.
Marketing was higher than planned. Travel was also up.
We will look into it and update next month.
- No figures or drivers
- Not traceable to the close pack
- Rewritten each month from scratch
Operating expenses were $412K, $24K (6.2%) over budget.
Marketing +$17K: trade show deposit paid in September for October. Timing, not run rate. TB 6100
Travel +$7K: Q3 customer visits, within the annual plan. TB 6420
Action: move the deposit in the Q4 reforecast. Budget v3
Reviewed and signed off by the controller
Adoption measure · finance team
Weekly active use of the approved AI workspace
People who use AI well, and know when not to.
- 01
Consistent daily use
Teams work from shared patterns, so output quality no longer depends on who wrote the prompt.
- 02
Safe use people understand
Everyone knows what data can go into each tool and when a person has to sign off.
- 03
Builders inside your team
A few people learn to turn repeated tasks into reusable workflows for everyone else.
Leaders, teams, and builders each get their own track.
Every program is built for your people, your tools, and your security rules. Remote or onsite.
Leadership briefing
- What AI can and cannot do for your business today
- Standards for use, review, and data
- A short list of priorities leadership agrees on
Team workshops
- Hands-on sessions grouped by function and experience
- Exercises built from each team's own work
- Guidance for your approved tools and data policies
- Playbooks, shared prompts, and workspaces to keep
Builder track and handover
- Custom assistants and retrieval over company knowledge
- Simple agentic workflows with review steps
- Administrator handover and adoption measures
- Follow-up support within the agreed scope
Leadership education, team training, and system-specific onboarding are scoped separately. Training can be standalone or part of an implementation. A fixed proposal based on people, formats, and how much material is built from your own work.
Built with your team leads, taught on your own work.
Your IT and security owners and a lead from each team take part from the start.
Scope
We confirm tools, access, and data rules with IT and security, and choose the teams and work to start with.
A program plan and agreed adoption measures.
Build the material
Team leads share real examples. We turn them into exercises, prompts, and review checklists.
Exercises from each team's own work.
Run the sessions
Leadership briefing, team workshops, and the builder track, remote or onsite.
Confident daily use and patterns teams keep.
Review adoption
We review the adoption measures with each lead and hand over playbooks and workspaces.
Internal owners for what comes next.
Common questions
Who is the training for?
Executives, managers, operators, and knowledge workers, from first-time users to the people who will build workflows for everyone else. Sessions are grouped by function and experience.
Which tools do you cover?
ChatGPT, Claude, Gemini, and Microsoft Copilot, plus patterns that work across any large language model. We teach on the tools you have licensed.
How is this different from the vendor's own training?
Vendor training explains the product. Ours starts with your team's documents, requests, and decisions, and the review habits that make the output safe to use.
How do you measure adoption?
We agree one or two measures before the sessions, such as weekly active use or time to a reviewed first draft, and review them with each team lead afterward.
How does training connect to implementation?
Training builds fluency across the team. Implementation puts AI into a specific workflow connected to your systems. Many clients train first to find the workflow worth implementing, or train after launch so the team adopts the new process.
Related services
Working session
Get your team using AI well.
45 minutes on one team. We look at the tools you have and how people use them today, and recommend where training should start. Nothing to prepare.
Your request is received.
Choose a time for your 45-minute session now, or our team will follow up to arrange it.
Choose a time Explore AI implementation