Update Studio

## Summary The core GetYourGuide integration is functionally working — bookings can flow between GetYourGuide and Understory. The team has made strong progress, going from kickoff on March 3 to working main flows in roughly three weeks. We are now fixing remaining edge cases before submitting the integration to GetYourGuide for their formal review and approval. ## What's done - The main booking flow works end-to-end: availability lookups, reservations, bookings, and cancellations. - Infrastructure and backend services are deployed. - Scope has been managed well — add-ons and open bookings are descoped from v1 to keep focus. ## What's left - Fixing remaining edge cases (e.g. ticket generation for GYG bookings). - Submitting the integration to GetYourGuide for their external review and certification. - Building the self-service setup flow in the backoffice so hosts can connect to GYG on their own. Currently using a temporary test interface. ## Why "At Risk" The **March 31 target date will likely be missed.** The main reason is that GetYourGuide requires an external review of our integration before it can go live, which typically takes around two weeks. We haven't submitted yet, so even with a submission this week, the earliest realistic go-live is mid-April. The team flagged this timeline risk already on March 17. ## What's going well - Fast execution by the team (Hans Emil, Lasse Legaard, Bjørn, with design support from Sari). - Strong commercial pull — at least two high-volume customers including Lalandia are ready to use the integration from launch, and several more have requested it. - Good collaboration with GetYourGuide's integration team to navigate their requirements.

Plan is to kick off the GetYourGuide project in March, following the Planday project which has been started now. The GYG integration is currently in the 'blocked' state due to the [Booking Reservations](https://linear.app/understory-io/project/booking-reservations-75d12c92427d) project, which is a requirement from GYG to be able to build the integration. The idea is that both of those projects can be built somewhat simultaneously, and the blocker doesn't change the starting-date, neither the expected timeline. I've also set the target date of the integration to April, where the idea is to be ready for testing mid-/end-April.