Context-switching between tools costs more than you think. We measured it, and the numbers changed how we build.
I counted my switches for a week
Before we wrote any code for Wingmnn, I did something tedious: I tracked every single time I switched between apps for five workdays. Not the big, intentional switches — I already knew about those. I tracked the tiny ones. The ones that take three seconds and feel like nothing. Open inbox, see a name, wonder when I last met with them, switch to calendar, find the meeting, realize I had an action item, switch to task manager, don't find it, switch back to inbox to search for it. That's six switches in under a minute, and I'd already forgotten what email I was replying to. By Friday I had a spreadsheet with over 1,800 entries. Some days hit 400. The University of California, Irvine famously found it takes 23 minutes to refocus after an interruption. But those were external interruptions — someone tapping your shoulder. What I was tracking were self-inflicted ones. The ones where you interrupt yourself because your tools don't talk to each other. Nobody studies those, but I'd argue they're worse, because you can't turn them off. They're built into the workflow.
The tab illusion
When I tell people about this, the first response is always the same: 'Just keep everything open in tabs.' I know. I had 37 tabs open when I started that tracking exercise. Tabs don't solve the problem. They solve access — yes, everything is one click away. But they don't solve context. When I switch from an email to my calendar, the email disappears. Not from my browser, but from my working memory. I have to re-load it when I switch back. Who was I replying to? What had they said? What was I about to write? That cognitive re-loading is the real cost, and tabs do nothing about it. It's like having every book in a library on your desk simultaneously and calling it 'organized.' The information is accessible. The understanding is not.
What we built instead
The engineering insight that drives Wingmnn isn't 'put everything in one app.' Plenty of tools have tried that, and they end up being mediocre at everything. The insight is: bring context to wherever you already are. When you're reading an email, you shouldn't have to leave to check your calendar, look up the sender, or find related tasks. That information should just be there — because the system knows what you're looking at and what's related to it. This sounds simple. It is absolutely not. Making it work required us to build something we internally call the context layer: a unified index that cross-references every piece of data in real-time. When a new email arrives, it's not just filed in your inbox. It's instantly matched against your contacts, your calendar, your tasks, and your financial records. Every entity — every person, company, project, date — becomes a node in a living graph. That's why, when you open an email in Wingmnn, you see the sender's recent meetings with you, their open tasks, and their last transaction, without searching for any of it.
The hard part nobody warns you about
The technical challenge isn't the indexing. It's the speed. People don't wait for context. If the related information takes even two seconds to load, they'll do what they've always done — open another tab and find it themselves. So the context layer has to be faster than the human impulse to switch. We spent three months on this alone. The first version was accurate but slow. The second was fast but missed connections. The version that shipped can resolve a new email against your entire graph — contacts, calendar, tasks, finance — in under 200 milliseconds. That's fast enough that the sidebar is already populated by the time your eyes finish reading the subject line. If it were any slower, nobody would use it. They'd just open another tab.
What it actually changed
I re-ran my tracking exercise after using the prototype for two weeks. My switches dropped from 350 per day to about 60. Most of the remaining ones were intentional — navigating to a specific module to do focused work. The anxious, searching, 'where did I see that' switches were almost entirely gone. But the number that surprised me wasn't the switch count. It was the quality of my responses. When you have full context while writing an email — the person's history, your commitments to them, the relevant tasks — you write better replies. Not more polished, just more thoughtful. You reference things you would have forgotten. You catch promises you're about to break. You spend less time second-guessing yourself because you can see the whole picture. Context doesn't just save time. It changes the quality of your thinking.