Hero supporting text reinforces the headline

The hero headline and its immediately following supporting text are read as a unit — visitors process them together in their first pass. When the supporting text introduces a different topic than the headline, visitors receive two half-messages instead of one complete one. Neither registers clearly. For example, a headline about speed ("Ship faster") followed by sub-text about security ("Enterprise-grade security for your team") leaves the visitor unsure which of the two attributes is the actual value proposition. The dissonance also signals inconsistency in how the product thinks about itself — a subtle trust signal. The sub-headline's job is to answer the question the headline raises, not to pivot to a new claim.

Read the headline and sub-text together and ask: can you summarize both in one sentence? If not, rewrite the sub-text to amplify or specify what the headline already started.

Paired examples:

Headline: "Ship faster"
Weak sub-text: "Enterprise-grade security for your team."  ← different topic
Strong sub-text: "Deploy to production in one click — no CI pipeline to configure."

Headline: "Never lose a customer again"
Weak sub-text: "Our platform leverages advanced ML to power your workflow."
Strong sub-text: "Predict churn 30 days early and automate retention outreach."

The sub-text's structure should be: [verb or result] + [mechanism or specificity]. In app/page.tsx or components/HeroSection.tsx, locate the <p> or sub-headline element immediately below the <h1> and update it to answer the question the headline raises.