The hero targets a self-serve individual ("Get Loom for free," "the easiest screen recorder you'll ever use") while the body pivots to enterprise signals — SSO, SCIM, custom data retention, a dedicated Enterprise section, and testimonials from a Chief People Officer and a Co-CEO. A solo user who lands on "free" and "easy" reads three sections before hitting enterprise security copy and loses the thread of what they signed up for. An enterprise buyer who lands on the page sees "free" and "easiest screen recorder" and wonders if this is a serious tool for their org. Split the page into two distinct paths above the fold — a self-serve entry and a team/enterprise entry — or pick the primary buyer and build the page for them, with the secondary path as a secondary CTA.

Every async video tool, every Vidyard, every Zoom clip feature, every Slack huddle could run this headline without changing a word. The page has a real positional claim available — Loom is the tool that replaces the meeting you were about to schedule, the email chain that was about to take three days — but the hero buries it in the subheadline behind "AI-powered" and "supercharge productivity," two phrases that appear on competitors' pages verbatim. Kieran Flanagan's testimonial ("Begin writing an email. Get to the second paragraph and think 'what a time suck.' Record a Loom instead.") is the sharpest articulation of Loom's actual value on the entire page, and it's sitting in a carousel. Move that specific behavior — the moment of switching from email to video — into the hero, because that's the word Loom should own: the replacement.

" in the body with its own "Learn more" link, but it's positioned as a product announcement rather than a reason to choose Loom over anything else. This is the most differentiated thing on the page — no competitor is offering automatic Jira ticket population from a screen recording — and it's treated like a changelog entry. A developer or engineering lead who lands on this page and is evaluating Loom against Zoom's built-in recording or Slack clips would have no idea this feature exists until they scroll past the hero, past the "easiest screen recorder" section, past the editor features. Pull the bug report capability into the hero or into a dedicated above-the-fold proof point aimed at engineering buyers, because right now the page's most defensible claim is hidden behind generic copy.

Katie Burke's quote about connecting personally without "75 different one-on-one calls" directly addresses the meeting-replacement use case. Erica Goodell's quote about "hundreds of hours" directly addresses ROI. David Okuinev's quote about executive communication directly addresses the enterprise buyer. None of these are placed adjacent to the claim they support — they're pooled together in a rotating strip that treats all proof as interchangeable. Anchor each testimonial to the section it validates: put the hours-saved quote next to the productivity claim, put the executive quote next to the Enterprise section, put the meeting-replacement quote in the hero.