Phone
Address
Wehlistraße 291/1/47
1020 Vienna
THE WERKSTATT
I build the workshop. Your team does the work.
Werkstatt is where your team builds and maintains your company's software itself. AI agents do the coding, your people make every decision. I set it up, build the first real application with you, and teach your people to run it. Your software, your house, your people.
What this actually is
Most companies rent the software they depend on. Someone else builds it, someone else maintains it, and every change costs a ticket, a quote and a wait in another company's sprint.
Werkstatt turns that around. It's a workspace in the browser where the people who know your business describe what they need, in their own words. AI agents build it, test it and review it. A named person in your company approves the plan, tries the result and decides when it goes live.
It comes into your company through one engagement of two to three months. I set it up, we build the first application together, and your team learns to run it.
Then I leave. That's the point.
Why This Works Now
Code got cheap. Systems didn't.
Agents now write code faster than ever. Left alone, they produce work that looks plausible, that nobody checked and nobody answers for. Speed makes that worse, not better.
What's missing isn't another model. It's a process where your people decide and the agents do the work.
Building got cheap
Software that was never worth commissioning suddenly is: the quote tool nobody likes, the scheduling spread across three systems, the one spreadsheet that quietly runs the business.
Unsupervised agents are a liability
An agent working alone makes mistakes faster and more consistently than a person. Without checks and someone who answers for the result, more speed means more damage.
The right person is already on your team
The person who notices every Tuesday morning that something is off should be the person who changes it. Understanding the code was never the requirement. It was the toll.
Distance makes software rot
Software decays when the people who build it aren't the people who live with it. That used to show up as delay. Now that building is fast, it shows up as damage, in weeks instead of years.
How It Works
One change, one path
Everything you want changed becomes a card on a shared board, from the first wish to production. Every card takes the same path, and your people decide at three points along it.
1. Describe and clarify
Someone on your team describes what they need, in their own words, with examples and files. An agent asks questions until there's a plan with criteria anyone can check. Then that person gives the Go.
2. Build and check
Only after the Go do the agents work on their own. They split the work into tasks, build them one by one and run automatic tests. A review agent and an audit agent inspect the result. Budgets and limits cap how far they go without a person.
3. Try it and accept
The person opens a live preview, tries the result and checks every criterion one by one. They give their Acceptance or ask for changes, and the agents go back to work.
4. Release
Nothing reaches the outside world without its own Release. Afterwards Werkstatt checks that the delivery actually arrived. The previous version stays one step away.
People Decide
Three approvals. None of them can be switched off.
The approvals are part of the structure, not a setting. A workflow that tries to skip one can't be published. Each decision is tied to an exact version and recorded in a log that can only grow. For software, acceptance and release need two different people.
Go
On exactly this plan, with criteria anyone can check. Only then do the agents start working on their own.
Acceptance
A person tries the result in a running preview and checks each criterion. Accepted, or sent back with changes.
Release
Before anything reaches your customers or your data. Checked after delivery, with a one-step way back.
When a run fails, the Werkstatt says what happened, what was kept, who can fix it and what comes next, in plain words. Logs are there if you want them, but nobody has to read them.
It measures results, never how a named person worked. Who did what, yes. Ratings of people, never.
Under the Hood
One workshop for every AI agent
Coding agents like Claude Code and Codex are each a harness: the tooling that lets an AI model read, write and run code. Werkstatt is a harness of harnesses. It runs those agents inside one process with one set of rules, so you don't have to pick a vendor, learn each tool, or trust any of them blindly.
Your subscriptions, your costs
The agents run on your personal Claude and Codex subscriptions, signed in by a named person. Credentials stay on your installation. No markup on AI costs, no resale.
Same rules for every agent
Whichever agent does the work, it passes the same three approvals and stays within the same budgets. Three bans always apply: no effect on production without permission, no connections outside allowed addresses, no writing outside its own workspace.
Models change, your process doesn't
Today's best model won't be next year's. Switch providers without changing how your team works. For companies that only allow processing in the EU, I'm testing a route with EU-hosted open models.
You always know who did what
Provider, model and version are recorded on every run, every change and every release. Each release carries its own evidence: what's in it, who accepted it, which tests passed.
Four Phases
From empty installation to a team that ships without me
Two to three months end to end. An engagement, not a subscription. Afterwards you keep a credit for sparring, reviews and small changes, and it never expires.
1. Set up
Your own installation, people and roles, the repository, your AI model access, and the limits for agents. The path from request to release is in place before the first card.
2. Foundation
Data model, sign-in and permissions, test and production environments, automatic delivery. Then the most important workflow of your application, finished all the way to production.
3. Build-out
The first version becomes complete, including moving data out of your old systems in checked runs. Your team builds one module on its own. I guide, review and approve.
4. Handover
Going live together, training, and a manual for running and recovering. The final test: someone who wasn't involved runs an agreed workflow alone, using only the docs. That proves your team can take over.
What You Own at the End
Your own installation. Plus the record of every decision made in it.
The repository. All the code of your application, in a normal Git repository.
The documentation and the delivery path. Set up, written down and tested by your own people.
A permanent right to Werkstatt. Use, inspect and change it for your own company. Let someone else take over any time. Nothing depends on me staying.
Who This Is For
Companies of 20 to 200 people without a development team
You have a quote tool nobody likes, scheduling spread across three systems, and the one spreadsheet that quietly carries the business and nobody dares touch. Every change goes through someone outside.
Internal tools: quotes, order tracking, scheduling, inventory, shift plans. The tools your team works with every day.
Apps for your customers: booking, order status, self-service. The reasons customers call you today.
What you bring: one capable person who knows your business closely and is willing to describe things precisely and check honestly. They don't need to code. I train exactly that person during the engagement.
The first pilot
A cultural venue in Salzburg is replacing several tools that don't share their data with one core system, from September to December 2026. The deadline is fixed because the old system runs out at the end of the year. The more important result is the second one: the team keeps developing the application itself with Werkstatt. There are no results to report yet. I'll share them once there are.
Who Builds Your Workshop
Fifteen years of production systems
Including registration for one of the world's largest charity runs: 350,000+ sign-ups a year from 200 countries, with payments across more than 30 providers.
I know the agency model from inside
Ten years as co-founder and technical lead of the agency Neonblack. I know what a small change costs an agency and why it still takes weeks. The Werkstatt is the way out.
Software on a real shop floor
Eleven years at Kässbohrer, a maker of car transporters, and a master's thesis on connecting ERP systems. The people who know the process are almost never asked. I ask them.
Products shipped this way
b10cks, RAVN Mail, Kessel and gh0st were all built by one person with the workflow I set up for you. The code is public, so you can read it before we talk.
Bring the problem, not the specification
You don't need to know what to build yet. Bring the one tool that slows your team down today. In 30 minutes we'll find out whether the Werkstatt fits and who in your company would be the right person for it. If it does, you get a written proposal within a week.