Product Market Fit - the only thing that matters
Jack breaks down Marc Andreessen's famous 2007 essay on why market beats team and product every time, then plays a clip of Michael Seibel explaining why most founders who think they've found product-market fit haven't — before closing with a friend's theory on how AI is quietly collapsing PMF for companies like Chegg overnight.
This is a solo essay episode. Jack is staring down product-market fit at his own startup, Layer Code, and pulls together the two pieces of writing on the topic that have shaped his thinking most: Marc Andreessen's 2007 essay on startups, and Michael Seibel's post on what real PMF actually feels like.
Along the way he plays clips from both an ad-read customer testimonial and the Seibel interview, and closes with a friend's theory on how AI is raising the bar for what counts as a satisfying product almost overnight.
The Q&A below is experimental — extracted from the episode transcript with AI. If you spot a mistake, let us know at jack@scalingdevtools.com.
Marc Andreessen's essay: team, product, or market — which matters most?
Andreessen wrote this in 2007, and it's still incredible. Look at a broad cross-section of startups — 30, 40, or more, enough to screen out pure flukes — and two things jump out. First, there's an incredibly wide divergence of success: some insanely successful, some highly successful, many somewhat successful, plenty that outright fail. Second, there's an equally wide divergence in the caliber of the three core elements of any startup: team, product, and market. The team can range from outstanding to remarkably flawed, the product from a masterpiece to barely functional, the market from booming to comatose. So what actually correlates with success? Team caliber is the suitability of the CEO, senior staff, and engineers relative to the opportunity in front of them. Product quality is how impressive the product is to someone who actually uses it — how easy, how feature-rich, how fast, how polished, how buggy. Market size is the number and growth rate of customers or users for that product.
So why does Andreessen argue market matters most?
If you ask entrepreneurs or VCs which of team, product, or market matters most, most say team — partly because early on you know far more about the team than the product, which isn't built yet, or the market, which hasn't been explored. We're also raised on slogans like 'people are our most important asset.' If you ask engineers, many say product — startups invent products, customers buy and use them. Andreessen takes the third position: market is the most important factor in a startup's success or failure. In a great market — one with lots of real potential customers — the market pulls product out of the startup. The market needs to be fulfilled, and it will be fulfilled by the first viable product that comes along. The product doesn't need to be great, just basically functional, and the market doesn't care how good the team is as long as they can produce that viable product. Customers are knocking down your door; the job becomes answering the phone and responding to everyone who wants to buy. That's the story of search, keyword advertising, internet auctions, and TCP/IP routers. In a terrible market, you can have the best product in the world and an absolutely killer team, and it doesn't matter — you'll break your pick for years trying to find customers who don't exist, and your team will eventually get demoralized and quit. That was the story of video conferencing, workflow software, and micropayments, at least as of 2007. When a great team meets a lousy market, market wins. When a lousy team meets a great market, market wins. Only when a great team meets a great market does something special happen.
Can a great product ever create its own market?
Absolutely, and it's the best-case scenario — VMware is the standout example. Its product was so transformative that it catalyzed a whole new movement toward operating system virtualization, which turned out to be a monster market. But that's not the type of outcome you should bank on if you're a founder hoping for it.
Given all that, what's a founder actually supposed to do?
This is where Andreessen introduces Ron Rachleff's corollary: the only thing that matters is getting to product-market fit — being in a good market with a product that can satisfy that market. You can always feel when PMF isn't happening: customers aren't quite getting value, word of mouth isn't spreading, usage isn't growing fast, press reviews are lukewarm, sales cycles take too long, and deals don't close. You can always feel it when it is happening: customers are buying as fast as you can make it, usage is growing as fast as you can add servers, money is piling up in the checking account, you're hiring sales and support staff as fast as you can, reporters are calling, and you're getting Entrepreneur of the Year awards. Andreessen's contention is that most startups fail because they never get to product-market fit. He divides a startup's life into two parts — before PMF and after — and argues that before PMF, you should focus obsessively on getting there: change out people, rewrite your product, move into a different market, tell customers no when you don't want to, tell customers yes when you don't want to, raise a dilutive round if that's what it takes. You can ignore almost everything else. Successful startups usually screwed up all kinds of other things along the way — channel model, marketing plan, press relations, compensation policy — and still succeeded, because they found PMF. Meanwhile plenty of startups with every operational box ticked — HR policies, great interview process, catered food, top-tier VCs on the board — go straight off a cliff because they never found it. Founders love to credit their success to all sorts of things afterward, but in almost every case the actual cause was product-market fit.
What did Michael Seibel add to this, in the clip Jack plays?
Seibel talks to a lot of founders who believe they've found product-market fit when they haven't, and it's a huge problem because they start hiring, increasing burn, and optimizing a product before they've actually discovered what needs to be built. His starting point is that Andreessen's post was the single most influential thing he ever read on the topic, and he thinks the term gets misused about 98% of the time — as if it's flexibly defined, when it isn't. The most common mistake is conflating 'I built the thing customers want' with product-market fit itself. PMF is what happens after you've built the thing customers want, and the only way you actually know you've built it is that people are using it in an explosive, almost destructive way. It's intellectually convenient to separate those two ideas, because it's much easier to look at your product and declare it's what customers want than to actually go get a lot of customers using it explosively. Seibel argues most founders, even most YC founders, never find product-market fit at all, and that more acquisitions than people realize are of companies that never found it. Once you find it, it's basically your company to screw up — you'll get there if you execute. Before it, you can execute brilliantly and still end up with nothing.
Does having customers or growth before PMF count for anything?
Seibel is clear that going from zero customers to one customer isn't product-market fit. He likes that Andreessen's definition is experiential rather than a checklist, because any other definition gets gamed — people find loopholes for it. Stripped down, the real questions are: is the growth almost killing you, and is it profitable? People conveniently forget the second part — money piling up in the bank is by definition profit. Seibel points out that plenty of founders will say 'the growth is killing us' while actually scaling negative margins, effectively paying someone a dollar of value for 75 cents and calling it traction. And when founders ask him whether they should optimize for growth, retention, or profitability, his answer is always the same: yes, all of it — building a successful company was never a single-variable problem, and you can't reason your way around product-market fit not being there.
What's the 'hair on fire' analogy about, and why does it matter for early product decisions?
It comes from Sequoia's language about finding customers who have their hair on fire — Seibel extends the metaphor to make it concrete. If your friend's hair is on fire, that fire is the only thing they care about in the world; it wouldn't matter if they were hungry or running late. Hand them a hose and they'll put it out immediately — the perfect solution. Hand them a brick, and they'll still grab it and try to use it, because the problem is that urgent. To find product-market fit, you need problems dire enough that users are willing to try half-baked, imperfect V1 solutions. That's exactly why YC pushes founders to build MVPs: in a good market, an MVP is all you need to get initial customers interacting with you and giving feedback that shapes V2, V3, and V4. Small companies have the advantage of moving fast, giving unusually good customer service, and having customers who expect less. So the playbook is: choose a market where users have real, meaningful problems, launch quickly, and listen. Once you've actually reached product-market fit, you can start optimizing the core product, hiring specialists, and making strategic investments — and you've already gotten further than most startups ever do.
How is Jack applying this at his own startup, Layer Code?
There are six people at Layer Code. One core engineer is pushing hard on the platform where they already have customers, and the other five are shipping MVPs in teams of two every single week, trying to validate messaging or slight product variations to find something that actually resonates as a hair-on-fire problem — while also talking to a lot of people building voice agents to get a sense of where those problems really are. Jack's read is that skipping the step of launching and listening breaks the whole theory: you need a hypothesis about the market, an MVP launched into it, and a real reaction from people before you know whether to double down. Layer Code's current framing is that they need to find the pull before they can even focus on product-market fit itself, since PMF is further down the road — the immediate goal is making something people actually give a damn about, which will likely take a lot of launches and tweaks. He points to Supabase as an example of a product that found its pull not by changing the product, but by repositioning it as 'open source Firebase' — suddenly solving a real problem, avoiding vendor lock-in, that developers already had.
How is AI changing what product-market fit even requires?
A friend, Elliot, sent Jack an article arguing that product-market fit is shifting fast with AI. There's always a threshold for what people want — a brick is a low threshold, a hose is a high one — and that threshold typically rises as a market matures and expectations increase. But AI is pushing that threshold up exponentially in some categories, to the point that nothing satisfies users anymore, and existing product-market fit can simply implode. Chegg, the online homework-help tool, is the example given: its product-market fit collapsed because AI got good enough that the bar for what a homework-review tool needs to deliver shot up so high that the old product was suddenly a dead market.
Links & references
This episode is brought to you by WorkOS.