Kat Mañalac - How to Launch (Again and Again)

Core Philosophy Shift: Launch should be redefined from a singular, high-stakes event into a continuous, iterative process; assuming consistent shipping of new features, a startup is "always launching."

Risks of Perfectionism: Teams spending six months perfecting pixels before launch risk failing to gain traction on release, leading to startup failure before a second opportunity arises.

Strategic Value of Continuous Launching:

• Allows founders to practice and refine pitches before a full product exists.
• Validates whether an MVP resonates with users.
• Helps identify the correct target user segments by comparing response rates across different channels.

Silent Launch:

• Requires only a domain name, company name, short description, contact info, and a call to action (e.g., newsletter signup).
• Example: Product Hunt's "Ship" tool allows pre-launch companies to collect interest.
• Observation: In a sample of 10 Startup School companies, only ~50% possessed a functional landing page.

Friends and Family Launch:

• Intended for idea-stage pitch testing or early MVP feedback.
• Methodology: Founders should observe friends/family using the product and ask specific feedback questions.
• Limitation: This group often lacks representativeness as ideal users; founders should exit this phase rapidly.
• Historical Example: Reddit's initial launch was restricted to its YC batch founders before expanding.

Launch to Strangers (Market Validation):

• Purpose: To confirm "hair on fire" problems and willingness to pay/download.
• Case Study (Lug): Before building the app, founders rented a truck, stationed themselves at Ikea, and manually fulfilled delivery requests for users struggling to tie down cargo to manually validate demand.

Online Community Launches:

• Internal YC Launches (Bookface): A low-risk environment with ~4,000 founder peers; ideal for early feedback.
• Startup School Forum: Recommended for immediate testing with ~40,000 founders who provide high-quality product feedback.
• Case Study (Magic): A simple landing page shared on Reddit and Hacker News generated 40,000 signups overnight, pivoting the company from a blood pressure app to an on-demand personal assistant.
• Platform Comparison: Conversion rates for launches on TechCrunch, Product Hunt, and Hacker News are converging in terms of user acquisition and customer conversion.
• Best Practices for Community Launches:
  • Research community-specific rules and moderators before posting.
  • Connect with existing community members for advice if not already an active participant.
  • Tone: Write conversationally ("like you talk") and avoid marketing jargon; focus on intellectual curiosity and problem-solving insights.
  • Engagement: Proactively suggest specific topics for discussion to guide user questions.

Request for Access Launch (Waitlist & Viral Loops):

• Used to manage high demand and incentivize virality.
• Mechanisms: Implement waitlists and allow users to skip the line via actions like tweeting or referring others.
• Case Study (Superhuman): Utilized a referral system and email signatures ("Sent by Superhuman") to drive organic growth and user acquisition.

Influencer and Blogger Outreach:

• Strategy: Identify industry lists or blogs via SEO search (e.g., "best wedding website builders") and pitch for inclusion.
• Efficiency: Can yield high impact with low volume; one company contacted 50 bloggers, secured 4 responses, and achieved massive early growth.
• Constraint: Avoid paying for placements at early stages; seek creative, non-paid routes for inclusion.

Hardware/Physical Product Pre-orders:

• Utilize pre-order campaigns to fund production and validate demand.
• Case Study (Sheer Text): Launched unbreakable pantyhose via a compelling video, Hacker News, Product Hunt, and a network of friends/investors, successfully navigating a male-dominated audience.

New Feature/Product Line Launches:

• Case Study (Stripe): Consistently launches new products (e.g., Stripe Atlas) via Hacker News threads, blogs, and press, maintaining high community engagement.
• Case Study (Glossier): Operates on a scientific cadence (every 6–8 weeks), activating all launch vectors (community, social, press, ads) for every product release.

Building Independent Communities:

• Founders should start building email lists and networks immediately, even pre-product.
• Case Study (Symmetria): Founder Gaddy Evron built a database of hundreds of contacts over time; this list facilitated a high-impact TechCrunch launch and secured VC social sharing.

Forward-Looking Advice:

• Do not delay development to prepare for a single "launch day"; treat launch as a continuous lifecycle.
• Leverage Demo Days and existing networks (like YC partners) for support, though response times may vary during those periods.