Courses & workshops
AI workshop
I do not give talks about what artificial intelligence is. Everyone has heard that. We spend the day taking three tasks from your own week and making them work.
- Same-day reply
- Fixed price
- No lock-in
- Your own tasks
- Up to 12 people
- Held at your office
- Material you keep
Service
AI workshop
How the day looks
The morning goes on what actually makes the difference: how to give a model enough context, how to notice when it makes things up, and where the line sits on what you can put in.
In the afternoon people work on their own tasks while I move around the room. That is where it sticks. I have never seen anyone change habits from watching a screen all day.
What I ask for in advance
- Two or three concrete tasks people spend time on every week. Preferably the boring ones.
- A note on what may and may not go into external tools, so we do not step in it.
- A sense of where the participants are. There is a big difference between a group that uses it daily and one that never has.
What usually comes out of it
Typically two or three things people start using immediately, and a list of things that would need real development. That list is often the most valuable part, because it comes from the people doing the work.
I send a follow-up document with what we built, including the prompts that ended up working, so new colleagues can catch up later.
Deliverables
What you get
Concrete deliverables, not a report of recommendations someone else has to find time for.
- A day at your office
Morning on the technical side, afternoon with people working on their own tasks while I move around the room.
- Your own tasks
Built around two or three things people actually spend time on weekly. Not examples from a webshop selling coffee.
- A follow-up document
What we built, including the prompts that ended up working, so new colleagues can catch up later.
- A list of next steps
What surfaced along the way that would need real development. That list is often the most valuable part.
Process
How it works
Four steps. You know what happens when, and you can stop after any of them.
- 01
Your tasks up front
I ask for two or three concrete tasks people spend time on every week, then build the day around those instead of using my own examples from someone else's industry.
- 02
Morning: the technical part
Short and concrete. Not a talk about what the technology is, everyone has heard that, but how to actually get something usable out of it.
- 03
Afternoon: hands on
People work on their own tasks while I move around the room. That is where it sticks. I have never seen anyone change habits from watching a screen all day.
- 04
Material you keep
A follow-up document with what we built, including what ended up working. New colleagues can catch up later without sitting through the same walkthrough again.

Who does the work
I am the person you will be working with
My name is Mikkel and I have been building for the web since 2010. There is no project manager in between, and you will not get a junior on the job because the senior was busy. What you agree is what gets built, and I am the one building it.
Day to day I am a partner at Bigum&Co, and I have worked on more than 400 projects across ecommerce, pharma, construction and the public sector. Call or write — I usually reply the same day, and I will say straight away if the job is not a fit.
- Experience
- 16 yrs
- Projects
- 400+
- Rating
- 5.0
- Reply time
- Same day
In depth
AI workshop
Why generic AI courses rarely work
People have seen the talk about what artificial intelligence is. They have heard about transformer models, seen the example of writing a poem about a cat, and been told it changes everything. It has not changed how they work on a Tuesday.
The distance between understanding the tool and using it is not theory. It is having tried it on something you actually have to deliver, with someone sitting next to you who can say why the answer came out badly. That experience does not transfer through slides.
So I spend the afternoon on exactly that. People take a task they had to do anyway and we work on it. Some get it solved in twenty minutes and are surprised. Others discover their task is harder than it looks, which is also a useful outcome — now they know where the line is.
That puts a requirement on group size. Past twelve people I cannot get around, and it becomes a lecture instead. Then we split it across two days.
What people typically take home
Two or three things they start using immediately. It is rarely the most impressive thing that becomes a habit — usually it is the dull task that suddenly takes five minutes instead of forty.
A better sense of when not to use it. That is actually the most important part. People who have watched a confident-sounding wrong answer appear with a colleague looking on remember it afterwards.
And clarity about what may go where. Most places either have no guidelines or a memo nobody read, and people use the tools anyway without it being agreed. That conversation is easier to have when everyone is in the same room.
Reviews
What people say about me
Mikkel Tschentscher is my lifeline when something is urgent and nobody else can work it out.
Torben Wiese(translated from Danish) Mikkel is a man after my own heart. Executes at lightning speed, has an eye for detail and is always there when you need him. It does not get better than that.
Tini Owild(translated from Danish) He is simply a pro. Highly competent and precise, brings good input, and is a huge support.
Carsten Johan Thessen(translated from Danish)
Services
Why me
- 16 years of experience
I have built for the web since 2010 and seen most of the ways a project can come off the rails. It makes the estimates more honest.
- 400+ projects
Across ecommerce, pharma, construction and the public sector. Chances are I have seen something close to your job before.
- You talk to the person coding
No project manager in between, and no junior on the job because the senior was busy. What you agree is what gets built.
Brands I have worked with
A selection. Some freelance, some through agencies, some across several years.
Questions
Frequently asked questions
- How many can attend?
- Up to twelve, if there is going to be time to help each person in the afternoon. For more than that we split it across two days rather than turning it into a lecture.
- Do people need to be able to code?
- No. Most of my workshops are for marketing, sales, administration and management. For a development team I build a completely different day.
- Can we have it online?
- It can be done, but it works better in person. The afternoon relies on me being able to look over shoulders, which is hard over video.
- What does a workshop cost?
- It depends on length, group size and how much preparation your tasks require. Write what you have in mind and I will come back with a fixed price.
- Can you run a follow-up?
- Yes, and it works well. Half a day three or four weeks later, picking up whatever caused trouble once people had tried it on their own.
- What if some of the participants are far ahead?
- Then I ask about it in advance and split the day. Mixed groups where half are bored do not work, and running two sessions beats aiming for the middle.
