Sep 5, 2018 · 59m · y-combinator
Michael Seibel - Building Product · Y Combinator
0:00 / 0:00
▶ Watch on YouTube →
gold bands on the timeline = statements, start to end. Hover to read, click to jump. CC turns on captions
At Y Combinator Startup School, YC CEO Michael Seibel outlines essential strategies for building successful startup products, focusing on tight problem definition, customer analysis, rapid iteration, and disciplined execution. Drawing from his experiences co-founding Justin.tv and Twitch, Seibel delivers actionable guidance on validating MVPs, tracking event-driven metrics, and converting desperate early adopters into loyal users.
How this conversation actually went
Every chapter scored 0–10 on four independent dynamics. Hover any point for the reasoning behind the score. The partners hold 97% of the talking time here. How this is scored →
The partners as informed peer 0.0 Guest teaching 0.0 Guest disagreement 0.0 The partners pushing back 0.0
speaking balance: gold is the partners, purple is the guest (3 minute bins)
Sharpest disagreement ▶ 52:05 Audience member pushes on zero revenue KPI tracking
An audience member questions whether a startup should really track revenue as their primary KPI when making zero dollars.
Hardest push from the partners ▶ 52:25 Seibel bluntly defends strict KPI trackingSeibel firmly rejects avoiding the revenue metric, stating that seeing a zero should motivate the founder without excuses.
Biggest teaching moment ▶ 27:57 Seibel calls out ineffective analytics toolsSeibel corrects founders relying solely on Google Analytics, explaining why events-based platforms are mandatory for product development.
The partners hold their own ▶ 46:05 Dismantling the Steve Jobs visionary mythSeibel methodically lists the technical flaws of the original iPhone to demonstrate that true innovation comes from continuous iteration rather than infallible artistic dictation.
the scores for every segment, with the reasoning behind each
| Chapter | Topic | The partners as informed peer | Guest teaching | Guest disagreement | The partners pushing back | Why |
|---|---|---|---|---|---|---|
| Core Survival Principles and Personal Background | 0 | 0 | 0 | 0 | This segment is a solo lecture monologue detailing Michael Seibel's early startup background and survival factors at Justin.tv. Because there is no guest interaction, all scores are zero per monologue scoring rules. | |
| Defining the Problem You Are Solving | 0 | 0 | 0 | 0 | Solo lecture segment outlining the importance of defining startup problems clearly and narrowly, illustrated with the Poppy case study. As a monologue, all interactive dynamics are zero. | |
| Identifying and Analyzing Your Target Customer | 0 | 0 | 0 | 0 | Monologue covering customer profiling, frequency versus intensity of user pain points, and pricing strategies. Per monologue instructions, all scores remain zero. | |
| Validating the MVP and Product Utility | 0 | 0 | 0 | 0 | Solo presentation emphasizing fast MVP construction and warning founders against treating products like precious artwork. As a monologue, all scores are zero. | |
| Customer Targeting, Pricing Strategies, and Handling Bad Customers | 0 | 0 | 0 | 0 | Monologue advising founders to target desperate early adopters, avoid bad customers, and structure enterprise discounts effectively. Zero interactive dynamics apply. | |
| Establishing Effective Product Metrics and Analytics | 0 | 0 | 0 | 0 | Solo instruction on selecting event-based metrics over standard pageview analytics and making tracking integral to product specifications. Scores are zero for monologue delivery. | |
| Structuring a Repeatable Product Development Cycle | 0 | 0 | 0 | 0 | Monologue recounting early development failures at Justin.tv and prescribing a structured, objective bi-weekly product sprint cycle. All scores are zero. | |
| Distinguishing Pivoting from Iterating and Avoiding Product Dictatorship | 0 | 0 | 0 | 0 | Solo lecture defining pivoting versus iterating and warning against acting like 'fake Steve Jobs' who ignores customer feedback. Monologue scoring rules apply. | |
| Case Study: Listening to Users and the Transformation of Twitch | 0 | 0 | 0 | 0 | Monologue concluding the presentation with a case study on how listening directly to gaming streamers enabled the transition from Justin.tv to Twitch. All scores are zero. |
Statements from this episode (22)
Seibel: Early Justin.tv founders paid themselves $500 monthly
“We were each given 500 dollars a month walking around money, which technically is against the law because it was below minimum wage, but who cares about laws?”
Seibel: Justin.tv survived due to technical founders, low spending, and ego
“Those were the three things that saved our company, made our company work, and strangely, I don't even think, if you take one of those things away, any one of them, we would have died.”
Seibel: Founders unable to state their problem in one sentence lack understanding
“The first thing I ask founders, can you state the problem clearly in two sentences? If you can't, you don't know the problem, right? In fact, it should really only take you one sentence. So if someone asks you a problem you're solving and you find yourself del…”
Seibel: On-demand marketplace models require easily replaceable labor with common skills
“The Uber model only works because there's a whole bunch of basically replaceable people with a common skill. Well, it turns out the people who've got the skills to watch infants and make parents comfortable with that tend to have nanny jobs where they work lot…”
Seibel: Car buying websites are built for dealerships, not car shoppers
“It turns out a lot of the car buying websites are not built for the person who's shopping for a car, because that person doesn't have a problem very often. They're actually built for the person who's selling a car. That person has a problem every day. Every da…”
Seibel: Low-frequency, low-intensity problems make customer acquisition extremely difficult
“And so if you have both an infrequent and low intensity problem that you're trying to solve, you're going to have a problem getting a lot of customers even interested in talking to you.”
Seibel: Startups should almost always launch with a price, not for free
“So strangely, starting with a higher price or a price is almost always better than starting free. Almost always better.”
Seibel: Building an MVP in two weeks prevents problem and customer drift
“Typically, the longer it takes, the more you're going to have MVP and problem drift or customer drift. If you decide to only build your MVP in two weeks, it's a lot easier to stay on task and make sure actually solving that problem for that customer.”
Seibel: MVPs are bad, so startups must target the most desperate customers
“It's an MVP. You know you've made something bad. Like, that's the definition of MP. It's bad. So the real question is like, how do you find people who are willing to use a bad product? Right? They have to be the most desperate. The most desperate. And so a lot…”
Seibel: Founders should ignore product feedback from investors and friends
“The kind of community of startup people and or investors usually don't have the problem that you're solving. So if you're using investors as a trigger for, am I solving the right problem? Or like, Do they find this useful? It's almost never the case. I'm almos…”
Seibel: Startups cannot build sophisticated products without event-based analytics
“For all of those things, you want an events-based metrics product. Mixpanel, Amplitude, Heap. I think we funded like, 50 of them. There are like, a hundred of them out there. You should be using one of them. If you're not, you can't be sophisticated at buildin…”
Seibel: Startups should track only 5 to 10 stats initially
“If your analytics product has got too many analytics in it in the beginning, it will be hard to use. And part of what you're doing, if you've never used product like Mixpan before, is learning how to use it. And most importantly, teaching your employees and yo…”
Seibel: Justin.tv's 2006 chat-right, video-left layout survived unchanged on Twitch
“The major product decisions that Justin TV made that carried through to Twitch to today was chat on the right, video on the left. We decided that in 2006. It is the same way, 2018.”
Seibel: Primary startup KPI must be revenue or daily active users
“Almost always, if you ever are going to charge money to your customers, this number should be revenue. Almost always. If you are never going to charge your customers money, like Facebook, then maybe it should be a usage based metric. Like how often do your cus…”
Seibel: Solving a startup problem typically takes two years, not months
“So, if you're not thinking that the process of coming up with a solution for this problem is probably more like a two-year process, you're doing it wrong. If you are unsatisfied with significant progress in under two years, you're probably doing it wrong.”
Seibel: Pivoting changes the customer or problem; iterating changes the solution
“So, I define pivot As changing the customer or changing the problem. This should be rare. This should happen infrequently. Many times this means you should start a new company. I defined iterate as changing the solution.”
Seibel: Steve Jobs released a 'shitty MVP' iPhone and iterated every year
“Real Steve Jobs released a shitty MVP that was revolutionary, but still fairly shitty, and every year iterated it. Until you have the thing in your pocket right now, which is pretty damn good. Real Steve Jobs iterates and talks to customers. Fake Steve Jobs ju…”
Seibel: Gamers were 20% of Justin.tv traffic for years before Twitch launched
“Gamers have been streaming on Justin TV since almost the beginning. At any given time, they were 20% of our traffic for years.”
Seibel: Justin.tv reached $24M in five years, then $1B in three
“And if you look at the history of Justin TV, in the first five years, it went from being worth nothing to being worth about twenty four million dollars. In the next three years, it went being worth twenty four million dollars to being worth a billion.”
Seibel: Startups must track revenue as their KPI even when it's zero
“If your KPI is revenue, and the number is zero, should you still be tracking that as your top line KPI? The short answer is yes. You should be depressed looking at that number every week until, like, that's the answer.”
Seibel: The top presale mistake is discounting below breakeven
“The number one mistake I see with presales is discounting. The number one mistake is that basically, especially hardware founders will misunderstand how much they need to charge so they don't lose money, and so their pre-sale becomes their death.”
Seibel: Justin.tv's biggest product mistake was spending months swinging for home runs
“Our mistake was that at JustinTV. It was thinking every time, we've got the home run. Let's only swing for home runs. And of course, it would take three months to do it, because we gotta make it perfect, right? And then the whole spike, spiral of death.”