Skip to content

Your team already uses AI, just without boundaries or a trace.

Client data goes into random tools, and when a client or lawyer asks who made the decision and on what basis, there is nothing to answer with.

Training is led by engineers with AI systems in production, not career trainers. Instead of trend slides we work on your real process: context, tool choice, boundaries, verification, and trace.

  • You talk to an engineer, not a salesperson.
  • 30 minutes, no sales presentation.
  • No prep or homework on your side.

In short

Price
from €1 200 / day nettypically €1 200–1 500 per day; quoted per scope after one call
Format
1 or 2 days, online or on-sitea workshop group of up to ~15 people, split into several groups in a larger company
Who teaches
Engineers with systems in productionthe program comes from production deployments and work on your process
For whom
Boards and teams that use AI or are about to startfor teams that need a shared AI working standard on real tasks

Engineers who deploy, not trainers.

The AI course someone on the team has already sat through usually ends in slides and prompt tricks. Here you are taught by the engineers who build and run those same systems in production for Polish companies.

Who teachesA typical AI courseA training facilitatorSyntalith trainingAn engineer who ships AI systems in production
On whatA typical AI courseGeneric examplesSyntalith trainingYour real process and data
What it teachesA typical AI coursePrompt tricksSyntalith trainingContext, boundaries, escalation, trace
ComplianceA typical AI courseSkippedSyntalith trainingOperator duties under GDPR and the AI Act
After the sessionA typical AI courseSlidesSyntalith trainingMaterials and a way of working that stay with you

See the deployments

1:1 course participants

People we've trained one-on-one.

A team goes through the same working standard, just in a group.

  • Kuba Koziej, CEO and co-founder of MoreGrowth and board member at Natu.Care
    Kuba Koziej

    CEO & co-founder of MoreGrowth, board member at Natu.Care

    I went from barely shipping a frontend to building full applications with a backend and a database, and deploying them safely instead of hoping they would hold. We worked through the parts I kept tripping on: Docker, the coding agents and tools, and when it is worth reaching for skills, MCPs and connectors. It stayed practical the whole way, on what I actually wanted to build.

  • Hlib Utkin, public administration

    Hlib Utkin

    Public administration

    A large stream of documents passes my desk every week. I now review, draft and prepare them with Claude in a fraction of the time, and research that used to eat an afternoon takes minutes. It is wired into the services I already work in, so the documents reach me instead of me hunting for them.

  • Ivan Chepurin, Senior Software Engineer at Immutable
    Ivan Chepurin

    Senior Software Engineer, Immutable

    I came in using coding agents ad hoc and left orchestrating them: loops, an agent kanban, a full development cycle that ships. What stayed with me is running context and cost on purpose, and building my own harnesses instead of waiting for a tool to ship one. It changed how I work day to day.

  • Oleksandr Usyk, co-founder and art director at jakotako
    Oleksandr Usyk

    Co-founder & Art director, jakotako

    I run a design studio, not an engineering team, and I still left with something working. We built an agent loop that pulls in leads and keeps an eye on the competition, and I put my own site together with Claude. It was hands-on, on my real work, not a talk about AI.

Five 1:1 trainings delivered, every review signed by name.

What your team learns.

Each module pairs hands-on work with Claude and ChatGPT Work with the discipline that makes it trustworthy in a real process. We fit the scope to the team and the goal.

  1. Theory · the foundation

    How the models actually work and where they fail, on neutral examples before we work on your tasks.

    01Foundations · Model

    AI foundations: how models work and where they fail

    How AI models actually work and where they fail, before we touch your data: where errors and the only-plausible answer come from.

  2. 02Claude · Context

    Claude Cowork and ChatGPT Work: context, task and working together

    How to give the model context and a task, how to run multi-hour work on one document, and when to start the conversation again.

  3. Practice · the drills

    Concrete drills on your process: tool, boundaries, escalation, trace.

    03Documents · Analysis

    Claude and ChatGPT in the team's daily work

    Documents, files, offers, analyses, correspondence: your team's real, everyday tasks moved onto the model, with verification of the result.

  4. 04Tools · Boundaries

    Agentic workflow: prompt, automation, or agent

    When a conversation with the model is enough, when a repeatable workflow is better, and when an agent should use tools, and where a human must approve the result.

  5. 05GDPR · Escalation

    Data safety and oversight

    GDPR-compliant work in Anthropic and OpenAI tools: what can go in, what cannot, which data settings to turn on, where the model must stop, and how to set escalation.

  6. 06Trace · AI Act

    Trace, quality, and AI Act duties

    How to leave a decision trace, measure the quality of work with AI, and how training supports the literacy duty in Article 4.

We run most trainings on Claude and Claude Cowork, because that is what we build with in production, but we also work in ChatGPT and ChatGPT Work, the non-technical counterpart to Claude Cowork, and other tools, and if your team prefers a particular one, we teach on it.

Three groups, three scopes.

Who will be in the room: the board deciding where AI makes sense, or the team that has to use it from tomorrow? Each group needs a different conversation, so we fit the scope to who is in front of us.

Boards and decision-makers

You decide where AI enters the company and at what cost, and every vendor's offer sounds the same.

  • Where AI and agents are an advantage, and where they are a risk
  • How to read an AI vendor's offer and what to demand in the contract
  • What the AI Act means for a company deploying AI
  • A short session focused on operational decisions

Operations teams

Your people already reach for AI on the job, each in their own way and with no rules.

  • Hands-on work with Claude and ChatGPT on your real tasks and data
  • Context, boundaries, and catching the plausible-but-wrong answer
  • What can go into the model and what can't, data-handling rules
  • Materials and a working standard that stays with the team

Team leads

You have to roll AI out in the team so it sticks and doesn't fracture into 20 styles.

  • How to spread AI work across the whole team
  • Shared rules and a working standard across the whole team
  • What stays in the team after the training, and how to keep it
  • Keeping quality and a trace in daily work

Formats and prices

from €1 200

per day · net

One day or two. A per-day price, stated up front.

The same formats, online or on site: for one workshop group (up to ~15 people) or several groups in a larger company, with one shared working standard. The ~15 is a group size, not a cap on the training. The final quote depends on scope, headcount, and the number of groups.

1 day · introduction

Boards, decision-makers, teams starting with AI

One day on your own examples: what AI and agents do well, where the boundaries are, and which data-handling rules to adopt from tomorrow.

from €1 200

per day · net

2 days · workshop on your process

Teams that will use AI daily

Day one: hands-on work with Claude on your tasks. Day two: boundaries, escalation, trace, and a working standard that stays with the team.

from €1 200

per day · net

The day rate typically falls between €1 200 and €1 500 net; final quote per scope after one call. The program, attendance list and materials stay with you.

Who this is for, and who it isn't.

We described above which group you fit; this is about readiness. If the second column describes your case, another provider usually fits better, and we'll say so before the quote.

Ready if

  • You have a real process on the table, beyond curiosity
  • Your team is about to reach for AI on the job and needs boundaries first
  • You care about a decision trace and the Art. 4 AI Act literacy duty
  • The session should use your own data instead of generic examples
  • Working with AI should become a habit for the whole team, beyond a couple of enthusiasts

Probably not if

  • You want a trend lecture with no work on your own tasks
  • You only need prompt tricks and a certificate for the wall
  • You want cheap off-the-shelf training with no fit to your process
  • You expect a guaranteed result or an official endorsement from the model vendor
  • You are a technical founder who wants to build software with agents: see the AI-Native course

AI Act · Art. 4

AI skills that stay with your team.

Art. 4 of the AI Act has applied since 2 February 2025 and requires companies deploying AI to take measures that ensure a sufficient level of AI literacy in the people working with it. The provision does not prescribe a form: a closed training with a program, attendance list and named certificates is one recognized way to meet it. This is not legal advice.

EU AI Act 2024/1689, Art. 4 (EUR-Lex)

From a call to a program that stays.

Training starts with one conversation about the team and the goal. We run the rest in a clear order.

  1. 01A call about the team, process and goal: we set the group, format and scope.
  2. 02You get a quote and a program tailored to your tasks and data.
  3. 03We run the training online or on site, on real examples.
  4. 04You keep the materials, attendance list, named certificates of completion and a working standard that helps document AI literacy under Art. 4.

No seats sold off the shelf: every training is quoted per scope after a call.

Training questions

  • How soon can you run it?

  • How many people can take part?

  • Online or on site?

  • Do we need Claude or ChatGPT accounts and licenses?

  • Why engineers?

  • How do you know it sticks, instead of slipping back to old habits by Monday?

  • We're a small team without much technical depth. Is this for us?

Tell us who we're training and we'll send you the program and the quote.

  • 30 minutes with the engineer who would build it, not a salesperson.
  • A review of the processes that cost you the most time and money.
  • A written summary: what to automate, in what order, with cost ranges.
€030 minutes · written takeaway within 2 business days
Let's talk about training for your team

Times are shown in your own time zone. We work with clients across time zones.

No sales deck and no obligations. If automation doesn't make sense, we'll write that too.

Full pricing

from €1 200/day net · quoted per scope · taught by engineers with systems in production