Should ixigo merge ConfirmTkt into the ixigo app, or keep running both train brands separately?

Introduction

ixigo acquired ConfirmTkt in 2021. ConfirmTkt built its brand on one promise: helping train travellers get confirmed tickets, through waitlist predictions, alternative trains and route suggestions. ixigo Trains offers similar features inside a broader app that also sells flights, buses and hotels and now runs on TARA, its AI assistant. Today ixigo runs both brands, sharing much of the backend but with separate apps, designs and audiences.

The trade-off: should ixigo merge ConfirmTkt into the ixigo app, or keep running both? Merging promises lower costs, one brand and easier cross-sell. Keeping both protects a loyal audience and occupies more space in app stores and search. I'll work through this as a structured trade-off and finish with a recommendation.

Step 1

Clarifying Questions (3 minutes)

• What's driving this question now?

• Why it matters: Cost pressure, cross-sell goals, or the AI relaunch each lead to different answers.
• Hypothetical answer: The AI-native relaunch makes maintaining two front ends expensive, and leadership wants more train users to discover flights, buses and hotels.
• Impact: Both cost and cross-sell matter.

• How different are the user bases?

• Why it matters: If they overlap heavily, merging is easier.
• Hypothetical answer: ConfirmTkt users skew toward smaller cities, sleeper class and Hindi; ixigo users are more mixed. Overlap is moderate.
• Impact: Migration risk is real for ConfirmTkt's core users.

• Does "merge" mean shutting down the ConfirmTkt app?

• Why it matters: There are options in between, like keeping the brand as a mode or a lite app.
• Hypothetical answer: Open to options.
• Impact: We can consider a spectrum, not just two extremes.

• What is the time horizon?

• Why it matters: Short-term booking loss vs long-term efficiency.
• Hypothetical answer: Decide within two quarters; judge results over 12 months.
• Impact: Experiments must measure longer-term retention.