How Madison, Wisconsin Built Its Startup Community Without a Plan

Brad Feld’s The Startup Community Way rests on a provocation that most cities and policymakers find either liberating or threatening, depending on their disposition: that entrepreneurial ecosystems cannot be engineered from the top down, and that attempts to do so generally slow the very thing they are meant to accelerate.

The Madison, Wisconsin story is one of the cleaner pieces of evidence in favour of this thesis. It is not a story of government initiative or institutional design. It is a story of a small group of founders who decided, in 2009, to stop waiting for someone to build what they needed. The core arguments of The Startup Community Way set out the theoretical context for what follows, and are worth reading alongside this case study.

The context

In 2009, Madison had recognisable ingredients for an entrepreneurial culture: a research university with genuine output, a reasonably educated workforce, a cost of living that allowed for some risk. It had almost none of the infrastructure that converts those ingredients into a functioning ecosystem. There were no meaningful accelerators. Venture capital was scarce. The dominant economic culture leaned toward the long, slow rhythms of biotech and academic research and development rather than the faster iteration cycles of technology startups.

Talented graduates left. The incentive structure pointed toward Chicago, San Francisco, and New York, and most people followed it.

What changed was not a policy decision or a new institution. A handful of founders, Zach Brandon, Jon Eckhardt, and Chris Meyer among them, began meeting informally, in cafés, to share intelligence and maintain the kind of peer contact that helps early-stage companies survive the isolating years. These were, initially, gatherings of five or six people. They did not incorporate. They did not seek grants. They began with the assumption that the conversation itself had value, and that if enough people showed up, other things would follow.

This is, almost precisely, the model Feld describes.

Feld’s argument and its application

The Startup Community Way draws on complexity science to argue that startup ecosystems are what researchers call complex adaptive systems: entities that evolve through interaction, feedback, and iteration, rather than through central direction. The implication is counterintuitive for those accustomed to institutional thinking. The most productive thing a city government, university, or corporation can do for an entrepreneurial ecosystem is usually to step back, support, and resist the temptation to manage.

Entrepreneurs, in Feld’s framework, must lead. Others, investors, educators, policymakers, serve as what he calls feeders, contributing to the system without attempting to govern it. The distinction matters because top-down control tends to optimise for legibility and accountability rather than for the messy, nonlinear dynamics through which real communities form. The argument for guiding rather than controlling makes the operational implications of this distinction concrete.

Capital Entrepreneurs, as the Madison group eventually named itself, operated by instinct in ways that align closely with this analysis. They kept the meetings open to anyone building a startup. They did not create a formal membership structure or a curated application process. They focused on creating conditions, regular contact, shared knowledge, a growing sense that Madison was a place where serious entrepreneurial work was happening, rather than on delivering outcomes they could measure quarterly.

This is harder than it sounds. The pressure to demonstrate impact, to produce reports, to justify the time spent, is real and persistent. The founders resisted it, which is one reason the community grew into something durable rather than collapsing into the kinds of programmatic activity that look like ecosystems on a slide deck and feel like bureaucracies in practice.

The obstacles, honestly stated

The early years were not a clean arc. The three obstacles Capital Entrepreneurs faced, credibility, resources, and cultural inertia, were genuine, and none of them resolved quickly.

Credibility was perhaps the most stubborn. Madison’s established business community was sceptical of startups in a way that was not merely conservative but had a specific local flavour: the culture of the research university, with its long timelines and its tolerance for failure in service of knowledge, does not map cleanly onto the faster failure cycles of technology startups. The founders had to earn the right to be taken seriously through persistence and through the accumulation of visible wins, which took time they sometimes did not feel they had.

Resources were limited in the most straightforward sense. Events were self-funded. Promotion relied on personal networks. There was no polished infrastructure. In retrospect, the constraint may have been useful. It prevented the group from building the kind of overhead that would have required them to spend time sustaining an organisation rather than building a community. But it was not comfortable.

The cultural obstacle was the deepest. Madison had not developed a shared vocabulary for failure as a productive part of the process. Changing that required sustained effort at the level of storytelling: making local successes visible, but also making local failures discussable, which is the harder task.

The turn came gradually. Within two years, the character of the meetings had shifted. The number of participants had grown. Local institutions began attending rather than ignoring. Several Capital Entrepreneurs startups raised significant rounds and, crucially, remained in Madison. That last fact mattered enormously to the ecosystem’s self-perception: proof that success did not require departure.

The results, in proportion

By 2020, Madison ranked among the top fifteen American cities for startup activity by Kauffman Foundation metrics. Venture capital presence had quadrupled. The University of Wisconsin had integrated entrepreneurship programming tied directly to Capital Entrepreneurs events. The group had influenced similar founder-led efforts in Minneapolis, Des Moines, and Milwaukee.

It is tempting, at this point, to declare the experiment vindicated and the thesis proved. The honest version is more modest. Madison’s trajectory reflects a confluence of factors: the quality of the university’s research output, a regional economic moment that happened to favour technology, the particular character of the founding group. Disentangling the contribution of Capital Entrepreneurs from those other elements is not straightforward.

What can be said with confidence is this: the community did not emerge from a managed programme, and it did not thrive because institutions took charge of it. The causal story Feld tells, in which founder-led bottom-up activity creates the conditions for ecosystem development, is at minimum consistent with what happened in Madison. Whether it is the full explanation is a different question.

What the case study adds to Feld’s argument

The Startup Community Way is a book that benefits from concrete illustration; its conceptual vocabulary, complex adaptive systems, community or ecosystem fit, feeders versus leaders, can feel abstract when presented without grounding. Madison provides some of that grounding, and does so without the awkwardness of a success story that has been too thoroughly polished.

The roughness is important. The early years of Capital Entrepreneurs were uncertain in ways that no case study written after the fact can fully convey. The founders did not know it would work. They were making a bet on a principle, that genuine community built through sustained, open interaction would generate outcomes that no amount of institutional engineering could replicate, without the evidence that would have made the bet comfortable.

That is, in the end, what Feld’s book is asking its readers to accept: that the uncertainty is the point, that the discomfort of emergence is preferable to the false comfort of managed systems. Madison’s founders, whatever else they did, demonstrated a practical willingness to live with that uncertainty long enough for something to form.

A book worth reading alongside any serious attempt to understand how entrepreneurial communities actually develop. The practical guide to applying the complexity mindset works through what that willingness to live with uncertainty looks like in operational terms, for readers who want the applied follow-through alongside the case study.