Your guides already have the stories
After a tour, your guide answers one WhatsApp message the way they'd tell a friend what happened. FieldNote asks a couple of follow-up questions, drafts the post, and puts it in your review queue. You approve it. It goes live on your website and your Google Business Profile.
Fifteen minutes on a call, or one page by email first. No pressure either way.
The problem
Every tour produces a moment worth writing up: a guest reaction, a close call, a detail only someone standing there would know. None of it gets written down. By the time anyone sits at a keyboard, the specifics are gone and what is left is generic. So your website and Google Business Profile stay quiet between bookings, not because you lack material, but because nobody has time to turn a day in the field into a paragraph.
How it works
Your guide gets a single message asking how it went. They answer with a voice note, the same way they already talk to friends and family. Three minutes. No app. No login. Nothing to install.
Guide's part: doneA couple of short questions pull out the specific details that make a story worth reading: what the guests said, what made this day different. Then it drafts the post. Every line traces back to something the guide actually said. Nothing is invented, nothing is padded.
Our partYour team reads it and approves it, or edits first. Nothing publishes without your sign-off. You are always the last check before anything goes live.
Your part: five minutesApproved posts publish to your site and your GBP, so the places people actually find you stay fresh between bookings. Handed over ready to paste, or published directly, whichever fits your setup.
AutomaticThe proof
FieldNote was built for Mike Brown Tours, an owner-run tour business out of Cape Town - wine routes, Table Mountain, the Garden Route, with the occasional Kruger safari. Mike is a real guide, over sixty and not a tech guy at all. He talks after a tour. The blog writes itself.
A guide's voice note about two lions resting beside the safari vehicle in Kruger became a full published post. The guide talked. The story wrote itself.
Read it live: mikebrowntours.com/blog/mating-lions-kruger-safari
And it is not just big-five drama. An ordinary Table Mountain and penguins day tour became "The Day a Swiss Guest Couldn't Stop Talking About Shark Spotters" - the story was one guest's fascination, and the pipeline caught it. Your most ordinary tour day already contains a story.
Browse the whole thing: mikebrowntours.com/blog. Every post sourced from a guide speaking, not writing.
The rules we run by
Every line in a draft traces to something a guide said. Think of it as a very good interviewer plus a very fast typist, not a content generator. Thin story? We hold it rather than pad it.
Your team reviews every draft before it publishes. You are the last check, always. If a draft is not worth publishing, it does not publish.
WhatsApp voice notes, the app they already use every day. If a sixty-something tour guide can do it, and he has been for months, your guides can.
The pilot
The ask
If it works, you keep a website and a Google Business Profile that update themselves from what your guides are already doing. If it does not, you will know within a fortnight, with real drafts to judge, not a demo.
WhatsApp +1 604 740 1009 · grant@ideoshi.work