Arrival information must be easy for guests to find without exposing it too early.
Guests need reliable access close to check-in, while hosts need property instructions kept within the booked stay.
Who you’d be doing this for
“I was outside with my luggage, scrolling through messages trying to find the door code.”
Datu Do · Guest
A traveler arriving at a booked stay after receiving host instructions across multiple messages.
What is at stake
Guests are asking hosts for entry instructions after booking because the details are hard to retrieve at arrival. You must weigh quick access for booked guests against keeping property information appropriately contained.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- fast arrival access vs. property information protection
- shared GraphQL contract vs. native flexibility
- first-version speed vs. reusable service design
- host detail richness vs. guest scanability
Why AirBnB
Booked stays depend on guests reaching the property smoothly, and the native apps are where guests return when arrival questions become urgent.
Written with these in mind
Not your kind of problem? 45 more at AirBnB, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.