Stockholm

Origin and history

The term "founder stage: Stockholm" originates from global startup and venture capital vernacular, emerging in the late 2010s. It is named by analogy to the psychological phenomenon known as Stockholm syndrome, where hostages develop a bond with their captors. This conceptual framework was created to describe a specific, counterproductive dynamic observed within early-stage companies. Its documentation and discussion proliferated on entrepreneurship forums and in startup advisory content. The stage is not tied to a physical location but uses the city's name metaphorically to label the behavioral pattern. Its history is rooted in the analysis of common founder mistakes during a company's initial growth phase.

What it is for

This conceptual stage serves as a diagnostic tool for identifying a founder's excessive emotional attachment to their initial product or strategy. It is for recognizing when a founder's identification with their creation hinders necessary pivots or objective criticism. The framework is used by investors, advisors, and co-founders to articulate a specific type of strategic inertia. It provides a shared vocabulary to discuss the resistance to change that can doom an early venture. Its purpose is to provoke self-assessment in founders who may be prioritizing preservation over product-market fit. Ultimately, it is for catalyzing a crucial transition from a creator mindset to a scalable business operator mindset.

Overview

The founder stage: Stockholm describes a period where the founder becomes psychologically captive to their original idea, team, or product build. In this stage, the founder defends initial choices with disproportionate fervor, often interpreting feedback as a personal attack. This attachment can manifest as an unwillingness to change core features, an inability to replace underperforming early team members, or a refusal to abandon a failing initial go-to-market strategy. The founder acts as if their survival is tied to the preservation of the original concept, despite mounting evidence requiring change. This stage typically occurs after the initial launch but before achieving sustainable traction, often coinciding with the first significant external feedback. It represents a critical juncture where overcoming this psychological bias is essential for the venture's evolution.

What to know

A key indicator of this stage is the founder consistently dismissing user data or market signals that contradict their original vision. Founders in this stage often use emotional language like "betrayal" or "not understanding the vision" when discussing suggested changes. It is crucial to know that this attachment is frequently subconscious and rooted in the founder's identity, having poured immense personal effort into the creation. The stage forces a binary decision: to remain emotionally invested in the original artifact or to become objectively committed to solving the core problem for the market. Not all attachment to a vision is negative, but the Stockholm stage is defined by its rigidity and resistance to adaptive iteration. Understanding this stage requires separating the founder's legitimate conviction from a maladaptive captivity that prevents necessary evolution.

Common questions

How is this different from ordinary founder passion and vision? Passion fuels persistence, while the Stockholm stage blinds a founder to adaptive iteration. What are the early warning signs? These include avoiding customer interviews that might challenge assumptions, and rationalizing every piece of negative feedback. Can a founder identify this stage in themselves? Self-identification is difficult but possible through rigorous adherence to metrics and appointing a trusted advisor with veto power on certain attachments. Does this mean the initial idea is always wrong? No, but it means the initial solution is rarely perfect, and the founder's attachment can prevent finding the right solution. How long does this stage typically last? Its duration is variable and depends on external pressures; it can last until cash runs out or a pivotal board intervention occurs. Is it always detrimental? Yes, by definition, as it describes a state where psychological captivity actively hinders the company's survival and growth.

Pros and cons

A potential pro is that a founder's deep belief can inspire early teams and attract initial believers, providing crucial early momentum. The significant con is that this stage creates strategic brittleness, causing the company to miss pivotal opportunities to pivot and leading to failure despite the founder's dedication. Founders who do not escape this stage often regret wasting significant time and capital on a solution the market did not want, while blaming the market for its lack of understanding. The common mistake is conflating the founder's ego and identity with the product's specific features, rather than aligning with the customer's core problem. Investors often view a founder stuck in this stage as a red flag for future fundability, as it suggests an inability to execute based on evidence. The stage almost universally leads to strained relationships with co-founders and early employees who see the necessary changes the founder refuses to make.

Who it suits

This stage is not a chosen methodology and therefore does not suit any founder intentionally. It is, however, a trap that particularly ensnares first-time founders with deep technical or creative backgrounds who view the product as a personal masterpiece. Founders who have not previously experienced significant professional failure or rigorous market rejection are more susceptible, as they lack the reference point for adaptive survival. It can also suit founders in echo-chamber environments where early supporters are friends or family, insulating them from objective criticism. Ironically, very persuasive founders can be prone to this stage, as they can temporarily convince others to ignore contradictory data. The stage does not suit founders with prior startup experience who have learned to treat the initial product as a testable hypothesis rather than a final artifact.