Training for organisations
Built on your own work, not on a generic curriculum.
A hands-on AI program designed around what your people actually do. Nothing is designed until we have interviewed you. Most of the room's time is spent working on your own material, and what people do with it afterwards is followed up and reported back.
How the program is shaped
Understand, build, apply.
Understand — fundamentals
What these tools actually do, in plain language, no technical background assumed. How to tell whether an answer is correct. What can and cannot go into which tool, and why.
Build — hands-on, on your own material
Small groups working on something real they brought: a report, a forecast, a proposal, a shortlist. Everyone builds one working assistant on their own content.
Apply, and track it — ninety days after the room closes
What people actually did in the three months after: workflows changed, use cases trialled, working rules adopted. Collected from participants and sent to your leadership as a short note.
Delivered in person or remotely, whichever suits your calendar and your sites. The structure, the group work and the assistant each participant builds are the same either way.
Fundamentals, then hands-on, then application
Three stages, and the third one runs after everyone goes home.
Most AI training stops when the room empties, which is exactly when the habit either forms or does not. The last of the three stages runs after that.
The program
Your people are already using AI. The question is whether it happens structurally, or around you.
Some of it informal, most of it without a shared framework, much of it without a policy behind it. The program brings that use into the open and gives it a structure. Three options, by scope:
Leadership working session
CXOs and senior leadership, one session, peer-level rather than a briefing. Best when you want leadership aligned first — it is also what most determines whether a wider program lands.
Leadership plus selected departments
The leadership session, plus one to three department groups over consecutive days, each with function-specific use cases built from the preparation interviews. Best when you want the approach proved in one or two functions first.
Full organisational program
Leadership, plus department cohorts across the organisation. Best when you want one shared baseline across everyone, rather than several.
Each department cohort runs in three parts: foundations (AI awareness, the tool landscape, prompt discipline, responsible use, working with agents — consistent across every group); your work, specifically (custom use cases built for that function from the preparation interviews — this is where the program earns its value); and hands-on practice (a real scenario from that function; people leave with something they can use, not a certificate). Technical cohorts take a shorter foundations section and go further into governance, security and enterprise AI architecture.
Governance and responsible use
Runs through every day, not a module at the end.
- Data leakage. Confidential material pasted into external tools, with no idea where it goes or how long it is kept.
- Confidently wrong answers. The risk is use without the habits to catch an error before it reaches a report or a decision.
- Bias and fairness. Screening and prioritisation can embed historical patterns without anyone intending it.
- Accountability. No training resolves the legal question, and we say so. The working principle: AI drafts, humans own decisions.
- Unofficial use. The people most likely to be using AI without sanction are often the most capable, so your highest performers may currently represent your highest data risk.
What your organisation has at the end: a common language for AI across everyone who attended, a leadership team fluent enough to evaluate an AI proposal rather than nod at it, function-specific use cases ready to trial, a governance conversation started, and the note at ninety days on what people actually changed.
What this program does not deliver
Organisational AI transformation is not a training outcome.
This program builds the foundation: shared language, baseline capability, and visible leadership commitment. Embedding AI into your workflows, redesigning how roles operate, and building governance infrastructure are the next layer. That work is different in nature and requires a different kind of engagement.
This is stated before the program rather than after it, because a proposal that oversells the outcome underdelivers the trust the program runs on.
What we need from you
- Your leadership team and department heads: thirty to forty-five minutes each, before the program.
- Cohort groupings confirmed, so the rooms can be arranged.
- The pre-read exercise completed and returned by attendees, since the worked examples are built from it.
- A room with reliable wifi, or a working video setup if the program runs remotely, and people released to attend properly.
- Any existing AI policy you have, so the program builds around it rather than across it.
A short call to confirm the cohorts.
Not a sales meeting. A conversation about whether this addresses a problem you recognize in your organization, and what you would need to see to hold the answer under scrutiny from your CFO and your board.
Rajeev, who runs the engagement. Not a qualifier.
Bring one workflow you already know is painful. We trace it one or two layers out loud with you, tell you what we would need to see to answer it properly, and say what we could not answer.