Projects
Case studies covering the starting situation, ownership, system boundaries, architecture and what was learned — without invented success stories.
Decisions need context. Project write-ups therefore show more than the outcome: the starting situation, the scope of responsibility, the system boundaries and the reasoning behind the architecture.
Where projects are confidential, clients are described anonymously. Availability, performance or cost figures are published only once they have been measured, evidenced and approved.
A project write-up appears here only once the client has approved it. References without that approval we discuss directly instead.
-
Case study
AI-Enabled Document Analysis and Process Automation
A hybrid pipeline of text recognition, rules, language processing, classification and language models – delivered as a custom business application.
-
Case study
Entwickler Journal – custom publishing platform
Replacing a WordPress site with a bespoke PHP and Markdown architecture for articles, series, projects and content in two languages.
-
Case study
AuraHarmony – multilingual product website for a mobile app
A multilingual website for a native iOS and Android product, covering product communication, a blog, knowledge content and privacy by design.