The Context Tax: what juggling five client logins actually costs you
Every time you switch from one client's world to another, you pay a tax in minutes, mistakes, and mental residue. Here's what that tax really adds up to — and why no client's tool can refund it.
There’s a cost nobody puts on your invoice. You pay it in the ninety seconds between logging out of Acme’s Notion and finding the right tab for Studio North. You pay it again when you open the wrong client’s workspace in a meeting and have to talk while you fix it. You pay it a third time that evening, when you sit down to plan tomorrow and realise the only way to see your actual day is to open five tools and hold the total in your head.
I call it the Context Tax, and if you work across several unrelated clients, you are one of its heaviest payers.
It isn’t the switching. It’s the residue.
The obvious cost is the switch itself — the logins, the tab-hunting, the “wait, which account am I in.” That’s real, but it’s the small part. Browser profiles and password managers already shave it down.
The expensive part is what psychologists call attention residue: when you move from one context to another, a piece of your mind stays behind. You’re in Studio North’s brand review, but part of you is still chewing on Acme’s proposal deadline. The work in front of you gets a diluted version of you. Multiply that across six, eight, ten switches a day and you’re running the whole day at a discount.
You can’t feel each individual tax. You feel the aggregate: the vague sense that you were busy all day and moved nothing meaningful forward.
The math nobody wants to do
Say you switch clients eight times a day. Say each switch — the mechanical part plus the re-orientation — costs you six minutes before you’re genuinely productive again. That’s 48 minutes a day. Across a five-day week, roughly four billable hours gone. Not to work. To the seam between the work.
Four hours is a client half-day. It’s the retainer you didn’t have time to pitch. It’s the reason Friday afternoon feels like triage instead of a finish line.
And that’s just the time you can see. It doesn’t count the dropped ball — the invoice you forgot because it lived in a client’s tool you hadn’t opened in a week — or the quiet stress of never being sure you’ve seen everything.
Why your clients’ tools can’t help
Here’s the trap: every tool you use to do the work is owned by a client. Their Notion. Their Asana. Their Slack. You are a guest on their tenant, and a guest sees exactly one house.
No client’s tool will ever show you your Tuesday across all your clients, because from that tool’s point of view, your other clients don’t exist. The one view you most need — everything, today, across all of them — is structurally impossible inside any single one of them. You end up being the integration. You are the human API holding five disconnected systems together, and the API is tired.
That’s why so many of us quietly keep a separate master list — a notebook, a text file, a whiteboard — because nothing we’re given can show us the whole. It half-works, and it’s a symptom worth taking seriously. (More on that in your own master list.)
Paying it down
You don’t beat the Context Tax by switching faster. You beat it by needing to switch less — by having one place that already knows about all your clients, so the whole picture is a glance instead of an assembly job.
That’s the entire reason I’m building TinyHub: a private home base that sits above your clients’ tools and gives you the one view none of them can — your whole day, every client, one screen. It doesn’t replace their Notion or their Asana. It just means the total finally lives somewhere.
If the tax I’ve described sounds like your week, take a look — it’s free while we’re in beta.
Follow the build
Occasional notes on building TinyHub in the open — what shipped, what's next. No spam, ever.
You're in. Next build note lands in your inbox.