About Yatrika

India’s tour operators run a ₹26 billion industry on WhatsApp groups.

We’re building the operational layer they deserve. Every booking tracked. Every driver visible. Every rupee accounted for.

Why We Built This

Nobody had solved operations.

OTAs like MakeMyTrip solved discovery. Payment apps solved collection. But the actual running of a trip — the bookings, the driver, the route, the expenses, the margin — that still happens on WhatsApp groups, Excel sheets, and phone calls. For operators running ₹50 lakh seasons, this is a structural problem.

Tour Command Center is not a booking platform. It is the operational layer underneath. The system that tells an operator where their vehicle is right now, whether the fuel bill makes sense, and whether this trip actually made money — before the driver even returns.

We started by talking to operators in Ladakh, Manali, Bir Billing, and Harshil Valley. We read their PDF itineraries, their WhatsApp cancellation policies, their handwritten expense sheets. What we built is a direct response to what they showed us.

₹26B+ India’s tour and travel market in 2025
303 Cr domestic tourist visits annually
88% of tourism spending is domestic
The Problem

Five pain points. No existing solution.

01

Booking chaos

WhatsApp threads, no single record

02

Zero visibility

Operator blind once vehicle leaves

03

Route integrity

No way to verify driver took right route

04

Expense leakage

Fuel claims on paper, no cross-check

05

Margin mystery

No operator knows net profit per trip

“From the moment a traveler confirms their booking to the moment a trip ends and accounts are settled — the operator has complete visibility. Every stop, every expense, every rupee.”

— Tour Command Center product brief, 2025
Our Approach

Built on operator research. Not assumptions.

Research first

We talked to operators before writing a line of code.

4 real operator itinerary PDFs analyzed. Operators in Ladakh, Harshil Valley, Bir Billing, and Manali-Kasol interviewed. Their cancellation policies, payment flows, and WhatsApp habits became our product spec.

India-specific constraints

Built for BSNL 2G and ₹6,000 Android phones.

The Driver PWA is 30KB — not 3MB. It works offline. It loads in 3 seconds on 2G. Indian hill station connectivity is a design input, not an afterthought.

Honest about the problem

We don’t oversell. We solve specific problems.

Tour Command Center is not an OTA. It does not compete with MakeMyTrip. It is the operational layer underneath — for operators who already have customers and need to serve them better.

The Team

Built by a small team obsessed with the problem.

We are not a large company. We are a focused team that spent months talking to tour operators before building anything. The best products come from deep understanding of one specific problem.

RS
Romil Sarna FOUNDER, TOUR COMMAND CENTER

Building the operational infrastructure for India’s tour operators. Previously worked across product and technology. Based in Jaipur.

Our Commitment

Built in India. For India.

UPI-native from day one

Every payment flow is built around how Indian operators and travelers actually transact — UPI, bank transfer, cash. Razorpay for payment links.

WhatsApp is infrastructure

We don’t compete with WhatsApp. We use it. Booking confirmations, traveler stop pings, operator alerts — all through Meta Cloud API.

Offline-first for the field

The Driver PWA works in Spiti Valley on BSNL 2G. It queues actions offline and syncs when network returns. India’s geography is a design input.

Get In Touch

We’d love to hear from you.

Whether you’re an operator ready to try the platform, an investor, or someone who wants to work with us — reach out directly.

WhatsApp Chat with us directly
Email hello@yatrika.co.in
Twitter / X @yatrika_in
Ready to streamline?

Your next trip should run itself.

Join operators who've stopped losing money on every trip.

No credit card · Cancel anytime · Data export always available