Sortie is being built as a planning-first travel app. Our goal isn't to become a toolbox containing every travel utility imaginable. We're focused on making the whole planning journey work beautifully.
This page separates what Sortie already supports from the V2 improvements and genuinely new capabilities we're building next.
Roadmap dates are target windows rather than guaranteed release dates. Priorities may move as we learn from users, uncover technical issues, or find better ways to solve a problem.
Sortie already supports AI-assisted itinerary planning, native multi-city trips, Trip Stitching, and collaborative shared itineraries. The cards below describe current product capabilities; Free/Pro availability varies by feature.
Create and organise an active trip with the structure complex travel actually needs. Free includes one active trip; existing Free allowances are preserved.
Build and edit a day-by-day itinerary around stops, timing, bookings, and travel between destinations.
Sortie already provides AI-assisted tools for building and improving an itinerary while preserving your decisions.
Keep the movement and accommodation structure of a real trip connected to the itinerary.
Keep reservations and supporting details alongside the plan, with booking links, parsed flight details, and attachments in context.
Find places, stays, and experiences, save them into collections, and bring them back into trip planning.
Share a view-only trip or invite one collaborator to edit and build the same canonical itinerary with you.
Add a public Sortie itinerary to an existing trip and continue editing the result as a native multi-city itinerary.
Browse public Sortie itineraries and use published templates as a starting point for your own planning.
Export a polished itinerary with days, stops, travel times, bookings, and key trip details for offline reference.
Sortie currently covers roughly 800 destinations, with destination search, pages, continent browsing, discovery, suggested-itinerary infrastructure, and Discover/planner integration.
Destination coverage and destination depth are not currently the same thing.
Sortie follows a DB-first model for place search: fetch once, store, improve, reuse. External paid APIs are intended as fallbacks rather than the default source for every search.
Place records bring together identity, destination, location, images, descriptions, facts, search information, and nearby data. Quality and depth currently vary as this foundation improves.
A multi-source image pipeline is being refined around exact-place matching, reuse of already-sourced imagery, quality checks, reliable fallbacks, and storage efficiency.
Public trip pages, public itinerary infrastructure, and generated/template itineraries are developing together.
Publishing more itineraries is not the goal. Publishing good itineraries is.
Sortie works across desktop, tablet, mobile, and small mobile screens, with the planning surface adapting to the way you are using it.
A dedicated phone app focused primarily on the on-trip experience—not simply responsive web work. The initial product will centre on viewing, navigating, bookings, documents, on-trip actions, and offline resilience.
Planning often happens on a larger screen. Travelling does not. The responsive web application will remain the richer planning surface initially, while the native app focuses on the journey itself.
Plan a Trip already exists. The next version will improve generation quality, control, fine-tuning, preservation of user decisions, and itinerary intelligence.
Fill a Day already builds out an existing itinerary day. Future work will bring better contextual suggestions, finer control, and more precise tuning around pace, interests, and existing plans.
Optimise a Day already exists. Future improvements will focus on smarter ordering and routing, better timing, stronger constraint handling, and clearer recommendations.
Day Health and trip readiness already exist. The next version will add deeper diagnostics, clearer explanations, and more actionable fixes for overloaded or inefficient days.
Better descriptions, traveller-relevant information, categories, official websites where available, location, imagery, visit duration, nearby recommendations, related experiences, Save to collection, and Add to trip.
Save a place, add it to a trip, or add it to a specific day where appropriate.
Multi-select saved places, choose a trip, segment, and day, then get a suggested placement.
Bookings should reference the relevant itinerary stop rather than creating duplicate place records.
Improve routing, segment-aware suggestions, travel-day placement, hotel anchors, and cross-city itinerary refinement without changing the native trip structure.
Expand the existing Trip Stitching flow with better previews, more flexible composition, and stronger continuity across stitched destinations.
Offline access to the full itinerary, bookings, addresses, notes, tickets, documents, and selected imagery. The initial mobile app will already aim for basic offline resilience.
Improve organisation for the tickets, PDFs, booking confirmations, reference numbers, and attachments already supported in Sortie.
Skip a stop, move it later or tomorrow, replace it, or find something nearby.
Potential reminders for upcoming bookings, time to leave, the next stop, and important travel moments—without overpromising notification functionality.
Extend the current owner-plus-one-collaborator model toward small-group planning of approximately five people per trip, with a smoother shared planning experience.
Expand the existing booking and experience integrations only where commercial options genuinely improve the planning process.
Improve the quality scoring, publication thresholds, approval controls, destination relevance, and itinerary structure already used for public itinerary surfaces.
Places, things to do, neighbourhoods, experiences, suggested itineraries, planning information, and collections—with expansion following demand and quality rather than forcing every destination to reach equal depth.
These are ideas we're interested in, but they are not currently committed roadmap items.
Some may become important. Some may never be built. We'd rather solve the core travel-planning experience exceptionally well than accumulate features simply because other travel apps have them.
The roadmap follows the product loop: protect the foundation, make the trip useful in motion, then connect the pieces with care.
Sortie already has most of its major nouns:
Destinations · Places · Collections · Trips · Segments · Days · Stops · Bookings
The next phase is about building better verbs between them:
Discover something
→ save it
→ add it to a trip
→ put it on the right day
→ attach the booking
→ use it while travelling
→ carry the whole thing in your pocket
Want to see the planning workflow in action? Start with a destination, save a few places, and build a trip around them.
Explore destinations
