Loom replaced half our meetings, and nobody misses them.

Product lead at a fully remote company—65 people across four time zones. We were drowning in meetings. Every update was a meeting, every review was a meeting, every “quick sync” turned into a 30-minute block that could’ve been a 3-minute explanation. At one point I counted 22 meetings in a single week. Zero time for actual work.

About six months ago, I tried something different. Instead of scheduling a meeting, I’d just record a Loom. Quick 3–5 minute screen recording, talk it through, send the link. Design review? Loom. Sprint update? Loom. Explaining product decisions? Loom. The only meetings I kept were the ones that actually needed back-and-forth—planning, retros, that kind of thing.

It caught on. Now about half the team uses it regularly. Our engineering lead does code review walkthroughs on Loom instead of pairing on every PR. Our designer shares Figma walkthroughs without booking 30-minute review calls with five people. Even customer success sends Looms to clients to explain new features instead of jumping on demo calls.

The math is kind of crazy. A 30-minute meeting with five people costs 2.5 hours of total time. A 4-minute Loom costs 4 minutes to make, maybe 5 minutes per person to watch—and people can watch at 1.5x, on their own schedule, without getting pulled out of flow.

The one thing I’ve noticed is that the quality of a Loom depends entirely on how much I think before hitting record. If I just jump in and ramble, it turns into a 10-minute video that’s unclear. If I take 60 seconds to think it through first, it’s a clean 3-minute Loom that actually lands.

I’ll usually jot down 3–4 bullet points before recording. If I’m in a rush, I’ll quickly talk it out using Willow Voice, skim the transcript to organize my thoughts, then record. It sounds like extra steps, but the whole thing takes maybe 5 minutes—and it’s way better than sending a rambling Loom people have to watch twice.

We still have meetings where they make sense. Planning sessions need real discussion, 1:1s matter for the human side, and some topics are just too sensitive or complex for async. But for routine updates and walkthroughs, Loom has basically replaced them. It’s freed up something like 6–8 hours a week across the team.

For other remote teams using Loom or similar async video tools—how did adoption go? We still have a few people who default to meetings for everything, and I’m trying to bring them along without sounding preachy.