Hi, I'm Deep.I'm building the travel planner I wanted to use.
I'm a software developer who loves the idea of a great trip, but never loved the work of putting one together. Flytinerary is what I started building to change that.
Every trip began the same way. I'd save a few places, compare flights, open maps, check hotel prices and try to work out how to fit everything into the days I had.
The problem wasn't finding somewhere interesting. It was knowing which places belonged in the same journey — and whether the travel time, hotel changes and cost actually made sense.
That's the question behind Flytinerary: what's the best journey I can actually take with the time and budget I have?
What guides the product
A few things I keep coming back to.
01
The route comes first
A beautiful list of cities means little if you spend half the holiday changing hotels or waiting for connections.
02
Real constraints matter
Your departure city, dates, budget and travel style should guide the plan — not get added after it is made.
03
Ship, listen, improve
I keep working on the details: clearer routes, better suggestions, fewer bugs and a simpler experience on mobile.
Where I'm focused now
Making the next version more useful than the last.
Flytinerary is an independent product, and it's still evolving. I'm working on the route decisions, the itinerary details and the small usability problems that become obvious when somebody tries to plan a real holiday.
Compare route options before committing to a destination
Build day-by-day itineraries around your time and budget
Make road trips and nearby experiences easier to plan
No perfect launch story. Just building, fixing, learning, and making the next trip easier to plan.
