PageGoblin PageGoblin

The Hoard / B2C SaaS

catchable.io landing page review.

Goblin scored catchable.io 5.9/10 across twelve conversion dimensions on 02 Oct, 2026.

Goblin's Score

5.9

Out Of 10

"Catchable knows who it is and what it does. Clear value prop, solid demo, good copy. But missing named users, no pricing transparency until the FAQ, and the second CTA form could vanish."

catchable.io

/

02 Oct, 2026

Full Report

8/10

Hero clarity

Goblin understands in five seconds: AI chat to-do extraction, linked to source, no manual work.

What You Got Right

  • Headline 'Your AI chats are full of to-dos. We catch them.' is direct and names the audience (people who chat with AI)

    • What's Wrong

  • Subheadline mentions 'No copying, no pasting, no forgetting' but glosses over WHO specifically benefits most
  • 'Early access · Claude first' tag is vague about what 'early access' means and who gets it

    • 8/10

    CTA prominence

    One clear CTA above fold: 'Join waitlist' button in hero form is visible and single-mindedly focused.

    What You Got Right

  • Single, unambiguous CTA in hero with email input and submit button, no competing links or secondary actions above fold

    • What's Wrong

  • Button label 'Join waitlist' is generic; doesn't signal exclusivity or founding member discount mentioned in FAQ
  • No visual emphasis (color, size, micro-copy) to make the CTA feel urgent or special vs. a standard form

    • 8/10

    Value prop specificity

    Goblin sees the benefit clearly: real commitments extracted from chat, linked back, no manual effort. Concrete and specific.

    What You Got Right

  • Value prop names exact outcome: 'No copying, no pasting, no forgetting' and shows a demo with three to-dos caught from one conversation

    • What's Wrong

  • Doesn't quantify time saved or volume (e.g., 'saves 10 minutes per day on task capture')
  • For whom exactly? Entrepreneurs, engineers, product managers, or all AI users? Unclear persona.

    • 2/10

    Trust signals

    Goblin sees nothing trustworthy above fold: no user counts, no logos, no testimonials, no named customers, just Catchable saying 'trust us.'

    What's Wrong

  • No user count, no logos, no early adopter testimonials anywhere above fold or within one scroll
  • Footer mentions 'Mono' (the company behind Billable) but no link context or proof that Billable users vouch for Catchable

    • 7/10

    Copy concreteness

    Goblin likes the examples: 'email the three beta users by Friday and ask for quotes' is specific. 'Remind me to test the webhook on staging' is real. Copy avoids buzzwords.

    What You Got Right

  • Demo conversation uses actual phrases and contexts ('Stripe webhook,' 'staging,' 'domain renewal') that feel authentic, not made-up

    • What's Wrong

  • FAQ answer 'We plan to charge $8 a month' uses vague future tense; should say 'Costs $8/month after launch' or 'Currently $5 for waitlist signups'
  • Section 'You make plans in chat. Then the chat scrolls away' is abstract; could name the pain more sharply ('Lost 40 client follow-ups last week to a closed tab')

    • 1/10

    Social proof depth

    Goblin finds zero social proof anywhere: no named testers, no quotes, no logos, no case studies, no user counts. Page assumes credibility from silence.

    What's Wrong

  • No testimonials, no named early users, no case studies showing who used it and why
  • Mentions 'Mono' (Billable team) but provides no proof that Billable customers trust Catchable or that early testers validate the concept

    • 6/10

    Objection handling

    Goblin sees FAQ answers on security, pricing, and availability, but no objection handling on the main page. Privacy concerns are buried in separate sections.

    What You Got Right

  • Security section addresses 'No screen reading' and 'Items, not transcripts,' showing restraint and data minimalism

    • What's Wrong

  • Pricing buried in FAQ: most visitors won't scroll that far. '$8/month, $5 for waitlist' should be above fold or near CTA
  • No objection on 'Will it actually catch my to-dos?' until FAQ. Main concern (false positives/negatives) deserves inline reassurance

    • 7/10

    Visual hierarchy

    Goblin sees clear hierarchy: h1 headline dominates, demo splits conversation and board side-by-side, smaller sections follow. Eye flow is logical.

    What You Got Right

  • Hero section (h1 + subheadline + form) is visually distinct from body sections; demo is two-column and easy to scan

    • What's Wrong

  • Three-step section (Step 1, Step 2, Step 3) uses numbered list but visual weight is flat; no icon or color to differentiate from other h3 sections
  • Footer links ('Terms', 'Privacy', 'Cookie settings') are small and de-prioritized; no clear next step after FAQ

    • 7/10

    Mobile rendering

    Goblin can't see the rendered page but HTML structure suggests responsive design: form inputs use proper type attributes, labels are semantic, no fixed widths indicated. Likely mobile-friendly.

    What You Got Right

  • Form uses <label for>, <input type='email'>, inputmode, autocomplete attributes — best practices for mobile input

    • What's Wrong

  • Demo section (data-demo) is two-column in HTML; likely stacks to one column on mobile but Goblin cannot verify rendering
  • No indication of font sizes, tap targets, or viewport meta in preprocessed HTML; assuming responsive but cannot confirm mobile UX

    • 6/10

    Page speed signals

    Goblin sees clean, minimal HTML structure with few inline styles or heavy third-party scripts (preprocessed). Astro static site generation is efficient, but Goblin cannot verify actual load time.

    What You Got Right

  • Minimal semantic HTML, no heavy external libraries visible in main content, Astro framework suggests static site generation

    • What's Wrong

  • Google Analytics consent banner and cookie settings button present; likely loading Google Analytics, which adds overhead
  • No preload hints, no image optimization clues visible; Goblin cannot assess image sizes or lazy loading

    • 8/10

    Form and CTA friction

    Goblin approves: email + optional website field, no credit card gate, no captcha, one-click submit. Low friction entry to waitlist.

    What You Got Right

  • Single required field (email), optional secondary (website), clear submit button labeled 'Join waitlist,' no login or payment required

    • What's Wrong

  • Form repeats twice on page (hero + footer); second form is redundant and reduces perceived urgency
  • No error messaging example visible; 'One email when we launch' is reassurance but doesn't address what happens if already on waitlist

    • 3/10

    Pricing clarity

    Goblin has to scroll to the FAQ to learn pricing: '$8 a month regular, $5 locked for waitlist.' This should be visible above fold or near the CTA.

    What's Wrong

  • Pricing is hidden in FAQ accordion, not visible until user clicks 'What will it cost?'
  • No mention of $5 founding price near the CTA; missed opportunity to make waitlist irresistible ('Lock in $5/month for life')

    • Priority Fixes

  • Move pricing ($5 founding, $8 regular) into or near the hero CTA to justify the action and reduce FAQ scrolling
  • Add social proof: 3-5 named early testers or a user count (e.g., '200+ on the waitlist') above the fold or in the demo section
  • Remove the duplicate waitlist form in the footer and replace it with a single-form focus or a different CTA (e.g., 'Read the blog' or 'See the docs')

    • Things Goblin Respected

  • The demo is concrete and real: shows three actual to-dos caught, one skipped, and the exact conversation phrases that trigger the catches
  • The product knows its limits: 'It won't be perfect, which is why every item lands for your review' is honest and builds trust
  • Copy avoids jargon and stays specific: 'email the three beta users by Friday,' 'Stripe webhook on staging,' 'renew the domain before the 12th' — all real language from real work