OnePatchYC F26 landing page report.
← Back to YC F26

Your landing page’s weakest score is Trust.

Fix Trust

Score over time

85807570656055Resolve AI 72 on Feb 10 (Wayback)Resolve AI 72 on Feb 28 (Wayback)Resolve AI 69 on Apr 2 (Wayback)Resolve AI 71 on May 4 (Wayback)Resolve AI 71 on Aug 8 (Live)Cleric 78 on Aug 8 (Live)Traversal 75 on Apr 14 (Wayback)Traversal 64 on Apr 29 (Wayback)Traversal 70 on May 12 (Wayback)Traversal 66 on Jun 4 (Wayback)Traversal 71 on Jun 30 (Wayback)Traversal 70 on Jul 10 (Wayback)Traversal 69 on Aug 8 (Live)Deductive AI 61 on Aug 12 (Live)OnePatch 73 on Aug 8 (Live)OnePatch 65 on Sep 15 (Live)Aug 8Sep 15
Past reportsShow past reportsHide past reports
  1. Sep 15, 202665LiveOverall −8 · Value props −14 · Information hierarchy −13Viewing
  2. Aug 8, 202673First tracked report — strongest Information hierarchy 81, weakest Trust 55View →

Trust

56Fair

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

OnePatch
Cleric
Resolve AI
Trust read
OnePatch"Backed by Y Combinator" badge above the headline
Resolve AICustomer logo wall: Coinbase, DoorDash, Expedia Group, Snowflake, Zscaler
ClericBanner: 'Cleric Named a Gartner® Cool Vendor in AI for SRE and Observability'
TraversalProduct UI screenshot: 'Production World Model™ — 1,749,612 total nodes, 30 node types' with details panel
Deductive AIBanner: "Excited to announce that Deductive AI is joining forces with Elastic"

CTA

62Fair

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

OnePatch
Resolve AI
Traversal
Cleric

Problems

  • demo click feels costly and sales-gated
  • no self-serve CTA despite Install nav
  • button small vs headline, off to the right
  • no supporting secondary CTA

Value props

62Fair

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

OnePatch’s headline undersellsStop Shipping Blind.Ship at agent speed. OnePatch instruments your stack, verifies every PR in prod, and fixes what breaks.

Working

  • Hero screenshot shows real fixes in flight
  • Subhead uses concrete verbs: verify, fix
  • YC badge adds instant credibility

Could improve

  • H1 sells visibility, not auto-resolution
  • No numbers or proof points in the fold
  • On-call pain never mentioned

Information hierarchy

68Fair

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

Information hierarchy annotations on the desktop capture123
  1. Book A Demo button — Primary CTA is small, right-aligned below the subhead, and styled identically to Sign In and Docs, so nothing marks it as the one action.
  2. Docs nav button — Docs is boxed with the same weight as the demo CTA, creating an equal-weight exit right in the scan path.
  3. Subheadline block — Right-aligned value prop sits detached from the headline across the fold divider, forcing a Z-scan jump before the visitor reaches the CTA.

Mobile web

76Fair

The phone experience as a first-class citizen.

Mobile web annotations on the mobile capture12
  1. Book A Demo button — Desktop-proportioned button floats small in the phone column instead of going near full-bleed for the thumb.
  2. Cropped incident cards — Product screenshot bleeds off the right edge, cutting incident titles like 'Gmail requ…' mid-word and reading as broken.

Competitors

inferred from product, audience, and value prop