Headline communicates an outcome, not just a feature

Feature-based headlines describe what the product has. Outcome-based headlines describe what the visitor gets. The distinction matters because visitors are not buying a feature — they are buying a result: faster shipping, fewer support tickets, a design that doesn't embarrass them. When the headline names only a feature ("AI-powered analytics dashboard") or a technology attribute ("Real-time collaboration platform"), the visitor must do mental translation work to connect the feature to their own situation. Many of them won't bother. Headlines that name the outcome — "See what's actually driving revenue" — do that translation for the visitor, making the product immediately relevant without effort.

Read your current <h1> aloud and ask: "Is this about the product, or about me (the user)?" If it describes the product's capabilities rather than the user's future state, reframe it.

Transformation examples:

Before: "AI-powered project management"
After:  "Ship what your team actually finishes"

Before: "Real-time collaboration platform"
After:  "Your team, finally on the same page"

Before: "Enterprise-grade security"
After:  "Ship fast without compromising compliance"

The reframe is one step: find the outcome the feature enables, and lead with that. In app/page.tsx, locate the <h1> and update the string. If the headline is rendered from a CMS or from a constants file (lib/constants.ts, content/home.mdx), trace the source and update it there so all pages remain consistent.