Before we started, we read articles about couples who built retreats together. They were uniformly inspirational and almost entirely useless as preparation.
Here's the version that would have been more helpful.
## How the Roles Divided (And How We Expected Them To)
We expected the division to be clean: one of us would handle the land and operations, one would handle guests and programme. We expected this because it roughly mapped to our existing personalities and professional backgrounds.
What actually happened is more complicated. In retreat week, both roles collapse into a single, continuous, high-stakes improvisation. One of us is dealing with a guest who wants to talk after the evening session when the kitchen still needs to be closed; the other is fixing a hot water problem that appeared at 9pm on day three. The clean division turns out to be a preparation-week fiction.
What we've found actually works is a clearer division of authority rather than a cleaner division of tasks. One of us has final say on programme decisions during retreat week; the other has final say on operations and logistics. When both of those things collide — which they do, constantly — we have a standing rule: defer to the person whose domain is being most directly affected, and discuss it later.
Later matters. The mid-retreat discussion when everyone is tired is almost always the wrong time.
## Living Where You Work
This is probably the thing we underestimated most comprehensively.
When the retreat ends on a Sunday, the guests leave and the land is still there. The building is still there. The planning spreadsheet for the next retreat is still open on the laptop. The next group arrives in ten days. And you are both, simultaneously, at home and at work, with no spatial transition to help you change modes.
The solution we've arrived at — and it took a full year to implement and actually keep — is one designated non-retreat day per week. Not a day when we do admin instead of physical work. Not a day when we deal with guest enquiries instead of cooking. A day when neither of us is a retreat operator. This is harder to maintain than it sounds; the land always has something that needs doing, the inbox always has something that feels urgent. But the days we protect this boundary, we are perceptibly more functional the rest of the week.
## Guests Who Become Part of Your Daily Life
Small retreats — and ours holds a maximum of 10 guests — produce something you don't get at scale: guests who become genuinely familiar within three days. By Wednesday of a five-night retreat, there's a warmth and intimacy that can feel wonderful, and also blurs a professional boundary in ways that aren't always straightforward.
We've had guests who begin to treat us as personal confidants, who bring problems that go beyond what a retreat is designed to address, who project onto the setting a therapeutic relationship that isn't what we offer. We've also had guests who became lasting friends and have returned multiple times, referring others, writing about their stays in ways that reached people we'd never have reached otherwise.
Navigating this — maintaining genuine warmth while holding a clear enough boundary that we don't get drawn into something we're not equipped for — is a skill we're still developing. The honest truth is we sometimes get this wrong in both directions.
## What Strains a Partnership
The end of a retreat week, when everyone is tired and the clearing-up isn't done and there's a disagreement about whether a guest complaint needed to be handled differently — this is the moment most likely to produce a real conflict. Not a discussion. A conflict, with the particular sharpness that comes from shared exhaustion and shared stakes.
Real-time disagreements about guest-facing decisions are the worst kind: one of us has already committed to a course of action in front of a guest, and the other disagrees with it, but the guest is right there. Whatever you think of the decision, this is not the moment to relitigate it. We've learned, slowly, to hold this until the guests are not in the room.
## What We've Put In Place
Two practices that have made a measurable difference:
A weekly "what went wrong" conversation, on the Monday after a retreat ends. Not "what could be better" — that's too gentle and produces too little. Specifically: what went wrong, what was our contribution to it, what do we change. This is uncomfortable enough to be useful.
A standing rule that neither of us makes a significant programme or pricing decision alone. Not because we don't trust each other's judgment — we do — but because sole decisions made under pressure tend to be worse than ones made with a second perspective, even when the second perspective is ultimately overruled.
## Why It Has Also Made Us Stronger
We've spent two years building something together that didn't exist and couldn't exist without both of us. There is a particular kind of shared pride that comes from that, and a particular quality of trust built from having navigated difficult situations repeatedly. The retreat would not be better with a different partner model. It would just be different, and probably lonelier.
That said: we'd tell anyone considering this path that they should do it with clear eyes about what it costs relationally. The rewards are real. So is the friction.
---
*We're honest about the process as well as the product. If you're thinking about building an eco retreat, we occasionally offer one-to-one consultations for founders — details on the About page.*