The network is the work.

The visible parts of an ecosystem

When we talk about building entrepreneurial ecosystems, we tend to talk about the visible things. The big accelerators, the pitch competitions, the coworking spaces, grants, founder meetups, mentorship programs.

Those things matter. They give ecosystems structure, they create reasons for people to show up, and they often become the most visible evidence that something is happening in a region. That said, I think there is something we consistently overlook: the value of these ecosystems lives in the networks and communities they build, not just in the programming a region can point to.

The more conversations I have with people working in or adjacent to these spaces, the more convinced I become that the real work of these organizations is their network.

A lot of that conviction came out of a conversation with Tim Scales, who has spent years on the organization side of this, most recently running American Underground in Durham and now designing founder programs for ecosystem organizations across the Triangle. He has watched this work from close enough to be specific about it.

Two categories of work

Tim put a useful distinction around this when we spoke. To paraphrase him, there is the process work: reviewing applications, assembling a cohort, matching founders with mentors, planning the event. And then there is everything else.

The introduction you make between two people because they should know each other. The founder who is not technically part of the program anymore but gets an email because you saw something that could help them. The investor you remember meeting a few months ago because a founder needs their expertise.

Tim broke those into two categories: the ESO operations, and the actual ecosystem cultivation.

The operational side

The operational work is easy to name, easy to identify, and often easy to track. The number of applications submitted, the size of an accelerator cohort, the hours spent running events. All of it is measurable and obviously visible, and a lot of it already has infrastructure built around it, both to track the work and to help execute it. This work is genuinely important. It is also only the first category.

The cultivation side

The second category is a lot more elusive: the actual cultivation of the ecosystem being built, the relationships, connections, and network that grow both inside and around the parts that are easy to grasp.

In an accelerator, the application, the length of the program, and the curriculum are the operational part. The cultivation part is the people the accelerator is able to surround the founder with.

Direct introductions. Mentorship. A conversation that happens because a founder attended an event that got mentioned during a session. It is far harder to measure, and it is an extremely impactful side of the work to acknowledge.

What follows if you take that seriously

When you start treating this second category as a central part of what these organizations do, relationship building stops looking like something adjacent to ecosystem development and starts looking like one of, if not the, central mechanism behind it. A few things follow from that.

The highest-value work never reaches the report

Some of the highest-value work done in an ecosystem almost never appears in a program report. The introduction made between two founders. The hour spent helping an entrepreneur who reached out from a different city. The dinner organized last minute after an event. This kind of thing goes undocumented and unreported or, in other words, it becomes invisible.

And yet these are exactly the things that make an ecosystem more connected, and therefore more useful to the entrepreneurs operating inside it.

The tooling only covers the first category

The invisibility of this work shows up in the infrastructure around it, too. There are countless tools for managing applications, curriculum, events, and cohorts. There are far fewer designed around remembering the context behind hundreds or thousands of relationships, and making that context useful later.

The value chain crosses organizations

This work also does not stay neatly inside a single organization. A university entrepreneurship program knows a founder and makes an intro to an accelerator, which connects them to a mentor, who bridges them to an investor. Two years later the same founder meets someone at a coworking space and connects them back to the university.

Who owns that value chain? Not the university, not the accelerator, not the investor, and not the coworking space. The value existed in the connections between all of them. Tim called this out himself, too: a lot of ecosystem-level effort does not run through formal institutions at all, it runs through loose collaboration.

Three places to start

If we accept that the network is a core part of the work, then the infrastructure supporting that network should be treated as a core piece of ecosystem infrastructure too. I think there are three places we can start.

Name ecosystem cultivation as actual work

If introductions, relationship maintenance, context capture, and informal collaboration are central to ecosystem impact, they should not be treated as the miscellaneous things program managers happen to do between their real responsibilities. Taking that seriously affects job descriptions, time allocation, reporting, and eventually what we measure as output for an organization.

Build serious infrastructure around the network

We have plenty of programmatic infrastructure already: application management software, calendars, curriculum, event registration. Remembering what people care about, preserving relationship context, following up on introductions, and making a network last beyond a teammate leaving all need to be prioritized too. That could mean software, shared processes, or something as simple as better relationship-oriented documentation.

Think at the ecosystem level, not just the organizational one

We have a lot of really strong organizations. The open question is how we make the connective tissue between those organizations stronger, and ideally durable through the transition of people. An ecosystem cannot be truly durable if its connective tissue depends entirely on whichever individuals happen to hold the relationships today. In practice that might look like better referral paths, a shared understanding of who is doing what, or simply more communication between ecosystem builders.

The network is the work

I want to be clear about this: accelerators matter, demo days matter, coworking spaces matter, and mentorship programs matter. I think all of it compounds when each piece is contributing to the network that lives in the ecosystem they serve.

The network is far more than a tool ecosystem builders use to do the work. Building, maintaining, and strengthening that network is the work.