Staff Engineer & AI consultant Amsterdam
I help teams turn scattered AI use into reviewed, repeatable work on tasks they already do.
10+ years across software, platforms, and distributed systems. I test what helps, then leave your team able to run it.
Clear scope Practical handover
00 The signal
Teams need a clear way to use the AI tools they already have on work they do every week.
The team has tools, but people use them differently.
Work comes back for another round of edits.
Useful context gets copied between docs, tickets, and spreadsheets.
A useful demo needs a path into the routine.
01 Services
I bring an engineering approach to AI adoption: pick one task, agree what good looks like, test on real inputs, and hand over what works.
Use current team tasks to practise giving context, structuring requests, reviewing outputs, and weighing cost against quality.
In the roomUse a real task, then turn the useful parts into examples and a playbook.
Take-home
Worked examples, shared terms, and a short playbook for the next attempt.
Choose one recurring process. Map where it slows down, test a small change, add review points, and document the version your team keeps.
Good candidatesCase handoffs, recurring reports, or meeting notes turned into tracked actions.
Take-home
A tested workflow, concise documentation, and an internal owner.
Look at one recurring task and how the team uses its current tools. Compare retries, cost, and reviewed output quality before changing the routine.
The decisionWhich steps need a better prompt, a simpler process, or no AI at all?
Take-home
A short priority list, tested changes, and a clearer standard for future use.
Each engagement stays focused on one clear piece of work, with a practical handover.
02 Worked example
Illustrative
example workflow
Before
Meeting notes stay in a transcript, a document, or someone’s memory. Decisions are easy to miss.
After
A draft list of decisions and actions is checked by an owner, then becomes the confirmed action list.
An illustrative workflow for turning meeting notes into a confirmed action list.
03 Approach
We start with a real point of friction and work toward a version your team can explain and use.
Find the recurring task that absorbs attention, creates rework, or loses context.
Agree what a useful result looks like, who reviews it, and where judgment stays human.
Try the smallest workable change on the material your team actually handles.
Document what changed, show the pattern, and leave someone on the team ready to run it.
I’m an Amsterdam-based Staff Engineer with more than 10 years of experience across software, platforms, and distributed systems. I’ve evaluated AI tools and helped teams adopt them in practical ways.
I focus on choosing changes that are useful, checking whether they work, and making the process manageable for the team.
Independent practice
Amsterdam, NL
05 Book a conversation
Bring a workshop idea or a recurring process you want to improve. A little context is enough to begin.
15 minutes
We’ll get acquainted, talk through what your team needs, and see whether working together makes sense.