I founded Gray Matter in 2016. It took a decade to find its purpose. After 14 years as an architect at one of Switzerland’s largest critical infrastructure providers - directing the Zero Trust transformation since 2022 - the purpose became clear: Zero Trust and governed Agentic AI are inseparable, and both need architecture that works in practice, not just in frameworks. The hardest problems sit in the gaps between policy and implementation, governance and delivery, architecture and operations.
What I Advise On
Zero Trust Architecture Building security architectures that work across fragmented enterprise estates, governance models, and legacy constraints. Horizontal policy woven into connectivity - so controls do not fail at the seams. Security that adapts to the user, not the other way around.
Governed Agentic AI Designing autonomy that is bounded by policy, identity, observability, and operational controls. The same conditions that make Zero Trust difficult at scale - fragmented identity, inconsistent policy, legacy complexity - also make Agentic AI risky to deploy. I help organisations adopt AI safely through Graduated Autonomy: enabling useful automation while preserving control, traceability, and accountability.
This is not theoretical. I build and operate autonomous AI systems in practice - from governed security operations to spec-driven engineering workflows. When I advise on AI governance and agentic coding adoption, it comes from operating these workflows, not from treating them as a trend.
Enterprise Scale Context
Zero Trust and AI governance are rarely limited by tooling alone. In large organisations, the harder problems are fragmented ownership, uneven governance, legacy integration constraints, and the challenge of applying consistent policy across users, systems, and regions.
My experience comes from leading one of Switzerland’s most significant transformations across this complexity:
- Multi-region, multi-entity environments - 100+ subsidiaries, 3,500+ locations, 5M+ users across employees, customers, partners, and suppliers under one policy fabric
- Legacy integration and technical debt - decades of legacy IT, IoT/OT, and industrial control systems integrated without breaking critical services
- Governance and stakeholder alignment - approved across IT leadership, executive management, and the board, then funded and executed as a multi-year programme covering all seven Zero Trust pillars
Why Direct Engagement Works
Continuity The person who designed the architecture is the same person who guides implementation. No handovers, no re-education, no context lost between phases.
Aligned Incentives My success is measured by your outcomes, not billable hours. The engagement is focused on delivering results with direct access to the person doing the work.
Current Practitioner Experience My guidance comes from recent, hands-on experience building the systems I advise on. I still architect and build - which means recommendations reflect current operational reality, not yesterday’s best practices.
This model is not right for every engagement. If you need a team of 50 consultants or a global programme management office, a larger firm is the appropriate choice. I design at scale, then guide your teams through execution.
How I Work
Survivability Over Theory If a policy cannot survive peak operational loads or a legacy SAP instance, it is a liability, not a security measure. I prioritise resilient, pragmatic architecture over theoretical models. Architecture that cannot survive contact with your budget, organisational culture, and legacy systems is not architecture - it is theory.
Technology-First Advisory I help you decide what technology you need - and what you don’t. Whether selecting Zero Trust platforms, AI frameworks, or agentic coding toolchains, I guide your team through evaluation, RFI/RFP processes, and PoC design. When I recommend a product, it is because I believe it serves your interests.
Resilience Over Perfection I design for failure - not to prevent it, but to survive it. The architecture that wins accepts concentrated dependencies deliberately and designs for graceful degradation. I do not design for a world where technology never fails - I design for a business that survives when it does.










