The trip that started it all

It wasn't a single dramatic moment. It was smaller than that — the kind of frustration that doesn't feel important until you look back and realize it changed the direction of your life.

Paras Prateek, Supriya Kumari, and Birendra Kisku met the way a lot of lifelong travel partnerships start: as classmates at IIT Kharagpur, thrown together by hostel corridors, shared deadlines, and the particular restlessness of engineering students who spend all week solving problems on paper and all weekend wanting to be anywhere but campus. Somewhere between second-year exams and the long, humid Kharagpur summers, the three of them fell into a rhythm of planning trips together — first weekend trips within West Bengal, then longer breaks that pushed further out, into the hills, down the coast, across state lines.

None of them remember exactly which trip it was. That's the honest version of this story — there wasn't one lightning-bolt moment, there was a pattern that kept repeating until it was impossible to ignore.

What planning a trip actually looked like

Here's what a "simple" long-weekend trip looked like for three college students trying to plan around exams, budgets, and everyone's wildly different idea of a good itinerary:

One person would have a Google Doc going with a rough list of places, half-filled-in and abandoned after the second day because nobody wanted to be the one updating it. Someone else would have twelve browser tabs open — a train booking site, two or three blogs about "top places to visit in [destination]," a forum thread from 2019 with comments arguing about whether a particular trek was worth it, and a maps tab with pins that didn't match anything in the document. The actual decision-making happened in a WhatsApp group, buried under normal college chatter, where someone would ask "so are we doing the fort or the lake on day 2" and get three different answers, none of which referenced the document that supposedly had the plan in it.

Budgets lived in someone's notes app. Transport options lived in another tab. And the information itself — what's actually open, what's actually worth the detour, what the weather will realistically be like — was scattered across sources that didn't agree with each other and were, more often than anyone would like to admit, just wrong. A blog post recommending a restaurant that had closed two years earlier. A "best time to visit" claim that assumed you'd never bothered to check a weather forecast. A comment thread confidently stating an entry fee that had since doubled.

None of this is a story unique to Paras, Supriya, and Birendra. It's the story of almost every group trip almost everyone has ever planned. What made it different for them is that they were engineers who spent their weekdays being trained to look at a messy, inefficient process and ask: why does it have to work this way?

The realization

Somewhere across dozens of trips — some smooth, most involving at least one moment of "wait, why didn't anyone check this before we left" — a shared realization started to form. It wasn't that travel itself was the hard part. Booking a train, finding a decent place to stay, figuring out what to eat — none of that individually was difficult. What was hard, consistently and predictably hard, was the organization of it. Pulling together dozens of scattered, contradictory, and often outdated pieces of information into something that actually held up once you were standing at a train station with a backpack and forty-five minutes to make a decision.

The three of them started noticing this pattern outside their own trips too — in friends' group chats, in Reddit threads full of people asking questions that had clearly been asked (and half-answered) a hundred times before, in the sheer volume of travel content that existed online next to the surprisingly small amount of it that was actually current and useful at the moment someone needed it.

Disorganized information isn't a content problem. It's a trust problem. When you can't tell which of your fifteen open tabs is right, you either over-plan out of anxiety or under-plan and hope for the best — and both of those make trips worse, not better.

From frustration to first prototype

Turning that frustration into something real took longer than any of them expected, and looked far less glamorous than the eventual pitch deck slide makes it sound. The earliest version wasn't an app. It was closer to a shared internal tool the three of them built to solve their own problem first — pulling structured information about places, transport, and timing into one place instead of across a dozen tabs, and testing whether a system could actually generate a workable day-by-day plan instead of just a list of "top 10" recommendations copy-pasted from everywhere else.

The gap between "this works for us" and "this works for anyone" turned out to be enormous — which is a separate story about years of engineering work, most of it invisible to anyone using the product. Real-time flight and availability data. Logic for handling the fact that a plan generated at 11pm needs to hold up to reality at 8am the next day, when a flight is delayed or a place turns out to be closed. The unglamorous, constant work of keeping information from going stale, which is exactly the problem that started this whole thing.

Where Zippy Trips is today

Zippy Trips exists because three people who traveled together through college got tired of doing the same disorganized dance every single trip, and decided the fix wasn't a better spreadsheet template or a more detailed blog post — it was software that could hold all of it together, reliably, for anyone.

The company is still early. It's an MVP, pre-launch, building toward real usage numbers and actively raising a seed round to get there — the same scrappy, figure-it-out energy that got three college students through a decade of trip planning is still very much how the team operates today. But the core belief hasn't changed since those first disorganized WhatsApp threads back in Kharagpur: the hard part of travel was never the destination. It was always the disorganized mess standing between wanting to go somewhere and actually being ready to.

What's next

If there's a thread that connects the earliest hostel-room trip-planning sessions to what the team is building now, it's this: every feature Zippy ships gets tested against a simple question — would this have saved us an argument in that WhatsApp group ten years ago? If the answer is yes, it's worth building. If it's just another feature for the sake of having one, it isn't.

The goal was never to build "another AI travel app." It was to fix the specific, familiar, maddening problem of disorganized trip planning that Paras, Supriya, and Birendra lived through long before it had a name — or a product built around solving it.

What almost didn't work

It's tempting, in hindsight, to tell this story as a straight line from frustration to solution. It wasn't. There were long stretches where the idea sat untouched — busy semesters, job offers that made "build a travel startup" feel like an indulgent side project, and more than one conversation among the three of them about whether the problem was actually big enough to justify building a company around it, or whether it was just something that annoyed three specific people on their specific trips.

The turning point wasn't a single decision so much as an accumulation of evidence. Every time one of them mentioned the idea to another traveler — a friend planning a trip, a cousin asking for recommendations, someone in an online travel group — the same story came back: yes, this is annoying, yes, I've dealt with exactly this, yes, I usually just give up and wing it by day three. That pattern, repeated enough times across enough different people, is what eventually turned "our problem" into "a problem worth building for."

Even then, the earliest work was slow and unglamorous in a way that doesn't make it into a tidy narrative. Long stretches were spent just trying to represent travel information — places, timings, transport options — in a structured way that a system could actually reason about, rather than the free-text blog-post format that most travel content exists in. That's not a flashy problem to work on, and it's not one that produces a demo-able product quickly. It's the kind of foundational work that has to happen before anything else does, and it's easy to underestimate how long it takes until you're the one doing it.

Lessons that came out of building this the hard way

A few things became clear during those early years that still shape how the team thinks about the product today.

The problem was never "not enough travel content." If anything, the opposite was true — there was an overwhelming amount of travel content available, scattered across blogs, forums, and apps. The actual scarcity was in structured, current, trustworthy information, organized in a way that could actually produce a usable plan rather than another list to manually cross-reference.

Solving it for three people first, before solving it for anyone, mattered more than it seemed like it should. Building for your own real, specific, recurring frustration — rather than an abstracted "target user" — kept the early product honest. It's much harder to convince yourself a feature is good enough when you're the one who's going to rely on it for your next actual trip.

Engineering discipline around error handling and data freshness turned out to be as important as the AI itself. A system that occasionally gives a wrong answer confidently is worse than one that's slower but honest about what it doesn't know — a lesson that shaped the graceful-degradation approach used throughout Zippy's itinerary engine today, rather than something bolted on as an afterthought.

A trip planned then versus a trip planned now

It's worth being concrete about what's actually different. A trip planned during those IIT Kharagpur years meant a shared document nobody consistently updated, a dozen open browser tabs, and a WhatsApp thread carrying the real decision-making. A trip planned on Zippy Trips today starts with a destination and a set of dates, and produces a day-by-day plan — generated against live data, adjustable without breaking the rest of the schedule — in a fraction of the time that first shared Google Doc took just to get started.

That gap between those two experiences is, in a very literal sense, the entire reason the company exists. Every engineering decision documented elsewhere on this blog — the caching and prefetching that make generation fast, the cross-day rebalancing that keeps a plan coherent when something changes, the deliberate honesty about what's verified versus estimated — traces back to specific, remembered frustrations from a decade of trip planning that happened long before any of it had a name.

The part of the story still being written

Zippy Trips today is still an early-stage company — an MVP, pre-launch, actively raising a seed round, with a small team wearing far more hats than a mature company would ask of its employees. That's worth being upfront about, rather than presenting the company as more finished than it is. The founder story isn't a closed chapter; it's the opening one, and the version of Zippy Trips that exists a few years from now will likely look meaningfully different from what exists today — shaped by the same instinct that got three college students through a decade of chaotic trip planning: notice what's actually broken, and go build the fix, even when it takes longer than you'd like.

Why this story is worth telling now

Origin stories are often told retroactively, cleaned up and simplified once a company has enough traction to make the narrative feel inevitable. Zippy Trips isn't at that stage, and this account is deliberately not written as though it were. The company is still early — still proving itself, still building, still closer to those disorganized WhatsApp threads in spirit than to a finished product with all the answers. Telling the story honestly, including the parts that took longer than expected and the uncertainty that's still part of building something at this stage, matters more than telling a polished version that skips ahead to a tidier ending.

If you're reading this as a potential investor, an early user, or simply someone who's lived through the same disorganized trip-planning frustration Paras, Supriya, and Birendra did — the honest version of this story is the more useful one anyway. It's not a finished company's highlight reel. It's a still-unfolding attempt to fix a problem three people first ran into as students, long before they had the tools, the funding, or the experience to build the fix properly. That work is still very much in progress.

Key takeaways