Cursor's head of design reviews startup websites built with AI

Executive overview

Most AI-built startup websites share the same core failure: visitors can't answer "what is this?" within five seconds. Ryo Lu, head of design at Cursor, reviews seven YC founder websites and surfaces the same gaps repeatedly — vague headlines, cluttered CTAs, jargon-heavy copy, and visual inconsistency that signals vibe-coded output.

The fix isn't more polish. It's clearer thinking about message, audience, and hierarchy before reaching for a tool.

Visitors ask four questions in order: what is this, is it for me, does it work, is it credible — most sites fail at question one.

The four questions every homepage must answer

• What is this? — visitors should know within five seconds, without reading sub-headlines
• Is it for me? — speak directly to the target user in their language, not yours
• Does it work? — show proof through demos, case studies, or specific customer quotes
• Is it credible? — social proof matters, but only after the first three questions are answered
• Don't lead with credibility (YC logo, investor names) before explaining the product
• Every section should have one clear CTA; eliminate competing buttons and links

Hero section fundamentals

• If you use a clever or aspirational headline, add a literal sub-headline that explains exactly what the product does
• Name the company clearly — visitors shouldn't have to hunt for it
• Never start the hero with a negative ("stop doing this") without immediately stating what you offer instead
• Jargon from your internal vocabulary means nothing to first-time visitors; use words your users already say
• The book-a-demo or sign-up CTA should be above the fold, not buried below it

Visual quality and AI default styles to avoid

• AI slop signals: massive shadows, purple gradients, generic Helvetica typography, sloppy alignment
• Use system fonts if unsure — safe defaults beat bad choices
• Define a small set of core design tokens (colors, spacing, type scale) before generating UI; AI composes well from a solid foundation
• Inconsistent component styles — different icon sets, mixed shadow treatments, varying border radii — read as unfinished
• Don't clip, animate, or parallax elements randomly; motion should direct attention, not steal it
• Scroll-jacking removes control from the user; avoid it

Messaging and copy

• Talk in the user's problems, not your product's concepts — nobody asks for "progressive discovery"
• Show the before/after: the old world and the new world, the problem and how you solve it
• If your product integrates with many tools or services, show all of them visually; a logo grid is clearer than a list
• Avoid framing like "transform your workflow" without showing the specific workflow
• Six words of product description and five CTAs is the wrong ratio; invert it
• Quotes and testimonials help, but don't make visitors extract your value prop from them

Demos and interactive elements

• Make the demo the primary CTA if it's your strongest asset — Freya (voice AI) was the clearest site reviewed, largely because the demo was immediate and accessible
• Constrain initial demos to produce good output; a broken first run kills trust
• Don't gate the product behind a sign-up wall before showing value — let users try at least one action first
• For AI products with wait states, show what the model is actually doing (tool calls, steps in progress) rather than generic spinners or looping placeholder messages

Specific site findings

• Crunched: headline too vague for non-target visitors; logo carousel hover animation broken; needed a literal sub-headline explaining the product
• Velvet: striking video demos but almost no copy; visitors couldn't distinguish it from Sora or other video models; logo too small; pricing appeared before the product was understood
• Clavis AI / Strata: two brand names created immediate confusion; jargon-heavy section headers ("progressive discovery, smart navigation, precise execution") explained nothing; Excel-screenshot-style chart undermined credibility
• Codecrafters: purple gradients throughout; company name absent from hero; inconsistent design across marketing pages, product, and pricing; about page linked out to YC launch page instead of a dedicated page
• Slashy: messaging relatively clear but littered with alignment issues, inconsistent image sizes, mixed shadow styles, and competitor logos used as identity crutches
• Freya: best site reviewed — clear messaging, accessible demo, good language for enterprise audience; main fix needed was changing "meet the team" CTA to "book a demo"
• Finta: clever time-based copy ("back to building by 5:12 PM") landed but the target customer (US-based C-Corps) was buried far down the page; visual hierarchy broke down mid-scroll due to inconsistent card and section treatments
• Vibeflow: prompt-first product showed nothing before sign-up; error states hit during review; UI felt fully AI-generated with no coherent design system; suggestions appeared before any user action

Breaking out of the template

• Many YC sites share the same structural template: top nav, two-button hero, logo strip, feature grid, pricing — this is fine for clarity but forgettable
• If brand differentiation matters, break the template deliberately; don't break it by accident
• A focused, plain site with strong messaging outperforms a visually busy site with weak copy
• Prioritise: what the product is → who it's for → proof it works → who built it