How We Build a Guide
People sometimes assume our destination guides are put together from a listicle and a stock photo library. They're not. Every guide starts the same way every trip of ours starts: we're trying to find the version of a destination that isn't just the top ten landmarks everyone already knows about.
Step one: we go looking for the parts that don't make the postcards
[Describe your actual research process here — do you travel to every destination yourselves before writing a guide, or research remotely too? A mix of both? Give a concrete example: "Before we wrote the Japan guide, we spent [X weeks/researching for Y months] mapping out..."]
We're not interested in a checklist of famous sights with no connective thread between them. A guide is only worth publishing if it reads like something we'd actually hand a friend — the order that avoids backtracking across a city, the neighborhood that's better at night than during the day, the meal you'd regret skipping.
Step two: we build it into an actual day-by-day plan
This is where a lot of travel content stops and ours keeps going. Once we know what belongs in a guide, we sequence it into mornings, afternoons, and evenings that actually make geographic sense — so you're not crossing back over a city you already covered the day before. [Add detail: how long does it typically take to go from research to a finished day-by-day guide? Do you test-walk routes, time them out, use Google Maps to verify distances?]
A guide is only worth publishing if it reads like something we'd actually hand a friend.
Step three: we build the tools, not just the words
This is the part that's a little different about what we do. Most travel guides end at the words on the page. Ours don't — every destination guide is built to plug straight into WanderPlan, our own offline-first travel app, so the budget estimates, the day-by-day plan, and the packing checklists we wrote aren't just something you read once. You can import them straight into your own trip planner with one tap and actually use them on the ground.
[Add a specific example of a "hidden gem" or logistical hack you're proud of including in a recent guide, and why it mattered]
Why we still do it this way
It would be faster to write generic guides. It wouldn't be honest to who we are — two people who plan every one of our own trips this obsessively anyway. If a guide has our name on it, it's because we'd actually use it ourselves.