"I'm not drowning in work. I'm drowning in tabs."
That quote came from a Director of Operations at a 200-person SaaS company. She said it casually, almost as a joke. But no one in the room laughed.
Over the past three months, I sat down with 50 Ops leaders across B2B SaaS companies ranging from 30-person startups to 500-person growth-stage firms. The goal was simple: understand how Ops teams actually spend their time, what makes the job painful, and what they wish the rest of their company understood.
The answers surprised me. Not because the problems were unfamiliar, but because of how universal they were. Regardless of company size, industry vertical, or team structure, these leaders described the same friction. The same exhaustion. The same invisible tax on their productivity.
Here's what the data says.
The Numbers That Should Worry Every CEO
Let's start with the headline findings.
67% of Ops time is spent context-switching. Not answering questions. Not solving problems. Not doing the work their title describes. Two-thirds of their day is spent hunting for information across disconnected tools, switching between browser tabs, and reconstructing context that should be at their fingertips.
The average Ops professional checks 5.3 tools per request. A single Slack message asking "What's the renewal status for Acme Corp?" triggers a workflow that touches Salesforce, HubSpot, the billing dashboard, a shared Google Sheet, and Slack DMs with the account manager. Five tools. One answer.
200+ internal requests per week. That's the median across our sample. For Ops teams at companies above 200 employees, the number climbs past 300.
15+ minutes per response. Not because the answer is complex. Because finding the answer requires a scavenger hunt across your entire tech stack.
Do the math. If your Ops team handles 200 requests per week at 15 minutes each, that's 50 hours of labor. Per week. Just responding to internal questions.
"Quick Question" Is the Most Expensive Phrase in Your Company
When I asked Ops leaders to name their most dreaded type of request, the answer was nearly unanimous.
"Can I ask you a quick question about [customer X]?"
This phrase, sent via Slack at 2:47 PM on a Tuesday, is the single most expensive sentence in B2B SaaS. Here's why.
There is no such thing as a quick question in Operations. Every "quick question" requires context. Context lives in tools. Tools require logins, searches, cross-references, and interpretation. The person asking the question sees a 30-second interaction. The Ops professional sees a 15-minute scavenger hunt.
