Case studies
A Lausanne agency site heavy with motion, built fast in Webflow
A dark-theme VC site the Berlin team updates on its own
A scenography portfolio as spatial as the stage work itself
A modular editorial platform built for high-volume brand content
102 construction projects migrated into one mobile-first site
A WordPress to Webflow migration that kept every local ranking
Selected work
What these projects have in common
Different industries, different budgets, one working method: understand the business first, design for the decision the visitor has to make, then build it so the team can run it without me.
One person, start to finish
Every project on this page was strategised, designed, built and optimised by the same person. Nothing was lost in a handoff, because there was no handoff.
Handed over, not held hostage
Each client owns their project and can edit it without calling me. That is a design constraint from day one, not a favour at the end.
How to read these case studies
Every project above follows the same four-part structure: the context the business was operating in, the challenge that made a new site necessary, the solution I built, and the outcome it produced. That structure exists because a portfolio of pretty screenshots proves nothing. What matters is whether the site changed something measurable for the company running it.
The work spans hospitality, industry, professional services and startups, in Valais, across Suisse romande and beyond. Some were full builds from positioning through launch. Others were rescues, a site that looked fine and converted nothing, or a Webflow project that had outgrown the way it was originally set up.
Why the mix of Webflow and custom builds
You will see both on this page, and that is deliberate. Webflow is the right answer when a marketing team needs to publish without a deploy and the logic is content-driven. A custom Astro or Next front end with a headless CMS is the right answer when there is heavy data, product logic, or a performance budget a visual builder cannot hold. The decision gets made in the first week, on the merits, and I say which one before anyone pays for it.
What is not on this page
Client work under NDA, projects where the brief changed so often that the result stopped representing anyone's best thinking, and sites that have since been redesigned by someone else. A portfolio that shows everything is a catalogue. This one is a selection, and the omissions are as considered as the inclusions.
They trusted me (Still do)
FAQ
Straight answers about the work on this page.
Can you show me work in my industry?
Probably, and it matters less than you would think. The projects here span hospitality, industry, professional services and startups, and what transfers between them is the method, not the sector. If your industry is genuinely unusual, that is a reason to talk it through on a call rather than a reason to look for a specialist agency, most of what makes a site work is the same everywhere.
How long did these projects take?
Between two and eight weeks, scope depending. A focused one-pager lands at the short end. A multilingual CMS build or a custom front end with API integrations sits at the long end. Where a project included a strategy sprint first, add one to two weeks before design started. Each case study states its own timeline.
Are these built in Webflow or custom code?
Both, and each case study says which. Webflow wins when your team needs to publish without a deploy and the logic is content-driven. Custom (Astro or Next with a headless CMS) wins on heavy data, product logic, an app on the same domain, or a performance budget Webflow cannot hold. I recommend one before you pay, not after.
Do the clients maintain these sites themselves?
Yes, that is the point. Every build ships with a CMS the client can actually operate, a documented structure, and a handover session. On Webflow the project sits in your workspace with me as a collaborator you can remove. On custom builds the repository is yours from the first commit and deploys run in your own hosting account.
Do you only work with companies in Valais?
No, though Valais is home. I am based in St-Luc in the Val d'Anniviers and work with businesses across Valais and the wider Suisse romande, as well as teams in Geneva, Zurich and outside Switzerland entirely. Remote or on-site, the work is the same, and most of it happens in a shared document and a weekly call either way.
What happened to these sites after launch?
Launch is the start of the useful data, not the end of the project. Where a case study quotes a number, it comes from the client's own analytics or Search Console after launch, not from a projection made during the pitch. Several of these clients are still working with me on SEO, content and iteration, which is where most of the compounding actually happens.