For people whose job is not writing code. Product, operations, marketing, finance, legal, founders. You already know which parts of your work are worth fixing, and that judgement is the hard half. The tools have finally caught up enough that you can build the fix yourself.
What used to take a developer, a budget and a quarter is now often an afternoon of your own. The only thing between the two is technique, and technique is quick to pick up.
The same material at four sizes. Start free and on your own, sit with one of us for half an hour, or put a whole team through it in an afternoon.
A written course that takes somebody with no technical background from nothing to a working app, with an AI agent doing the typing. Published module by module as it is finished.
Best if you want to try this on your own first, at no cost and no commitment.
Start the courseBring one real thing from your own week and we work on it together, live, on your screen. Not a demo and not a lesson: your actual problem, half an hour, further along than when you started.
Best if you learn fastest by doing it once with somebody sitting next to you.
See how it worksBuy time in a block and spread it across your team. Everyone brings their own work. After the first few sessions we know your systems well enough to skip the preamble.
Best if several people need this and you would rather not book it a week at a time.
How blocks workEveryone in one room with their own laptop and their own backlog. We work through real tasks rather than exercises, and people leave having built something they actually needed.
Best if you want a whole department moving at once rather than a few enthusiasts.
Plan a sessionNone of this needs programming. It needs knowing what to ask for, how to say it, and how to tell whether the answer is any good.
The spreadsheet you rebuild every Monday, the deck you assemble by hand. Describe it once properly and most of these start running themselves.
Hundreds of tickets, survey answers, contracts or call notes. Sorted and summarised in minutes, instead of never.
The thing IT will not prioritise and a spreadsheet cannot quite do. That is now an afternoon rather than a project nobody funds.
Show the idea instead of describing it. A rough working version moves a meeting further than any document.
Not generic AI prose. Your tone, your structure, your rules, applied consistently because you wrote them down once.
The most valuable skill and the one nobody teaches: how to check an answer you could not have produced yourself.
No sample problems. You bring the thing you have been avoiding, and that is what we do. It is the only version that transfers back to your desk.
Everything gets said in ordinary words. Where a technical term is genuinely unavoidable we define it once and then use it properly.
You type, we sit beside you. Watching somebody else do it looks easy and teaches almost nothing.
DenkWork ships production software with AI every day. What we teach is our own working method, not a curriculum assembled from other people’s posts about it.

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.
Tell us roughly who needs to get better at this and what they are trying to get done. We will say which of the four is the right size, and if none of them are, we will say that instead.