Cloud and platform architecture
Target architectures, platform design and technical guardrails that do not just look good in concept decks, but continue to work under real constraints.
Direct access to the responsible expert
I step in when platforms need to become sustainable, operational processes must stay under control and new AI capabilities have to be integrated cleanly into existing systems.
Service model
Architecture on its own is not enough. Only when platform, operations and extensibility fit together do you get systems that survive day-to-day reality and do not fall apart with the next change.
Target architectures, platform design and technical guardrails that do not just look good in concept decks, but continue to work under real constraints.
Automation, rollout paths, monitoring and operating models that keep technical complexity from turning into permanent operational stress.
Add LLM and assistant capabilities where interfaces, security and operational boundaries are already under control, not as a demo but as a production extension.
Project spotlights
Context: Further development of an enterprise-wide loyalty platform with app, backend and integration components in a retail environment with high organisational and technical interdependence.
Role: Technical project lead with responsibility for architecture decisions, technical guardrails and coordination across multiple sub-teams.
Technical core: Azure Functions, event-driven flows, APIs, SAP-related integrations and standardized deployment and operating processes across team boundaries.
Impact: Clear technical guardrails in a complex programme, more stable integration flows and faster delivery of new capabilities despite distributed responsibilities.
Context: Greenfield build of an on-premises platform for multiple containerized services, with a focus on standardising infrastructure and rollouts.
Role: Architecture owner and implementation lead for cluster build-out, ingress, storage, deployment standards and monitoring.
Technical core: Idempotent Ansible roles, Helm-based deployments, a standardised TLS and ingress strategy plus a central monitoring stack.
Impact: Reproducible infrastructure instead of manual exceptions, significantly lower operational effort and faster onboarding for new services.
Context: Feasibility project for AI-supported voice interaction in an existing VoIP environment with real interfaces and real system boundaries.
Role: Target architecture design, technical interface definition and iterative prototype delivery.
Technical core: LLM integration, Python-based dialogue logic and robust communication paths between AI and telephony.
Impact: A credible prototype that showed how AI can be connected to production-adjacent systems without ignoring architecture or operations.
How I work
You work directly with the person making technical decisions and thinking through their operational consequences. No handovers between sales, architecture and implementation, and no unnecessary coordination layers.
Profile
I work at the intersection of architecture, implementation and operations. My role becomes valuable where technical complexity should not be passed on, but instead structured clearly and delivered in a way that holds up over time.
Contact
If you are looking for direct technical ownership in a platform, integration or AI initiative, a short intro call is the best way to find out whether I am the right fit.