Ask most freelancers how often they switch between clients in a given day, and the honest answer is usually "I don't actually know, more than I'd like to admit." It's worth actually counting, because the number tends to be higher than intuition suggests, and the cost per switch is higher than it feels in the moment.
A reasonable way to estimate it
Take a freelancer managing five active clients. Even a modest pattern, checking in with each active client roughly once a day, responding to an urgent message here, drafting something there, easily produces multiple genuine context switches daily, not counting the smaller ones that happen within a single client's work but across different projects for them. One detailed breakdown of this exact scenario estimated three switches a day across five clients as a realistic baseline, which works out to fifteen switches a week, each one requiring a fresh re-briefing of whatever AI tool is being used.
Why the real number is probably higher than the estimate
That baseline assumes a relatively calm, predictable week. Add a client emergency, a same-day request, a call that runs long and pushes the rest of the day's schedule into overlap, and the actual number of switches climbs well past the baseline on any given day. Freelancers rarely control when a client's urgent need arrives, which means the switching pattern is often reactive and clustered, several switches packed into a short window, rather than evenly spread across the week.
Why counting this matters even without a precise number
The exact count matters less than the fact that it's genuinely higher than most people account for when they think about their own time. "I switch between clients a few times a day" feels manageable in the abstract. Fifteen, twenty, sometimes more switches a week, each one requiring a full re-briefing of context that was already established, adds up to a substantial, specific chunk of a working week that isn't billable and isn't creative output. It's pure overhead, and it's worth actually acknowledging as a real cost rather than an ambient background frustration.
What to actually do with this number
Track your own switches for a single representative week, roughly, doesn't need to be precise. The number is usually higher than expected, and having an actual figure, even approximate, makes the case for fixing the underlying problem far more concrete than a vague sense that things feel scattered. It's the difference between "I probably lose some time to this" and "I'm losing four hours a week to this, every week, indefinitely, unless something changes."
If your own count comes out higher than you expected, it's worth a look at what removes the re-briefing cost from each switch at indexbrain.online.
