CofiaYC W26 landing page report.
← Back to YC W26

Your landing page’s weakest score is Trust.

Fix Trust

Score over time

80706050403020Process Street 68 on Jun 13 (Wayback)Process Street 69 on Jun 26 (Wayback)Process Street 68 on Jul 12 (Wayback)Process Street 69 on Aug 5 (Wayback)Process Street 68 on Aug 26 (Wayback)Process Street 68 on Sep 9 (Wayback)Process Street 69 on Sep 22 (Live)Scribe 63 on Sep 5 (Live)Tango 61 on May 13 (Wayback)Tango 62 on May 28 (Wayback)Tango 56 on Jun 9 (Wayback)Tango 31 on Jun 17 (Wayback)Tango 62 on Jul 1 (Wayback)Tango 62 on Sep 19 (Wayback)Tango 74 on Sep 20 (Live)Skan.ai 67 on Feb 4 (Wayback)Skan.ai 66 on Mar 17 (Wayback)Skan.ai 68 on Apr 4 (Wayback)Skan.ai 73 on Jul 28 (Live)Soroco 37 on Apr 18 (Wayback)Soroco 59 on Jul 20 (Wayback)Soroco 65 on Jul 28 (Live)Cofia 64 on Apr 21 (Wayback)Cofia 64 on Sep 22 (Live)Apr 21Sep 22
Past reportsShow past reportsHide past reports
  1. Sep 22, 202664LiveInformation hierarchy +16 · Value props −14Viewing
  2. Apr 21, 202664First tracked report — strongest Mobile web 76, weakest Trust 38View →

Trust

42Poor

Proof that the product is real, competent, and safe to try.

Cofia
Skan.ai
Process Street
Trust read
Cofia"Backed by Y Combinator" badge in the desktop navigation
Process StreetDetailed product screenshot showing the "Infrastructure Fund Utility and Energy Investments Process" workflow with numbe
Scribeimplicit context Scribe may benefit from pre-existing familiarity among its target audience.
TangoStylized product demo panel showing "Capturing your clicks" with numbered Click and Fill out steps
Skan.ai"Trusted by Global Leaders" stat band: "4 in 5 Top US Banks" through "1 in 4 Fortune 50"
SorocoNo visible trust signal identified.

Value props

58Fair

Title, subtitle, hero — do they sell the product's true value?

Cofia’s headline undersellsComplete workflow mapping for AI automation that actually worksFor ops team with people-heavy processes.

Working

  • 'actually works' hits AI-fatigue pain
  • Names a concrete capability: mapping
  • Targets a specific buyer: ops teams

Could improve

  • Subhead adds no outcome or specifics
  • Typo: 'ops team' reads sloppy
  • Hero art decorates, shows no product

CTA

68Fair

Copy, size, verb, cost-feel — does the primary CTA earn the click?

Cofia
Tango
Process Street
Scribe
Skan.ai

Problems

  • 'Request' feels like asking, not getting
  • click implies form + waitlist delay
  • no payoff echo from the headline

Mobile web

70Fair

The phone experience as a first-class citizen.

Mobile web annotations on the mobile capture12
  1. Request access button — Desktop-proportioned button; should be near full-bleed for thumb reach on mobile.
  2. Four-line hero headline — Headline barely scaled down, wrapping into four heavy lines that dominate the fold.

Information hierarchy

84Strong

Does the design help or inhibit what the page is trying to say?

Information hierarchy annotations on the desktop capture123
  1. Subline copy — "For ops team with people-heavy processes" has a typo and low-contrast grey type that under-weights the audience message.
  2. Y Combinator badge — The boxed outbound badge is the most visually prominent nav element, drawing attention away from the CTA path.
  3. Blog Security links — Two exit links sit above the fold before the visitor reaches the single conversion action.

Competitors

inferred from product, audience, and value prop