Services
Four shapes of engagement. Each names what you get, how long it takes and how it is priced — because “architecture consulting” without those three is a conversation, not something anyone can buy.
I am a software architect who still writes production code — twenty-five years of it, across a cross-state public-sector platform in .NET and React and a multi-tenant SaaS in TypeScript that I own end to end. German and English, remote across the EU or on site around Stuttgart. How I build, in detail and with the trade-offs named, is on the approach page.
Availability
An outside read of a system you already run.
I go through the code, the data model and the way it is operated, and talk to the people who carry the pager. Boundaries, tenancy and isolation, the failure modes nobody has hit yet, the migrations that will get harder every month you wait.
Best before a funding round, a rewrite decision, or the first hire who has to understand the whole thing.
Coding agents in a real codebase, with the guardrails that make it safe.
I build with AI coding agents daily — Reynt is the evidence — and the interesting part was never the tool. It is the discipline around it: architecture boundaries a machine cannot quietly cross, tests that fail when it does, and review that stays human. I set that up with your team and work in it alongside them.
Best for a team that has tried agents, seen the quality dip, and wants the productivity without it.
The shape decided before the team starts moving fast inside it.
Technology selection with the trade-offs written down, service and module boundaries, the data and tenancy model, the authentication and permission model, and the guardrails that keep the shape intact once six people are committing to it.
Best at the point where a prototype is about to become the product.
Building it, not just diagramming it.
Full-stack work inside your team: TypeScript, C#/.NET, Kotlin and Go, on Kubernetes. I write production code every week and have no interest in an architecture role that does not. Where it helps, I coordinate the developers around me — that was the job on MUSES.
Best when the plan exists and the constraint is senior hands.
How it starts
01
A paragraph is enough: what the system does, what is going wrong or what is being built, and roughly when you need someone.
02
Free, and mostly me asking questions. At the end of it I will tell you whether I am the right person — sometimes the answer is no, and it is cheaper for both of us to find that out here.
03
Scope, deliverable, duration and price in writing, usually within two working days. No retainer, no minimum term beyond what the work needs.
04
Contracted through octabits — DK2 Ventures UG (haftungsbeschränkt). Reviews start immediately; delivery engagements typically within two to four weeks.
Terms
Honesty
Every project I publish ships a “when not to use this” section. It would be strange for the person who wrote them not to have one.
What the system does, what is going wrong or what is being built, and roughly when you need someone. A paragraph is enough — the reply comes from me, usually within a working day or two.