WhoBuilt

Cursor Head of Design Roasts Startup Websites

Nov 20, 2025· 36 min· 184K views·Watch on YouTube

Speaker

Rio Lu, head of design at Cursor, reviews YC founder websites built partly or fully with Cursor alongside the host on Y Combinator’s Design Review.

Make the product clear

Reviewing Crunch, Rio and the host found the hero vague and its motion distracting. They recommended a literal subheadline that explains the product for investment bankers, investors, and consultants. Rio also advised using consistent design tokens and components, and avoiding default AI styles such as purple gradients and oversized shadows.

Explain what makes the product different

Velvet’s videos looked striking, but the page did not explain what a brand video was, who the product served, or how it differed from tools such as Sora. Clavis AI added confusion with two product names, many competing calls to action, and jargon such as “progressive discovery.” Rio recommended describing customer problems in familiar language and showing which tools the product connects.

Keep the experience consistent and specific

CodeCrafters’ pages changed styles and colors, and its company name was hard to find. Slashy had clear messaging, but inconsistent screenshot sizes, borders, and alignment weakened the presentation. Rio and the host also advised prioritizing what a product does before emphasizing YC backing or other credibility signals.

Make the audience and next step obvious

Freya clearly explained its AI voice agents for customer service and offered an accessible demo, though the page hijacked scrolling and its main call to action, “Meet the team,” was unclear. Finta’s accounting and tax service looked polished, but the audience of U.S.-based C corps, LLCs, and PBCs could appear earlier. For Vibe Flow, Rio recommended showing example projects and letting visitors try a constrained demo before requiring sign-in.

Design useful waiting states

While trying Vibe Flow, Rio explained that AI products should show what is happening during a wait, including running actions and any user confirmations. Progress information should focus attention without becoming a wall of text; random messages and multiple unexplained spinners can distract. The demo’s inconsistent details, unclear controls, repeated failures, and sign-up wall made it harder to understand or try.

Takeaways

  • Put a plain-language description of the product and its intended audience near the top of the page.
  • Explain the customer problem and how the product differs using terms customers already understand.
  • Give each page one clear primary action and make the next step predictable.
  • Use consistent typography, spacing, components, and product imagery across pages.
  • For AI waits, show useful progress and let visitors try a focused demo before asking them to sign in.

Mentioned in this talk

Search inside this talk

What was claimed 15

Show all 15 facts

Related talks

Cursor Head of Design Roasts Startup Websites, Rio Lu · WhoBuilt