stripe.com
Score by dimension
Copy uses product-centric language ('accept payments', 'financial services') rather than developer vernacular ('payment rails', 'revenue optimization', 'settlement reconciliation') that Series B technical buyers use internally.
Top gap: Replace 'accept payments' with developer-specific pain point like 'eliminate payment infrastructure rebuilds' or 'stop managing 5+ payment vendor integrations.'
Copy addresses generic growth without triggering the specific Series B inflection point: scaling payment volume, vendor consolidation, or margin pressure from payment processing costs.
Top gap: Add context to the trigger: 'When payment volume exceeds [X], legacy processors fail—standardize on a single platform' or reference the Series B funding → revenue acceleration timeline.
Rules: No outcome signals matched.. LLM: Outcomes are vague ('grow your revenue', 'work individually or together') and lack measurable specificity; 'from your first transaction to your billionth' is scale-as-metaphor, not a concrete outcome metric..
Top gap: Headline must name a measurable, time-bound outcome (e.g. '47% lift in 90 days').
4 named logo(s) detected; 32 testimonial block(s); 1 case study link(s); 24 quantified ROI claim(s)
Top gap: Add specificity to existing proof (named customers, dollar amounts).
What this scan misses
The 5th dimension (channel-audience alignment) needs media and attribution data a URL scan cannot read. The full Reality Audit covers all 5 dimensions in 12 days.
If you are stripe.com, embed your grade with the Reality Audit badge.