Behind the Scenes: How I Built a Coaching Container That Actually Works

When I launched my coaching practice, I did what most new coaches do: I built a six-month program with weekly calls, a giant curriculum, and a dozen bonus templates. It looked impressive. It was also exhausting—for me and for my clients. Halfway through the first cohort, I realized we were spending more time covering material than solving actual problems. The container was too full to be useful.

So I stripped it down. I asked clients one question: 'What would make this worth it for you?' The answers were consistent: clarity, accountability, and someone who could see their blind spots. Nobody said 'more modules.' That feedback became the blueprint for everything I've built since.

Here's what the container looks like now. We start with a deep-dive session—90 minutes—where we map the current state, the desired state, and the three biggest obstacles. I record it and send a summary within 24 hours. That single document becomes our North Star. Every subsequent session ties back to it. If a topic doesn't serve one of those three obstacles, we don't spend time on it. This keeps us honest and prevents the drift that plagues long engagements.

After the deep dive, we meet every other week for 60 minutes. The cadence matters. Weekly felt frantic; monthly felt disconnected. Biweekly gave clients enough time to implement and enough frequency to maintain momentum. Between sessions, they have access to async voice-note support. They can send a question, a draft, a decision they're wrestling with, and I respond within one business day. This is where most of the real coaching happens—in the messy middle, not on the call.

I also built a client portal with three sections: Current Focus, Resources, and Wins. Current Focus lists the one to three priorities we agreed on. Resources holds the frameworks and templates relevant to those priorities—nothing more. Wins is a running log of progress, big and small. Clients update it; I read it. It sounds simple, but it changes the energy of the engagement. People stop measuring themselves against an imaginary timeline and start noticing their actual movement.

One of the biggest mistakes I made early on was over-delivering on calls. I'd pack 60 minutes with tactics, frameworks, and action items. Clients would leave overwhelmed and implement maybe 20 percent. Now I aim for one insight and one action per session. That's it. The insight shifts how they see the problem; the action gives them a concrete next step. The rest emerges over time. Less is more when the goal is transformation, not information transfer.

I also stopped pretending to be available 24/7. I set clear boundaries: voice notes answered within one business day, calls rescheduled with 24 hours' notice, no weekend replies. This wasn't about being rigid; it was about modeling the same alignment I teach. If I'm burned out, I can't hold space for anyone. Clients respect the boundaries because they feel the consistency. They know when they'll hear from me, and they trust it.

Another iteration: I introduced a mid-point review. At the halfway mark of a three- or six-month container, we pause and ask, 'Is this still the right focus?' Sometimes the answer is yes. Sometimes the client has made so much progress that the original goal is obsolete. We recalibrate. This prevents the sunk-cost trap and keeps the engagement alive and relevant.

What I'd do differently: I'd start with a smaller container. Three months, not six. It's easier for clients to commit, and it forces both of us to prioritize. I'd also build the async support from day one—it's the secret weapon. And I'd charge more from the beginning. Undercharging attracted clients who weren't fully invested, which drained energy and diluted results. Raising my rates didn't just improve my business; it improved my clients' outcomes because they showed up more committed.

The through-line in all of this is simplicity and honesty. A coaching container isn't a library of information; it's a relationship with structure. The structure should serve the relationship, not the other way around. If you're building a practice, start with the smallest version that can deliver a real result. Test it. Ask for feedback. Iterate. The container that works is the one that helps people move, not the one that looks best on a sales page.