I've spent 25 years getting software into production. Since 2025, that software has been AI.

I started at Cisco, where I ended up leading organisations of more than 250 engineers. You learn two things at that scale: that most problems are coordination problems wearing a technical costume, and that nothing counts until it's running for real customers.

Later I was fractional CTO of a community platform serving 2 million users. Small team, real load, no room for architecture that only worked in a diagram. That job taught me to understand the business before touching the system — because every shortcut I took without doing that came back with interest.

Since 2025 I've been shipping production AI systems daily — hands-on, not from a slide. Most recently, live enterprise agentic-AI work under human-in-the-loop requirements that regulators would sign off on. It shipped because we started with the approval boundary, not the model.

Why Shipwright? A shipwright builds vessels that actually sail. Not models of ships, not renderings of ships — hulls that go in the water and come back. That's the job as I see it: getting things to production, seaworthy. The word “ship” doing double duty is not an accident.

I work in English and Italian, with working German, from Zürich.