Key takeaways
- A client success team structure in coaching is about ownership. Every key moment, from sales handoff to testimonial, needs one person accountable.
- The CSM owns the client. The coach owns delivery. Sales owns the promise. Most refunds start where those three lines blur.
- Teams tend to grow in four shapes: founder does it all, first CSM, 2 to 4 CSMs with a lead, then a Head of CS with pods by offer.
- Assign clients by pod, round-robin or by stage. Pods work best once you have more than one offer or coach.
- Write the sales to CS handoff down as an SOP. A bad handoff is the most common place a $10k client starts to go wrong.
A good client success team structure in a coaching business gives every key client moment one owner. The coach owns delivery. The Client Success Manager (CSM) owns the client and the outcome. Sales owns the promise and the handoff. Community, support and ops roles get added as the business grows, usually in that order, and a Head of Client Success takes over once there are several CSMs or several offers.
I'm Diego, founder of CSM Council. Through Scale With Fulfillment, I run fulfillment for coaching offers, some of them doing $1M+ months. Most broken back ends I walk into don't lack people. They lack clear ownership. Three people think someone else is handling the refund request. Nobody is.
This guide covers who does what, a RACI table for the moments that decide refunds and renewals, the usual team shapes by stage, how to assign clients, the sales handoff SOP, and when to hire the next person.
The roles, in plain words
Coaching CS isn't SaaS CS. If you're coming from software, the client success vs customer success manager guide covers the difference. Here's who's on a coaching team.
| Role | What they own | What they don't own |
|---|---|---|
| Coach / founder | The method, group calls, 1:1 sessions, content | Chasing clients who went quiet |
| Client Success Manager (CSM) | The client: onboarding, check-ins, first win, risk, saves, renewals | Coaching the method |
| Community manager | Skool, Circle or Slack: posts, events, wins threads, engagement | Individual client risk |
| Support / VA | Access, logins, scheduling, invoices, simple tickets | Saves, renewals, hard conversations |
| CS ops | Tools and data: GoHighLevel, Close, Typeform, dashboards, automations | Talking to clients |
| Head of Client Success | Retention, refunds, renewals as numbers. Hiring, training, SOPs | Running a full book |
| Sales (closer, setter) | Booking, closing, the promise made on the call, the handoff | Delivery after payment |
The line that matters most: the CSM owns the client. Not the coach. Not "the team." One named person per client.
RACI table for the key moments
RACI means:
- R = Responsible. Does the work.
- A = Accountable. One person. Answers for the result.
- C = Consulted. Gives input before.
- I = Informed. Gets told after.
This is a typical split. Adjust it to your company. In a small team, the founder holds most of the A's.
| Moment | Coach | CSM | Community | Support/VA | CS ops | Head of CS | Sales |
|---|---|---|---|---|---|---|---|
| Sales handoff | I | C | I | I | C | A | R |
| Onboarding call | I | R | C | C | C | A | I |
| First win | R | A | C | I | I | ||
| Check-ins | C | R | C | C | A | ||
| Refund request | C | R | I | I | A | C | |
| Renewal | C | R | I | A | C | ||
| Ascension | C | R | I | I | A | R | |
| Offboarding / testimonial | I | R | C | C | C | A |
Notes on the moments that go wrong
Sales handoff. Sales does the work. The Head of CS is accountable for the standard. If the handoff is bad, CS has to push back, not quietly absorb it.
First win. The coach delivers the content that gets the win. The CSM is accountable for making sure it happens and gets logged. A client with no first win by week 3 is a refund risk. That's a CSM problem to solve, even when the cause sits with delivery.
Refund request. The CSM runs the save call. Sales gets consulted because they know what was promised. The Head of CS decides on exceptions. The coach gets consulted, not dragged into every save.
Ascension. Two R's. The CSM spots the client who's ready and warms them up. Sales closes, if your model uses sales for bigger offers. One A, the Head of CS, so nobody fights over the credit.
Offboarding. The CSM asks for the testimonial and runs the exit. The VA removes access. The community manager handles the goodbye in Skool if it's a happy exit.
Team shapes by stage
These are typical patterns I see, not data. Revenue bands vary a lot by offer and price, so I won't put numbers on each stage.
Stage 1: founder does it all
The coach sells, delivers, onboards, answers Slack and handles refunds. Maybe a VA helps with scheduling.
What breaks first: onboarding calls slip, check-ins stop, and refund requests come out of nowhere. The founder doesn't have time to notice the quiet clients.
Stage 2: first CSM
One CSM takes onboarding, check-ins, risk and saves. The coach goes back to coaching. A VA handles access and admin.
What to get right: give the CSM the client, not just tasks. They own the at-risk list and they report refunds and renewals to the founder weekly.
What breaks next: the book grows past capacity, because nobody did the math. The CSM to client ratio guide shows how to calculate it.
Stage 3: 2 to 4 CSMs plus a lead
A senior CSM becomes team lead. They still run a smaller book, but they also train new CSMs, review the at-risk lists and own the SOPs. A community manager often joins here, because the community has outgrown "the CSM posts when there's time."
What breaks next: inconsistency. Each CSM runs check-ins their own way. Data lives in four different spreadsheets. This is when a CS ops role, even part-time, starts paying for itself.
For scale, here's one data point from my own seat. At Acquisition Ace, the business ran 7 figures a month with 3 full-time client success people. Lean teams work when the systems are tight.
Stage 4: Head of CS with pods by offer
The Head of Client Success owns retention, refunds, renewals and ascension as numbers. CSMs sit in pods, one per offer or per coach. CS ops owns the tools and dashboards. Support handles tickets. Community runs the community.
What to get right: the Head of CS reports to the founder in money. Cash saved, renewals closed, refund rate. Not "number of calls done."
If you're aiming for that role, read the Head of Client Success guide.
Summary
| Stage | Who's on CS | Who holds the A's |
|---|---|---|
| 1. Founder does it all | Founder, maybe a VA | Founder |
| 2. First CSM | 1 CSM, VA | Founder, CSM for day-to-day |
| 3. Small team | 2 to 4 CSMs, team lead, community manager, part-time ops | Team lead |
| 4. Full team | Head of CS, pods of CSMs, ops, support, community | Head of CS |
Become an S-Tier CSM.
Earn more and work with the top 1% of coaching offers & agencies.
How to assign clients: pod vs round-robin vs by stage
Three common models. Pick one on purpose.
| Model | How it works | Works best when | Watch out for |
|---|---|---|---|
| Round-robin | Next new client goes to the next CSM in line | One offer, one coach, similar clients | CSMs don't build depth on any one coach. Books drift out of balance after refunds and renewals |
| Pod | CSMs grouped by offer or coach. Clients go to their pod | Several offers or coaches. Stage 3 and up | A pod can sit idle while another drowns. Cross-train at least one backup |
| By stage | One CSM onboards, another runs the middle, another handles renewals | High onboarding volume, long programs | Clients get handed over 2 or 3 times. Each handoff is a risk |
My default for most coaching offers: one CSM owns the client from onboarding to renewal. Use pods once you have more than one offer. Use by-stage only if onboarding volume is crushing everything else, and then keep it to two stages at most: onboarding, then everything after.
Whatever model you use, cap new clients per CSM per week. A launch that dumps 30 new clients on one CSM breaks the book for months.
The sales to CS handoff SOP
This is where most refunds start. The closer promised something. The CSM never heard about it. Week 3, the client says "that's not what I was told."
Write it down. Here's a version to adapt.
1. Within 1 hour of payment: closer fills the handoff form
Use a form in GoHighLevel, Close or Typeform. Required fields, no skipping:
Client: name, email, phone, time zone Offer and start date: which program, PIF or payment plan, first payment date Their goal, in their words: what they said on the call What was promised: anything specific, including timelines and results discussed Why they bought now: the trigger Red flags: hesitation, a partner who wasn't on the call, money stress, past bad experiences Special terms: discounts, custom payment dates, bonuses Call recording link: so the CSM can listen
2. Same day: automation kicks in
CS ops sets this up once:
- Client added to the CRM with the handoff fields attached
- Slack channel or DM created
- Skool or Circle invite sent
- Onboarding call booking link sent
- CSM assigned by your chosen model, and notified
3. Within 24 hours: CSM sends a welcome
A short Loom. Their name, their goal said back, what happens on the onboarding call.
4. Within 48 hours: onboarding call happens
No new client goes 48 hours without a call. If they haven't booked, the CSM calls them.
5. On the onboarding call: CSM checks the promise
Ask: "What made you say yes? What do you expect in the first 30 days?" If the answer doesn't match the handoff form, flag it to the Head of CS that day.
6. Weekly: sales and CS review together
Fifteen minutes. The Head of CS and the sales lead go through every refund request and every mismatch from the past week. Fix the pitch or fix the onboarding. Don't argue about blame.
When to hire the next person
Hire by the work, not by gut feel. These are the triggers to watch.
Next CSM. When the hours math says your CSMs will pass about 85% of their max book within two months. Or when the warning signs show up: late onboarding calls, skipped check-ins, surprise refund requests. Start before you need them. A new CSM needs weeks to learn the offer and the coach.
VA or support. When CSMs spend real hours each week on logins, invoices and scheduling. Those are the cheapest hours you'll buy back.
Community manager. When the community needs daily attention and the CSMs are covering it in their gaps.
CS ops. When nobody trusts the numbers, or every CSM tracks clients in a different place.
Head of CS. When the founder is still the one solving every escalation, or when there are several CSMs and no one owns retention as a number.
A simple order to follow: support before your third CSM, ops before your fifth. It's a starting rule, not a law. Move it if your offer needs it.
The guide to hiring a client success manager covers the hiring process itself.
Checklist: is your structure working
- Every client has one named CSM
- Every row in your RACI has exactly one A
- The coach isn't running check-ins or refund saves by default
- The handoff form is mandatory and filled within 1 hour of payment
- Every new client gets an onboarding call within 48 hours
- Sales and CS review refund requests together every week
- Client assignment follows a model you chose on purpose
- Someone reports refunds, renewals and churn to the founder weekly
Next step
Draw your current team on one page. Fill in the RACI table with real names. Every empty A is a gap where clients fall through. Fix the biggest one this week.
If you want to see how other CSMs and Heads of CS structure their teams in coaching offers, that's what the CSM Council inside Skool is for.
Frequently asked questions
What does a client success team look like in a coaching business?
It usually includes the coach, one or more Client Success Managers (CSMs), and over time a community manager, a support VA, a CS ops person and a Head of Client Success. Sales (closers and setters) sits outside the team but hands every client over to it.
Who should own the client in a coaching business, the coach or the CSM?
The CSM should own the client relationship and the outcome tracking. The coach owns the delivery: calls, content and the method. When nobody owns the client, refund requests and missed renewals fall through the gap.
When should a coaching business hire its first CSM?
When the founder or coach is spending more time on onboarding, check-ins and refund saves than on coaching or selling. Waiting until refunds spike is too late, because a new hire needs time to learn the offer.
What is the difference between pod and round-robin client assignment?
Round-robin gives each new client to the next CSM in line. Pods group CSMs around one offer or one coach, so each CSM knows that offer and coach deeply. Pods scale better once you run several offers.
What should be in a sales to client success handoff?
The client's goal in their own words, what was promised on the sales call, payment type (PIF or payment plan), start date, red flags and any special terms. It should be filled in by the closer right after payment, before the onboarding call.
Does a coaching business need a Head of Client Success?
Once you have several CSMs, more than one offer, or the founder is still the one solving every escalation, yes. The Head of CS owns retention, refunds and renewals as numbers, and builds the team that hits them.
Written by
Diego Miescher
Founder of CSM Council and Scale With Fulfillment. Five-plus years running client success and fulfillment for coaching businesses doing $500K to $1M+ a month, and the person who hired and trained their CSM teams.