The Remote Work Wars Are Over: Why Sales Teams Must Pick a Side on Asynchronous vs. Synchronous
Remote work debate is cooling. Here's why sales leaders must choose a deliberate async or sync operating model to win in 2025
🔍 The News in 60 Seconds
After years of ping-ponging between "return to office" mandates and fully distributed models, the remote work conversation has reached a quiet truce. Companies like Atlassian and GitLab have doubled down on documented, async-first cultures, while others like Salesforce embrace a hybrid middle ground. The real shift? The debate is no longer about where work happens—it's about how teams communicate. Atlassian's recent report on async work captures this pivot: the winners will be teams that deliberately choose a rhythm and stick to it.
💡 Why This Matters for Sales Leaders
For sales teams, this isn't a philosophical exercise—it's a pipeline issue. An async-heavy model lets reps stack deep blocks for prospecting, founder calls, and deal strategy without the interruption of status-update standups at 9 AM sharp. But go too far in that direction, and you lose the fireside energy of a live deal review where one rep's question unlocks a new angle for everyone.
Steven's take: the trap is trying to do both without intent. Teams that default to "let's hop on a call" for every minor question kill three hours of selling a week. Teams that default to Slack threads for complex negotiation strategy waste days. The winning approach is deliberate—not reactive.
⚙️ The Practical Angle
The practical play here is designing a communication protocol, not just a policy. Start by mapping your team's week into three categories: deep work (prospecting, proposal writing), synchronous collaboration (deal reviews, pipeline meetings, coaching), and async coordination (standup updates, CRM notes, internal questions).
Then enforce it with tooling. For example, Steven's seen teams use n8n to auto-pull Slack standup updates into a shared doc, or trigger a weekly "deal pulse" email that surfaces top risks before the Monday call. The result? Reps get their focus blocks back, and the live meetings become high-value strategy sessions instead of reporting loops.
One simple rule: if a topic can be summarised in a written update with a decision, don't book a meeting. If it requires debate, context sharing, or team energy—schedule it and protect that time fiercely.
🚀 One Thing to Try This Week
Run a "meeting audit" on your calendar. Block out every recurring meeting for the next two weeks. For each one, ask: Could this be a 3-minute Loom or a written update in Notion instead? If yes, cancel the meeting and replace it with 30 minutes of protected selling time. If no, keep it—but make sure everyone shows up prepared.
Want to apply this to your own sales workflow? Let's talk: https://cal.com/stevencesca