Marketing, sales, HR, customer service and back office do not need a programming course. They need one task from their own week, worked through end to end in the room, and a verification step that stays in writing after the training.
These teams are usually already using models, quietly and with no agreed rules. The training does not start that; it brings it into the open and gives it a shape.
Copy, briefs, product descriptions. The biggest risk: the model adds a number or a quote nobody checked before it went out.
Proposals, call summaries, follow-ups. The risk: a commercial term that reads plausibly and does not match the price list.
Job descriptions, feedback, internal material. The risk: an assessment criterion that is hard to defend in a dispute.
Replies, ticket summaries, the knowledge base. The risk: a sentence about a refund or a warranty that contradicts your terms.
Statements, notes, correspondence. The risk: the model does not calculate, it fits the shape of a number to the sentence.
Minutes, letters, decks. The risk: a document someone signs without having had time to read it.
We do not tour twenty tools. We take the one thing that comes back every week in that department and get it to a working process, including the moment where somebody checks it.
A short call with someone who knows that team's week. It produces one job: a report, a proposal, a job description, a customer reply.
Nobody catches an error in someone else's example, because there is nothing to compare it against. We work on material these people know by heart.
We deliberately walk it into a mistake in front of the room. That is the only moment when "you have to check it" stops being a line on a slide.
One page: who checks, what they open, and who signs the document before it goes out. That is the thing that stays after the training.
3–4 hours
One department, up to 20 people
One task end to end plus the written verification step. The format most companies start with.
6–7 hours
A department or several teams, up to 30 people
Two tasks instead of one, more time on your own documents, and a separate block on where AI is simply the wrong tool for this work.
several sessions
A company rolling this out more widely
One department after another, a shared verification standard and a short check-in after a quarter. Priced as a package.
Online or on-site. No code, and nothing to install on company laptops.
The rate is here so you do not have to ask for it first.
for a half-day department training
A full day is priced higher, and a series across a season is priced as a package against the scope. Travel within Poland is included. Dates are agreed individually.
A team that will write code for two days? That is a separate offer at a separate price. See the technical workshop
I build AI systems that keep working after the demo, and I teach what I learned building them. Among others, I taught journalists at TVP's Akademia Telewizyjna how to use AI in newsroom work.
From $1,600 for half a day with one department, up to 20 people, online or on-site, travel within Poland included. A full day is priced higher because it holds two tasks instead of one. A series across a season is priced as a package against the scope. The two-day hands-on workshop at laptops for a technical team is a separate offer with its own price.
The audience, and what happens in the room. Here nobody writes code and nothing gets installed on a company laptop. We work on the documents this department already produces every week, in tools that run in a browser. The technical workshop runs two days, ends in working code, and is priced separately.
Tell me in your enquiry, and name the programme and how it settles. I will check what fits inside it and say plainly if it does not. I would rather settle that before we talk about dates than after.
Up to 20 for half a day and up to 30 for a full day. Above that the exercises stop working, because there is no time for everyone to run their own task and get feedback on it. For a larger group I suggest splitting into sessions, or a talk rather than a training.
Yes. The written verification step, a prompt set fitted to your documents, and the list of work this department deliberately does not hand to a model. The materials are yours, with no licensing strings back to me.
That is usually when it is worth the most. A team already using models with no agreed rules has habits and mistakes in place already, and nobody can see them. For that group the basics run shorter and the verification part runs longer.
Yes. I run the training in Polish or in English, and prepare the materials in whichever language the team works in day to day.
Tell me which department it is, how many people will be in the room and what task comes back for them every week. I will come back with a scope and a price. I reply within 24 hours.
Prefer email? Write directly: kontakt@szymonpaluch.com