Paseo Güemes HotelPaseo Güemes Hotel

Paseo Güemes Hotel is a 3-star hotel in the heart of Salta City, in the bar district and steps away from the historic center. It opened in February 2026, so I joined a brand new business still defining its audience across domestic tourism, international travelers, and a corporate segment.

Digitally, the starting point was minimal: domain, hosting, and WordPress installed, and the booking engine already running, but no site built. Without its own website, the hotel depended on OTAs and their commissions, lost direct bookings, and received scattered inquiries in messages that got lost without context. The constraints shaped the path: a tight budget, a site the hotel itself could maintain, inherited hosting and domain, content arriving in pieces, and a booking engine I had no direct access to, since the manager administers it.

I did not go straight to building pages. I started with a brief for the owner (business, goals, competitors, and audience), ran an analysis of the Salta hotel market with a positioning map and a definition of the ideal guest, and only then built desktop and mobile wireframes in Figma.

1. 01

   Direct booking first, OTAs in the background

   The whole site pushes toward the hotel own booking engine, with OTAs left as a discovery window rather than the main channel. The business goal was to cut commissions and stop losing direct bookings, so the messaging and the CTAs were organized around that.

2. 02

   A stack the client can edit, not custom development

   With a tight budget and the need for the hotel to maintain the site without depending on me, an editable stack beat a hand-built development. I picked a lightweight theme with a header and footer builder included, to protect mobile performance without adding licenses.

3. 03

   Hero hierarchy and CTAs spread across the journey

   A hero with video of the Güemes Monument, because location is the hotel number one asset, and a single strong booking CTA. Secondary calls to action were spread across sections so the booking button would not lose its impact by repeating in every block. For inquiries I added a floating WhatsApp button instead of relying on Instagram messages: it arrives with context and does not get lost.

• →Mobile-first site with Home, Rooms, Benefits, Location, and Contact
• →Identity applied end to end: palette extracted from the logo, type system, and logo versions for light and dark backgrounds
• →Direct booking integrated, WhatsApp and forms, plus local SEO foundations, automated backups, and optimized performance

The site is about to go live, so there are no hard metrics yet and I would rather not invent them. What is observable is already clear: the hotel moves from depending on OTAs to having its own direct booking channel, gains a digital presence that did not exist before, and inquiries now arrive through WhatsApp with context instead of getting lost. Building with content that arrived in pieces forced me to work in blocks and leave temporary placeholders instead of stalling. I also learned to choose the robust flow over the flashy one: not forcing the booking engine inside the hero and solving it with a direct button instead. If I did it again, I would lock down the real photos earlier, since they are the asset that converts most, and request the booking engine credentials from day one.