Loom solves async sending.
alfred_ solves async receiving.
Loom solves async communication by removing the need to write. alfred_ solves async communication by removing the need to read everything. Both exist because communication volume is too high. They just attack the problem from opposite ends.
Should I use Loom or alfred_?
- Loom is for explaining things visually without scheduling a call (outbound async communication)
- alfred_ is for managing what arrives in your inbox and calendar (inbound async communication)
- Loom was acquired by Atlassian in 2023; free tier now capped at 25 videos lifetime
- alfred_ is $24.99/month; Loom Business+AI is $20/user/month
- Most executives need both: Loom for sending visual explanations, alfred_ for managing what arrives
The question is not which tool is better. It is which side of the async problem you have. Loom helps you send. alfred_ helps you receive and respond.
The Core Difference: Sending vs. Receiving
Loom was acquired by Atlassian in October 2023 for $975 million. The premise was sound: async video messaging, where you record a short video instead of writing a long email, eliminating back-and-forth and scheduling overhead for things that are easier to show than explain. alfred_ is an AI work assistant for executives and knowledge workers. It manages the receiving side of communication: email triage, calendar management, daily briefings, and meeting prep.
These tools address genuinely different problems. A founder who records Loom videos for their team still needs to manage the inbox that fills up while they were recording. A knowledge worker drowning in email still occasionally needs to explain something visual without scheduling a 30-minute call. The comparison is worth making, but the conclusion is not "choose one." It is "understand which problem you actually have."
What Loom Does
Loom's core function is async video recording and sharing. You record your screen, your face, or both; Loom generates a shareable link instantly; the recipient watches on their schedule without needing to join a live call. For visual explanations like design reviews, software walkthroughs, onboarding sequences, and customer demos, this eliminates the overhead of scheduling a synchronous meeting for something that doesn't require real-time interaction.
AI features at the Business+AI plan ($20/user/month) add meaningful value: automatic video titles and summaries, chapter markers, action item extraction, and video-to-text transcription. For teams that produce high volumes of Loom content, these features reduce the friction of finding and consuming recorded videos. Deep integration with Confluence and Jira makes Loom particularly strong for engineering and product teams already in the Atlassian ecosystem.
The post-acquisition pricing structure has been a source of significant friction. The free tier was capped at 25 total videos lifetime and 5 minutes per video, a stark change from the original "record as much as you want" free model. For users who built a Loom habit on the generous free tier, this change effectively forced a paid upgrade within weeks. Alternatives including Vidyard (free plan with 4K recording and 15 AI videos/month), Descript ($12/month), and Veed (from €22/month) grew their user bases specifically in response to these changes.
Where Loom remains genuinely strong: any use case that benefits from showing rather than telling, with recipients who prefer video over text. Sales outreach, customer onboarding, complex technical walkthroughs, and UX feedback sessions are the documented strengths. It creates a content artifact (a video) that can be shared, replayed, and referenced.
What alfred_ Does
alfred_ handles the receiving side of the async communication equation. Every morning, it synthesizes your email and calendar into a daily briefing: what's urgent in your inbox, what's on your schedule, and what context you need for each meeting. Email triage surfaces the messages that require attention and deprioritizes the noise. Meeting prep pulls relevant email thread history before a call so you walk in informed. Task extraction identifies commitments made in email threads without requiring you to manually flag them.
alfred_ does not record video, generate shareable links, or help you explain visual information asynchronously. Those are Loom's strengths. alfred_'s value is the communication load that arrives regardless of whether you sent any Loom videos: the 50+ emails per day, the calendar with back-to-back meetings, the follow-ups that accumulate while you're in calls.
The practical frame: for every Loom video a manager sends to explain something to their team, they receive 5–10 responses in email about that same topic. Loom solves the sending problem; alfred_ solves the receiving problem.
Side-by-Side Comparison
| Feature | alfred_ | Loom |
|---|---|---|
| Direction | ||
| What it handles | Email triage, calendar, meeting prep, daily briefings | Async video recording and sharing |
| Communication direction | Inbound: helps you receive and synthesize | Outbound: helps you send and explain |
| Pricing | ||
| Pricing | $24.99/month | Free (25 videos lifetime); Business+AI $20/user/month |
| Email management | ||
| Meetings | ||
| Meeting prep | Yes: email context before each call | |
| Use case | ||
| Best for | Executives managing high-volume incoming communication | Teams needing visual async explanation without scheduling calls |
Who Should Choose Each Tool
Pros
- Your async communication problem is outbound and visual
- Regularly need to explain software interfaces, walk through design changes, or onboard team members
- Customer success teams handling complex product walkthroughs
- Sales teams doing personalized video outreach at scale
- Already in the Atlassian ecosystem (Confluence, Jira)
Cons
- Free tier capped at 25 videos lifetime, which forces a paid upgrade quickly
- No email management or calendar integration
- Post-acquisition pricing increases drew significant user dissatisfaction
- Strong alternatives exist: Vidyard (generous free tier), Descript ($12/mo)
Pros
- Your async communication problem is inbound and overwhelming
- Start every day with an inbox that takes an hour to parse
- Walk into meetings without context from prior email threads
- Communication anxiety is about what arrived, not about how to explain something you need to send
- Works regardless of which video tool your team uses
Cons
- Does not record video or generate shareable links
- Not a solution for explaining visual information asynchronously
- Requires email access to work
Our Verdict
Different tools for different ends of the async problem.
Atlassian paid $975 million for async video in 2023. In the same period, every major email client added AI drafting features, and AI meeting summarizers proliferated to the point of commoditization. What the market showed is that both problems persist simultaneously: people still send too much email and still need to explain things visually. Loom creates content: video recordings that serve as communication artifacts. alfred_ processes content, synthesizing the communications that arrive into something usable. One tool is about production; the other is about consumption and synthesis.
Best for
- Loom for visual explanations that would otherwise require a live meeting
- alfred_ for managing the inbox and calendar that fills up regardless
- Use both if you regularly explain things visually AND manage high email volume
Not for
- Loom if your problem is the inbox, not what you need to explain
- alfred_ if your primary need is showing rather than telling
Frequently Asked Questions
Can Loom's AI features replace what alfred_ does?
No. The AI features in Loom (video summaries, chapters, action item extraction, transcription) all apply to Loom videos you've recorded or received. They make Loom content easier to produce and consume. alfred_'s AI operates on your email inbox and calendar, two inputs that Loom never touches. Loom's AI makes your video library more navigable. alfred_'s AI makes your daily communication workload manageable. They don't overlap.
Should I use both Loom and alfred_ together?
Potentially, depending on your role. If you're a manager who regularly uses video for team updates or walkthroughs and also has significant external email and calendar volume, both tools add value in different domains. Loom handles the 'explain this visually' problem; alfred_ handles the 'manage what arrived while I was recording that video' problem. For individual contributors with primarily text-based communication, Loom may be unnecessary if the team doesn't have a video-first culture. alfred_ is useful for anyone with meaningful email and calendar workload, regardless of whether they use video.
Loom's free tier was cut to 25 videos lifetime. What are the realistic alternatives?
The strongest Loom alternatives depending on use case: Vidyard offers a free plan with 4K recording and 15 AI-generated videos per month, the best free tier in the market for most users who don't need Atlassian integration. Descript ($12/month) is unique for anyone who edits video by editing text transcripts, a genuinely different workflow for content creators and podcasters. Veed (from €22/month) is the simplest option for quick social and explainer content with easy text overlay and transcription. If the Atlassian ecosystem is not your primary environment, Vidyard's free tier is the most direct Loom replacement for most teams.
Try alfred_
Manage What Arrives While You're Recording
Loom helps with what you send. alfred_ manages what arrives: the email triage, the calendar context, the daily briefing that tells you what today actually requires before you record a single video. $24.99/month.
Try alfred_ Free