Amsterdam

Origin and history

The term "Amsterdam" in the context of founder stages originates from the global startup ecosystem of the early 21st century. It is not tied to a specific formal methodology but emerged as a widely-used descriptive label among investors, advisors, and founder communities. The concept was documented in venture capital blogs and accelerator playbooks throughout the 2010s. It serves as a conceptual model for categorizing the earliest phase of a startup's lifecycle. The name metaphorically references the city's historical role as a central trading port, implying a founder's focus on gathering resources and establishing initial connections. Its adoption spread as a shorthand to quickly communicate the specific challenges and priorities of this formative period.

What it is for

The Amsterdam stage exists to define the pre-launch, resource-assembly phase of a startup. Its primary function is to force clarity on the foundational activities required before a company can begin active operations or seek formal funding. This stage is for validating the core problem and solution hypothesis through direct conversation rather than building. It is for identifying and securing the essential initial resources, which often means finding a co-founder or securing a very small amount of angel or friend-and-family capital. The stage is designed to prevent premature scaling and misallocation of effort before product-market fit is even a possibility. It serves as a boundary, marking the transition from an idea in one person's mind to a tangible, shared venture with committed stakeholders.

Overview

The Amsterdam stage is characterized by a founder operating with an idea, immense uncertainty, and minimal tangible assets. The founder's identity is central; the venture is an extension of their vision, network, and personal execution capability. Key activities are externally focused: talking to potential customers, recruiting a co-founder, and mapping the competitive landscape. There is typically no product, no revenue, and no formal team beyond the founder themselves. The stage concludes when the founder has assembled the minimal viable resources, often a committed partner, a clear problem statement, and a rudimentary prototype or design, to begin the next stage of building and testing. This phase is fundamentally about persuasion and conviction, converting a personal belief into a shared reality.

What to know

A founder in the Amsterdam stage must know that their primary job is learning, not building. The most critical knowledge gained is a deep, nuanced understanding of the problem space from the perspective of the target user. Founders should know that the co-founder decision made here is one of the most consequential and difficult to reverse; misalignment at this point often leads to failure. It is essential to know that equity, roles, and vesting agreements, however informal, should be documented as early as possible to prevent future conflict. Founders must know that their personal network is their most valuable asset for accessing early advisors, potential customers, and talent. Understanding that this stage is primarily funded by personal savings or very close contacts is crucial for planning financial runway. Knowing when to exit this stage, when you have enough signal to act, is a key skill to develop.

Common questions

How do I find a technical co-founder if I am non-technical? What does a "validated problem" actually look like, and how many conversations are needed? Is it necessary to incorporate a company or trademark a name at this very early stage? How much equity should I give to an early advisor or a potential co-founder? What constitutes a "minimum viable" prototype for this stage, is a sketch or a detailed presentation sufficient? How do I approach potential customers for interviews without having anything to show them? Should I be applying to accelerators or incubators during the Amsterdam stage, or is it too early? What are the most common legal pitfalls to avoid before any formal funding or revenue exists? How do I balance continuing my full-time job with the demands of this foundational phase?

Pros and cons

A significant pro of the Amsterdam stage is its low cost of failure; a founder can explore multiple ideas or pivot quickly with minimal sunk cost. The flexibility is maximal, as there are no employees, customers, or investors to answer to. This stage allows for deep, unbiased market learning without the distortion of having a product to sell. A major con is the intense personal pressure and isolation, as the founder bears all risk and uncertainty alone, which frequently leads to burnout. The most common mistake is falling in love with the solution and building in stealth for too long, avoiding critical external feedback that could invalidate the premise. Many founders regret not vetting a co-founder more thoroughly on working style and risk tolerance, leading to destructive conflict later. Another frequent downside is the "idea paralysis," where founders remain stuck in perpetual research and networking without making a concrete decision to move forward.

Who it suits

The Amsterdam stage suits individuals who are inherently curious, resilient to rejection, and skilled at interpersonal persuasion. It is ideal for founders who have deep domain expertise in the problem they are solving, as this provides credibility and a network to leverage. This stage suits those comfortable with extreme ambiguity and who can operate for extended periods without external validation or measurable milestones. It is less suited for individuals who require structured environments, clear directives, or rapid feedback loops from a product in market. Founders who are overly protective of their idea and reluctant to share it openly for fear of theft will struggle immensely in this phase. It also suits those with some personal financial runway or a supportive personal network that can provide initial moral and sometimes financial backing.