The window is open. Not for long.
Only one in five EU companies with 10+ staff used AI at all in 2025. Most of your market is still deciding. The teams that move first get the head start.
SOURCE: EUROSTAT, DEC 2025 ↗Your competitors are rebuilding how they work with AI.
A 4-week sprint gets your team there first: real
experiments, ready-made handbooks, and a senior
engineer working alongside your people.
Experiments, training and handbooks. Delivered personally by Alexander.
Illustrative workflows. Not a live AI tool or a client result.
Not a strategy deck.
Not a generic course.
A senior engineer in your team.
The advantage doesn’t come from the licence. It comes from teams that change how they work, and the ones doing it now set the pace for their market.
Only one in five EU companies with 10+ staff used AI at all in 2025. Most of your market is still deciding. The teams that move first get the head start.
SOURCE: EUROSTAT, DEC 2025 ↗Seats get bought, a few enthusiasts use them, and the core work stays the same. That’s cost without speed. The workflow itself has to change.
A team that gets a little faster every week also learns faster every week. Wait a few quarters and catching up becomes a much bigger project.
No strategy handed over and left on a shelf. Experiments run on your real work, the winners are written down, and your team learns to run them without me.
We run 3–5 AI experiments on your team’s actual tasks, side by side with the current way. Keep what’s faster. Drop what isn’t.
Start from ready-made handbooks for engineering, operations and leadership: workflows, prompt and agent setups, review checklists, data rules. Adapted to your stack and policies.
Every experiment is timed against your baseline: hours, review effort, rework, tool cost. Show leadership the speed-up, not a feeling.
One team, real tasks, a fixed timeline. No months of discovery and no 80-page strategy. By week four your people work the new way and know how to keep improving.
Map where the team’s time goes. Pick 3–5 high-impact tasks and record how long they take today.
↳ Experiment backlog + baselineBuild an AI workflow for each task with your team, on your stack and approved tools. Run them on live work.
↳ Measured result per experimentHands-on sessions on the winning workflows. Everyone practises on their own tasks. Name your AI champions.
↳ Trained team + internal championsWrite the winners into your team handbook. Set the standards and a 90-day backlog of next experiments.
↳ Handbook + rollout planGains are measured on your work, not promised on a slide.
You see the numbers as the sprint runs.
Brief your leadership, train a team, or run the full sprint. Scope, timing and fees are agreed up front.
A focused session for the leadership team: how AI is changing work in your sector, where it hits your workflows, and what to test first.
Hands-on training on your team’s real tasks, built on the ready-made handbooks. People leave working differently, not just knowing more.
Experiments, implementation and training in one. Your team ends the month working AI-first, with measured results.
Remote delivery in English, aligned with European working hours. On-site sessions can be discussed.
Most AI programmes produce either slides or certificates. This one produces a team that works faster.
Months of discovery, a strategy deck, and junior staff doing the work.
A senior engineer building with your team. Working workflows in weeks.
Generic demos. Nothing changes on Monday.
Your tasks, your stack, your rules. The work changes in the same week.
Scattered prompts, uneven results, and nothing spreads.
One shared handbook, a team standard, and champions to keep it going.
15+ years in production engineering. Now I help teams work AI-first.
I’ve led engineering teams, worked on distributed systems and computer vision, built AI agents and automation, and created a 16-week Go programme that trained more than 20 engineers.
I’m not a strategist with slides. I sit with your team, build the workflows, review the output, and teach people to run them. Every session is delivered by me.
Make the team faster.
Make it stick.
Because licences aren’t adoption. In many teams, AI gets used for a few one-off tasks while the core workflow stays the same. The sprint changes the workflow itself, using the tools you’ve already approved.
The first experiments run on live work in week two, and you get before-and-after results by week four. I don’t promise a percentage in advance. We measure it on your tasks, including review and rework time, so the numbers hold up when you share them.
Plenty of places, and the sprint is designed to find them. AI output can be wrong in confident ways, so every workflow keeps a human review step. Tasks with messy inputs, unclear ownership or a lot of judgement often don’t get faster. Some experiments will lose to the current way of working; we drop those and say so in the results.
Step-by-step AI workflows for common tasks in each role, prompt and agent setups, review checklists, and rules for which data can go where. You start from a ready version, and we adapt it to your stack, tools and policies. Your team keeps it and owns it.
Both. Engineering sprints focus on things like bug fixes, code review and tests. Operations sprints focus on reports, documents and recurring analysis. Leadership briefings focus on where to start and who owns it. Digital agencies get their own version built around reporting, research, content and client delivery. Each engagement starts with one team.
No. Initial examples can use public, synthetic, or sanitised material. Company data is used only after your team agrees the tools, access rules, and handling requirements. Your internal security and legal owners remain part of that decision.
When you book a call, Cal.com handles the booking and receives the details you enter there. This site only records that a call was booked and which campaign link was used, with no name or email. No mailing list, no tracking or analytics, and no cookies are set by this site. The Cal.com calendar, which may set its own cookies, loads only after you accept in the cookie notice or click “Load calendar”. Your choice is remembered in your browser; clear this site’s data to be asked again. To have your booking details removed, ask Alexander on the call or reply to the calendar invite.
Fees depend on the format, team size, and scope. A written proposal sets out the fee, sessions, deliverables, tool costs, and responsibilities before you commit.
Book a 20-minute AI productivity discovery. We’ll look at where your team’s time goes and which workflows AI could speed up first.
Where your team’s time goes today.
The 2–3 workflows where AI could move fastest.
Whether a 4-week sprint makes sense. If it doesn’t, I’ll say so.
You leave with a shortlist of experiments worth running, whether or not we work together.
Pick a timeOpens the calendar. Booking is handled by Cal.com. Privacy