A Saudi corporate group asked for a customised Claude AI programme for its executives and its team players. Here is every question they asked, whether I can deliver it, and how. Company names are left out on purpose.
The enquiry came from the learning and development team of a group in Saudi Arabia. In short:
API integration and Claude Code training are not needed at this stage. Agreed.
My short answer: yes to all 16 topics and all 6 requirements.
Their question, then my answer. Each item is a live lab where a director works on a real decision or report, never a demo.
Each director brings one live decision. Claude writes the options memo, lists the risks, runs a pre-mortem ("it is a year later and this failed, why?") and argues the opposite side. The director decides. Claude never does.
Output: a one-page decision template they keep using after the course.
We take a raw Excel or ERP export and turn it into a monthly management pack: KPIs, variance against budget, commentary in plain English and a one-slide summary for the board. I build these packs every month for my own and client businesses, including a 10-store retail chain and a trading company.
Inbox triage, meeting notes to action lists, one-to-one prep, policy and circular drafting, and reading long contracts or reports in minutes. Each leader logs time before and after for one week, so the gain is measured, not guessed.
How to review what your team produced with AI, which work needs a human sign-off, a one-page AI use policy, and three adoption KPIs (active users, hours saved, processes changed). Leaders also judge the staff final projects on showcase day.
All 12 topics, in their order. Every topic ends with a short exercise on the participant's own work.
A four-box brief card. Weak prompt in, rewrite with the four boxes, compare the two answers side by side. Everyone leaves with the card laminated.
I run more than ten custom Skills every day: letterhead, monthly reports, email signature, feasibility studies. Staff write one Skill for a task their team repeats, such as a purchase order format or an HR letter.
One Project per department with its SOPs, glossary, templates and tone. Then nobody pastes the same background twice. We build the first department Project live in class.
Give two good examples. Ask Claude to put three questions to you before it starts. Make it grade its own draft against your checklist and fix the gaps. Three habits, practised on real files.
My own rule on every report: each figure is calculated from the source file and totals tie back, never typed in. Staff learn to ask for sources, an assumption list and a check table, then reconcile one sample.
Four data classes (public, internal, confidential, restricted) and what each may go into. On Team and Enterprise plans Anthropic does not train on your business data by default, admins control access, and Enterprise adds SSO and audit logs. Personal accounts are for nothing confidential.
HR screens CVs, procurement compares supplier quotations, finance reconciles a statement, sales drafts follow-ups, operations writes an SOP. I have built free tools for the first three, so teams see a finished version.
Fixed logic goes to rules or Excel. Judgement on text goes to AI. Most real work is hybrid. Example from 30 years of inventory control: the reorder point is a rule, the supplier email chasing the order is AI.
One file, one run: sales Excel in, written report out, then a 6-slide deck. Staff run the full chain in Cowork on their own data.
I run daily 8 AM news briefs, weekly SEO reports and monthly account packs on schedules. Staff set up one weekly report that arrives without anyone asking.
Haiku for quick sorting, Sonnet for most daily work, Opus for hard reasoning. Start new chats for new topics, use Projects instead of pasting, and know where the usage limits sit on your plan.
A 30-day plan. List who uses personal accounts for work. Export the chats and Projects worth keeping. Rebuild them as shared Projects and Skills in the company account. Then stop work data going into personal accounts, with a signed policy.
Their six requirements, answered.
About 70% of class time is hands-on. Participants bring their own anonymised files. Every module ends with a task done on a laptop.
One A4 cheat sheet per module, a prompt library by department, the brief card, starter Skill files and a safe-use one-pager. Included for every participant.
Each department team picks one process, rebuilds it with Claude and measures time before and after. They present it to Group 1 on showcase day. The best one becomes the first company Skill.
See tab 5 for the agenda and tab 7 for the trainer. Dates to suit you, Sunday to Thursday.
Both. Online by Zoom or Teams, or onsite in Saudi Arabia or the UAE. Hotel stay and travel are arranged by your team. Sessions are in English with Arabic subtitles, and the trainer speaks English.
Left out of scope, as you asked.
One day, 8 teaching hours, prayer times excluded. Delivered in English with Arabic subtitles. The split can change to suit you.
| Block | Group | Topics | Hours |
|---|---|---|---|
| Claude for executives | Group 1 | L1 decisions · L2 reporting · L3 productivity · L4 oversight · final project | 3 |
| Claude for team players | Group 2 | S1 to S12 · department labs · final project | 5 |
| Total | Both | 8 |
Your team buys the Claude subscription directly from Anthropic and activates it before the session. Claude Code is not needed.
Team Standard for everyone. It covers Projects, Skills, Cowork and admin controls, and your data is not used for training by default. Move to Enterprise if IT needs SSO and audit logs.
I teach from a manager's desk, not a lab. Every example is something I run in a real business: monthly packs, supplier reconciliations, stock reports. Your leaders get someone who has sat in their chair.
Availability: dates to suit you, Sunday to Thursday. Language: English, with Arabic subtitles.
WhatsApp +971 55 649 2370 · aziz@azizsaif.com · azizsaif.com