COMPANY SIZE: 20–300 employees, Seed–Series C, $2M–$30M ARR IDEAL ROLE: RevOps Manager, Head of Sales, Customer Success Lead, or Operations Manager at SaaS companies with distributed or remote-first teams running high-volume customer communication INDUSTRY: B2B SaaS, customer success, sales, professional services TRIGGER SIGNALS: Company going remote or hybrid, sales or CS team scaling, screen recording mentioned in job posts, async communication culture forming
POSITIONING ANGLE Don't sell async video — sell meeting reclamation. The pain isn't "we need better screen recordings"; it's "our team is in Zoom 25 hours a week and can't ship." Loom's pitch is that every 5-minute Loom replaces a 30-minute meeting, and that compounds fast across a 50-person revenue team. Lead with the meeting hours recovered, not the video quality. SUBJECT LINE Your team is in too many meetings — async video fixes that OPENING (first 2 sentences) Noticed your team is growing the sales and CS function while staying remote-first — that's exactly when async video communication stops being a nice-to-have and starts being the difference between a team that ships and a team that's perpetually in status meetings. The teams we work with at your stage typically reduce meeting load by 40% within 60 days of adopting async video workflows.
1. LINKEDIN: "Remote-first" or "distributed team" mentioned in company description → async culture is a stated value 2. JOB BOARDS: "Screen recording" or "async video" mentioned in CS or sales job postings → workflow is being adopted 3. TWITTER/X: Team lead posts about meeting overload or "we need async" → active pain being voiced 4. COMPANY BLOG: Post about remote work, async communication, or "how we run meetings" → operationalizing new norms 5. CRUNCHBASE: Remote-first or distributed company raises round → async tooling investment typically follows