Claims are specific and substantiated, not generic

Generic claims — "fast", "the best", "easy integration", "trusted by teams" — have been used on so many product pages that visitors filter them out on sight. They create no credibility because they cannot be verified and no competitor would dispute them. Specific claims — "average response time: 45ms", "2,400 SaaS teams", "connects to Slack in 2 clicks" — create credibility precisely because they can be verified and could be wrong. A visitor reading specific claims perceives that the company is confident enough to commit to a checkable statement. When more than 40% of a page's claims are generic, the page loses its signal-to-noise ratio: the specific claims get buried under the generic ones.

Audit your home page for its 5-7 most prominent claims. For each, classify it: does it include a number, a named entity, a concrete mechanism, or a verifiable outcome? If not, either make it specific or remove it.

Transformation patterns:

"Fast"                    → "Average response time: 45ms"
"Trusted by many teams"   → "Used by 2,400 SaaS teams"
"Easy integration"        → "Connects to Slack in 2 clicks"
"Works with any tool"     → "Works with GitHub, Linear, and Notion"
"Secure"                  → "SOC 2 Type II certified, AES-256 encrypted at rest"

If you cannot make a claim specific because the evidence doesn't exist yet, remove it. Three specific claims are more persuasive than three specific claims buried under five generic ones. Update the claims in whichever component renders the hero and features sections — typically app/page.tsx, components/HeroSection.tsx, or a features data array.