Market Timing: The Most Underrated Factor in Startup Success

Most startup post-mortems cite "no market need" as the cause of failure. But a large fraction of those failures are not really about market need — they are about timing. The market existed, or would exist. The team built something real. But the infrastructure was not ready, the regulations blocked them, or the cultural shift they needed had not happened yet. They were right about the idea and wrong about when.

Why Sequoia asks "why now?"

Sequoia's pitch framework includes a slide called "Why Now?" It is not a formality. The question forces founders to articulate what has changed in the world that makes their idea viable today when it was not viable five years ago. A good answer references a specific shift: a new API became available, a regulation changed, a platform reached critical mass, a cost fell below a key threshold.

The absence of a good "why now" answer is a strong signal that the timing may be wrong. If you cannot point to a specific change that unlocks your idea, you are either too early (the change has not happened yet) or too late (the change happened years ago and incumbents already captured the opportunity).

Great ideas that failed due to bad timing

Google Glass (2013–2015) was not a bad idea. Augmented reality overlays on the real world are genuinely useful. The problem was timing: compute density was too low to make the hardware comfortable, battery technology was inadequate for all-day wear, and there was no developer ecosystem to create the killer apps that would justify the form factor. The cultural backlash against always-on cameras accelerated the failure, but the underlying technology readiness was the root cause.

Tablet computers before the iPad were tried repeatedly through the 1990s and 2000s. Microsoft's Tablet PC initiative in 2001 was technically coherent but failed because capacitive touchscreens had not yet achieved the required sensitivity and cost profile. When Apple launched the iPad in 2010, the critical enabling technology — cheap, responsive multi-touch screens — had arrived. Same idea, right timing, different outcome.

Webvan (1999) was grocery delivery before the smartphone, before ubiquitous GPS, and before consumers were comfortable entering payment details online. The idea was sound. Instacart, operating with smartphones and mature e-commerce trust, built the same business 13 years later and succeeded.

How to assess infrastructure readiness

Infrastructure readiness means: are the foundational technologies your product depends on available, affordable, and reliable enough? This includes APIs, cloud compute, hardware components, payment rails, and communication infrastructure.

A practical checklist: Can you build an MVP today with off-the-shelf components at a cost that makes unit economics viable? If the answer requires technology that does not yet exist at production scale, you are probably too early. The classic example is LLM-based products before 2022 — the models existed but were too expensive and too slow for most commercial applications. After GPT-3.5 and especially GPT-4, the infrastructure readiness threshold was crossed for many product categories simultaneously.

How to assess the regulatory environment

Regulation can block a business entirely or create a moat for whoever navigates it first. Fintech, health tech, and legal tech are the most obvious examples. Before validating an idea in these categories, founders should answer: is the regulatory framework settled, in flux, or entirely unclear?

A settled framework (e.g., HIPAA for US health data) means the compliance cost is known and can be budgeted. A regulatory environment in flux (e.g., AI liability regulation in the EU) means either a significant risk of rules changing mid-build, or an opportunity to shape the framework if you engage early. An entirely unclear framework means you may be building on sand.

The Hacker News community is a useful early signal for regulatory risk — founders who have hit regulatory walls tend to document their experience in detail on HN.

How to assess cultural readiness

Some ideas require a cultural shift that no product can accelerate. Remote work tools existed before 2020 but were niche. The pandemic forced a cultural shift that Zoom and Notion rode — not because the tools suddenly became 10x better, but because the cultural barrier to adoption collapsed overnight.

Assessing cultural readiness is harder than assessing infrastructure. Useful proxies: Is the behaviour you require already happening informally, just without your product? Are there leading indicators in adjacent markets? Is the target demographic already comfortable with the closest analogue?

Timing as a score dimension in IdeaCheck

IdeaCheck scores your idea on timing (0–10) alongside market demand, technical complexity, and distribution. The timing score reflects what the Hacker News community said about similar ideas over time — including whether the community felt the market was ready at the time of the discussion, and whether conditions have since changed. A PASS ON verdict driven by a low timing score often means: the idea is sound, but the window has not yet opened, or has already closed.

Understanding timing is one of the most valuable things a founder can do before committing to an idea. It does not require a crystal ball — it requires honestly answering "why now?" and checking whether the infrastructure, regulatory, and cultural conditions match your answer.