Frontier Teams
A company-wide programme that gets every team using frontier AI in their daily work, not just the engineers.
Contents
audienceAll duration6 weeks formatLive
Frontier AI training for every team, delivered by Arclight, without replacing your existing ways of working.
Train marketing, sales, operations, finance and support to use AI well: clear habits, approved tools and shared prompts, while your existing systems and security rules stay exactly as they are.
Why this matters
Most companies already have AI tools. Far fewer have teams who know how to use them well.
The missing piece is a shared way of working.
Arclight starts with the tasks each team already does, then turns early wins into shared habits for frontline teams and for executives.
That means every team can adopt AI without a new platform, a rewritten process or any change to the tools and approvals already in place.
Includes
- Sessions held inside your own working week, at times agreed with each team
- Suits both frontline teams and leaders
- Prompting, research, writing, analysis, automation and optional agent building for each role
- Shared habits that last after the sessions
- Manager view of team progress
- Safe by default: sensitive data stays out of prompts
- Ready-made role tracks that need no setup from your team
- Materials and recordings kept in your own shared workspace
- Rollout plan for the company
- Optional champion network so each department has a local point of contact
Where it runs
This programme is new and flexible. It was designed around how real teams work and is currently offered in:
- London
- Dubai or Abu Dhabi
- New York
- Online, live
- Blended, mixing live sessions with self-paced work
The programme needs a named sponsor, and a lead in each division who reports on progress.
Enrolment
Enrol by email at contact@arclight.im, or book a call. Tell us your company size, the teams involved, your current AI tools, your preferred location and the outcomes you want.
See Booking by cohort if your teams differ in skill or experience levels.
How it works
Training runs inside your own working week, scheduled at times agreed with each team, with its materials stored in your shared workspace.
Arclight facilitators run the sessions. The programme then provides a company-wide adoption track.
That track checks where each team starts and builds a plan suited to the group it is meant for:
- A starter track for frontline teams
- A leadership track for managers
Your existing tools, approvals and security rules keep working exactly as they do today.
Access to sensitive data is never granted through training. Participants only use tools your security team has already approved, and only when the data involved is cleared for AI use.
Role-based starter tracks
Pick a role and a start date and the track is ready: agenda and workbook included, for both the team sessions and the manager briefing.
Ready-made tracks exist for sales, executives, finance, marketing, support, people, operations and training teams.
An incomplete brief, such as a team list without a goal, is flagged to you before the first session.
Teams outside this list can still be covered with a custom track, built with us. Any team without a ready-made track gets a custom outline, drawn from the same core modules.
Exec note
The leadership plan is not a one-off event. It is a rolling plan, reviewed with your leadership, with a typical lifetime of about six months. Agree it, then treat it as a regular part of the working calendar.
Add specialist modules from your plan
Some groups meet in person while others are online only, and a fixed format would fail for part of the group. Specialist modules are therefore chosen when the cohort timetable is built.
The optional extra module choices are:
- a role-specific workshop
- a manager clinic
- a role-based practice session
Vague plans, such as "use AI everywhere", are sent back because they would be read from the generic outline rather than from your own business.
The default track needs no extra preparation.
Follow-up
An optional follow-up module keeps the habits going after the last session. We send the invitation, and each team points us to the internal page where progress is recorded.
The standard programme structure handles the rest.
Modules
| Module | Outcome |
|---|---|
| Core skills | Prompting, research, drafting, review and the other everyday skills |
| Role mapping | Maps each role to the modules that matter to it |
| Peer groups | Connects each participant to a peer group in their own team |
| Manager briefing | Gives managers a short briefing on supporting their teams; offered only once a cohort has started |
| Team action plan | Turns a team session into a one-page action plan per team |
| Leadership plan | Turns a leadership session into a plan for the whole company |
Team playbook
Start by writing a simple adoption goal for your own business.
Then pick any team and a real task, and turn the session into a shared routine.
Participants and facilitators need a shared workspace, so that every participant can reach the same notes and prompts from any device.
Practice tasks must run in the team's own tools, not in a demo space.
The team lead must also be named in your programme's planning document, because the follow-up sessions sit under it and depend on that approval.
Manager sessions
Managers receive a toolkit, and role guides appear alongside the main agenda automatically for every team that joins the programme.
Manager access is intentionally strict:
- the manager must already be on the roster
- the manager must have been invited by you
- the team must have agreed its goals before the first day
- sensitive data stays out of prompts
Rollout checklist
The programme stays out of your way. Facilitators lead during the sessions. After that, your teams own the new habits.
Still, you should settle the following before the programme starts.
Brief managers before launch
For small teams, a short manager briefing before launch is enough. Larger groups need a full briefing session.
Pace sessions across departments
Most companies run sessions in parallel, but the default plan is one group at a time and therefore slower. With several departments, switch to shared waves, and cap group size at the department.
The follow-up clinics are not covered by the main schedule, and each extra clinic costs a facilitator's time.
Align teams across time zones
For a team spread across two offices, plan the sessions and the access rules for each site together.
Keep sensitive data out of every session.
Time zones are a common source of "works in London, fails in New York" scheduling issues.
Watch weekly usage habits
The programme runs its own group beside yours. The default cohort cap is set per department. Size your cohorts and calendars accordingly.
Retire stale use cases
Past cohorts are not closed automatically. Schedule a periodic refresher so stale use cases are retired.
Booking by cohort
Teams in most functions can join without friction.
Large, spread-out teams may need two extra steps: a kickoff call and a shared calendar. We recommend both for any company with several offices or time zones.
Mixed starting levels
Teams at very different starting levels can clash in a single cohort. For these we offer an optional add-on track, so each level learns at its own pace.
Access clash at launch
If an older plan is still in use across the company, the rollout can stall at launch because two teams expect the same access. This only appears once several teams join at once, which can make it look like a facilitation issue.
Fix it by pausing both plans, then restarting. The facilitator spots the stall early and suggests the remedy.
In a company with several divisions, start the programme from the head office. The planning team looks up each division's lead from the central programme record.
Contact
Questions about the programme? Write to contact@arclight.im or book a call.