FAQ
The product is intentionally narrow in the MVP, and that is part of the point.
TripScale is not trying to be every part of travel planning at once. These answers reflect the current shape of the product and the boundaries that make the first version more legible.
Common questions about the current TripScale vision.
What can I paste into TripScale?
Plain text, one public travel URL, or plain text plus one public URL. The product is meant to accept rough inspiration, not just structured search inputs.
Does TripScale use live booking prices?
No. The MVP uses modeled cost logic, destination data, distance-based flight assumptions, local transport rules, and travel-style tiers. That is deliberate because the product is trying to answer “roughly what kind of trip is this?” before live shopping begins.
What happens if the prompt is ambiguous?
TripScale surfaces a short destination choice step. The idea is to resolve ambiguity with a lightweight user decision rather than pretending to be certain when the input could match multiple places.
How much do saved defaults matter?
They matter a lot. Home airport, travelers, trip length, lodging and food level, and transport mode are the frame around the estimate. If a prompt clearly states something concrete, TripScale can still use that for the specific estimate.
What is included in the estimate?
Flights, stay, food, local transport, activities, and a soft buffer. The fuller view also shows a rough trip outline and the defaults that shaped the output.
Is TripScale trying to book the trip for me?
Not in this MVP. The current vision is estimate first, booking later. The product is about helping someone size the trip and react to it before they drop into all the booking detail.