How many people can take part at once?

The group size is set during the assessment, weighing your situation against practice density. The format leans heavily on practice, so as the group grows we add facilitators rather than thinning the practice.

How do you decide the schedule and the number of sessions?

The principle is to work around your business cycle. We check for deadline-heavy weeks, closing periods, and shift patterns during the assessment, then adjust the interval and time of day in the proposal.

Can we use our internal material for the practice?

We settle the range of material that can leave the organisation with your security owner before the design starts. Where it cannot, we adjust the curriculum so the practice runs on samples in the same format inside an approved environment.

What does it take to make this stick after the training ends?

Someone who will fold the guidelines into actual policy and work templates, and facilitator notes so the same content can be run again for new joiners. Both are delivered, and we can help you prepare later cohorts too.

AX Education

Enterprise AI training, matched to your organisation from the curriculum up

Instead of running a standard deck, we look at your workflows, your material, and your security policy first. What comes out of that is a proposal covering session structure, practice assignments, and internal usage standards.

See the design process

One offering: a custom curriculum consultation
Practice on real work output
Online, in person, or blended

Why us

Designed by a team that works with AI

Our internal knowledge base runs on Claude, and Claude Code and Cowork are part of our daily design, development, and documentation process. The material is not lifted from someone else's deck. It is how we actually work, written down.

Prompts and working sequences that hold up in practice, turned into training material.
No vendor lock-in. We run on tools your organisation can actually use.
Improvement ideas raised in a session come back as an owner-by-owner action list.

Curriculum design

How the curriculum gets designed

What to teach is decided after we have seen the organisation. Four stages produce the design, and the design is the proposal.

01
Assess the organisation and roles
It starts with who spends time on what.
Interviews and a pre-survey gather repeated work per team, how documents flow, approval steps, and the tools in use today. Security policy and the range of material that can leave the organisation are settled here too.
Stage outputAssessment summary and the list of tasks to train on
02
Design the curriculum
The assessment turns into sessions and practice assignments.
Topics are ordered by training impact, and each session gets its concepts, practice assignment, and prerequisites. The schedule is placed around your business cycle, and the whole design comes to you as a proposal.
Stage outputSession by session curriculum design and schedule
03
Run it around practice
People bring work they actually have to finish, and finish it in the session.
Concept explanation stays short and the rest of the time goes to practice. Participants bring their own documents as the assignment, and the facilitator reviews the output on the spot and points out where it stalled.
Stage outputPractice output per participant
04
Make the guidelines stick
What worked becomes an internal standard document.
Prompts and working sequences that repeatedly held up are grouped into standards per task, alongside the work a person must review and the material that must never go to an external tool. Delivered in a form you can drop straight into your wiki or knowledge base.
Stage outputDraft internal AI usage guidelines

Design variations

The design splits on what the assessment finds

There is one offering: a custom curriculum consultation. What follows is not a menu of packages for different audiences. It shows how the same design process produces different results depending on what the assessment surfaces.

The tool is in place, but only a few people use it

We collect how the people already using it well actually work, turn that into an organisational standard, and repeat short sessions team by team. This is the design for organisations whose problem is spread, not adoption.

Documents and reporting eat most of the team's time

Real reports and meeting notes become the practice assignments, and we rebuild the drafting, summarising, and review sequence. The output is written up as shared templates the team keeps using.

Security policy blocks external tools

We settle the range of material that can leave first, then build the curriculum around practice that runs only inside an environment your organisation has approved. If the environment itself is the gap, that becomes a separate conversation.

How it runs

How the practice actually works

There is more time doing than listening. Here is how a session runs, and what happens between sessions.

Pre-work: Before the session, everyone brings one piece of work they are currently handling. If the material cannot leave the organisation, we produce a sample in the same format inside your environment.
Session structure: A session runs as concept, demo, individual practice, review. The explanation stays short and most of the session goes to practice and review.
Review: The facilitator reviews what was submitted and comes back with comments on where the instruction fell short and what should have been asked again.
Between sessions: A question channel stays open, and the next session opens with the mistakes that came up across everyone's assignments.
Format: Online, in person, or blended. To keep the practice density, we add facilitators as the group grows.

Deliverables

What you keep when the training ends

Not a certificate. Documents and output the organisation keeps using.

Custom curriculum design

Assessment summary, session structure, per-session goals and practice assignments, and the schedule. Facilitator notes come with it so you can run the next cohort yourselves.

Practice output

Not toy examples. The documents and work participants actually had to deliver. It is already in use before the training ends.

Internal AI usage guidelines

Usage standards per task, the work a person must review, material that must not leave the organisation, and what to do when something goes wrong. Reviewed with your security owner so it does not conflict with existing policy.

Training is the second stage of the Alphaca Labs AX journey. The full picture, from diagnosis through build and operations, is on the services hub.

See the whole AX journey

자주 묻는 질문

Start with a curriculum that fits your organisation

Tell us where your work stands and what you are aiming at, and we will map out the assessment scope and design direction first. Session structure, schedule, and cost come in the proposal, after the assessment.