......and my retreats' business

There is a moment in every guide's career that splits time into "before" and "after." For me, that moment happened at 9:47 in the evening on the second night of a 9-day expedition through Torres del Paine, sitting alone outside the refugio while my eight clients slept inside, when I realized I had walked into the mountains without my personal locator beacon.

The PLB. The one piece of equipment I tell every junior guide is non-negotiable. The thing that, in a real emergency at altitude with no cell signal and weather closing in, is the difference between rescue and not. I had three backup communication systems with me. The trip was never in actual danger. But I sat there on a cold rock staring at the empty pocket where the beacon should have been, and something in me went very quiet.

I didn't forget because I'm careless. I forgot because in the 72 hours before that flight, I had answered 84 WhatsApp messages, processed 11 last-minute booking changes, sent 6 reminder emails about gear lists, fielded 4 dietary updates, manually written a "what to expect on day one" message for each client, called the transfer company twice to confirm pickup times, and answered the same question about altitude sickness in nine separate conversations.

My own checklist? I never got to it.

This is the story of what I did about it.


The work behind the work

I've been a mountain guide for eight years. Patagonia, Nepal, the Caucasus, the Cordillera Blanca. The kind of resume that books itself — clients refer their friends, expeditions sell out months in advance, reviews use words like transformative and unforgettable.

But here's what nobody tells you when you become an independent guide: the part of the job you were trained for is the smaller part of the job.

I trained for years to read terrain, manage altitude, make weather calls, hold space for people pushing themselves harder than they ever have. That's the craft. That's what people pay me for.

The actual day-to-day of running my business? It's logistics. It's replying. It's the same questions, in slightly different phrasings, from slightly different clients, every week of the year. It's reminding people about their gear three times before they pack. It's chasing the deposit. It's confirming with the transfer driver. It's answering "is the water safe to drink" for the hundredth time.

I used to think this was the price of being independent. That if I wasn't personally answering every message, I was letting my clients down. The truth is I was drowning, and I had stopped noticing because drowning had become my baseline.

This is something we've written about before in the broader retreat industry — the structural reasons most retreat leaders quietly quit after their second or third retreat. They don't quit because the leading is hard. They quit because the work around the leading is endless. I understood that essay differently after Torres del Paine.

The beacon was the thing that finally made me notice.


The math nobody calculates

If you're an independent guide and you actually count the hours, the picture is brutal.

For every day I spend in the mountains, I spend roughly two days on coordination work — answering messages, sending reminders, chasing paperwork, updating gear lists, troubleshooting last-minute changes. A 9-day expedition costs me close to three weeks of working time, and the actual paid work — the leading — is less than half of it.

The rest is unpaid administrative labor I've quietly accepted as part of the job.

I'm not unique in this. Talk to any independent guide, retreat leader, or expedition operator and you'll hear the same numbers. The difference between a professional and an amateur is sometimes not skill — it's bandwidth. The professional has somehow protected the cognitive space the work actually requires. The amateur is doing what I was doing: arriving at the trailhead with their phone still vibrating in their pocket.

The beacon I forgot wasn't a one-off mistake. It was the predictable outcome of a system that had been quietly failing for years.


What I changed

I came back from Patagonia and did something I had been resisting for a long time: I stopped trying to handle everything personally.

A friend told me about a WhatsApp bot built specifically for retreat leaders, expedition guides, and instructors who run programs. I was skeptical. I've tried tools before. Most of them either don't work, or end up creating more work than they save. But I had a 12-day expedition coming up in Nepal in eight weeks, and I knew if I went into it the way I'd gone into Torres del Paine, I'd forget something worse than a beacon.

Setup took one evening on my couch. I created what the bot calls an "activity code" — a short identifier my clients could send to a single WhatsApp number to get instant answers. I loaded my packing list into it. My day-by-day schedule. My altitude protocol. My logistics document. My emergency contacts. My pre-trip questionnaire.

Then I sent the bot's WhatsApp number to the eight clients on the Nepal expedition, with a short message: "For any questions before we leave, message the bot directly. It has everything. If something needs me personally, it'll route you to me."

What happened in the next two weeks changed how I work.

The packing list — the 6-page PDF I used to email and that nobody read carefully — now lived inside the bot. Clients messaged "PACKING" and got it instantly. They messaged "SCHEDULE" and got the day-by-day. "MEDICAL" gave them the altitude protocol I'd written years ago and updated through eight expeditions. "PAYMENT" gave them the link to pay the balance.

When the trekking permit office issued one of my permits two days late, I updated the bot once. All eight clients saw the new information. I didn't write the same explanation eight times.

Reminders — the ones I used to set 14 calendar alerts for and still forget half of — went out automatically. Day-7 reminder for medical insurance. Day-3 reminder for printed itinerary. Day-1 reminder for early pickup time. The bot did it.

For the first time in eight years, I had quiet evenings before a major expedition.


What that quiet did

I want to tell you what changed in the leading itself, because this is the part that genuinely surprised me.

When I got to Kathmandu for the Nepal trip, I was rested. Not "I slept on the plane" rested — actually rested. My head was clear. I'd had time to review my own protocols. I'd had time to research a section of the route I wasn't fully comfortable with. I'd written my own pre-trip checklist three days early, with time to think.

I didn't forget the beacon.

But more than that — the expedition itself was different. I was more present. I noticed earlier when one of my clients was struggling with the altitude. I had the bandwidth to spend a real hour with another client who was working through something emotionally on the third day. The whole thing felt less like a high-wire act and more like the work I was actually trained for.

When I got back, two reviews mentioned the same thing without being prompted: that I seemed unusually focused on each person individually. Like he was really there with us.

I had always been there with them. I just hadn't been able to show it for the last few years, because half my brain was still in the inbox.


What this is actually about

The bot didn't change my skill as a guide. The bot changed what was left of me when I arrived to do the work.

There's a concept in cognitive psychology called attention residue — the phenomenon where switching between high-volume small tasks leaves residual attention on the task you just left, degrading the quality of the next thing you do. For office workers it's a productivity issue. For guides, it's a safety issue. The brain that has been context-switching for nine hours is not the brain you want making the call on whether to push for the summit or turn back.

For most of my career I was that brain. I just didn't have the language for it.

I now use the bot for everything. The expeditions, obviously, but also the weekly mountaineering training group I run when I'm home in Israel — schedule changes, location updates, gear questions, registration. The class went from "the thing I push through after a long day" to something I actually look forward to.

I'm a better guide than I was a year ago. Not because I trained harder. Because I stopped doing six hours of work every day that nobody had ever asked me to do personally in the first place.


The harder truth

Most independent guides and retreat leaders are doing too much administrative work because they think it's a sign of dedication. That if they're not personally responding to every message, they're letting their clients down.

This is a misunderstanding. Clients don't want your manual labor. They want your competence, your attention, and your presence on the day they're with you. The administrative work isn't service. It's overhead. And overhead doesn't have to be done by you personally to count as "well taken care of."

If you're a guide and any of this sounds familiar — the late-night messages, the constant context-switching, the creeping sense that you're spending less time on the actual craft and more time on coordination — it's worth thinking about what your version of my beacon moment looks like. The forgotten thing that was a warning.

For most guides, it doesn't take a near-miss. It just takes noticing that the math doesn't work anymore — that the part of the job that pays you is shrinking, and the part that doesn't pay you is growing.

We've written about the tech stack independent retreat leaders actually need, and about the systems for managing participants that scale without burning the leader out. The bot is one piece of that puzzle. Not a replacement for guiding. A way to push the administrative weight off your shoulders so you can do the work you were actually trained for.

If you want to try the same bot I use, message it directly: https://wa.me/13025035139 on WhatsApp. Send "hi" and it'll walk you through setup. 

For me, the real measurement of success isn't the bot. It's that I haven't forgotten a piece of equipment in six months. And my Sunday afternoons before an expedition are quiet again.


If any of this resonates, and you're a guide, instructor, or retreat leader who has been quietly drowning in admin work, that's the work we love thinking about. Come tell us what your version of this story looks like.

 


Further Reading

If this piece resonated, our broader series goes deeper into the operational, financial, and emotional realities of running independent retreats and expeditions:

Follow our Facebook page for new articles as they're published.


RetreatsOS is the operational platform built specifically for independent retreat leaders, expedition guides, and instructors who run programs. Public retreat pages, integrated registration, payment plans and deposit collection with automated reminders, a participant management dashboard, the Buddy Bot WhatsApp assistant, and the operational infrastructure that turns the administrative layer of running retreats into a solved problem. If the beacon moment in this article sounded familiar, we're probably building for you. Learn more at retreatsos.com.