The person behind your itinerary
Geoffrey Monté
Travel planner. Software engineer. The one who reads the guidebooks so you don't have to.
How I got here
I've been a software engineer for over fifteen years. PHP, Symfony, architecture, team management — that's been my day job in Lille, through my own consulting company, Numerogeek. I'm methodical by trade. I like systems that work.
And then I did a world tour.
Not the backpacker kind where you figure it out on the ground. I planned everything. Every stop, every hotel, every train connection. I spent hundreds of hours reading guidebooks, cross-referencing blogs, checking reviews, building spreadsheets. The trip itself was extraordinary. But the preparation? Brutal.
When I got back, friends started asking for help. "You planned that whole trip — can you do mine?" So I did. Then their friends asked. Then colleagues. At some point I realized I'd built a whole methodology for this. I knew which sources to trust, which ones to skip, how to structure an itinerary that flows naturally from one day to the next.
That's how Voyage Adventure started. Not from a business plan. From people who didn't want to spend their evenings on TripAdvisor trying to tell the real reviews from the fake ones.
How I build your itinerary
I should be clear about one thing: I'm not a travel agency. I don't book your flights. I don't have contracts with hotel chains. I have no incentive to send you anywhere specific.
What I do is research. Properly.
For every destination, I go through the reference guidebooks — Lonely Planet, Routard, Michelin, and others. I cross-reference those with local sources: regional tourism boards, food blogs written by people who actually live there, transport forums where someone figured out the 6 AM bus schedule that no guidebook mentions. I talk to travelers in my network who've been there recently. I verify prices, check seasonal closures, look at what changed since the last edition was printed.
Then I build your trip around your constraints. Your dates, your budget, your pace. If you want to wake up at noon and spend every afternoon at the beach, the itinerary reflects that. If you want to cover three cities in five days, I'll make the logistics work — and I'll tell you honestly if it's too tight.
The result is a PDF you can open on your phone. Day by day, with addresses, transport options, price estimates, and the kind of practical details that save you from standing on a street corner with no plan at 7 PM.
Why a software engineer plans better trips
Software engineering is about solving problems with structure. I apply the same discipline to travel planning — logistics, dependencies, fallback options. Nothing is left to chance.
I've navigated border crossings at 4 AM, missed connections, found hidden restaurants down unmarked alleys. The itineraries I write come from knowing what actually happens on the ground.
I don't recommend a hotel because it "feels right." I check recent reviews, compare prices across platforms, verify location on satellite images. My tech background means I know how to find and validate information at scale.