First prompts are messy
Most travellers dump vibe + dates in one breath. Structure belongs in the guide panel, not the first message.
Flow · Research
From prompt to document —
and what we learned
One path every trip follows. Plus the early findings that keep that path honest, useful, and user-friendly.
The path
Three steps. One trip.
Every session moves from intent → conversation → a guide you can keep.
-
01
Request
Describe the trip in chat — dates, vibe, budget, must-sees, soft constraints.
-
02
Dialogue
Tripos clarifies, streams the answer, and proposes a day-by-day route.
-
03
Document
The PDF builds in parallel with visible progress — download when it feels right.
Research
How people actually plan with AI
We're early — so we study every session. Phrasing, edits, PDF trust. Findings feed the product the same week.
Edits beat restarts
People change one constraint (budget, pace, kids) more than they rewrite the whole trip. Branch rollback matters.
PDF = trust checkpoint
Users decide to pay when the document looks printable — not when the chat “sounds smart.”
Methodology
What we measure
We score itineraries on logistics between stops, match to the request, and PDF readability. Session analytics stay anonymized on the client before any upload.
As a starting startup we don't pretend to have peer-reviewed papers yet — we have shipping notes, user interviews, and weekly release loops.
Same week shipping
A finding on Monday can be a fix by Friday — small team advantage.
Anon by default
We study patterns, not personal trip diaries for marketing lists.
Building in public
API and longer write-ups land in News as we grow.
After the PDF
Pay once. Keep the plan.
No subscription. When the itinerary is ready, you pay for this trip — then take the PDF offline.
One-time charge
You're not renting access month after month. You buy the plan you used.
Keep the PDF
Share it with family, print it, save it for the flight — no account wall on the file.
Still iterating
Two student founders. This flow gets sharper every week with your feedback.
Early signal
Numbers from building in public
0
Early itineraries
0
Countries tried
0
Avg. first draft
0
Student founders