“Not a single dramatic moment — more like a Tuesday at 3pm when they realized they hadn't thought about videos that never get watched — the async promise only works if the other person opens it in two weeks. loom had absorbed it. When a code review via Loom walkthrough caught issues that text comments would have missed.”
When I'm they've just reviewed a designer's work and have 12 separate pieces of feedback, I want to replace status meetings and feedback sessions with videos that are actually watched, so I can give feedback on designs, documents, and code in a way that's clear without being a wall of text.
An individual contributor or people manager at a remote-first company who uses Loom as their primary format for communicating complex information asynchronously. They record walkthroughs, give feedback, share context, and replace 80% of the meetings they used to have. They are comfortable on camera — not because they love being on camera, but because they've made peace with the fact that async video is the clearest way to communicate nuance without a meeting. They have a good mic. They have a ring light. They did not buy these for fun.
To make loom the system of record for replace status meetings and feedback sessions with videos that are actually watched. Not aspirationally — operationally. The kind of intention that shows up as a daily habit, not a quarterly goal.
The tangible result: replace status meetings and feedback sessions with videos that are actually watched happens on schedule, without manual intervention, and without the anxiety of videos that never get watched — the async promise only works if the other person opens it. loom has earned a place in the daily workflow rather than being tolerated in it.
They've just reviewed a designer's work and have 12 separate pieces of feedback. Writing them all as comments would take 25 minutes and would lose the "and here's why" context. A Slack voice note is too short. A meeting is overkill and the designer is 9 time zones away. They're opening Loom to do a 6-minute screen walkthrough. They will say "um" four times. They will decide not to re-record. They will be right.
Records 5–15 Looms per week. Uses Loom for feedback, demos, project walkthroughs, and team updates. Works at a company with team members across multiple time zones. Shares Loom links in Slack and Notion — rarely via email. Has a Loom library they've never organized. Has watched back their own Looms approximately three times — always regrets it. Uses the comments feature occasionally. Uses the emoji reactions feature never. Has a corporate Loom account; would pay personally if they had to.
They've stopped comparing alternatives. loom is open before their first meeting. Bug reports include a Loom showing the exact reproduction steps. The strongest signal: they've started onboarding teammates into their setup unprompted.
Video processing and upload times can be slow for longer recordings. Videos that never get watched — the async promise only works if the other person opens it keeps recurring despite updates and workarounds. The 5-minute free limit made it useless for detailed explanations or walkthroughs. The switching cost was the only thing keeping them — and it's starting to look like an investment in the alternative.
Pairs with `zoom-primary-user` for teams managing the sync/async meeting balance. Contrast with `meeting-maximizer` archetype to surface the cultural change required for async-first adoption. Use with `figma-primary-user` for the design feedback use case that Loom was built for.