Count what you touched this morning, before ten o'clock.
Email first, probably. Then the calendar, to see what the day was going to do to you. Then whatever system actually holds your work - the management system, the CRM, the project board. Then a link somebody dropped in chat. Then back to email, because two replies landed while you were in the other thing. Then chat again, because the person who sent the link wanted to know whether you saw it.
I know this one from the inside. For a long stretch I was juggling quotes, client support questions, audits, social content and an inbox that never emptied, and the thing that wore me down was never the volume of any single one of them. It was the switching.
None of it felt like a problem while it was happening. It felt like Tuesday.
What is the Toggle Tax?
Toggle Tax is the cost of switching between the applications your work is scattered across - a few seconds of reorientation every time, compounding into hours off the week, and all of it paid by the person who has to carry the context from one system to the next.
The phrase came out of a Harvard Business Review article published in August 2022, researched by Rohan Narayana Murty, Sandeep Dadlani and Rajath B. Das. Worth getting right, since nearly every article on this subject gets it wrong: the researchers did the measuring, but the phrase itself came from their editor, Thomas Stackpole, who called it the toggling tax. The shorter version is the one that stuck.
What they measured is the part that should stop you. Twenty teams, one hundred and thirty-seven people, three Fortune 500 companies. Those workers switched between applications roughly 1,200 times a day. Any single switch cost only a couple of seconds of reorientation, which is precisely why nobody notices it happening. Added up, it came to just under four hours a week spent doing nothing except figuring out where they were.
One caveat I want on the table rather than buried at the bottom, because it changes how you should read that number. Those were mid-office and back-office teams: finance, HR, supply chain, recruiting, inventory. Not producers. Not advisors. Nobody whose day gets interrupted by actual human beings with actual problems. So treat 1,200 as a floor rather than a measurement of your week.
And treat the Toggle Tax itself as one mechanism inside something larger. The larger thing is Admin Drag, the work your best and most expensive people were never hired to do, quietly eating most of their week. Toggle Tax is one of the ways that drag actually happens, minute by minute, in a form nobody can point to afterward. Pilot Purgatory is another face of the same villain, approached from a different direction. The whole-week argument lives on the Admin Drag page. What follows here is one mechanism, examined closely, because this one is about to get more expensive and most people have not noticed.
What this looks like for a producer
"Switching between apps" stays comfortably abstract until you count your own.
A producer working a single renewal opens the agency management system to pull the account. Two or three carrier portals, each with its own login, its own layout, its own opinion about where the submit button belongs. The quoting platform. Email, to chase the missing loss run. Teams or Slack, because somebody in service needs an answer right now. Back to the CRM, so the activity gets logged. Then a spreadsheet, because the thing the client actually asked for does not exist as a report in any of the above.
Seven or eight context switches to move one account forward, and none of them is the work. The work is the conversation about whether that client's coverage still matches their business. Everything else is the toll you pay to reach the conversation. Multiply seven or eight by the number of accounts a producer touches in a week, and the arithmetic gets uncomfortable in a hurry.
Here is what makes it structural rather than merely irritating: none of those switches is optional. Nobody in your agency gets to decide the carrier's portal is inconvenient. The tax is levied by a system nobody there designed and nobody there can opt out of.
The part that is new
Every article written about this topic was written when the toggle set was stable. Email, spreadsheet, CRM, chat. Expensive, understood, largely accepted.
Then AI arrived, and the assumption - reasonable at the time - was that it would shrink the set.
It did the opposite. A general assistant lives in one tab now. A different one sits inside the document editor because it came bundled with the license. The carrier has its own assistant inside the portal. Somebody in marketing started using a fourth without mentioning it. Someone else quietly uses a personal account because the company one is slower. Four or five new destinations, none of which replaced anything.
The new switches also cost more than the old ones, for a reason that has nothing to do with the software being bad.
When you move from email to a spreadsheet, you carry the context in your head. You already know which client, which renewal, which number you were chasing. Reorientation costs you a couple of seconds.
When you move to an AI tool, you have to rebuild that context out loud. Who the client is. What the policy covers. What you already tried. What tone the email needs. What you are actually trying to accomplish. That is not two seconds of getting your bearings, it is several minutes of briefing a stranger who forgets everything the moment the tab closes.
Then you do it again in the next tool. Then again tomorrow, for the same client.
What it looks like when somebody actually fixes it
Mike Welker manages benefits at an agency in Utah. He sat in a session of mine last May and built his first AI assistant in the room.
What he did afterward is the reason I am telling you about him. Over roughly sixty days and four or five attempts - not one clean build, four or five - he put together a workflow that pulls production and cancellation reports from every carrier he deals with, standardizes them into one format, masks the protected health information before anything leaves his machine and restores it locally, and delivers the whole thing into a single dashboard his team uses daily. It replaced a platform they had been paying for on the benefits side. For daily lookups, it beats the management system.
He has not tracked the hours it saved him, and I am not going to invent a number on his behalf.
What I can tell you is what he stopped doing. He stopped being the connection between every carrier he works with. The switching did not get faster. It stopped being his job.
Why "just consolidate" misses
Everyone selling a fix for this lands on the same recommendation, and you can usually predict it from the logo at the top of their page: use fewer tools, consolidate the stack, buy the one platform that does everything, which theirs conveniently does.
That advice is sound and mostly unavailable. You do not control the carrier portals. You do not control the compliance system. Most of your toggle set was chosen by people who do not work for you and will never take your call about it.
The move that actually works is fewer handoffs.
Stop designing work that requires a human being to carry context from one system to the next. That is what your people spend the day doing, and it is the most expensive possible use of an experienced producer. They are functioning as the wiring between systems that were never going to talk to each other.
That is the job a Digital Crew takes. Not another destination in the tab bar - a governed set of agents that hold the context so nobody has to rebuild it on every switch. Scout goes and finds the thing. Scribe writes it down where it belongs. Coach has the brief ready before the meeting starts.
Which is the whole argument, and I will say it plainly: redesign the work before you deploy AI. Adding AI tools to a workflow that already loses four hours a week to switching does not close the leak. It adds taps.
Where to start
Count. Pick one recurring piece of work - a renewal, a proposal, an onboarding - and count the switches it takes end to end. It is the cheapest diagnostic available, and the number usually lands worse than people expect, which is exactly what makes it useful.
Then find the handoff that costs the most context to rebuild. That is where your first agent goes. Not the flashiest task on the list. The one where your people do the most re-explaining.
If you want a faster read on where your organization actually sits, that is what I built the AI Adoption Reality Check for. Six questions, about five minutes, and it names the one gap holding you back instead of handing you a generic score.
You hired producers to sit across from clients. Somewhere along the way the job quietly acquired a second one, carrying context between systems that were never going to talk to each other.
That second job you can give back.
Toggle Tax is the cost of switching between the applications your work is scattered across - a few seconds of reorientation every time, compounding into hours off the week, and all of it paid by the person who has to carry the context from one system to the next. Research published in Harvard Business Review in 2022 found workers switching applications roughly 1,200 times a day, adding up to just under four hours a week spent purely on reorientation.
The phrase originated with a Harvard Business Review article published in August 2022, researched by Rohan Narayana Murty, Sandeep Dadlani and Rajath B. Das. The term itself was coined by their editor, Thomas Stackpole, who used the phrase "toggling tax." The shortened form is what entered common use.
They overlap without being identical. Context switching usually describes moving between different kinds of tasks. Toggle Tax refers specifically to the cost of moving between tools and applications, which can happen many times inside a single task.
Frequently the opposite. AI tools tend to get added to a workflow without replacing anything, lengthening the toggle set rather than shortening it. AI switches also cost more than conventional ones, because the user has to rebuild context explicitly instead of carrying it in their head.
