Practice 01 · Experience Design & Interactive Worlds
Considered websites and interfaces, connected to the systems behind them.
Interactive showcase
Browse a fictional venue, reserve a seat at one of its events and see the same reservation from the team's side. It all runs in your browser; nothing is booked.
The Atrium
Concept demo · Fictional venueThe Atrium · Concept demo
A place for art, people and new perspectives.
The Atrium is a fictional venue. Events, dates and guests are sample data; nothing is booked, paid or sent.
Capabilities
Editorial websites and logged-in portals, set so the first impression online matches the one at the door.
Type, pace, light and motion are set so the site feels like the place it belongs to.
A CMS scoped to what the team actually changes, so a new event or menu goes live without a ticket.
A logged-in area where customers check status and act on it, in the same design language as the public site.
Reservation, enquiry and contact flows that confirm by email and land in one list your team already checks.
Requests that arrive by email, phone and social channels stop being retyped. One flow confirms by email and lands in one list.
The essentials and the booking action stay one tap away on a phone.
Every request reaches the CRM or operational tool behind it, where workflows and dashboards pick it up.
Tokens and components, documented for the next team and shared by the public site, portals and dashboards.
New pages are assembled from documented components instead of being redesigned each time.
Animation explains the page instead of delaying it, and respects the visitor's reduced-motion setting.
Keyboard access, readable contrast and responsive images in modern formats from the first build.
Browse, reserve, confirm
One journey, designed around the visitor and the team behind the desk.
01 · Browse
A clear, calm view of what is on, with the details people need before they decide.
02 · Reserve
Date, time and guests in one accessible step, limited to dates the event actually runs.
03 · Confirm
The visitor sees a clear confirmation, and the same record appears in the operator view.
Illustration with sample data. Nothing is booked.
Ownership
You own the repository, the domain, the CMS and the analytics. We hand over the access and the runbook. Ongoing support is a separate, scoped retainer, and only if you want one.
A typed codebase built for phones first and checked at tablet and desktop widths.
CMS access for events, menus and pages, where the scope includes it.
Design tokens and components shared by the site and anything built on it later.
A handover covering the components, the content model, analytics and deployment.
Aperitivo and afterwork bar
An editorial website, a reservation flow, events the team edits itself and email automation behind every request. A real client project, separate from the concept venue in the demo.
Places where the first impression is part of what people pay for: bars, restaurants, hotels, shops and service businesses with a physical room. If guests praise the room and you wince at the website, start here.
Yes, where the scope includes it. We set up a CMS around what your team actually changes, such as events, menus and pages, and hand over a short guide. Incontro Bar's team publishes events and gallery updates this way.
It depends on the scope, and we put the timeline in writing after the first call. You see a working version early in the build and review it as it develops. If the idea needs testing first, a two-week Discovery Sprint comes before the build.
A single-surface website typically costs CHF 8,000 to 12,000. A site with booking, CRM and automation behind it costs CHF 12,000 to 18,000. The total is fixed in the proposal and paid in milestones. A Discovery Sprint has a fixed price of CHF 3,500.
No. The Atrium is a fictional venue we use to show a reservation journey on sample data, and nothing in the demo books anything. Our client work, such as Incontro Bar, is listed under Work.
Send a link to what you have today, or describe what is missing. We read every brief ourselves and reply with questions about how the work runs now.
Discuss your experience