🕒
Your time
It starts when you start. Stop for coffee for forty minutes and nothing is missed, because nothing left without you.
About
Tours on your time, your pace, your interests.
BeeMyGuide is an audio guide that follows you instead of the other way round. It notices where you are, and tells you what happened there.
Skip the bus. Take the tour.
No 9:15 departure, no headcount at the corner, no guide with an umbrella walking faster than you want to walk.
What it actually is
Put the phone in your pocket and start walking. BeeMyGuide watches for the places around you and plays a short, well-written piece of audio about each one: the history, the architecture, the thing that happened on that corner that nobody put on a plaque. Then it goes quiet until there's something else worth saying.
You can also point it somewhere. Tell it where you're headed and it becomes a navigation tour, guiding you there and narrating what you pass on the way. Or build a route yourself: drop the stops you care about on a map, order them, add your own notes, and walk it, alone or shared with whoever you're travelling with.
🚶
Your pace
Linger at the one building you actually care about. Walk straight past the other nine. The guide keeps up either way.
🎯
Your interests
Architecture, or crime, or food history, or all of it. Set what you want to hear about and the queue changes shape around you.
Who's behind it
Me, Val. BeeMyGuide is a one-person operation: I design it, I decide what ships, and there is nobody else to escalate to when something is broken at eleven at night.
I've spent more than fifteen years in Silicon Valley, most of it doing one specific thing well: data aggregation and deduplication. Pulling records out of many uncooperative sources and working out which of them are secretly the same thing. It is unglamorous work and it is exactly the problem underneath this app. The same landmark shows up in five public datasets under four spellings, two of them wrong, one of them a hundred metres out to sea. Deciding that those five rows are one place, and which version of the truth wins, is most of what makes a guide feel like a guide instead of a spreadsheet reading itself aloud.
Away from the laptop I'm a dad. My nine-year-old plays soccer and I coach his team, which is its own lesson in logistics, weather and managed expectations. A fair amount of this product got thought through on the sideline of a Saturday morning game.
How it gets built
Worth being straight about, because people ask. I architected BeeMyGuide: the system design, the data model, the pipeline, every product call. The code was written by AI coding agents working in parallel lanes against a specification and an engineering contract I wrote and enforce. I review what comes back, reject what's wrong, and debug what breaks.
That's not a shortcut so much as a different shape of engineering: the hard part moved from typing to deciding, specifying, and being rigorous about what "done" means. It is also why a single person can ship an app with a real backend, a real catalog and twelve languages of narration.
Where it is today
San Francisco is seeded and walkable. Everywhere else is the work in front of me, both by expanding the catalog city by city, and by letting people build and share their own tours in places I haven't reached yet. If you'd like to help with either, or you have data you think belongs in here, I'd like to hear from you.
See where the data comes from →
Read why it costs money →
Tell me what to build next →
Questions, offers, complaints: hello@beemyguide.travel.