Travel Portal for Indian Tourists — Niche Research Note

Who does it:

• Retail travel agents in Tier 2/3 cities (Indore, Jaipur, Lucknow, Kochi, Guwahati) run the bulk of Indian tour package business. These are often sole proprietors or firms with 2–10 staff.
• Unorganized freelancers — ex-hotel staff, retired airline employees, school teachers' spouses — sell tours via WhatsApp groups, running the operation from a personal phone.
• Destination management companies (DMCs) in tourist hotspots (Jaipur, Kerala, Goa, Rishikesh, Leh) handle ground logistics for incoming groups. They receive confirmed bookings from agents upstream and execute manually.

What they use:

• WhatsApp for customer queries, supplier coordination, and payment screenshots. A single family trip to Kerala generates 40–80 WhatsApp messages across 3–4 group chats.
• Google Sheets or Excel for itinerary building, costing, and payment tracking. Agents rebuild itineraries from scratch for every enquiry, even for repeat destinations.
• Phone calls for hotel confirmation, especially in non-standard properties (heritage hotels, Ayurveda centers, adventure camps) that don't appear on OTA extranets.
• Walk-in brokers at railway stations and bus stands in tourist towns who source customers for agents for a ₹100–300 referral cut.
• Physical folders — some agents still print confirmations and keep hard-copy client files.

Where time and money leak:

• Rebuilding itineraries from scratch every enquiry: 45–90 minutes per custom quote. Most enquiries never convert, so this is pure sunk cost.
• Payment reconciliation: customers pay via UPI to personal accounts, agents pay suppliers via separate UPI or bank transfers. Matching who paid what for which trip is manual and error-prone.
• Supplier confirmation calls: a Goa agent calling Taj Holiday Village to check room availability spends 20 minutes on hold and callbacks. Failed confirmations mean re-quoting customers.
• Commission leakage to aggregators: agents who can't access direct hotel rates book through consolidators (like Travstarz, DOTW) and lose 10–18% of margin.
• No CRM: when a customer returns 18 months later for a Bhutan trip, the agent has no history and starts from zero. 30–40% of repeat business is lost because there's no recall system.

---

Who profits from it staying manual:

• Large OTAs (MakeMyTrip, Yatra, ixigo) — their business model depends on direct-to-consumer bookings. A network of smart agents that handles complex Indian itineraries (multi-city, heritage properties, adventure, pilgrimage combos) is a threat. They have no incentive to build agent tooling at accessible prices.
• Consolidators and brokers — companies that sell agents access to hotel inventory at marked-up rates profit from agents lacking direct supplier relationships. They prefer agents dependent, not empowered.
• Individual agent's own inertia — a veteran agent in Jaipur with 20 years of relationships doesn't feel acute pain from manual processes. The pain is gradual and absorbed as "just how it is."

Who is hurt:

• The agents themselves — they work 12-hour days, are invisible to customers who think "the OTA is the brand," and have no asset (no data, no client relationship in software). Their margin on a ₹50,000 family package is ₹3,000–7,500 (6–15%) and much of that is consumed by rework and coordination time.
• Customers — they get inconsistent itineraries, delayed confirmations, and no recourse when something goes wrong because the agent is personally managing everything and has no systematized operations.
• Small hotels and DMCs in non-metro destinations — they can't reach end customers directly and are completely dependent on agent networks they can't see or influence.

Who would pay to change it:

• Young, second-generation travel agents (inheriting a parent's agency) who see the manual overhead and want to grow beyond personal bandwidth. These are in the 28–40 age bracket, active on WhatsApp Business and Instagram.
• Small boutique DMCs who want white-label booking portals for their own supplier network rather than using WhatsApp and phone.
• A handful of NRIs booking for extended family in India — willing to pay for a service that coordinates Indian ground logistics without requiring their parents to manage WhatsApp chaos.

Pricing SHAPE:

• Per seat — not viable. Agents don't have fixed seats; they have per-trip revenue.
• Per order — the right anchor. Charge per itinerary generated or per booking confirmed. This aligns cost with value for the agent who is paying out of their margin.
• Per outcome — commission share on the booking. A risk-sharing model where the tool/platform takes 3–5% of the transaction. Works only after trust is established.

---

The narrow thing to start with:

Itinerary Builder as a managed service (Agencify first, productify later).

Day one, one agent and one virtual assistant (VA) handle itinerary construction for real travel agents on a per-quote fee.

What it does on day one:

• Agent sends a WhatsApp voice note or text: "Family of 4, Mumbai, 6 days, Rishikesh + Haridwar, budget ₹80,000, kids are 10 and 14."
• The service (VA + AI assist) builds a day-by-day itinerary with hotel options, transport, activities, and indicative pricing, delivered back on WhatsApp within 4 hours.
• The agent reviews, edits, sends to customer, and owns the relationship.
• The service charges ₹300–500 per itinerary build, refundable if the booking converts.

Who pays and how much:

• The travel agent pays — not the end customer. The agent's cost per non-converting quote today is ~2–3 hours of their own time valued at ₹200–400/hour. A ₹400 outsourced quote is cheaper than doing it themselves AND frees them to handle 3× more enquiries.
• Secondary: charge DMCs ₹1,000–2,000/month for a white-label itinerary portal where their hotel/car/activity inventory can be browsed and quoted by agents. This is a direct revenue line with zero customer acquisition cost at launch (the agents already call DMCs daily).

What this is NOT:

• Not a website with flight + hotel search (ixigo and MakeMyTrip own this).
• Not a B2C booking portal (capital-intensive, requires large supplier relationships).
• Not a general "AI travel agent" — the Indian package tour market is too complex for pure AI to handle (heritage properties with no API, pilgrimage circuits with specific rules, region-specific transport quirks like Shikara booking in Srinagar vs houseboat booking in Alappuzha).

---

B2C booking portals (not the wedge):

• MakeMyTrip — dominant in flights + hotels + packages. B2C focus, high customer acquisition spend, not agent-friendly. Has a "partner portal" for agents but adoption is limited outside metro agents.
• ixigo (Le Travenues Technology) — listed, strong in trains + buses + flights. B2C. Agent tooling is minimal.
• Yatra Online — listed, similar positioning to MakeMyTrip.
• Cleartrip — acquired by Flipkart, largely dormant on new development.
• Goibibo — owned by MakeMyTrip group (ixigo now merged entity). Dominant on budget flights.

Agent tooling (closer to the wedge):

• Tripbeam (unverified — appears to be a small SaaS targeting travel agents in India, not well-known)
• TravelDox (unverified — appears to be an older product, unclear if still active)
• Viator (owned by TripAdvisor) — DMC and agent tool for experiences, but primarily international-focused, high commission rates (25–30%), not tailored to Indian domestic tour patterns.
• Hubspot / Zoho CRM — some agents cobble together generic CRM for client tracking, but no travel-specific template dominates.

The gap: No dedicated, affordable, WhatsApp-native itinerary builder exists specifically for Indian retail travel agents. The agent either uses Excel or pays a web developer ₹15,000/month for a custom portal they'll barely use.

---

Fact 1: Indian travel agents won't pay for tooling.

Check it: Spend ₹0 and 2 weeks doing the following — call or WhatsApp 20 travel agents in 3 cities (Jaipur, Lucknow, Kochi) from a warm intro if possible (use any existing network). Ask them: "If I could build you a day-wise itinerary for any Indian destination in 4 hours for ₹400, would you use it?" Track yes/no ratio. If fewer than 4 out of 20 say yes with intent to pay (not "sure, send me details"), the wedge fails. Budget: ₹0–2,000 in phone call costs. Pass mark: ≥3 confirmed paying customers from 20 calls.

Fact 2: The per-quote fee model can't scale because supplier confirmations are the real bottleneck, not itinerary building.

Check it: After getting 3–5 paying agents, observe the full workflow for 30 days. Does the agent's bottleneck shift from "I can't build the itinerary fast enough" to "I can't get hotel confirmations"? If the limiting factor is supplier confirmation (phone calls, WhatsApp follow-ups), then the itinerary builder solves the wrong problem. The real product is a supplier coordination tool, not an itinerary builder. Budget: one month of the service operation (₹15,000–25,000 including VA time). Pass mark: agents request the service multiple times per week without prompting, and the next requested feature is "can you also call the hotel to confirm?"

Fact 3: A single DMC or hotel chain can replicate this by publishing their own WhatsApp-accessible catalogue.

Check it: Identify whether a large DMC (e.g., Kerala Tourism Development Corporation-affiliated operators, or a Rajasthan heritage hotel chain) could undercut the service by offering their own WhatsApp-based booking catalog for ₹0 to agents. If a well-resourced DMC with 5 staff can replicate the service at zero cost using Zoho Analytics + WhatsApp Business API, there's no defensible wedge. Budget: 2 days of competitive research (₹0). Pass mark: finding 3+ DMCs already offering agent-facing WhatsApp catalogs with real booking capability.

---

Budget: ₹25,000

Month 1 — Validation (₹5,000)

• Call/WhatsApp 30 travel agents across 4 cities (Jaipur, Indore, Kochi, Guwahati). Use personal network if available; otherwise cold WhatsApp outreach with a brief voice note intro.
• Goal: identify 5 agents willing to pay ₹400 per custom itinerary. These are not "interested" — they must agree to WhatsApp payment via UPI before the first itinerary is built.
• Deliver 5 real itineraries. Document: how long each took, what follow-up the agent needed, whether the booking converted.

Month 2 — Operation (₹12,000)

• Hire one part-time VA (₹8,000–10,000/month via Internshaala, Naukri part-time, or UrbanCompany for Biz outreach) trained on Indian domestic itinerary patterns.
• Run the service at ₹400/itinerary. Target 20 paid itineraries.
• Track: conversion rate from quote to booking, agent retention (do they come back?), and the next feature they ask for.

Month 3 — Decision Point (₹8,000)

• Review Month 2 data. Key questions: (a) Are agents repeating? (b) Is the bottleneck shifting from itinerary-building to supplier-confirmation? (c) Can a second VA be added profitably?
• If yes to (a): build a simple WhatsApp Business catalog of 3–5 trusted DMCs and test the white-label portal concept at ₹1,000/month.
• If no to (a): run the falsification checks from Section 5 before declaring the idea killed.

Pass mark for the 90-day test:

• ≥8 paying repeat customers (ordered 2+ itineraries)
• ≥30 total paid itineraries delivered
• VA cost ≤₹500 per itinerary at current volume
• At least 2 customers mention they would pay ₹800–1,000/itinerary if the turnaround was 2 hours instead of 4

---

AGENCIFY — then decide.

The Indian retail travel agent is buried in manual coordination work, lacks affordable tooling, and genuinely wastes 2–3 hours per custom quote. A per-quote itinerary service run by a VA + AI assist is the lowest-risk way to prove demand: it costs almost nothing to start, requires no supplier relationships, and validates willingness-to-pay before any software is built. Productizing (building software) should happen only after 20+ paying agents are asking for a self-serve tool. AI-fying (a fully autonomous agent) is premature — the Indian package tour domain has too many edge cases (heritage hotel booking quirks, region-specific transport rules, pilgrimage circuit constraints) that require human judgment and supplier relationships that don't exist in structured data. Build the agency first, watch where the friction migrates, and that becomes the product.

Availability confirmed against the .in registry (RDAP) on 2026-09-24. Prices and ownership read from our own intelligence tables. Nothing here is estimated.

Single-word, available now

• kenyas.in — available
• kenyas.co.in — available

Also available (compound)

• kenyahub.in
• kenyamart.in
• kenyakart.in
• kenyamandi.in
• kenyabazaar.in
• kenyadirect.in
• kenyasupply.in
• kenyaconnect.in

Listed for sale

• mytravel.in · price not listed on afternic · seller holds 55 domains

In the expiry pipeline — watch

• kenya.co.in · pending_delete · score 90

Taken and developed — do not chase

• kenya.co.in · entropy 4.67
• travelbazaar.in · entropy 6.76
• travelsupply.in · entropy 6.06
• mytravel.in · entropy 4.59
• gettravel.in · entropy 5.29
• gotravels.in · entropy 5.67

---

Generated 2026-09-24 10:37 UTC. Topic from our research queue; no market-size figure appears here unless a source is named. The domain block above is read from our own intelligence tables and confirmed at the .in registry (RDAP); the model wrote the analysis, not the domain facts.