2
1 Comment

Building Trajectories CRM

Hey everyone đź‘‹

I’m Somesh, founder of DigitioHub. After working on 60+ client projects and building multiple CRMs across industries, I noticed a common problem in the travel sector — everything is still manual and scattered.

Travel agencies struggle with:

  • Managing inquiries from multiple sources

  • Creating itineraries manually

  • Following up with leads consistently

  • Tracking bookings and payments

So, I decided to build Trajectories CRM — an AI-powered travel CRM designed to simplify and automate the entire workflow.

🔹 What we’re building:

  • Smart inquiry management

  • Auto itinerary generation

  • WhatsApp & email follow-ups

  • Booking & payment tracking

  • Centralized dashboard for travel businesses

We’re currently in the early stage and looking to:

  • Validate features with real travel agencies

  • Improve automation using AI

  • Build a scalable SaaS product

đź’ˇ Would love feedback from the community:

  • What features would you expect in a travel CRM?

  • Any tools you’ve used that worked well?

If anyone here is in the travel space or interested in collaboration, let’s connect

posted toAvatar for product Trajectories CRM
Trajectories CRM
  1. 1

    This is a solid problem to go after especially with how fragmented travel workflows usually are.

    One thing that stood out to me is that the features make a lot of sense, but it’s still a bit hard to picture what the first experience actually looks like for a travel agent using this day-to-day.

    With tools like this, the challenge is often less about capability and more about how quickly someone can go from “messy manual process” to a clear, guided workflow.

    I’ve seen this come up quite a bit with early-stage products when there are multiple entry points (inquiries, itineraries, follow-ups), users can hesitate simply because they’re not sure where to begin.

    Making that first “day 1” flow very obvious usually has a big impact on adoption.

    How are you thinking about guiding users through that initial workflow when they first start using Trajectories?