YC SUS: Aaron Epstein and Eric Migicovsky give website feedback

Hosts & Format: Aaron Epstein, a 2010 YC alum and co-founder of Creative Market, reviews websites of Startup School founders to provide direct feedback on clarity, design, and conversion.

Methodology: Reviews simulate a first-time user experience; feedback prioritizes "one-liners" (clear value propositions) over visual aesthetics, noting that if a visitor cannot instantly understand the product, the design does not matter.

Common Failure Modes:

• Vague Positioning: Founders often lead with broad, abstract vision statements (e.g., "business solutions reimagined," "future proof local and global decisions") rather than specific use cases or target audiences.
• Feature vs. Benefit: Sites list technical features (e.g., "backlink monitoring") without explaining the resulting user benefit (e.g., "rank higher in search results").
• Trust Deficits: Unprofessional design, missing logos, lack of SSL indicators, or "bare bones" templates significantly reduce credibility, especially for products handling money or sensitive data.
• Navigation & CTA Issues: Confusing Call-to-Action buttons, buried contact information, and mismatched domain types (e.g., .org for for-profit entities) create friction.

Specific Startup Feedback:

• SEO Buddy:
  • Critique: The "20 minutes of work" claim feels insufficient and the "daily missions" concept is undefined.
  • Action: Move feature descriptions (backlink monitoring, competitor research) higher; focus on "superpowers" (benefits) rather than features; experiment with auto-popping "talk to me" audio.
• CompuTest (Crypto Tax):
  • Critique: Lacks visual credibility and trust signals; the email link for "find out what we mean" is a poor conversion path.
  • Action: Build trust first with logos, product images, or founder stories; define a single clear goal (e.g., "schedule a consultation") above the fold.
• Sapsen:
  • Critique: Confusing positioning between a dating app, a community platform, and a marketplace; Russian-language content creates barriers for English-speaking reviewers.
  • Action: Clarify the core value proposition immediately; move tangible app screenshots to the top; ensure language consistency.
• Narration Box:
  • Critique: The AI audio demo sounds "robotic" and fails to match the "state-of-the-art" claim; unclear developer targeting (SDK vs. API).
  • Action: Highlight unique differentiators (e.g., emphasis on specific words) over generic AI claims; provide clear developer onboarding paths (SDK docs) immediately.
• Deco Echo:
  • Critique: Confusing business model (marketplace vs. B2B service); heavy reliance on wall-of-text and vague "upcycling" definitions.
  • Action: Focus on the specific customer journey (e.g., "T-Mobile sent waste, artist made a bag, we sold it"); lead with product visuals (marketplace) rather than abstract concepts.
• Breezy (Pet Insurance):
  • Critique: The "calculator" is abstract and uses industry jargon (reimbursement limits) that scares users; missing standard footer elements.
  • Action: Frame scenarios around user pain points (e.g., "My dog broke a leg, how much will I pay?"); add founder stories to humanize the brand.
• Taxonomy (Consulting):
  • Critique: Heavy jargon ("business solutions reimagined") obscures the offering; site appears to be for personal sales rather than inbound leads.
  • Action: Define specific industry specialization; use case studies to demonstrate expertise; ensure SSL is enabled.
• Day One (App Marketing):
  • Critique: Unfocused value proposition mixing "campaign effectiveness" with "fraud detection"; confusing domain name (day1.com vs day1.ai).
  • Action: Interview users to adopt their language; consolidate value props to the single most important benefit (e.g., "reduce bot traffic" or "optimize ad spend").
• Water Loom:
  • Critique: Overly broad messaging ("connect the common denominator"); inconsistent UI design and poor readability; .org domain confuses for-profit intent.
  • Action: Select one strong headline; answer FAQs directly on the page to avoid email handoffs; fix UI hierarchy and contrast.
• Boostly:
  • Critique: Vague value prop; confusing data database concepts for restaurant owners; ineffective "blinking" social proof notifications.
  • Action: Lead with the clear subtitle ("smart marketing for restaurants"); use specific customer case studies (e.g., "Joe's Restaurant doubled sales"); remove distracting animations.
• Loop Earplugs:
  • Critique: Imagery fails to reflect common use cases (music festivals vs. industrial); "20dB" jargon is not explained; clickable Wired article links do not work.
  • Action: Show product in real-world context (festivals/work); clarify that the product is non-electronic; fix broken media links.
• Form Facade:
  • Critique: "Wall of text" description; confusing pricing structure (free vs. paid tiers); small "Try It Free" CTA.
  • Action: Lead with the visual "Before/After" comparison of Google Forms; simplify copy to "Embed Google Forms with custom styling"; clarify the free tier.
• Crawl:
  • Critique: Primary page targets the wrong audience (job seekers vs. recruiters); confusing navigation between "developer portfolio" and "job crawling" features.
  • Action: Use the "resume builder" page as the homepage; clearly identify the target audience (developers) in the header.
• Unremote:
  • Critique: English language errors; relies on industry generalities rather than product specifics; video links are broken.
  • Action: Highlight specific features (e.g., "single-click video") with larger screenshots; use customer testimonials to explain unique value.
• Move Halal:
  • Critique: MVP is unclear; lacks logo and location visibility; too many "Shop" buttons confuse the product scope.
  • Action: Clarify the value prop ("Instacart for Halal products"); focus MVP on one vertical (e.g., meats) to test demand; ensure location availability is prominent.
• ReadUp:
  • Critique: Confusing between "distraction-free reading" and "social news aggregator"; unclear differentiation from Twitter/Facebook.
  • Action: Pivot to the community aspect (social reading platform); emphasize the "comment-only-after-reading" mechanic as a unique feature.
• Just Juno:
  • Critique: Website lacks basic information; scrolling images are too fast and blurry; value proposition is missing.
  • Action: Explicitly state it is an "interactive storytelling app for girls to learn Indonesian history"; replace scrolling images with static, descriptive screenshots.
• CallSwitchboard:
  • Critique: "Reminders" is confusing terminology; users cannot visualize how the elderly receive messages; key info buried in body text.
  • Action: Use a numbered list to explain the 3-step process (Record, Schedule, Receive); clarify the delivery mechanism (automated call).
• Softer:
  • Critique: Overpromising features (marketplaces, web apps, etc.) makes the value prop unclear; risk of feature bloat.
  • Action: Narrow focus to "website builder for startups"; allow users to edit a live demo on the site to demonstrate ease of use.
• Parsler Jr.:
  • Critique: Unclear service model (cooking vs. delivery); lack of visual context for the Indian lunchbox system; generic graphics.
  • Action: Clarify the "mom cooks, we deliver" model; use authentic photos of the logistics system (e.g., rickshaw delivery); link directly to WhatsApp for inquiries.
• General Happiness App:
  • Critique: Too broad ("achieve your happiness"); fails to describe the core product (goal tracker) on the homepage.
  • Action: Lead with the specific feature (goal tracking); explain the "small steps to big changes" philosophy on the app page first.
• JOINT:
  • Critique: URL is hard to spell; too much text and abstract concepts; black background feels negative; unclear core use case.
  • Action: Simplify the messaging to one core function; use a lighter color scheme; ask users to explain the value in their own words.
• Growth Channel:
  • Critique: Unclear service scope (ad buying vs. management); hidden expertise buried in tiny text; confusing industry focus.
  • Action: Lead with specific niche expertise (e.g., "Fintech ad specialists"); explicitly state what "running ads" entails; use case studies to prove results.
• Habitor:
  • Critique: Confusing app category (goals vs. events vs. workouts); unclear accountability mechanism; mixed platform links (iOS vs. Android).
  • Action: Focus on a single use case (e.g., workout accountability); clarify the "event" definition; fix platform discrepancies.
• G Links:
  • Critique: Auto-scrolling GIFs prevent user control; brand collaboration metrics are hidden in tabs; unclear free vs. paid model.
  • Action: Replace auto-scroll with static examples of influencer pages; move "brand reviews" above the fold; clarify the "build page for free" CTA.
• Brains (Entrepreneur Network):
  • Critique: Overuse of wordplay ("Brains," "Aims," "FundsHub") confuses the user; inconsistent design reduces trust.
  • Action: Use standard terms ("projects," "funding"); consolidate messaging to a single clear value prop; remove conflicting CTAs.
• Product Voice:
  • Critique: Value proposition buried; unclear if the product is a changelog tool or a feedback dashboard; looks like a landing page for a nearly finished product.
  • Action: Lead with "Add a changelog to your site with one click"; embed the live product on the homepage to show functionality immediately.
• Paper Flight:
  • Critique: Too broad ("share any content"); "content everything platform" is meaningless; enterprise focus is not immediately clear.
  • Action: Pivot to "Track attachment open rates"; frame as a "DocSend alternative" for sales teams; clarify pricing to avoid unnecessary demo booking for lower-tier plans.

General Strategic Recommendations:

• One-Liners Matter: The most critical feedback is improving the "one-liner" to answer "What is this?" and "Who is it for?" before any visual design tweaks.
• User Testing: Founders should not rely solely on internal feedback; they must test with strangers using tools like UserTesting.com or FullStory to observe where users get stuck.
• Show, Don't Tell: Replace abstract claims (e.g., "easy to use") with concrete examples or step-by-step visual walkthroughs.
• Focus on One Use Case: Avoid trying to serve "everyone"; focus on the single segment that gets the most immediate value to simplify the messaging.
• Trust Signals: Ensure the site looks professional (logos, SSL, consistent design) to build credibility, especially for financial or data-heavy products.
• Sync Pitch and Web: The website must reflect the current version of the pitch; founders should update their sites after receiving feedback on their "one-liners."