How can a startup clarify its value proposition if the description is confusing?

Use concrete examples of the service provided (e.g., 'refueling', 'changing tires') instead of general terms like 'servicing.' Quantify the efficiency gains for users, like managing more properties, to clearly articulate the value proposition.

What's the best way to launch an MVP for a user-generated content platform with minimal initial content?

Ensure the platform has replay value or focus on a smaller community that finds it useful, like early Facebook at Harvard. Consider 'priming' the platform by scraping existing content or user accomplishments from other sites.

How can founders get users or sales for products that take a long time to develop?

Use off-the-shelf technology for early prototypes to demonstrate capability. For sales, generate letters of intent or pilot agreements. Alternatively, start by selling the service manually before the full product is ready.

Should I charge for my MVP if it involves real costs, like services requiring people?

Yes, you should charge from day one for services with real costs. Offering services for free when there are expenses can lead to losing money and customers when prices eventually equalize the demand.

What are the best methods for capturing feedback after launching an MVP?

Focus on 'doing things that don't scale' initially. Personally call users, invite them to your office, host dinners, or create a WhatsApp group. This high-bandwidth feedback is crucial when you don't yet know the right questions to ask.

How should founders decide whether to continue with an MVP that lacks product-market fit or pivot?

Time-bound your efforts, committing to trying everything for a set period (e.g., six months). Use objective measures, like a skeptic's test, to determine if sufficient progress is being made. If not, be open to pivoting.

Is it important to patent a new technology service before releasing an MVP?

For a startup designed for rapid growth, the primary focus should be on finding users, building a product, and generating revenue. Patents are typically more relevant after achieving product-market fit, not as a prerequisite for an MVP.

Key Moments

YC SUS: Michael Seibel and Eric Migicovsky discuss How to Launch an MVP

Y Combinator

Science & Technology6 min read55 min video

Jan 24, 2020|64,567 views|1,293|42

Save to Pod

Key Moments

TL;DR

Launching a Minimum Viable Product (MVP) requires radical honesty about value, user pain, and iterative market testing. Even a bad product can succeed if it solves severe pain, but founders must avoid prolonging failure by setting clear time bounds for iteration.

Key Insights

If customers are willing to use a 'pretty bad' product because it uniquely solves their problem, that's a strong market signal, whereas needing a polished product to attract users suggests competitors are already performing well.

Instead of building a product from scratch, consider layering your MVP onto existing platforms as a Chrome extension or overlay for less effort and easier user acquisition.

If you lack domain expertise, immerse yourself in the industry: become a property manager for a week or volunteer to learn core pain points rather than guessing, as this learning phase can be expensive but necessary.

To validate user-generated content platforms, focus on a smaller, dedicated community or ensure the platform has high replay value, as demonstrated by Facebook at Harvard or 9GAG scraping content initially.

For hardware or high-risk MVPs (like self-driving cars), start with off-the-shelf components and simpler versions (e.g., a golf cart prototype) to demonstrate capability and validate core concepts before full-scale development.

When deciding whether to charge for an MVP with real costs, charge from day one, potentially even more than existing solutions, to rigorously test demand and identify users with the most significant pain.

The most effective feedback collection for early MVPs involves non-scalable methods: personal calls, hosting dinners, or WhatsApp groups, because you likely don't yet know the right questions to ask.

When pitching investors, present your current MVP and traction first, followed by the business model and then the long-term vision, to provide context and enable clear evaluation of your progress.

The core principle of MVP: solving severe pain points

The fundamental idea behind an MVP is to test if your product solves a problem people care enough about to use something imperfect. If you can find a small group of users (even just 10-100) who are willing to use a 'pretty bad' product because it addresses a significant pain point that existing solutions don't, that's a very good sign. Conversely, if you need a highly polished product to attract any users, it indicates that competitors are likely doing a good job. This principle applies across various industries, from software to hardware. The goal is to minimize effort while maximizing learning about user needs and the viability of your solution. Founders should be skeptical of their own product's value and have internal critics challenge its utility.

Strategies for building and launching MVPs

When entering a market with established competitors, consider overlaying your MVP onto existing products. For instance, a Chrome extension can add new data to an existing analytics platform without requiring users to switch entirely. For user-generated content platforms, where initial content is crucial, focus on creating replay value or cultivating a small, dedicated community, similar to Facebook's early days at Harvard. Alternatively, founders can actively generate initial content by scraping from other platforms or manually curating user achievements before the platform is live. For hardware or high-risk ventures like self-driving cars, start with off-the-shelf technology and simpler prototypes (e.g., a modified golf cart) to demonstrate capability and validate core concepts before investing heavily in custom development.

Gathering essential domain knowledge

If you're entering an industry where you lack personal experience, like property management or car care, it's crucial to gain deep domain knowledge. This might involve immersing yourself completely, such as becoming a property manager for a short period or volunteering with existing businesses. This hands-on learning is vital because it helps identify generalizable pain points and avoid building features that are too specific to initial clients. Without this insight, you risk building features that don't scale or offer broad market appeal. Prioritize understanding pain points users are already trying to solve with other tools, as they are more receptive to new solutions.

Iterating towards product-market fit

After launching an MVP, the key is to iterate based on genuine user value, not just adding features. Founders should be highly skeptical, asking if their current MVP provides any value. If not, they must find users experiencing severe pain and get them to use the MVP, then re-evaluate. This often involves iterating on the market rather than just the product. For example, Superhuman's founder identified that founders and sales professionals derived the most value from their early product, prompting a focus on that demographic. Founders can also experimentally 'turn off' their product (e.g., simulating server outages) to gauge user reaction and identify critical dependencies, a tactic impossible for large companies but feasible for startups.

Charging for your MVP and validating demand

For MVPs involving real costs (e.g., sending service providers), it's essential to charge from day one. This rigorously tests demand and identifies users who are truly desperate for the solution. In some cases, charging more than existing alternatives can be a powerful validation tool, forcing the question of whether people genuinely want what you're offering beyond just a cheaper option. The goal is to validate the novel aspect of your offering—like home service delivery—rather than the basic service itself, which may already be established. Generating Letters of Intent (LOIs) or pilot agreements, even without set pricing, can also serve as early sales validation for investors.

Managing founder conflict and decision-making

Co-founder conflict, especially regarding company direction, should be addressed proactively and respectfully. Avoidance often leads to founder breakups. A structured approach involves agreeing on tests to validate a particular direction and setting clear timeframes for experiments. If the experiment fails, the direction can be adjusted; if it succeeds, skepticism can be overcome. Brainstorming sessions should aim to generate a broad list of ideas first, without immediate filtering, before prioritizing. This prevents preemptively dismissing potentially valuable concepts and encourages a more thorough evaluation of possibilities.

Customer feedback and the 'do things that don't scale' principle

For early MVPs, prioritize high-bandwidth, non-scalable feedback methods. This includes personally calling users, inviting them to your office, hosting dinners, or creating WhatsApp groups. These methods are crucial because, at this stage, you likely don't know all the right questions to ask. Direct conversations allow for broad information gathering and the ability to probe deeply into user experiences. Documenting these interactions and debriefing regularly with co-founders can uncover critical insights for MVP refinement, like identifying a specific demographic (e.g., singles) that heavily uses the tool and tailoring experiments towards them.

Communicating with early customers and investors

When engaging early B2B customers or investors, honesty is paramount. For customers, frame the 'beta test' as a close collaboration where their feedback is vital for success, potentially even a premium feature that commands higher value. This avoids later disappointment for both parties. Similarly, with investors, ask clarifying questions about their feedback or the process instead of pretending to understand. This demonstrates sophistication and ensures alignment. Presenting your current MVP and traction before your long-term vision is crucial for investors to build context and evaluate your progress effectively, rather than just a grand, unproven idea.

Mentioned in This Episode

●Products

●Software & Apps

●Companies

●Organizations

MVP Launch & Iteration Checklist

Practical takeaways from this episode

Do This

Focus on testing your core hypothesis with the least effort.

Consider layering MVPs onto existing popular products (e.g., browser extensions).

If entering a competitive space, find a niche problem not solved by incumbents.

For UGC platforms, ensure replay value or a smaller, highly engaged community.

For complex products, start with simpler, safer versions (e.g., autonomous wheelchair before car).

Generate initial content yourself for UGC platforms if needed.

When clarifying your description, use concrete examples and avoid jargon.

Focus on problems people are already trying to solve.

Charge from day one for services with real costs.

Charge more than existing solutions to test desperation and value.

Study competitors thoroughly and understand why they failed.

If unsure about your MVP's value, turn it off temporarily and see if users complain.

Be a skeptic of your own MVP; have someone in your company challenge its value.

When pitching, present your current product first, then traction, business model, and finally vision.

Be honest with early B2B customers about the beta stage; frame it as close collaboration.

Don't inflate expectations; be transparent about the MVP status.

For platform risks, consider lifestyle businesses or rapid monetization if heavily dependent on another platform.

If you have real costs, charge from day one.

Time-bound your efforts to pivot if product-market fit isn't found.

Be honest with investors and customers.

Avoid This

Don't expect users to accept a polished product on day one if competitors exist.

Don't confuse automation of existing property manager tasks with replacing property managers.

Don't build features that are not generally applicable or based on assumptions without validation.

Don't assume that because something is done on paper it's broken and needs software.

Don't aim for a million users on day one for a UGC platform.

Don't introduce jargon in your company description.

Don't underestimate the price sensitivity of users in certain markets.

Don't launch a beta product as a full enterprise solution without disclosure.

Don't rely solely on white-label services if aiming for a scalable software company.

Don't price under your value; lean towards over-pricing.

Don't assume you know what happened at the 'beginning' of famous companies like Uber; research deeply.

Don't focus on patents before achieving product-market fit, users, and revenue.

Avoid building a business into perpetuity on a platform that could shut you down.

Don't rely on a platform (like YouTube) forever if it has leverage over your business.

Don't avoid difficult conversations with co-founders.

Don't dismiss ideas prematurely during brainstorming.

Common Questions

Focus on finding a small population of users with a problem that existing solutions aren't addressing. It's better to have users who are willing to use a less polished product because it uniquely solves their pain point, rather than requiring a highly polished product from day one.

Topics

Technology & Innovation Business & Entrepreneurship Pricing Strategy Product Development Startup Strategy Customer Acquisition Minimum Viable Product User Feedback Market Validation Feature Prioritization

Mentioned in this video

Companies

A platform mentioned as an example of a user-generated content network that started by scraping and faced issues when it went down.

High Five

A local news website aiming to help people in their 20s and 30s meet new friends with similar hobbies and lifestyles.

Justin.tv

A past company mentioned as an example of building a product with a scrappy MVP that users were willing to use despite its flaws.

Segment

A company whose idea was met with skepticism by a co-founder but gained traction on Hacker News, validating its demand.

Uber

Used as an example to explain that initial strategies, like the expensive Uber Black in San Francisco, were not always about heavy subsidies or the 'beginning' as commonly believed, but rather solving acute pain points.

Zephyrus

An analytics platform for competitive gamers, providing game-specific tools and data to analyze, track, and improve performance.

A professional networking platform mentioned in comparison to Fridge Worthy, noting its use as a social network.

Embark

A company building self-driving trucks, which they started as a cop car and later a rigged golf cart for demos.

Carnuba

A provider of an online back office and field service management platform for independent car care professionals.

Fridge Worthy

A social network where people share their accomplishments, with a question about launching its MVP.

Bien A Stop

A home wellness service and products marketplace for people's wellness objectives.

Blue

A platform where housewives resell products from suppliers using WhatsApp, compared to MeShow.

YouTube

A platform that poses a significant risk for businesses heavily reliant on it, as the platform itself could block services or compete with them.

PayPal

Mentioned alongside eBay as an example where a service became so mainstream on a platform that shutting it down caused backlash.

Airbnb

Mentioned as an example of a company that used 'doing things that don't scale,' like having a co-founder's direct phone number for customer service, in its early days.

Swish Technologies

A company building self-driving cars for ride-sharing and retirement communities, facing long development cycles.

eBay

Mentioned alongside PayPal as an example where a service became so mainstream on a platform that shutting it down caused backlash.

9GAG

A meme website that started by scraping content from other sites, cited as an example of building a user-generated content network.

GitHub

A platform where people participate, mentioned in the context of user-generated content networks.

Organizations

Y Combinator, mentioned in reference to its database of startups and advice given to founders.

Software & Apps

Crunchbase

A platform mentioned as an example of generating content by itself (media reports) before users started caring about their profiles.

Periscope

A live video streaming platform that was popular but discontinued by Twitter, serving as an example of platform risk.

TaskRabbit

A company mentioned for its iterative approach, starting broadly and then focusing on specific services like IKEA furniture setup.

Hacker News

A platform where Segment's co-founder tested the demand for his idea, which unexpectedly became a top story.

Media

Vine

A platform that was popular but eventually shut down by Twitter, used as an example of how platforms don't always maintain popular third-party services.

Products

Raspberry Pi

Off-the-shelf technology that hardware companies can use to build rudimentary versions of their products.