Frequently Asked Questions

I don't publish rates because every engagement is different. Factors include scope, complexity, timeline, and deliverables. I'm transparent about pricing once we've discussed your specific needs. Expect enterprise consulting rates - this is specialised, high-impact advisory work.

No formal minimum, but the nature of the work means most engagements are measured in weeks, not hours. A half-day call isn't the right fit; a 2-week assessment or multi-month architecture engagement is.

Typically: 50% on commencement, 50% on delivery for project work. Monthly invoicing for ongoing engagements. Swiss Francs preferred; EUR/USD possible. Payment terms: 30 days.

Yes, within limits. I typically work with 2-3 clients concurrently, depending on engagement intensity. I'm transparent about availability and will tell you upfront if timeline constraints exist. I don't overcommit.

For ongoing engagements, we establish contingency plans upfront. I maintain relationships with trusted specialists who can provide backup coverage for specific situations. This is discussed during engagement planning, not discovered during a crisis.

Primarily solo for strategy and architecture work - that's the point of direct expert access. For implementation-heavy phases or specialised needs (e.g., penetration testing, specific vendor expertise), I bring in trusted specialists as needed, always with your approval and transparency about who's involved.

I help you decide what technology fits your architecture and your problem - and what you don't need. Whether you're selecting Zero Trust platforms, AI frameworks, or agentic coding toolchains, I guide you through evaluation criteria, RFI/RFP processes, and PoC design. Every recommendation is documented in architecture decision records so you can see the reasoning behind it.

Every recommendation comes with full reasoning and rationale. I only recommend something when I believe it is the right fit for your situation, your problems, and your requirements. My default recommendation is often "integrate what you have" and "reduce the number of point solutions" - lower complexity, capitalise on existing expertise and knowhow. My reputation depends on your outcomes. If the architecture gets more complex instead of simpler, I don't get repeat business.

Because Zero Trust fails between components, not within them. Most companies already have capable tools - the challenge is making them work together. Too many point solutions, not enough horizontal integration. Before recommending new products, I evaluate whether better integration of existing products would achieve the same outcome. Complexity kills security.

I design and guide, not implement at production scale. My value is in architecture, strategy, and oversight - not in long-term operational configuration. I do build proofs of concept and reference architectures in sandbox environments to validate designs and demonstrate feasibility. Production rollouts and ongoing operations remain with your team, your integrators, or vendor professional services, with my oversight ensuring the architecture vision is preserved.

Clarity and direction. Depending on the engagement: a clear picture of where you stand, a prioritised path forward, a target state architecture you can build from, a business case that gets funded, a technology decision backed by rationale, or a validated proof that a concept works. The specifics vary - but you always walk away with concrete outcomes you can act on, not a stack of papers.

The decisions and the reasoning behind them. Every recommendation comes with full rationale - what was considered, what was chosen, and why. The architecture is clear enough to build from and extend. You move forward confidently because the logic is visible, not because someone is there to explain it.

Minor clarifications are included. Significant scope changes or new requirements are scoped as follow-on work. For ongoing relationships, consider a retainer arrangement that provides access for questions and periodic reviews.

Based in Switzerland (near Bern). I work with Swiss and European clients primarily. Travel for workshops and key meetings is standard; day-to-day work is remote. For international clients, we establish a working rhythm that accommodates time zones.

Direct, honest, and efficient. I prioritise architectural truth over telling you what you want to hear. If an assumption is wrong, a scope is unclear, or a timeline is unrealistic, I will tell you directly. The goal is clarity early, before expensive mistakes compound.

Strictly. All client information is confidential by default. I sign NDAs when required. I never use client-identifiable information in marketing without explicit permission.