Three reasons Dutch teams typically engage me directly, instead of going through a system integrator or large consultancy.
Decisions on landing zone, identity, networking and data residency are taken on the merits of your context, not based on what a partner needs to sell this quarter. No artificial vendor lock-in.
Same face from first call to delivery. No team rotation, no "the architect who designed this has left the project". The person who proposes a choice is the same one accountable for it eighteen months later.
The goal is to bring your internal architects and platform engineers to a level where they no longer need a consultant, not to make them dependent on one. Documentation, decisions and operational capability stay inside.
The practical things Dutch clients usually ask before the first call.
Day-rate friendly. Typical setups: focused architectural assessment (a few weeks), fractional architect alongside the internal team, or full delivery on a defined scope. T&M or fixed scope, depending on what fits the decision you need to make.
Independent consultant operating cross-border, EU-based. Setting up a Dutch entity (KvK) for local procurement; in the meantime invoicing in EUR via Italian VAT entity. Open to working through Dutch agencies or detachering structures where your procurement requires it.
English (primary) and Italian (native). Comfortable in Dutch professional environments; written and spoken Dutch on my side is limited. All meetings, documentation and delivery happen in English. Honest about it from day one, not at the first meeting.
Four focused service areas. Detailed pages in English.
Enterprise architectures, landing zones, governance, identity, security and cost control for platforms ready to scale.
Phased migrations to Azure with operational continuity, workload-by-workload assessment and a real rollback strategy.
CI/CD pipelines, Infrastructure as Code and release engineering to reduce lead time and post-release incidents.
Cost visibility per team, governance, rightsizing, reservations and continuous workload optimization on Azure.
EU-region first by default. West Europe / North Europe as primary regions for Dutch workloads, with explicit decisions on cross-region data flow when the architecture requires it.
Identity, logging, backup and lifecycle decisions made with GDPR and DPIA implications in mind. No legal advice — engineering decisions framed in a way your DPO can sign off.
Awareness of Microsoft Cloud for Sovereignty and EU Data Boundary. Pragmatic posture: use what materially reduces risk for your sector, skip what is only branding.
The fastest way to know if it makes sense to work together is a 30-minute call. I will tell you honestly if I am the right person for what you need, or if you need a different kind of help.
Based in Amsterdam. Easy to meet in person in NL or on video for EU clients.