naksha

Hotels & Resorts · 6 min

Where hotels quietly lose revenue — the five leaks

The five places money slips away between a guest's first enquiry and a confirmed booking — shown with example figures, not a claim about any one property.

By Thrinath Saragada, founder of Naksha AgencyPublished Updated
Resort entrance at dusk

Every figure below is an illustrative example to show how the leak works — your real numbers come from a diagnosis of your own property.

Most hotels and resorts don't lose bookings on the website. They lose them in the quiet gaps a guest never sees: an enquiry that lands in the wrong place, a follow-up that never goes out, a repeat guest nobody remembers. The same five leaks show up again and again — not because owners are careless, but because nothing in the setup is designed to catch them. Here is each one, how it drains money, and the system that plugs it.

  1. 01

    Enquiries land in a personal inbox

    The first message from a prospective guest usually arrives on one staff member's personal WhatsApp or a shared phone. When that person is off shift, asleep, or simply busy, the enquiry effectively doesn't exist — and the guest books whoever replied first. Nothing is logged, so no one even knows it happened.

  2. 02

    The second follow-up never happens

    Most bookings close on the second or third touch, not the first. Without a system that schedules follow-ups, the second message depends on someone remembering — and in a busy property, nobody does. The enquiries that go cold are invisible, so the leak is never measured.

  3. 03

    OTA commission eats direct demand

    Guests who would happily have booked direct get pushed to an OTA because the direct path is slower or harder to find. Every one of those bookings pays a commission a direct booking wouldn't — a tax on demand you already created and paid to attract.

  4. 04

    Nobody owns the guest database

    Repeat guests are the cheapest revenue in hospitality — no ad spend, no OTA cut. But if guest details live inside booking confirmations and someone's phone, there's no list to bring them back with. The most profitable guests end up the ones you forget.

  5. 05

    The owner sees the month after it's over

    By the time the numbers are totted up, the leaking month is already gone. Without a live view of enquiries in, conversions out and follow-ups pending, problems are only ever visible in hindsight — too late to act on.

A worked example

Here is the arithmetic on just the first two leaks, using example numbers. Plug in your own and the picture is usually worse, not better:

Enquiries in a month (example)
200
Reaching an owned, followed-up pipeline today
~60%
Enquiries quietly lost
~80 / month
If 1 in 10 of those would have booked
8 bookings
At an example average booking value of ₹12,000
₹96,000 / month

That is roughly ₹11–12 lakh a year leaking from one gap — before OTA commission or lost repeat guests. The exact figure is yours to measure; the point is that it is almost never small.

The fix — a checklist

  • Route every enquiry — WhatsApp, Instagram, calls, forms — into one inbox with an owner.
  • Automate a second and third follow-up so it never depends on memory.
  • Make direct booking on your own domain at least as easy as the OTA path.
  • Capture every guest into a database you control, and set a recall rhythm.
  • Put enquiries-in, conversions-out and pending follow-ups on one screen the owner sees daily.

None of this is a design problem. It is a systems problem — one inbox, one owner per enquiry, automated follow-up, direct booking on your own domain, and a guest database that outlives your staff. That is the system we build, and the leaks above are exactly what it is built to close.

Where we fix this

This is the gap Naksha builds systems to close in hospitality. The specific builds: