Web AppUnknown

Desti

Desti was an AI-powered iPad travel and mapping app spun out of SRI International. It helped travelers search hotels, restaurants, and destinations based on preferences and online reviews. The risk was not usefulness; users liked recommendations but completed bookings through trusted travel platforms where Desti could not capture revenue.

View source

Product snapshot

What it was

Acted like a personalized travel search engine, using AI and review data to recommend hotels, restaurants, destinations, and locations.

Who it was for

Travelerstrip plannersiPad users researching destinations

Problem / value

Help travelers find places that matched their preferences without manually searching across many travel sources.

Core workflow

Set travel preferences, search for destinations or places, review AI-ranked recommendations, then decide where to go or book.

Core dependency

Desti depended on travel review data, destination search, and a booking path that users trusted enough to complete inside or through the product.

Product form

iPad appTravel search appAI recommendation engine

Pricing model

The app struggled to turn useful recommendations into captured booking revenue.

Competitors or alternatives

TripAdvisorLonely Planetknown travel booking brandsNokia HERE

What happened

Summary

Desti was an AI-powered travel discovery and planning app. Public cemetery/category material makes the case useful for the gap between helpful recommendations and owning the transaction path.

Outcome

Desti is no longer presented as an active standalone travel-planning growth case in the linked public sources.

Core risk

AI planning utility without controlled booking revenue

Shutdown reason

The public sources do not provide a single verified shutdown reason; the useful builder risk is weak revenue capture when users can complete booking elsewhere.

Timeline

The product helped travelers discover destinations, hotels, restaurants, and places through an AI-assisted iPad experience.
The public record places Desti among failed or inactive travel startups.
The available public material is thinner than a founder interview, so the case should be read as a monetization-risk signal.

Before you build

Why it matters

This matters for AI discovery products. Better recommendations are not enough if the user takes the final transaction to Google, Booking, Airbnb, maps, or another platform.

Primary check

Map where booking revenue is captured, test repeat trip-planning use, and prove users will not complete the transaction elsewhere.

Checklist

Track recommendation clicks through to booking-intent actions.
Test a paid itinerary or concierge package before building full AI flows.
Compare user behavior against existing travel search and map habits.
Where exactly does the product make money?
What action proves booking or payment intent?
Why would the user return for the next trip?

Relevant if

You are building AI travel, itinerary, local discovery, or recommendation software.
Your product helps users decide but does not control the booking or purchase step.
You expect affiliate, booking, or subscription revenue without testing the path.

Less relevant if

You already own the booking relationship or have a committed distribution partner.
The product is sold B2B to travel operators rather than monetizing consumer planning directly.

Pre-build tests

Sell manual trip-planning help to travelers with a clear booking handoff.
Run an affiliate or booking-intent experiment before building the full app.

Transferable lessons

Map the full transaction path before building recommendation depth.
Test whether users return for multiple trips or only use the product once.
Validate the revenue model before polishing the planning experience.