← All Resources

How Many Athletes Can One Coach Realistically Manage?

March 5, 2026·Simma
Squad Management

How Many Athletes Can One Coach Realistically Manage?

It's Wednesday afternoon. You've got 28 athletes on your books, three of them raced last weekend, two haven't logged a session in nine days, and somewhere in last week's data there's a heart rate trend you meant to follow up on Monday. You just haven't had time. Because before you could open a single session file this morning, you had four emails to answer, a programme to adjust, and a new athlete enquiry sitting in your inbox.

You're not a bad coach. You're a busy one. And you're about to discover a number that every endurance coach eventually runs into.

The number everyone lands on

Ask ten experienced coaches how many athletes they can realistically manage with genuine quality, and you'll hear the same range repeated: somewhere between 20 and 30.

It's not a rule written in any coaching textbook. It's a pattern that shows up independently across forums, coaching platforms, and honest conversations between peers. Training Tilt, a platform that has worked with hundreds of coaching businesses over the past decade, reports that things tend to break down around the 30-athlete mark. Coaches on endurance forums consistently cite 25–30 as the ceiling for personalised service. One put it bluntly: you can take on 25–30 and still provide quality, or you can take on 90 if you're willing to do a half-assed job.

TrainingPeaks' own data tells a similar story — the majority of coaches on their platform maintain squads of just 1 to 19 athletes. Not because demand isn't there, but because capacity isn't.

Why the ceiling exists: a simple time audit

The ceiling isn't about coaching ability. It's about hours.

A TrainingPeaks coaching career guide estimates that meaningful coaching — reviewing sessions, adjusting programmes, communicating with athletes — runs to about 8–10 hours per athlete per month. At 40 hours a week, that caps a full-time coach at roughly 16–20 athletes before accounting for a single minute of business administration, marketing, or their own training.

Even at the leaner end — say 1–2 hours per athlete per week — 30 athletes consume your entire working week. And that's assuming no athlete has a bad race, no one gets injured, and nobody emails you on a Sunday night asking why their FTP test felt harder than it should have.

The real-world breakdown looks something like this for a coach with 30 athletes:

Weekly time budget:

That's 25–39 hours before you've done any actual coaching — the conversations, the race-week calls, the moments where your experience and judgment make the difference.

What breaks first

The ceiling doesn't announce itself. It creeps. And it almost always shows up in the same place: communication.

When you go from 15 to 25 athletes, the first thing that slips isn't your programming. Programmes are relatively efficient to manage once you have your systems down. What slips is the personal feedback. The weekly email that says "I noticed your Thursday tempo was 8 seconds per k faster than last month — your consistency is paying off." The message that says "Your heart rate was elevated in Tuesday's easy run. How's your sleep been?"

Those touches are what separate coaching from plan delivery. And they're the first casualty of a growing squad.

One experienced coach described it this way: when the squad grows past a certain point, you stop writing personalised feedback and start writing "great job this week" — because you literally don't have time to say anything more specific. Your athletes don't complain immediately. They just slowly stop feeling coached.

The retention problem hiding inside the capacity problem

Here's where it gets expensive. Athletes who feel personally coached stay. Athletes who feel like a number on a spreadsheet eventually leave.

Matt Dixon, founder of Purple Patch Fitness and one of the most respected voices in triathlon coaching, has spoken about the recurring themes he hears from athletes leaving other coaches. Three of the four most common complaints are communication failures: not understanding the rationale behind training, the coach not listening, and an inability to adjust when life disrupts the plan.

None of those are programming problems. They're all bandwidth problems.

Coach Nate Wilson from Catalyst Coaching frames athlete retention around two factors: how long an athlete generates revenue, and how long you can sustain genuine engagement with that athlete. When your squad outgrows your communication capacity, engagement drops — and revenue follows.

The irony is sharp. The thing limiting your business growth isn't a lack of athletes to coach. It's that coaching more athletes means coaching all of them worse.

The three responses coaches have to the ceiling

Once you hit the ceiling, you generally have three options:

1. Cap your squad and accept the revenue limit. Some coaches do this deliberately. They keep 15–20 athletes, charge premium rates, and accept that their income has a hard ceiling. It's an honourable choice — but it means turning away athletes and leaving money on the table.

2. Hire other coaches. This is the traditional scaling model, and it works — to a point. Training Tilt's analysis of coaching businesses found that with each coach you add, expenses scale roughly in proportion to revenue. Margins stay thin, and eventually you need a manager, which adds cost without adding revenue. You trade the coaching ceiling for a management ceiling.

3. Change what you spend your time on. This is the option most coaches don't realise exists. The ceiling isn't caused by coaching — it's caused by screening and communication. If you could spend less time reviewing every session file and writing every weekly update, you could coach more athletes without the quality dropping.

The question isn't "how many athletes can I manage?" It's "how much of what I'm doing is actually coaching, and how much is admin that's eating my capacity?"

Redefining the bottleneck

When coaches on forums talk about hitting the wall at 25–30 athletes, they rarely describe the problem as "I can't write enough programmes." They describe it as "I can't review enough data" and "I can't write enough emails."

One coach reported spending 80% of their day on administration. Another described being essentially on call 24/7. A third joked about 700 straight days without a single day free of coaching obligations.

The bottleneck isn't coaching expertise. It's the time it takes to screen a full squad's training data, identify who needs attention, and communicate meaningfully with every athlete — every single week.

That's a workflow problem. And workflow problems have workflow solutions.

What this means for your coaching business

If you're a coach with a growing squad, here's what's worth thinking about:

Know your number. How many athletes can you currently serve with the quality you're proud of? Be honest. If you're already sending "good week!" messages instead of specific feedback, you've already passed it.

Audit your time. Track a typical week. How many hours go to session review and screening? How many to writing summaries and check-ins? That's your compression opportunity — the work that, if made more efficient, unlocks capacity without sacrificing quality.

Separate screening from coaching. The act of reviewing 30 athletes' data to find out who needs attention is fundamentally different from the act of coaching those athletes. The first is pattern recognition across a dataset. The second is judgment, experience, and relationship. Only one of those requires you.

The coaches who break through the 30-athlete ceiling won't do it by working harder on Sunday nights. They'll do it by rethinking which parts of their workflow need a human, and which parts just need to get done.

If you're an endurance coach who's felt the ceiling — or you're heading toward it — we're building Simma to handle the screening and communication work that limits squad size. Your voice, your athletes, without the Sunday night emails. Join the early access waitlist.