For over two decades, I've been designing, building, and connecting digital experiences, products, and systems. From a simple idea to complex digital ecosystems.
Most of what I build, nobody should notice. The permission rule that quietly does the right thing. The import that runs at 3 a.m. The form that doesn't lose someone's afternoon. Complexity never disappears — it just gets moved. My job is to move it away from the people using the thing.
That takes more than one discipline. Design to understand people, engineering to make it real, strategy to make sure it's worth building at all — and enough curiosity to keep asking why.
Six disciplines that usually live in six different companies. Working across all of them is how the pieces end up fitting together. Select one to open it.
Sites and interfaces people can use without having to think about them. From editorial websites to multi-site WordPress ecosystems — with design systems that keep everything consistent long after launch day.
When an off-the-shelf tool stops fitting, I design and build the one that does: lightweight, maintainable web applications — often framework-free — with an architecture that can grow without a rewrite.
AI where it actually helps: assistants connected to real data, workflows that remove the repetitive part of a job, and no-code integrations that let a small team operate like a larger one.
Helping organisations decide what to build, what to buy and what to leave alone. Technical direction, transformation roadmaps, and an honest translator between leadership, vendors and developers.
Turning scattered information into something you can search, compare and trust — open-data publishing, data integration and discovery systems for public and cultural organisations.
The unglamorous layer that decides whether everything else works: hosting architecture, deployments, monitoring, integrations, media pipelines and the day-to-day operations behind live platforms.
Four directions from recent years — public information, culture and heritage, rural territories and a product of my own. Detailed case studies are available on request.
A digital intelligence platform for discovering, monitoring and organising public-sector information — so researchers can follow what institutions actually do, not only what they announce. An evolving product, shaped alongside the people who will use it.
Case study in preparationData accessibility, visualisation and digital tools supporting culture, regional development and place-based initiatives — including cultural routes connecting Greece's ancient theatres and the places around them.
Digital platforms supporting rural territories, tourism, regional identity and development initiatives — giving places that rarely make the map a way to present themselves on their own terms.
A personal software product exploring productivity, knowledge management and tasks — notes, clients and projects in one place, with AI-connected workflows that can read and act on it.
A ministry, a heritage foundation, a startup and a mountain village don't look alike. Underneath, they ask the same things: what do we actually need, what will it cost to run, and who keeps it alive after launch.
I started in web development, building sites by hand. The tools have changed more times than I can count. The problem hasn't.
Someone has a need they can't quite describe, a process held together by spreadsheets and goodwill, or an idea that has to survive contact with reality. I listen, map the mess, and then build the thing — or tell you honestly that you don't need to.
Over the years the work widened: from websites to platforms, from platforms to products, from products to the strategy around them. Lately it's automation, open data and AI. Through all of it I've kept writing code — it's the part that keeps the advice honest. Today I do this independently and as founder and managing partner of UNICORG.
Good. Those are usually the interesting projects.
Let's talk.
