Jan 29, 2020, 3:09 PM ETConference Presentation, Webinar, Fireside Chat, Interview

YC SUS: Kat Mañalac and Eric Migicovsky discuss Week 2 SUS Lectures

Reject the "Perfect Launch" Myth: Spending weeks perfecting a single channel is inefficient; prioritize speed over perfection to maximize "surface area" for discovery.
Recurring Launch Value: Every launch reaches a new audience (approx. 0.00001% of the world) since most people remain unaware of the startup, making repeated launches necessary for feedback and growth.
Channel Optimization: Allocate only a few hours to a few days per channel for messaging and feedback; avoid weeks of stress on individual channels unless launching specific campaigns (e.g., Kickstarter or press pitches).
Re-launching Updates: Treat major product updates as new launches, utilizing the same channels (Product Hunt, Hacker News, email, blog posts) used for the initial release.
Marketing as Engineering: Apply iterative testing to marketing messages, using actual user quotes to refine messaging before a public re-launch.

Waitlist Efficiency: The longer users remain on a waitlist, the harder they become to re-engage; launch an MVP as quickly as possible.
Hypothetical vs. Real Testing: Validate features by building the smallest working solution (MVP) and giving it to users; avoid asking users about hypothetical future features or solutions they haven't experienced.
Pricing Experiments: In B2B/enterprise, pricing can be A/B tested privately without public announcements; founders often charge too little and should not fear high prices given the alternative of internal engineering costs.
Hardware Validation: Success requires selling the first single unit; do not attempt mass production or revenue scaling before proving one customer loves the product.
Non-Scalable Hacking: Use manual workarounds (e.g., standing outside a store to deliver services) to validate demand before automating or building full infrastructure.

Segment Interview Groups: Separate interviews into "non-users" (to understand the problem/existing solutions) and "current users" (to get feedback on improvements); do not mix these contexts.
Incentive Warning: Do not pay users to answer surveys; if a user requires financial incentive to discuss a problem, it likely lacks a "burning" pain point.
Context Over Solutions: Focus interviews on understanding the user's daily life and problem frequency rather than asking what features they want; let the user's narrative flow naturally.
Network Effects: For products relying on network effects, ensure the MVP is useful even for a single user to prevent early adopters from leaving due to a lack of initial network.
Geo-Targeted Launches: Launch in specific metro areas by leveraging personal networks, local events (e.g., standing outside IKEA), and physical tactics (e.g., door hangers, elevator ads).

Influencer Outreach: Success in influencer marketing is a numbers game; expect low response rates (e.g., 1 response from 50 emails) and be prepared to send hundreds of emails.
Micro-Communities: Target specific Facebook groups, subreddits, or niche Twitter hashtags (e.g., parents of children with cerebral palsy) rather than solely focusing on top-tier influencers.
Media Relations for Biotech: Time launches around specific events like paper publications or conferences; pitch to specialized reporters (e.g., Fierce Biotech, STAT) with exclusive angles.
Avoiding "Whale Hunting": Startups should avoid targeting large enterprises (e.g., Walmart) as first customers; target smaller, accessible customers who can make quick decisions and provide rapid feedback.
Reference Strategy: Use "X for Y" comparisons (e.g., "Uber for movers") only if the reference is a widely recognized household name and the analogy is clear.

Revenue vs. Growth: Organic revenue from the first single sale is the only valid start; do not assume success requires selling thousands of units immediately.
Funding Sources: Prioritize funding from customers to reduce reliance on investor capital; this approach makes future fundraising easier.
Pivoting Permission: Founders are permitted to rebuild or relaunch if user discovery reveals the initial hypothesis is incorrect; stopping a non-working model is not failure but a necessary learning step.
Municipal Sales Cycles: Selling to governments requires understanding budget cycles (6-12 months) and verifying line items; there are no reliable "hacks" to accelerate this timeline.
Dual Audience Management: When users (kids) differ from payers (parents), narrow the niche to where the user and payer are the same entity (e.g., IB students) to align incentives.

Bio/Healthcare Launches: Avoid "breaking things"; ensure HIPAA compliance and ethical considerations are met before launching; consider partnering with existing compliant platforms to avoid legal hurdles.
Re-launching "Dead" Companies: Investors look for evidence of deep industry insight and lessons learned from previous pivots rather than just the fact of the return.
Porch Ship Launch: Launching in a specific city requires manual ground operations and leveraging local networks rather than relying on broad digital marketing.
Inspirit (Smartwatch): Attach sensors to existing devices (e.g., other smartwatches via Bluetooth) to validate the technology before building custom hardware.
Wellen (Yoga): Expand within the current city first to perfect the MVP; adding multiple locations simultaneously complicates iteration and product development.