Endless tabs during a deal close weren't a discipline problem
During a deal close, work spread across gmail, a crm, two doc tabs, slack, and a calendar, with tabs piling up as each step required reopening the last few to recall context. The initial assumption was a personal discipline problem, but the real issue was structural: the work genuinely lived across half a dozen apps that don't share state with each other, so no tab manager or tab-organizing setup could fix it, since the sprawl wasn't a browser issue at all.
What actually solved it was handing the information-gathering step to a , which read the relevant thread, pulled the crm record, checked the calendar, and presented in a single view — then stopped and waited for approval before writing anything back. The tab count dropped as a , not because tabs were managed better, but because the reason for opening them in the first place disappeared.
Key points
- A deal close required juggling gmail, a crm, two doc tabs, slack, and a calendar, driving constant tab growth
- Tab managers and vertical-tab setups didn't help because the was apps not sharing state, not the browser itself
- A gathered info across apps into a single view, which reduced tab count as a byproduct
- The agent paused and waited for confirmation before writing anything back, rather than acting automatically
- The real identified was the information-gathering step, not the final write/action step