Somewhere right now, a founder is delaying a launch because “the market isn’t ready.” Somewhere else, another founder just shipped, watched the silence roll in, and reached the same conclusion after the fact: too early, wrong moment, bad luck. Both may be misdiagnosing the problem.

The entrepreneur and Idealab founder Bill Gross studied roughly 200 companies, half from his own incubator, half from outside it scoring each on five factors: idea, team, business model, funding, and timing. Timing came out on top, accounting for 42 percent of the difference between success and failure, ahead of team and execution and well ahead of the idea itself (Bill Gross, TED). But in Gross’s own account, timing was never simply a launch date.

It was about whether the world had become ready for what a company was offering — whether the underlying technologies, behaviors, and infrastructure were already in place. His own examples are broadband penetration and GPS adoption: conditions a founder depends on but doesn’t control (Idealab). That is a real, mostly external condition. It is also easy to confuse with a second, much more internal question: whether a team has matched its product to the right customer and the right job to be done. Conflating the two is why so many products die of a diagnosis they never actually had.

None of this argues that timing doesn’t matter, Gross’s data says otherwise, and nothing below disputes it. The claim here is narrower: timing matters enormously, but founders often blame timing for problems that actually belong to positioning, product-market fit, or use-case selection. One of the least likely case studies on a venture blog shows both halves of that claim inside a single company: bubble wrap. Its inventors spent years failing before landing, almost by accident, on the question they should have asked from day one, and the material never changed. Only the use case did.

What “Timing” Actually Means In Product Launches

Founders talk about timing as a single dial. Too early, too late, or just right. In practice, the word collapses at least three separate variables into one, and treating them as one is where the trouble usually starts.

Market readiness

This is whether the infrastructure, economics, regulation, and behavior a product depends on already exist. Gross’s own shorthand for this is broadband penetration and GPS adoption (Idealab), but the same logic applies to a payments product that needs functioning payment rails, a hardware product that needs a viable supply chain, or a consumer app that needs enough people already carrying the device it runs on. Market readiness is largely outside a founder’s control. You cannot will broadband penetration, checkout infrastructure, or regulatory approval into existing faster than they naturally arrive.

The use case

This is the specific, narrow job a product does for a specific person in a specific moment. A “ready” market doesn’t want a technology in the abstract; it wants a particular problem solved. This part sits almost entirely within a founder’s control, and it is the part most often confused with timing.

The gap between them

This is where most failure analysis goes wrong. When a launch underperforms, it is tempting to conclude the market wasn’t ready. But a market can be fully ready for a category of solution while being uninterested in the specific application in front of it. Two products can target the same ready market, at the same moment, and only one has found the job that market actually needs done.

That gap is close to invisible from inside a company. A team watching its own product underperform sees external conditions: macro headwinds, an unconvinced market, bad timing. What is harder to see, because it requires an uncomfortable kind of honesty, is that the team has built a good answer to the wrong question, for a market that would have said yes to a different one.

Bubble Wrap: When the Market Was Ready and the Product Wasn’t (Yet)

In 1957, two engineers working out of a garage in Hawthorne, New Jersey, set out to build something with almost no relationship to the product the world now knows. Alfred Fielding and Marc Chavannes were trying to invent a three-dimensional textured wallpaper aimed at the mid-century modern design taste of the period.

Their manufacturing process was almost an accident: running two plastic shower curtains through a heat-sealing machine trapped hundreds of small air pockets between the sheets, producing a sheet of film that was not the sleek wall covering they had pictured (Smithsonian Magazine, Sealed Air).

That failure alone wouldn’t be interesting, most failed consumer products stay failed. What makes bubble wrap worth studying is what the inventors did next. Rather than dismiss the material outright, they patented the process and began cataloguing other uses for it, more than 400 by one count, according to Smithsonian Magazine’s account of the invention (Smithsonian Magazine).

One of those ideas, greenhouse insulation, made it off the drawing board and into real tests. It was no more successful commercially than the wallpaper had been (Smithsonian Magazine).

That detail matters: this wasn’t a team short on imagination about where their product might fit. It was a team that had tried two of the most intuitive markets available to it, home décor and agriculture, and gotten nothing back. By this point, Fielding and Chavannes had tried two markets and neither had produced a viable business, even as the company they’d formed around the material, Sealed Air Corporation, incorporated in 1960, kept the lights on (Sealed Air).

So, to confirm the framing question directly: were Fielding and Chavannes struggling for years because the market wasn’t ready for their product, or because they hadn’t yet matched it to a market that already was? The evidence is more consistent with the second explanation than the first. By the early 1960s, manufacturers were already facing the practical problem of protecting increasingly delicate products, from consumer electronics to early business computers, during shipment. Bubble wrap didn’t need that problem to be invented.

It needed to be recognized as the same problem the wallpaper and greenhouse pitches had missed.

That recognition came from IBM. According to Sealed Air’s own account of its history, shortly after the company was founded in 1960, Bubble Wrap’s cushioning properties were put to use protecting IBM’s 1401 computers during shipment (Sealed Air). One industry account adds a more specific detail: it was a marketer named Frederick Bowers who, about a year after the company’s founding, recognized the packaging potential and connected it to IBM’s need to ship its new 1401 line (The Packaging Company).

The breakthrough wasn’t a fundamental reinvention of the material. Its core physical properties; lightweight, sealed, air-filled cushioning, were already present in the version that had failed as wallpaper and failed as insulation. What changed was the application: cushioning fragile freight instead of decorating walls or warming greenhouses.

That match didn’t make the business overnight. Sealed Air still had to build sales channels, prove the material against cheaper incumbents like sawdust and shredded paper, and scale manufacturing before Bubble Wrap became the default choice for shippers, a reminder that finding the right use case is necessary but not sufficient; someone still has to build the company around it. Decades on, the payoff is real: Sealed Air Corporation reported 5.4 billion dollars in net sales for 2025 (Sealed Air, Q4 and Full-Year 2025 Results), built on a material that spent its first three years being rejected twice.

The lesson worth sitting with isn’t “pivot until something works,” which is too generic to act on. It’s narrower: the inventors’ first two markets were plausible and reasoned, and still wrong, because in both cases the product’s real advantage; light, sealed, air-cushioned protection, was incidental to what the buyer actually cared about, whether that was appearance or heating cost. It only became the whole story once someone found a buyer for whom that exact property was the entire point.

Right Market, Wrong Use Case: The Failure Founders Rarely Diagnose Correctly

Bubble wrap is a clean version of a pattern that repeats constantly in modern product launches, usually in a much murkier form. Founders rarely misjudge whether a market exists as badly as Fielding and Chavannes appeared to with wallpaper. What they misjudge far more often is which specific problem, inside a real and ready market, their product is actually solving, and for whom.

Slack is the modern version of the same story, minus the false starts. Stewart Butterfield’s company, Tiny Speck, spent roughly three years and significant venture funding building Glitch, a whimsical browser-based multiplayer game with a devoted niche following that never reached the player base it needed to be commercially viable; the company shut the game down in December 2012 (Wikipedia).

What survived the closure was an internal messaging tool the team had built purely to coordinate the game’s development, not designed as a product, but built to solve the team’s own communication problem. Once Tiny Speck looked at that tool as a standalone offering rather than scaffolding for a game, it recognized a real customer problem in distributed teams drowning in scattered email threads. What changed wasn’t the existence of that problem; it was the team’s recognition that the tool it had built for itself might solve it for other people too.

That recognition still needed deliberate positioning to become a business. In a memo to his team in July 2013, Butterfield argued that Slack couldn’t simply be sold as a messaging tool, because most buyers didn’t yet know they needed one; the company instead had to sell the reduction in email and organizational chaos that came from using it (Stewart Butterfield, “We Don’t Sell Saddles Here”). Matching a product to a real problem, in other words, was only half the job.

Someone still had to make customers recognize the problem as theirs. Slack launched publicly in 2013. Salesforce agreed to acquire it in December 2020 in a cash-and-stock deal valued at approximately 27.7 billion dollars (Salesforce), a transaction that closed in July 2021 (Yahoo Finance).

What connects bubble wrap and Slack isn’t luck or persistence in the abstract. In both cases, the team had already built something with real, differentiated value before it understood what that value was actually for. The wallpaper had the physical properties of protective cushioning long before anyone shipped a computer in it. The messaging tool had the properties of enterprise collaboration software long before anyone sold it as one. In both cases, years were lost not because the market wasn’t ready for what the team had, but because the team kept describing what it had in terms of the wrong job.

It is worth distinguishing this carefully from genuine “too early.” A market that lacks the infrastructure, regulation, budget authority, or behavioral habits to adopt a category of product at all is a timing problem in the strict sense, no amount of repositioning fixes it, because the thing the product depends on hasn’t arrived yet. But a market that is fully capable of adopting a solution, and simply isn’t interested in this specific application of it, may not have a timing problem at all.

It may have a positioning or product-market-fit problem wearing a timing costume. The two call for different responses: genuine timing failure calls for patience, or a smaller wedge into the market that doesn’t depend on the missing infrastructure; positioning failure calls for re-pointing the same product at a different buyer or a different job, often without changing the product at all.

How to Tell the Difference Before It Costs You Years

The instinct after a weak launch is to look outward: macro conditions, competitors, “the market.” That instinct is comfortable, because it doesn’t implicate the product. Based on cases like these, it deserves to be challenged before a team concludes the market is to blame.

A more useful diagnostic starts with a narrower question than “is the market ready?” It asks whether there is a specific, describable person, in a specific, describable moment, for whom the product’s core property, not its category, its actual mechanical advantage, is the single most important thing available to them right now. Fielding and Chavannes could describe bubble wrap’s core property accurately the entire time: sealed air pockets, lightweight, cushioning.

What took years was finding the person for whom that property, not the material’s appearance or its price, was the deciding factor. Tiny Speck could describe its messaging tool’s core property early: fast, searchable, always-on team communication. What took a company-ending crisis was recognizing that description, not “a companion to our game”, as the actual product.

In practice, that means treating weak early traction as a use-case question before treating it as a timing question. If a product is getting used intensely by a small, specific group and ignored by everyone else, that pattern should prompt a use-case and customer question before it prompts a timing diagnosis, it often means the wrong buyers are seeing the right product, or the right buyers are seeing the wrong pitch.

If, on the other hand, a product draws polite interest but no real usage, even from the people who most plausibly need it, that leans closer to genuine timing failure: something structural may still be missing, and repositioning alone won’t manufacture it.

The honest version of this exercise is uncomfortable, because it requires separating what a team is proud of having built from what a market is actually willing to pay for. Bubble wrap’s inventors patented their process and catalogued hundreds of hypothetical uses before finding the real one, and the real one wasn’t the most impressive item on that list, it was the one that matched a market need that was already forming.

Most founders don’t have four hundred alternative use cases to fall back on. But the underlying discipline is the same: describe the product’s actual advantage in plain terms, separate that description from the market you originally imagined for it, and go looking, deliberately, not accidentally,for the buyer whose problem that advantage happens to solve better than anything else available to them.

Closing

Fielding and Chavannes weren’t wrong that they had built something with real physical value. They were wrong, for about three years, about whose problem it solved. That is a more survivable mistake than “the market wasn’t ready,” because it is a mistake founders can go looking to fix, rather than a condition they simply have to wait out. The harder question, the one worth sitting with after a launch goes quiet, isn’t whether the timing was off. It’s whether the product has already found its IBM, and no one in the room has recognized it yet.

‍

read - The Efficiency Trap: What AI Productivity Gains May Really Cost

‍

‍