Course Materials
All materials required to follow the online course are provided in electronic format.
Why three levels?
A clear progression: from understanding to automation
We do not offer generic lectures about the future of technology. Our program follows the UNESCO progression of AI competence levels (Understand, Apply, Create) and addresses real challenges in your company:
01 / AIskorak (UNDERSTAND)
For employees who use AI occasionally (or not at all) and want to automate personal daily tasks without compromising company data.
02 / AIzazov (APPLY)
For teams that want to change and accelerate one specific business process, with strict quality control and security.
03 / AIzum (CREATE)
For teams that already manage their processes well and are ready to take the next step by building a prototype (agent/script) that independently handles part of the work.
The program follows the UNESCO progression of AI competence levels: Understand, Apply, Create. This does not represent UNESCO accreditation or certification of the program.
01 / AIskorak
From your first prompt to confident AI use
For employees who use AI occasionally and without rules, or do not use it yet. The work is based on tasks from your company, not examples from scripts.
What will you learn?
- How to tell which tasks benefit from AI and which ones do not.
- How to write a strong prompt with a role, context, task, and desired answer format.
- How to recognize fabricated or unreliable information and verify it before use.
- Which business data you may and may not enter into AI tools.
- How to choose the right type of tool for the task.
- How to turn three of your own business tasks into tested, repeatable AI prompts.
What do we do in the training?
1. AI without mystery
What it can do, what it cannot do, and where mistakes happen.
What it can do, what it cannot do, and where mistakes happen.
2. How to talk to AI
Bad prompt, improved prompt, and comparison of results.
Bad prompt, improved prompt, and comparison of results.
3. Which tool for which task
The same task through different types of AI tools.
The same task through different types of AI tools.
4. AI for more productive work
Administration, HR, finance, and work on your own task.
Administration, HR, finance, and work on your own task.
5. Content and communication
One piece of information adapted for different channels and audiences.
One piece of information adapted for different channels and audiences.
6. AI for business growth
Analyzing your own offer from the perspective of a customer, competitor, and investor.
Analyzing your own offer from the perspective of a customer, competitor, and investor.
7. Your AI plan
Three concrete tasks you continue using after the training.
Three concrete tasks you continue using after the training.
What happens after the training?
“30 days, 3 tasks.” The participant uses three tasks from their plan and briefly records how long they took before, how long they take with AI, and what still had to be corrected manually. This is how we measure whether the knowledge has truly transferred into daily work.
What is AIskorak not?
- It is not a programming or API course.
- It does not introduce AI into company processes; it introduces it into an individual’s work.
- It does not provide regulatory compliance, but it does show that AI literacy measures have been taken.
- It does not promise savings in advance; it measures them for participants through concrete tasks.
02 / AIzazov
From individual use to a process the whole team can use
For teams that want to change one specific business process, not just the way an individual works.
What will your team learn?
- How to choose a process using clear criteria: frequency, time spent, cost of error, and measurability.
- How to measure the baseline before making any changes.
- How to work with your own documents and data, with a clear rule for what may leave the company.
- How to introduce mandatory quality checks before an AI output is sent to a client or colleague.
- How to create a standardized prompt that other team members can use as well.
- How to define where AI stops, who approves the result, and who is responsible.
What do we do in the program?
1. Which process first?
Prioritizing processes and selecting one candidate.
Prioritizing processes and selecting one candidate.
2. Measuring before change
Setting the starting point and the measurement method.
Setting the starting point and the measurement method.
3. Working with documents
The first workflow based on anonymized company examples.
The first workflow based on anonymized company examples.
4. Quality checks
A checklist and catching errors before sending.
A checklist and catching errors before sending.
5. A prompt others can use too
A shared library of standardized prompts.
A shared library of standardized prompts.
6. Roles and boundaries
Who may do what, where it stops, and who approves.
Who may do what, where it stops, and who approves.
What happens between the two days?
Between the two full days there are two short online meetings. In the first, we remove whatever got in the way immediately, and in the second, we check whether the team is measuring the right data. This ensures that the second day is not just another exercise, but work based on real experience from your company.
What is AIzazov not?
- It is not an advanced prompting course, but a change to one team process.
- It does not build software or integrations.
- It does not promise savings in advance; it measures them on the selected process.
- It does not solve all processes at once, but one process end to end.
03 / AIzum
From a structured process to AI automation
For teams that already have one process under control and want to automate it. The goal is for you to leave the session with a prototype that works on a real task.
What will the team learn?
- How to distinguish an agent, a chatbot, and a simple script, and know when to use each one.
- How to decide what should not be automated based on task frequency and the cost of error.
- How to map a flow: trigger, steps, branches, and stop point.
- How to build in a point where the system stops and requests human confirmation.
- How to define what is logged, rolled back, and reported when the agent makes a mistake.
- How to assess cost, maintenance, and accountability before moving into production.
What do we do over two days?
1. What an agent is and what it is notSorting real company tasks.
2. When not to automate
We challenge every candidate with the question of the cost of error.
We challenge every candidate with the question of the cost of error.
3. Mapping the flow
Trigger, steps, branches, and control points.
Trigger, steps, branches, and control points.
4. Building the first working part
The smallest piece that works from start to finish.
The smallest piece that works from start to finish.
5. When the agent makes a mistake
We intentionally trigger an error and create a recovery plan.
We intentionally trigger an error and create a recovery plan.
6. Human control
Who approves, who is responsible, and what is kept as a record.
Who approves, who is responsible, and what is kept as a record.
7. Cost and maintenance
Who maintains the solution and what it realistically costs.
Who maintains the solution and what it realistically costs.
Why are the two days consecutive?
Unlike AIzazov, this level focuses on building. Development requires long, uninterrupted blocks of work, which is why the two days are consecutive. After 30 days, we have an online check-in with one main question: does the prototype still work?
What is AIzum not?
- It is not the delivery of finished software; the training produces a prototype.
- It does not replace a development project, but shows what is worth developing further.
- It does not move an agent into production or take responsibility for production use.
- It is not a course on one specific tool.
The same principle across all three training levels
No theory without a concrete result
Each level is based on real business tasks and ends with something you can show, use, and verify after the training.
Your tasks, not our examples.
We tailor the program to the situations and processes in your company.
Every workshop has an output.
A plan, prompt, checklist, process, or prototype—something concrete remains after the session.
Business data stays protected.
Exercises are done using fictional or anonymized data.
We measure what changed.
We do not end with a satisfaction survey. We check what has actually moved into practice.
Measuring impact
How do we know the training was effective?
We do not only measure whether participants liked the training. We look at what was learned, what is still being used after 30 days, and—when the company has baseline data—what changed in the process itself.
1. REACTION
At the end of the training, we measure the usefulness, clarity, and relevance of the program.
2. LEARNING
Knowledge is checked through a concrete output: a personal plan, a prompt library, or a functional prototype.
3. BEHAVIOR
After the training, we check whether tasks and processes are actually being done differently.
4. RESULT
When the company has a baseline figure, we can track the change in a specific business metric together. That result is not promised in advance.