There is a Kerala itinerary in your office that has been rebuilt from scratch roughly forty times. Each rebuild starts with somebody asking in the group whether anyone has the latest version, ends with a file called Kerala_9N_final_v3_ok.xlsx, and takes between forty minutes and an afternoon depending on who is doing it.
Multiply that by every destination you sell, by every consultant who sells it, by every season. The itinerary has not changed. The knowledge has not changed. Only the file location has, and it has changed forty times.
This is not an argument that spreadsheets are bad. It is an argument about where exactly they stop, because a lot of agencies buy software before they understand that, and end up with a slower version of what they had.
What Excel and WhatsApp genuinely get right
Be honest about the incumbent. Excel needs no training, bends to any shape of business, works offline, and does arithmetic you can see and check line by line. It has never had an outage that mattered to you. A good consultant can build a workable quote in it at eleven at night from a hotel lobby, which is more than can be said for most travel platforms.
WhatsApp is even harder to beat. The customer is already there. They read it, they reply on it, they forward your itinerary to the family group where the actual decision gets made. No software will move an Indian traveller off WhatsApp, and no software should try.
So keep WhatsApp. The question is never whether to replace it — it is what the office runs on behind it, and whether a customer's enquiry survives the moment the consultant handling it goes on leave.
The quote treadmill
The real cost of rebuilding a quote is not the forty minutes. It is that the output varies by whoever built it. One version of your Kerala itinerary includes the houseboat lunch and one does not. One prices the Munnar transfer at last year's rate. One has a typo in the hotel name that a customer will find and mention. Your product is inconsistent, not because your team is careless, but because there is no canonical version of it anywhere.
A package catalogue solves this in the dullest possible way. Build the package once — destination, duration, inclusions and pricing, whether it is domestic, international, pilgrimage, honeymoon, adventure or fully custom — attach the day-by-day itinerary of activities, transfers and stays, and quote from it. Customisation then means editing a copy of something correct rather than rebuilding something from memory.
The second benefit is quieter and worth more. A catalogue forces your inclusions and exclusions to be consistent. Most disputes on a trip are not about the hotel; they are about whether the entry ticket was included, and the honest answer is usually that it depended on who wrote the quote.
The enquiries that die between seasons
Ask an agency how many enquiries they handled last month and you will get an estimate. Ask how many they converted and you will get a better estimate. Ask what happened to the rest and the room goes quiet. Most agencies can name their bookings and cannot name their enquiries.
A travel enquiry has a long and patient life. Somebody asks about Europe in July, cannot make it work, and goes the following March. Somebody prices a honeymoon eleven months before the wedding. By the time the enquiry matures, the consultant who took it has moved on and the thread is on a phone nobody has.
Capturing the enquiry as a lead — destination interest, budget and source — logging follow-ups against it, and moving it from new through quoted and follow-up to converted or lost costs about a minute per enquiry. What it buys is a list you can actually work in the lean months, when the alternative is discounting to strangers.
The source field is the one people skip and the one that pays for the whole exercise. Two seasons of it tells you which referral, which listing and which spend genuinely produces bookings, and you stop renewing the ones that do not.
Where the money and the costs drift apart
Spreadsheets are excellent at arithmetic and poor at state. A quote sheet tells you a trip should cost around ₹96,000 to run. It does not know that the hotel is confirmed while the coach was only enquired about, that one of two vendor invoices has landed, or that the customer has paid sixty per cent and the balance is due before ticketing.
So agencies keep three parallel records: bookings in one place, payments in the accountant's file, vendor costs scattered through WhatsApp history. Each is maintained by a different person and none of them agrees with the others at any given moment. Reconciliation happens when someone forces it, usually in a slow week, usually too late to change any decision.
Bring them together and the questions get boring, which is the goal. What is outstanding from customers. What is payable to vendors. Which departures are underpaid this week. Gap-free numbered GST invoices with the CGST and SGST split, discounts shown as lines, split-tender payments and a hosted pay-link on anything unpaid — all sitting where the booking lives rather than in a separate book that has to be matched to it.
The banquet hall in the same office
A large number of Indian travel agencies also run events. A hall, a lawn, a wedding season that pays for the quiet months. In most offices this is run as a completely separate business by the same people: its own diary, its own advance register, its own arguments about whether the balance was collected.
Structurally it is the same shape as a tour. An enquiry, a quote, an advance, a balance, a chain of vendors, and a date that cannot move. Running banquet, MICE and group-departure events — weddings, receptions, birthdays, corporate functions — through the same enquiry-to-paid flow and billing them on the same GST invoices as your tours means one dues board instead of two, and one answer when somebody asks what the business collected this month.
What travel software has to do before it earns its keep
The floor is higher than most products clear. Before anything else, a system has to do these things, and if it does not, it is a filing cabinet with a login.
- Quote from a stored package and its itinerary in minutes, and let a consultant customise a copy without rebuilding the whole thing.
- Hold every traveller and corporate client as one profile — phone, email, address, and a GSTIN for B2B billing — so bookings, invoices and payments all hang off it.
- Carry a real passenger manifest per booking: name as on the ID document, age, the document, and preferences.
- Move a booking honestly through enquiry, quoted, confirmed, partially paid, paid, travelling and completed, so the office can see its own position.
- Record vendor bookings against a trip with their cost and their state, so margin is not a season-end reconstruction.
- Raise gap-free GST invoices with the tax split and share a pay-link the customer can settle from their phone.
- Fire payment-due, departure and document reminders on a schedule, moving from pending to sent to done, instead of relying on someone remembering.
Notice how much of that is bookkeeping rather than cleverness. Travel software does not fail because it lacks features. It fails because it makes quoting slower than the spreadsheet it replaced, and consultants quietly go back to the file.
What you do not need in year one
The other half of the decision is what to ignore, and this is where most switches go wrong. An agency buys everything, switches on everything, uses two things, and concludes that software does not work for travel.
Do not start with dashboards you have not decided to act on. A report is only useful if somebody has already agreed what they will change when it says something uncomfortable. Do not start by connecting every system you own. Do not start by building thirty packages you sell once a year.
Start with the catalogue and the booking, because that is where the daily pain is. Add billing and payments next, because that is where the money is. Add reminders third, because that is what removes the chasing. Everything after that — the deeper reporting, the vendor payables view, the events side if you run a hall — can wait a season and will be adopted far more willingly once the first three are habit.
Moving the catalogue over, once
The migration people dread is not the migration they have to do. You are not moving ten years of history. Historic trips can stay in the spreadsheets exactly where they are; nobody is going to query a 2023 Manali quote.
What you move is the catalogue. Take the packages you actually sell — usually far fewer than you assume, often twelve to twenty — and enter each one properly once, with its real inclusions, its real exclusions and its day-by-day itinerary. That is a fortnight of evenings for one careful person, and it is the last time anyone rebuilds those itineraries.
Then enter live bookings and the customers behind them, and start every new enquiry in the new place from day one. Run both systems for a month if it makes you comfortable. The moment it becomes obviously worth it is the first time somebody asks for the Kerala itinerary and nobody has to go looking.