PollenYC W26 landing page report.
← Back to YC W26

Your landing page’s weakest score is Trust.

How Pollen ranks

  1. 1.Rogo72
  2. 2.Hebbia71
  3. 3.Pollen70
  4. 4.Brightwave53
Fix Trust

Score over time

80706050Rogo 72 on Sep 20 (Live)Hebbia 68 on Apr 4 (Wayback)Hebbia 74 on Apr 25 (Wayback)Hebbia 59 on May 15 (Wayback)Hebbia 62 on Jul 11 (Wayback)Hebbia 61 on Aug 21 (Wayback)Hebbia 59 on Sep 8 (Wayback)Hebbia 71 on Sep 20 (Live)Brightwave 62 on Mar 24 (Wayback)Brightwave 65 on Apr 13 (Wayback)Brightwave 66 on Apr 21 (Wayback)Brightwave 53 on Sep 22 (Live)Pollen 70 on Aug 12 (Wayback)Pollen 70 on Sep 21 (Live)Aug 12Sep 21
Past reportsShow past reportsHide past reports
  1. Sep 21, 202670LiveCTA −4 · Information hierarchy +2Viewing
  2. Aug 12, 202670First tracked report — strongest Information hierarchy 76, weakest Trust 56View →

Trust

54Fair

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

Pollen
Rogo
Hebbia
Trust read
Pollen"Backed by Y Combinator | Robinhood Ventures" badge above the headline
RogoCustomer/partner logo strip: Tiger Global, Moelis, Nomura, Société Générale, Rothschild & Co, BNP Paribas, Raymond James
HebbiaCustomer logo row: Morgan Stanley, MetLife, Centerview, OHA (mobile capture)
BrightwaveNo visible trust signal identified.

CTA

64Fair

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

Pollen
Rogo
Hebbia

Problems

  • 'demo' implies sales-call cost
  • no value or payoff in copy
  • hero button small vs headline
  • no headline language echo

Value props

76Fair

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

Pollen’s headline sellsEmail Paul your work. Get it done, your way.Hire an AI employee trained on your firm’s exact workflows. Same results, in minutes.

Working

  • "Email Paul" makes the mechanic instantly concrete
  • "AI employee" frames value as headcount, not tooling
  • "in minutes" names a speed outcome

Could improve

  • No hard numbers or proof metrics in the fold
  • Illustration decorates; never shows email-in, file-out
  • "Same results" is unverifiable without an example

Mobile web

76Fair

The phone experience as a first-class citizen.

Mobile web annotations on the mobile capture123
  1. Hero Book a demo — Desktop-proportioned button floats at a third of the column width instead of a thumb-friendly full-bleed tap target.
  2. File-name ticker row — Items like Investment_Co… and Consolidated_Holdings clip mid-word at both screen edges, reading as broken layout.
  3. Header link row — How it works, Why Us, and Security vanish on mobile with no hamburger, cutting off secondary navigation paths.

Information hierarchy

78Fair

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

Information hierarchy annotations on the desktop capture123
  1. Duplicate Book a demo — Header 'Book a demo' repeats the hero CTA at equal weight, splitting the one action across two targets.
  2. Low-contrast CTA button — The lavender 'Book a demo' fill sits close in value to the cream background, weakening the one-second find.
  3. Nav links row — 'How it works', 'Why Us', 'Security' plus 'Sign in' give four exits before the visitor reaches the demo ask.

Competitors

inferred from product, audience, and value prop