Trip-First Discovery for Vehicle Rentals

When I was exploring Upcar, a peer-to-peer vehicle rental marketplace, I wasn't initially looking for a product problem. I was simply trying to understand how the platform worked.

Like most rental marketplaces, the experience starts with inventory. Users search for vehicles, browse results, apply filters, compare options, and eventually book. At first glance, that felt completely reasonable. After all, Upcar is a vehicle marketplace.

You can explore Upcar here.

The more time I spent exploring the product, however, the more I noticed how people naturally think about travel. Most people don't wake up wanting a Toyota Corolla. They want to get somewhere.

A traveler landing at SFO is thinking about Napa Valley. A family planning a weekend getaway is thinking about luggage, comfort, and budget. Someone looking for a vehicle for Uber is thinking about long-term affordability. The vehicle is simply a means to achieve an outcome.

That observation became the starting point for a deeper exploration.

The Idea

Most vehicle rental platforms begin with inventory. The user is expected to translate their needs into vehicle specifications before the platform can help them.

The process usually looks something like this:

Need a Trip

↓

Search Vehicles

↓

Apply Filters

↓

Compare Options

↓

Book

The more I thought about it, the more I wondered whether the flow could be reversed. Instead of asking users to discover vehicles, what if the platform first tried to understand the trip? What if discovery started with intent?

Looking at User Intent

To test the idea, I started listing the kinds of requests travelers naturally make. What stood out immediately was that people rarely talk about vehicle models.

Instead, they describe where they're going, how many people are traveling, how much luggage they have, their budget, and the reason for the trip.

A sentence like:

"I'm landing at SFO with my wife and need a car for Napa Valley this weekend."

contains a surprising amount of information. The destination suggests the type of drive. The number of passengers influences vehicle size. The trip purpose influences comfort expectations. The budget influences ranking.

In a traditional search experience, the user manually converts all of that context into filters. In a conversational experience, the system could do that work instead.

Following the Idea Further

Once I started thinking about discovery through the lens of intent, another question emerged.

Should every user see the same ranking when it comes to price?

A traveler searching for the cheapest option and a traveler planning a luxury weekend are looking at the same inventory, but they're optimizing for completely different outcomes.

That led me toward the idea of intent-aware ranking.

The inventory doesn't change. The ranking does.

A family road trip should surface different vehicles than a luxury getaway. A budget-conscious traveler should see different recommendations than someone looking for comfort. The marketplace already contains the inventory. The challenge is understanding what the user actually values.

The Missing Piece

While thinking through the experience, I noticed another limitation in traditional search flows.

Travel planning is rarely a single interaction. People refine their requirements as they think.

They start with:

I'm landing at SFO.

Then:

I'm traveling with my wife.

Then:

We'll have two bags.

And eventually:

Which option is cheapest?

Most search experiences treat every interaction as a fresh query. That felt wasteful. A conversational system should remember context and continuously update recommendations as new information becomes available.

The more I explored the idea, the more it felt less like search and more like planning.

Building a Prototype

At that point, I wanted to move beyond theory.

I built a lightweight prototype to explore what a trip-first discovery experience could look like. The goal wasn't to redesign Upcar. The goal was to test a hypothesis.

Could vehicle discovery become more intuitive if users described trips instead of searching inventory?

You can try the interactive prototype here.

The prototype focuses on three ideas:

• Intent-aware recommendations
• Context retention
• Guided comparison

Instead of selecting filters, users describe their travel plans. The system extracts context, generates recommendations, and continuously adapts as the conversation evolves.

An Example Journey

Imagine a traveler enters:

"I'm landing at SFO with my wife for a Napa Valley wine trip this weekend."

Rather than immediately showing inventory, the system first understands the context. It identifies the destination, the number of travelers, the likely luggage requirements, and the nature of the trip.

Based on that context, it can recommend vehicles that better match the user's intent. A convertible might be ideal for the experience. A Tesla might appeal to convenience and comfort. A luxury sedan might balance practicality and premium travel.

If the user later asks:

"Which one is cheapest?"

the system doesn't need to start over. It already understands the trip and can simply rerank recommendations based on the user's updated priority.

What I Learned

This exploration reinforced something I've noticed across many marketplaces.

Users don't think in products. They think in outcomes.

The closer a product gets to understanding the outcome a user is trying to achieve, the less effort the user needs to spend navigating inventory.

For vehicle rentals, that outcome is often the trip itself.

Whether trip-first discovery becomes the future of vehicle rentals is difficult to say. What became clear during this exploration, however, is that AI creates new opportunities for marketplaces to understand intent before presenting options.

And that makes discovery feel far more natural.