Practitioner-led AI adoption

Zdopt runs AI programmes for organisations and colleges. Every session ends with something the participant can reproduce at their own desk on Monday morning, on the licence they already have.

Two audiences
Organisations and colleges
Nine programmes
Three hours to four days
Priced per cohort
Not per head, not per day
Checked at day thirty
Usage, not satisfaction
Tools taught across the programmes
Claude
Claude
ChatGPT
ChatGPT
Microsoft Copilot
Microsoft Copilot
Gemini
Gemini
Notion
Notion
Claude
Claude
ChatGPT
ChatGPT
Microsoft Copilot
Microsoft Copilot
Gemini
Gemini
Notion
Notion
Claude
Claude
ChatGPT
ChatGPT
Microsoft Copilot
Microsoft Copilot
Gemini
Gemini
Notion
Notion
Claude
Claude
ChatGPT
ChatGPT
Microsoft Copilot
Microsoft Copilot
Gemini
Gemini
Notion
Notion
The problem

All three are decided before anyone opens the tool — which is why we start with the room where those decisions get made, not with the room that wants the training.

In organisations
01

No sponsor

Nobody senior owns the licence decision, the rollout order, or the measurement. Training without a sponsor does not survive contact with a budget cycle.

02

No licence

Half the capability taught needs a paid or enterprise tier. On free accounts the agenda quietly becomes a demonstration.

03

No measurement

Nobody agrees what success looks like before the room opens, so nothing gets checked after it closes. Week five arrives and there is no baseline to compare against.

On campus
01

Students are judged on what they build

Recruiters have stopped asking whether a candidate has heard of AI. They ask what the candidate has actually shipped with it.

02

Faculty are asked to teach it anyway

Most AI training for colleges demonstrates the tools rather than using them, and nothing survives past the week it ran.

03

Nobody checks day thirty

A form signed at the end of day two tells you the session happened. It does not tell you the department kept using any of it.

Who we work with

Both start in the same place: the room that decides, not the room that asks. Sponsors first in an organisation, faculty first on a campus.

For organisations

AI adoption programmes

Five tracks, from the sponsor who signs the licence decision to the engineering team shipping agents. Leadership runs first — it is where licence tier, first functions and measurement get decided.

  • Leadership3 hours · Up to 15
  • Fluency1 day · Up to 30
  • Function Practitioner2 days · Up to 25
  • Practitioner, your stack2 days · Up to 25
  • AI Builder4 days · Up to 20
See the five tracks
For colleges

AI training for campuses

Four levels, from a free live build for the whole campus to students shipping production-grade agentic workflows. Faculty first, because a department that can teach it outlasts a batch that attended it.

  • L0 · Live build demo90 minutes · Up to 150
  • L1 · Faculty Development Programme2 days · Up to 30 faculty
  • L2 · AI Practitioner30 hours · Up to 60 students
  • L3 · AI Builder48 hours · Up to 40 students
See the four levels
How we work

Every session ends with something the participant can reproduce at their own desk on Monday morning, on the licence they already have.

If they cannot open it again on their own machine after we leave, we have not taught it. That single rule decides what goes into a session and what gets cut.

01

Your workflows, not case studies

The live build in every track uses one of your real workflows, not a worked example from a deck.

02

Built by people who ship

Delivered by practitioners who work on these platforms in production, not by trainers working from a content library.

03

Measured on use, not satisfaction

We baseline before, then check usage at day thirty. The target is sixty percent still using it.

04

Delivered by the founders

The people who scope the engagement are the people who run the room. No handover to a junior trainer between the proposal and delivery.

Measurement

What we contract on
60%

Still using it thirty days later, measured against a baseline agreed before the room opened. That is the number the engagement is judged on.

Day 0 → day 30Bars show the shape of the two readings, not a client's results — we have not published any yet.

A completion certificate tells you the session happened. We agree what success looks like before the room opens, so there is something to compare against after it closes.

Every track is sold on something the room takes away, so here is the thing itself rather than a description of it. Pick an audience and step through the ladder.

3 hours · Up to 15

Sponsors leave able to decide a licence tier against actual seat maths, name the first three functions to roll out, approve a data-sharing policy, and sign off on how adoption will be measured.

A one-page adoption plan they own, not one we wrote for them.

See the five tracks
ADOPTION-PLAN.PDF
One-page adoption plan
Licence tierDecided against seat maths
First three functionsNamed, in rollout order
Data boundaryWhat leaves the building
MeasurementBaseline, day N, day thirty
Owned by the sponsor — not written by us
Who delivers this

No handover to a junior trainer between the proposal and the classroom.

Sam David

Sam David

Co-founder

ServiceNow and Claude expert. Owned a three million dollar delivery portfolio as a specialisation head. Leads the Claude track and the agentic build curriculum.

LinkedIn
Anish

Anish

Co-founder

Registered Notion partner and award-winning Microsoft Copilot expert. Leads the Microsoft track and enterprise workflow tooling.

LinkedIn

Zdopt has applied to the Claude Community Ambassadors programme.

Next step

Thirty minutes on what you have already tried, which functions are asking for this, and where the licences currently sit. We will tell you which track fits and which one does not.

Book a call See the programmes
contact@zdopt.com+91 91235 88240