Written by
Jonny Stuart
The research on context-switching is well-established. After an interruption, the average knowledge worker takes 23 minutes to return to full focus (University of California, Irvine). Workers who switch between apps regularly lose up to 40% of their productive capacity (American Psychological Association). The average worker toggles between applications roughly 1,200 times per day.
In this post
Tool Sprawl Makes It Structural
What almost none of that research addresses is what context-switching looks like at an agency - where you are not just switching between tasks, but between entire client worlds.
Each client has its own brief history, relationship dynamics, active deliverables, budget status, and communication style. Switching from Client A to Client B is not like switching tabs. It is like changing jobs for 45 minutes, then changing back.
Why Agencies Have It Worse
A developer switching between two features on the same codebase loses 15 to 30 minutes of productive focus per switch (Atlassian, 2025). That is the baseline most context-switching research is built on.
Agency teams are not switching between features. They are switching between:
Client contexts (different brands, different briefs, different approval chains)
Tool environments (Client A uses Slack, Client B uses Teams; some projects are in Asana, others in Monday.com)
Communication registers (one client wants daily updates, another prefers weekly summaries)
Creative modes (strategy in the morning, production in the afternoon, revisions in between)
Each switch carries its own reorientation cost. And unlike a developer returning to familiar code, an account manager switching to a new client brief has to rebuild an entire mental model from scratch - who said what, what is outstanding, what the client cares about this week.
Microsoft's 2025 Work Trend Index tracked 275 interruptions per day for the average knowledge worker during core hours. At agencies, where client communication is constant and tools multiply with each new account, the actual number is likely higher.
The Billable Hour Problem
For most knowledge workers, context-switching is a productivity problem. For agency teams, it is a profitability problem.
Every hour of cognitive reorientation is an hour that could have been billed. Every tool switch, every Slack channel re-read, every attempt to find last week's brief in a folder structure that made sense at the time - all of it is uncharged time.
Asana's 2023 research found that workers lose an average of 3.6 hours per week to app-switching alone. At a 15-person agency, that is around 54 hours per week across the team. At an average billable rate of $80-$100 per hour, the math is uncomfortable - not because the number is catastrophic, but because it is consistent and invisible.
Nobody logs time against "looked for the brief." Nobody invoices for "reread the Slack history to remember where we landed." But it happens every day, across every project, for every person on the team.
The Multi-Client Multiplier
The context-switching research almost exclusively studies workers managing one project or one product at a time. Agency teams manage five, ten, sometimes twenty active client relationships simultaneously.
That multiplier changes the calculus. A single 23-minute reorientation period, repeated across five client switches per day, is nearly two hours of the workday consumed by cognitive overhead. For a senior account manager handling eight clients, the number climbs higher.
The structural pattern we saw in our own studio: the people most affected by context-switching were the best people. The ones who were most across each client's account. The ones who had the most to re-load when they switched. They were paying the highest cognitive tax because they carried the most context.
And because they were good at it, it looked fine from the outside. Deliverables shipped on time. Clients were happy. The hours just quietly expanded to absorb the overhead.
Tool Sprawl Makes It Structural
Context-switching at agencies is not just about jumping between tasks. It is about navigating a tool environment that multiplies with every new client and every new hire.
A 15-person agency might routinely have people working across:
Three or four project management tools (because different clients or older retainers started on different platforms)
Multiple Slack and Teams workspaces
Shared Google Drives and separate client portals
Time tracking that lives in a different system from project budgets
Each tool switch carries a loading cost. Each platform has its own notification stream, its own search, its own file structure. The more tools, the more switching. The more switching, the more hours absorbed.
This is what makes context-switching at agencies different from the generic productivity problem it is usually described as. It is not a personal habit issue. It is a structural one - and it gets worse as the agency grows, not better. We look at the full cost of tool sprawl in more detail in how much your tool stack costs per year.
Reducing the Cost Without Reducing the Work
The standard advice is to time-block: protect deep work sessions, batch client communications, limit notifications. All of that helps. But it treats the symptom rather than the cause.
The deeper fix is reducing the number of environments a person has to navigate. When time tracking, project management, client communication, and budget visibility all live in one place, the reorientation cost per switch drops significantly. The brief is where the task is. The budget is where the project is. There is no separate system to check.
That is the architecture AgencyFlo is built around. One platform for the full operational picture - so your team spends less time finding context and more time doing the work that justified the hire. Apply for early access: agencyflo.ai
See also: why your senior people are doing junior work - which covers the related problem of how tool fragmentation traps experienced staff in coordination overhead.
Key Takeaways
Context-switching costs knowledge workers up to 40% of their productive capacity. For agency teams managing multiple clients, the cost is higher because each switch involves rebuilding a complete client mental model.
The average worker loses 3.6 hours per week to app-switching alone. Across a 15-person team, that is a consistent and invisible drain on billable hours.
Agency context-switching is structural, not personal. It gets worse as the agency grows because more clients means more tools, more workspaces, and more environments to navigate.
The fix is not time-blocking alone. It is reducing the number of environments a person has to navigate - which means fewer tools, not more.
Frequently Asked Questions
What is the cost of context-switching for agency teams?
Research puts the general productivity loss at 40% of cognitive capacity. For agency teams, the direct cost is in billable hours lost to reorientation. An average of 3.6 hours per person per week, multiplied across a team of 15, represents a material monthly loss at typical agency billing rates.
Why do agencies suffer more from context-switching than other businesses?
Because agency teams manage multiple complete client contexts simultaneously, not just multiple tasks. Each switch requires rebuilding a full mental model - brand context, project history, relationship dynamics, outstanding items. The cognitive cost is higher than task-switching within a single project.
How many tools does the average agency team use?
BetterCloud's 2026 research puts the average SaaS application count at around 42 tools for smaller firms. For agencies, the number grows with each new client that brings its own preferred tools and communication platforms.
Does time-blocking help with agency context-switching?
It helps. Batching similar work (all client emails in one block, all production work in another) reduces the frequency of switches. But it does not address the underlying cause, which is the number of separate tool environments a person has to navigate.
What is the best way to reduce context-switching at an agency?
Reducing the number of platforms the team works across. When project management, time tracking, and client communication are connected in a single system, the reorientation cost per switch drops because the context a person needs is in one place rather than four.
