The Hotel That Couldn't Be Found Online : Hotel Pauwa had earned its reputation the hard way. Positioned near Pashupatinath in Kathmandu and the lakeside in Pokhara, the hotels had real guests, real reviews, and a physical presence that spoke for itself. The digital version had made a start — individual branch pages existed, and the site gave visitors a sense of each location. But when a Nepali traveler from Butwal wanted to actually book a room, the journey hit a wall: a basic inquiry form, a phone number, and then waiting. For a family planning a pilgrimage visit or a couple booking ahead for a Pokhara trip, that gap between interest and confirmation was where the decision died. The hotel had built enough of a digital presence to be found — just not enough to convert anyone who found it.
Two Cities. One Broken Journey : The harder problem wasn't that the website looked outdated — it was that there was no real booking system at all. A guest interested in the Pokhara property had no way to check room availability or confirm a reservation without calling directly. A family managing a visit across both properties had no way to handle that from a single place. The entire process depended on someone at the hotel picking up fast enough, and responding correctly enough, for the guest to stay interested. That dependency was costing real bookings. The design had to close that gap structurally — a multi-property booking flow, room-level selection, OTP-based login, and a payment flow that kept the guest on the platform rather than routing them somewhere else mid-journey.
Built for the Guest Who Won't Call
The solution had to work for a Nepali traveler comparing options on their phone while deciding where to stay. Every step of the booking flow was mapped against one question: does this give the guest a reason to continue, or a reason to stop? Room filters reduced the decision surface at the point of selection. OTP login removed password friction without removing security — practical for users who don't manage multiple app accounts. The checkout flow was kept to the minimum steps that still captured what the hotel actually needed to confirm a reservation. A personal dashboard gave returning guests visibility into their booking history — useful for repeat travelers and families who book seasonally around festivals and pilgrimage dates.
What Changed When the Website Finally Worked
The shift wasn't cosmetic. When the booking engine went live, Hotel Pauwa stopped depending on a phone call to convert a curious visitor into a confirmed guest. A traveler could now move from landing on the site to completing a reservation without leaving it, without waiting for a callback, and without being handed off anywhere else. The experience was consistent across both properties — same flow, same trust signals, same confirmation. For a hotel whose physical hospitality had always been its strongest argument, the website finally started making that argument on its own.
