When trainers calculate their effective hourly rate, they usually count the coaching hours and divide by revenue. The time spent writing programs, building training blocks, and updating sessions between cycles rarely enters the calculation. It should. That time is a real cost, and it's larger than most trainers think.
The accounting most trainers don't do
Consider a trainer with twenty active clients who writes new programs every six to eight weeks. Each initial program takes approximately ninety minutes to build. Block transitions — updating an existing program for the next training phase — take forty-five to sixty minutes per client. Mid-cycle adjustments for schedule changes, injuries, or equipment availability add another twenty to thirty minutes per month per active client.
Run that math across twenty clients over a month and you're looking at eight to twelve hours of programming work, conservatively. At a coaching rate of $60 to $80 per hour, that's five hundred to a thousand dollars worth of your time every month going to work that doesn't appear on any invoice.
Why it's easy to undercount
Programming time is diffuse. It happens in the evening, between sessions, on Sunday afternoons. It doesn't feel like a full working hour because it's distributed across dozens of short sessions at a desk or on a laptop. The cognitive overhead — keeping track of where each client is in their block, what adjustments were made last cycle, what the next logical progression looks like — is also invisible in the time accounting, even though it's real work that consumes mental energy.
This diffuse quality is also why the time cost tends to grow quietly. Adding a fifth client to your roster feels like twenty percent more coaching work. In reality, it's twenty percent more coaching work and the same proportional increase in programming, admin, and communication overhead — which may or may not show up in your awareness until you're routinely working evenings to keep up.
What that time is worth in revenue terms
If eight hours of programming time per month could be converted to four coaching sessions, at your going rate, that's a direct revenue increase — or the same revenue from fewer total working hours, which is a different kind of value. The programming hours you're currently putting in are not worthless. They produce the programs your clients receive and trust. But they're also hours that are structurally identical to hours you bill, except without the billing.
This is the business case for investing in tools that reduce programming time. The question is not whether you're doing important work when you write programs. The question is whether you need to spend as much time doing it as you currently do.
The quality question
The obvious concern with reducing programming time is quality. If it takes ninety minutes to write a good program, and you now spend forty-five, are you writing a worse program? The answer depends on what's consuming the ninety minutes. If you're spending the bulk of that time on structural work — building out session templates, applying progressive overload calculations, managing volume across the block — then tools that handle that work don't reduce quality. They reassign the systematic work so your forty-five minutes can focus on the judgment-intensive decisions that actually differentiate your programming.
If the ninety minutes is mostly thoughtful, non-reducible programming work, then yes, cutting it in half would reduce quality. But for most trainers, that's not what's happening. The majority of programming time goes to structure, not judgment.