Frameworks come and go. What stays: understanding problems, thinking ahead and delivering solutions that hold up in production. Since 2010 I've been building software for companies and agencies — full stack, because I want to see the full picture, not because it looks good on a resume.
Each of these tools was born from a problem that annoyed me personally.
Time tracking with e-invoicing. From the booked hour to a finished XRechnung or ZUGFeRD invoice.
Born because my hours lived in one tool and my invoices in another — and since mandatory e-invoicing, a PDF no longer cuts it.
VisitVisual bug reporting for web agencies. Screenshot, browser context and annotations in one click.
Born because client bug reports usually consist of 'doesn't work' and a blurry phone screenshot.
VisitFree GDPR check for websites. Automatically scan cookies, trackers and consent banners.
Born because I had to manually check GDPR compliance on every project handoff — every single time.
VisitClassic tests don't work on LLM output — every answer is different. How rubrics and an LLM-as-judge turn "looks good" into an actual measurement.
Read moreHow to build your own MCP server in TypeScript in a single afternoon – with a runnable mini example and the lessons I already did differently on my second server.
Read moreHow MCP servers turn a chat partner into a colleague with real hands – and why every connected server should be a deliberate decision, not a default.
Read more