AsakanaYC F26 landing page report.
← Back to YC F26

Your landing page’s weakest score is Trust.

How Asakana ranks

  1. 1.Cut+Dry72
  2. 2.Asakana70
  3. 3.Pepper67
  4. 4.OrderEZ60
Fix Trust

Score over time

757065605550Pepper 55 on May 17 (Wayback)Pepper 61 on Jun 7 (Wayback)Pepper 61 on Jul 3 (Wayback)Pepper 58 on Aug 10 (Wayback)Pepper 62 on Aug 29 (Wayback)Pepper 62 on Sep 12 (Wayback)Pepper 67 on Sep 20 (Live)Cut+Dry 61 on Apr 22 (Wayback)Cut+Dry 62 on May 8 (Wayback)Cut+Dry 62 on May 20 (Wayback)Cut+Dry 64 on Jun 6 (Wayback)Cut+Dry 72 on Sep 20 (Live)OrderEZ 60 on Apr 14 (Wayback)OrderEZ 62 on May 13 (Wayback)OrderEZ 60 on Jun 9 (Wayback)OrderEZ 60 on Sep 20 (Live)Asakana 54 on Apr 21 (Wayback)Asakana 70 on Sep 20 (Live)Apr 21Sep 20
Past reportsShow past reportsHide past reports
  1. Sep 20, 202670LiveOverall +16 · Trust +24 · Mobile web +20Viewing
  2. Apr 21, 202654First tracked report — strongest Value props 72, weakest Trust 28View →

Trust

52Fair

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

Asakana
Cut+Dry
OrderEZ
Trust read
Asakana"Backed by Y Combinator" badge
PepperProduct demo parsing "Hey I need 20 pounds tomato…" into order line items (Tomatoes | 20lb, Iceberg Lettuce)
Cut+DryCase card: "75% customer adoption in less than a year — Harbor Foods, multi-location broadline distributor" over a real
OrderEZDetailed product UI screenshot showing inventory table with order callout "Ninkasi $2,276.63 COMPLETED"

CTA

68Fair

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

Asakana
Cut+Dry

Problems

  • click feels like a sales-call commit
  • no value payoff in the label
  • no low-friction alternative CTA

Mobile web

72Fair

The phone experience as a first-class citizen.

Mobile web annotations on the mobile capture123
  1. Overlapping demo card — The WeChat message card renders on top of a ghosted 'ERP ORDER DRAFT' table, producing an unreadable jumble of superimposed text.
  2. Broken tofu characters — The message ends in placeholder boxes (missing-glyph characters), which reads as a rendering bug on mobile.
  3. Book a Demo button — The primary CTA is desktop-proportioned, spanning roughly half the column instead of a thumb-friendly full-width tap target.

Information hierarchy

74Fair

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

Information hierarchy annotations on the desktop capture123
  1. WeChat message card — The raw message text wall with heavy highlighting demands close reading and shows the problem, not the ERP-draft outcome Asakana promises.
  2. Broken emoji glyphs — Tofu boxes (口口口) at the end of the message card read as a rendering bug and undercut polish at the key demo moment.
  3. Seven-link nav row — Six nav items plus Login sit at equal weight beside 'Book a Demo', giving seven exits before the primary action.

Value props

82Strong

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

Asakana’s headline sellsAutomate order entry for food distributorsOrders from text, calls, voicemail, email and WhatsApp become drafts in your system.

Working

  • Names exact buyer: food distributors
  • Lists all five messy input channels
  • Hero shows real WeChat order being parsed

Could improve

  • No numbers: time saved, error rate, order volume
  • Pain of manual keying never named
  • Mobile hero demo renders as jumbled overlap

Competitors

inferred from product, audience, and value prop