Why Your AI Travel Writing Doesn't Sound Like You

Every travel blogger has done it. You paste your notes into ChatGPT, ask it to write a post, and two minutes later you have 800 words that are technically correct, reasonably structured, and completely hollow. It reads like a tourist brochure assembled by someone who has read a lot of tourist brochures.

You change the headline, tweak a few sentences, and publish it. Or you close the tab and decide to write it yourself later. Later never comes.

The problem is not the AI. The problem is that the AI knows nothing about you.

---

Every session starts from scratch

Here's what happens when you open a new ChatGPT conversation and paste in your Ao Nang notes. The model reads what you gave it. It has no idea you've been to Thailand three times. It doesn't know that your Ao Nang piece is the fourth in a series, or that your voice tends toward personal observation over itinerary. It doesn't know you hate the phrase "hidden gem" or that you always structure your posts around a central feeling rather than a day-by-day rundown.

It produces something competent and generic because competent and generic is all it can produce without context.

You can try to fix this with a long system prompt — "write in a conversational tone, first person, avoid superlatives." It helps slightly. The output is still not yours. Tone instructions can approximate a style but they can't replicate a voice built up across years of specific writing about specific places.

Your voice isn't a style. It's an accumulation.

---

What voice actually is

Your travel writing voice is the sum of:

• The particular things you notice (light, food, how a place makes you feel at 11pm)
• The things you don't say (you'd never write "nestled" or "vibrant culture")
• The structure you reach for when you sit down to write (do you open with a scene or an opinion?)
• The context only you have (three trips to Thailand means you can say things a first-timer can't)
• The reference points that recur across your posts (you probably have three or four places that show up as comparisons again and again)

None of that is in a system prompt. Most of it isn't even something you could articulate explicitly. It emerges from reading a body of work written by the same person over time.

Which is exactly the problem with asking a stateless AI to write for you.

---

The context problem, specifically

The Ao Nang post on WanderingBong works not because the writing is clever but because the writer has been there three times and the third trip knows things the first trip didn't. Read the Ao Nang guide and you'll notice the piece doesn't describe Ao Nang the way someone who read about it would. It describes it the way someone who knows it does — with the kind of specific opinion ("the west-facing bars are worth the uphill walk; the beachfront ones aren't") that you can only have if you've been wrong about something first.

That's not in the notes. It's in the history.

An AI that only sees your notes from one trip has none of that history. It's writing about the destination, not writing as you about the destination. The difference is audible.

---

What actually helps

The fix is not a better prompt. It's giving the AI something to work from that it currently doesn't have: your archive.

If the model has read everything you've written — your whole history of posts, the voice, the recurring references, the structure you default to, the things you care about — the output changes significantly. Not because it's doing anything magical but because it now has actual material to work from.

This is what the Roami pipeline is built around. The agent doesn't just read your notes from the current trip. It reads the body of work. It knows what Ao Nang sounded like in your voice the first time, and the second, and the third. It knows that your Ladakh writing is quieter and more interior than your Thailand writing. It knows not to suggest you open a post about Koh Lanta with a summary of its location relative to the mainland.

The tenth post you write through the pipeline sounds more like you than the first, because by then the agent has more of you to work from.

---

The import question

If you already have a blog, the first thing Roami does is read it. You give it your blog URL, it pulls in your published posts, and the voice profile starts immediately — not from scratch, but from the body of work you've already produced.

If you're starting from zero, the archive builds as you log and write. It's slower, but by your fifth post you'll notice the difference.

Either way, you stop re-explaining yourself to the AI every session. It knows.

---

One honest caveat

This works well when you've built a consistent body of work. If you've written ten posts in ten different voices, the model is going to have a confused view of what "your voice" is — because you haven't settled into one yet.

That's not a product failure, it's a feature of the underlying problem. The AI is a mirror. If you give it inconsistency, it reflects inconsistency back. If you give it consistency, it amplifies it.

Which is also an argument for starting the archive early, writing regularly even when it doesn't feel like much, and letting the voice find itself over time.

---

See how the pipeline works → · How three trips to Thailand became six published posts →

---

Related: You're Going to Forget This Trip — and what to do about it · How Three Trips to Thailand Became Six Published Posts