Bring anything from your work you would like to do faster, better, or at all, and we will spend half an hour on it together.
One to one, hands-on, and not a demo. Just you and someone who does this every day: share your screen, we point AI at something real, and you leave with it further along plus a sense of how to keep going on your own.
The sessions that go best are the ones where somebody arrives with a real, unglamorous problem they have been avoiding. Toy examples teach nothing.
A feature, a fix, a script you keep meaning to write. We point a coding agent at it and get it working.
The report you rebuild every Monday, the inbox you triage by hand. Most of these are an afternoon of work away from running themselves.
Documents, tickets, customer feedback, survey answers. Reading all of it was never the job. Knowing what is in it was.
"Could AI do this?" is a completely fine thing to arrive with. Half an hour is usually enough to find out.
If you have never opened one of these tools, we will spend the time getting you set up properly. That is often the most useful thirty minutes we can spend.
Share your screen and describe the problem in your own words. No prepared brief, no tidying up first. The messy version is the useful one.
You drive, we sit next to you. You watch how the request gets framed, where it goes wrong, and how it gets pulled back. That part is the real lesson.
What worked, what to try next, and what to stop doing. Written down, so it survives the walk back to your desk.
Nothing is pre-baked. We work on your thing, live, and sometimes it fights back.
There is no deck and no follow-up sequence. If we can be useful later you will know where to find us.
No curriculum, no homework. One problem, half an hour, something further along than when you started.
Two partners run DenkWork day-to-day. They lead engagements together with the wider engineering team across our offices and sourcing networks.

Originally from the Netherlands, Melvin has been the founding engineer of five VC-backed companies that have collectively raised over $400M. In Silicon Valley he led 100+ engineer teams at companies like Wag.

Önder runs operations and client relationships from Rotterdam. He brings years of management experience and has founded and built businesses in the Rotterdam area.
Setup is the slow part. Downloads and sign-ins can eat a whole session, and the ones that go best are the ones where that is already done.
One session is one person and one problem. If you want a team moving, or you already know you will be back, buy the time in a block instead. Ten hours or more comes at a lower rate.
Hours are yours to spend how you like. Split them across your team, spend several on one hard thing, or keep a standing slot. After the first couple we know your stack and your codebase, so later sessions start further along.
Talk to usTell us roughly how many hours and how many people, and we will come back with a number. [email protected]
No. A good share of the people we sit with have never opened a terminal, and the tools have moved far enough that it stops being the barrier it was. If you can describe what you want clearly, you can do this.
Usually Claude Code or Codex for anything that touches code, and whichever assistant fits for everything else. If your company has already standardised on something, we will work in that instead. The habits transfer.
Half an hour of senior time, one to one, on your own work. No package, no retainer, no follow-up sequence. If half an hour is not enough to be worth it to you, do not book it.
Most things do not finish in thirty minutes, and that is fine. The point is to get past the part where you are stuck and leave you able to keep going without us.
Please do. Two people watching the same session is not twice the value, it is considerably more, because afterwards there are two of you who saw it work.
Half an hour, your problem, no pitch. The worst case is that you learn where these tools still fall over, which is worth knowing too.