Do the Math: You're Paying a Second Salary in App Switching
Photo by Photo by Flipsnack on Unsplash on Unsplash
There's a moment that happens in almost every small startup's Slack. Someone shares a screenshot of their browser tabs — 34 open, half of them SaaS logins — and everyone laughs. Then everyone goes back to work, toggling between eight platforms to complete a task that should've taken eleven minutes.
Nobody's laughing at the math, though. Because the math is ugly.
The Invoice You Never See
Every tool on your stack has a sticker price and a hidden price. The sticker price shows up on your credit card statement. The hidden price shows up in your team's calendar.
Consider where the hours actually go:
- Context switching. Research out of UC Irvine famously found it takes over 23 minutes to fully refocus after an interruption. Even if your team only loses five minutes of flow per app switch, and switches 40 times a day, that's real money walking out the door.
- Integration maintenance. Somebody owns the Zapier account. Somebody notices when the HubSpot-to-Notion sync breaks. Somebody rebuilds it at 9pm on a Thursday. That somebody is on your payroll.
- Onboarding and re-onboarding. Every new hire spends their first two weeks learning your stack. Every tool you add extends that runway. And every time you swap a tool — goodbye Monday, hello ClickUp — you pay that cost all over again for the whole team.
I talked with operations leads at a handful of US startups under 25 employees, and the pattern was consistent: teams estimated they lost somewhere between 15 and 25 hours a week collectively to what one ops director in Austin bluntly called "feeding the machine." That's a half-time employee. Unpaid. Invisible on every dashboard you own.
Calculating Your Actual Tool Tax
Here's a back-of-napkin framework. Grab a coffee and a shared doc.
Step 1: Count the switches. For one week, have three team members jot down (or use a tool like RescueTime to track) how many times they move between apps to complete a single task. Multiply the average by your headcount and the average minutes lost per switch.
Step 2: Price the plumbing. Estimate monthly hours spent fixing broken automations, updating permissions, and reconciling data between systems. Be honest — check who's actually doing it. It's usually your most senior person, which means it's your most expensive person.
Step 3: Add the learning curve. New tool rollouts, abandoned rollouts, and re-training after swaps. If you've changed project management platforms in the last 18 months, you already know this number stings.
Step 4: Divide by revenue. Total those hours, apply your average loaded hourly cost, and compare it to monthly revenue. Most teams I've run this with land between 3% and 8% of revenue — a tax nobody voted on.
When Fewer, Deeper Wins
The default instinct when a tool frustrates you is to add another one. That's how a five-person team ends up with 22 subscriptions. (We've written before about the subscription graveyard — auditing your way out of SaaS sprawl is step one.)
But the deeper move is consolidation with intention. A $30/month tool that replaces three $12/month tools isn't just cheaper on the invoice. It removes two integration points, two login flows, and two places where data can silently rot.
Ask three questions before adding anything:
- Does this overlap with something we already pay for, even partially?
- Who will own its maintenance — by name?
- If it disappeared tomorrow, would anyone notice within a week?
If the answers are "yes," "nobody," and "probably not," you've just talked yourself out of a tax increase.
The Uncomfortable Conclusion
Venture-backed software marketing has sold small teams a seductive idea: that the right stack is a competitive weapon. Sometimes it is. But more often, the stack is a second job your team didn't apply for.
The leanest teams I've seen aren't the ones with the most tools. They're the ones who treat every addition like a hire — with a salary (the maintenance hours), a job description (what exactly does it own?), and a probation period.
Run the numbers this week. Your future self, finally finishing a task in one tab, will thank you.
