How TravelM8 estimates prices

One context in, ~26 rows out

When you fill in the planner, your inputs become a single normalised TripContext — passport, home country, destination, dates, traveler counts, style, preferences. That context fans out across roughly 18 pipelines that each own one slice of the trip (visa, lodging, flights, food, activities, eSIM, FX, gear, transit, shopping, tips, tax, refund, buffer, advisories, and more). Each pipeline emits one or more rows on your dashboard.

Pipelines run in parallel and render as they resolve, so the dashboard never blocks on the slowest one.

Six trip shapes decide what runs

Not every pipeline runs for every trip. A short domestic hop doesn't need flights; a Schengen-internal trip doesn't need visa, eSIM, or FX rows. We classify your trip into one of six shapes — domestic-short, domestic-long, Schengen, visa-free international, visa-required, or advisory — and each pipeline decides for itself whether to run.

The shape badge appears at the top of every dashboard so you can see which logic applied to your trip.

Editorial baselines, multi-source

For each of our destinations, three travel styles (backpacker / mid-range / luxury), and the round-trip flight from the user's home, we hand-curate baseline prices. Each value is cross-referenced from at least two of:

• Lonely Planet city guides — long-form editorial with budget breakdowns
• Official tourism boards (visitnorway.com, spain.info, vietnam.travel, egypt.travel, and equivalents)
• Public price listings on major OTAs and metasearch engines: Booking.com, Hostelworld, Skyscanner, GetYourGuide — all publicly accessible, no API or affiliate relationship needed
• Recent traveler reports from r/travel and destination-specific forums (sanity check on outliers)

Every value is reviewed weekly by an automated research agent that runs every Monday at 09:00 UTC. The agent cross-checks each cell against at least two sources and only updates a price when the corroborated delta is meaningful (≥3%); otherwise it leaves the existing value alone and notes the destination in a "no-confidence" section of its review PR. A human reviewer merges or rejects each weekly batch. The "as-of" date shows alongside each row's source citation on the dashboard.

Source citation is mandatory

Every dashboard row shows the source it came from with an as-of date. If a pipeline can't produce a sourced estimate, the row is dropped — we don't render uncited numbers. This is the trust layer; without it the entire estimate is just guesswork in a nice typeface.

Failure-soft, never absent

When a pipeline fails (timeout, partner outage, missing rule), we degrade to a rule-based fallback estimate and tag the row with an "estimate" badge — but the dashboard never breaks. You always see a complete cost picture; we just tell you which numbers are softer than others.

Visa rules are different — government-sourced

Visa rules are not editorial. Every visa row cites the destination country's official authority — NADRA for Pakistan, UDI for Norway, Egyptian e-Visa for Egypt, the Schengen Border Code for EU travel, and equivalents elsewhere — with a one-click "Verify with X" link straight to the source. We don't opine on visa rules; we point you at the people who own them.

Seasonal multipliers

For destinations where peak-season pricing meaningfully changes the trip cost — Tromsø in aurora season, Madrid in EU summer, Buenos Aires in southern summer, Mediterranean hotspots in August — we apply documented multipliers on hotels and flights only. The dates you pick determine which season applies; the math is transparent in each row's breakdown.

The buffer

Every plan shows a buffer (10–15% of subtotal, depending on travel style — luxury at 10%, mid-range at 12%, backpacker at 15% because the variance is wider). It's explicit, not hidden — disclosed to cover normal swings in food, transit, and unknowns. You can toggle it off in the dashboard if you want the raw subtotal.

For current rates, ask Concierge

The dashboard estimates are an editorial baseline. For your specific dates, Premium members can ask the AI Concierge — a research-savvy travel planner with live web search and web fetch — to recheck any row. Concierge runs date-bound queries on Booking, Skyscanner, and editorial sources, returns prices labeled (live-checked: site.com, May 1) vs (typical — not checked for your dates), and never quotes a number from training data without a search to back it up.

When you re-open a saved trip more than three days after you last asked Concierge, the dashboard surfaces a banner reminding you that prices may have shifted — so you remember to recheck before booking.

What this isn't

These are not real-time quotes for the booking surfaces themselves. The actual price you pay when you click a Book button through to a partner depends on dates, availability, and partner pricing on the day. Our estimates are calibrated to come within ~15–20% of real prices for the corresponding dates and travel style. Concierge layers live-searched prices on top for Premium members; the dashboard affiliate links go straight to the partner's booking flow where the price is the price the partner is showing.