CASE STUDY · TIRAVA
Tirava started without a previous website or digital booking system. The first launch therefore treated the offer, multiple languages and inquiry path as one product from the start.
The task in one sentence.
A greenfield launch that defined the offer, booking logic and inquiry path together for the first time as one multilingual digital product.
What can be shown with confidence.
No projection and no invented uplift: these three changes can be inspected directly in the delivered system.
0 → 1
Tirava started without a previous website or existing booking system.
CENTRAL
The guided intake was part of version one and did not need to replace a legacy system.
MULTILINGUAL
The offer and next steps were structured for guests with different languages from the first launch.
Before launch there was no Tirava website, digital booking system or established digital inquiry path.
This was not a redesign or migration. The digital offer, booking sequence and required information had to be defined together for the first time.
The offer and booking logic were first translated into clear decisions, required information and an understandable sequence.
That became a multilingual platform connecting the offer, route and booking for the first launch. The central inquiry intake was part of version one.
The launch created Tirava's first dedicated digital booking path. It asks for the required information in a repeatable order and brings new inquiries into one shared structure.
The published effect is deliberately operational. Revenue, conversion and time-saving figures will only be added when approved measurement data is available.
I assess the current inquiry path and identify the smallest intervention that creates order and measurable data first.