From Contacts to Help: The Four Stages a Network Must Cross
Entrepreneurial networks are often described as if they were containers of resources: add more contacts, and more help should be inside. This chapter focuses on the stages between a founder’s relationships and the advice they actually receive. The practical value of the distinction is diagnostic: it lets a founder ask whether the problem is reach, the availability of relevant knowledge, the activation of a relationship, or the conversion of a response into usable advice.
That vocabulary matters because the word network compresses several different things. A founder may have many contacts, speak with people frequently, know who would probably help, and still receive little good advice. Those observations can coexist because they describe different states of the relationship between a person and a resource.
Formation creates potential; action makes it move
The first distinction is between the network formation problem and the network action problem. Formation concerns how an entrepreneur creates and embeds themselves in relationships that make resources available. It includes meeting potentially useful people, maintaining contact, and building enough trust or reciprocity that a future request is plausible. Action concerns what happens when the entrepreneur needs something: activating a tie, asking for help, and obtaining the resource.
The distinction is not a division between “building a network” and “using a network” in a simple chronological sense. Formation can improve the conditions for action, but action can also begin while a relationship is being formed. A founder who has spent months talking with an experienced operator may later ask for detailed advice through an established tie. Another founder may meet a specialist for the first time at exactly the moment a difficult question arises and ask for guidance in that first exchange. The first situation relies on a resource that has become available over time; the second combines contact formation and resource mobilization.
The Danish study of nascent entrepreneurs makes the difference measurable through two related outcomes. Advice availability captures whether people in the entrepreneur’s network would help and give advice if a specific challenge arose. It is a statement about potential support. Advice mobilization captures the amount of good advice the entrepreneur reports actually receiving during the startup process. It is a statement about a resource that has moved from potential into an experienced exchange.
This gap is not a technical footnote. Suppose a founder’s former colleague would gladly review a pricing model, but the founder never asks because the relationship has gone quiet. The advice is potentially available, but it has not been mobilized. Suppose instead that the founder asks a close relative for help with a specialized regulatory question. The relative may be highly supportive yet unable to provide relevant expertise. Here, the relationship is active, but the resource is a poor fit. In both cases, counting contacts would hide the failure point.
The same logic applies beyond advice. A person in a founder’s network may know an investor, a supplier, a potential employee, or a public support program. That connection can create a route to the resource, but the route still depends on relevance, access, trust, timing, and action. The relationship does not automatically transfer its contents merely because it exists.
The formation/action distinction also corrects a deterministic view of networks. A network can facilitate or inhibit action, but people act. Entrepreneurs decide whom to approach, whether to reactivate a dormant tie, how much context to provide, and whether to follow up. The structure around them matters, yet it does not substitute for the behaviors through which a resource is requested and exchanged.
Four measures that should not be collapsed
The most useful way to read the evidence is to separate four stages.
Reach concerns who is accessible or potentially contactable. It is the broadest stage and the one most closely associated with the everyday idea of network size. Reach can expand when a founder meets new people or enters a different professional setting. But reach alone says little about what those people know, whether they would respond, or whether the founder can make a useful request.
Availability concerns whether relevant support is present in the relationships a founder can draw on. It is narrower than reach because it includes an expectation of help, not merely a name or communication channel. A founder may have wide reach but limited availability if contacts are distant, unwilling, or unrelated to the problem. Conversely, a small set of trusted relationships may contain substantial availability for recurring questions.
Activation is the interaction that turns potential into a request and a response. It belongs to the network action problem. Activation may involve choosing the right person, deciding when to ask, framing the question, and navigating the social meaning of asking. A tie can be available but dormant. A founder can also activate a new relationship directly when an immediate problem exposes a gap in the existing network.
Mobilization is the resource actually obtained: in the study’s case, self-reported good advice. Mobilization is not guaranteed by a positive response. Advice may be too vague, arrive too late, or fail to address the decision the founder must make. The study’s measure captures whether good advice was reported as received; it does not verify the quality of every exchange or show whether advice improved the venture.
These stages can reinforce one another, but they are not interchangeable. Repeated contact may increase availability. Availability may make activation easier. Activation may produce mobilization. Yet the chain can also branch or stop. A founder can move directly from reach to a new request. A founder can remain at availability because no request is made. A request can be answered without producing advice that the founder considers good.
It helps to treat each stage as an interface between the founder and the surrounding social environment. The founder owns the definition of the immediate problem: a vague wish for “more advice” is difficult for any relationship to answer, while a question about a particular pricing choice or regulatory uncertainty gives a potential helper something concrete to engage with. The network supplies possible people and knowledge, but it does not decide which resource is relevant. The founder must select a relationship or search for one.
The next interface is the request. A person may be willing to help, yet willingness remains only a possibility until the tie is activated. Activation changes the state of the relationship: the founder makes contact, explains the need, and creates an opportunity for a response. The other person still controls whether they respond and what they know, so the founder cannot manufacture mobilization by asking alone. This is why a network diagnosis should not assign every failure to either the founder or the network. The bottleneck may be an absent resource, an unmade request, an unresponsive tie, or an answer that does not fit.
The stages also imply different signals of progress. New conversations can indicate expanding reach. A person’s expressed willingness to help suggests availability, but not yet a delivered resource. A timely, specific response indicates that activation has occurred, while advice that changes the founder’s next decision is closer to the practical meaning of mobilization. These signals are useful precisely because they are not treated as substitutes. A founder who tracks only the number of conversations may mistake motion for progress; a founder who tracks only successful answers may miss the gradual formation of relationships that make future answers possible.
The state model explains why “having a network” is a weak endpoint. A resource can be available without being requested. It can be requested without being mobilized. It can be mobilized without being useful for the next decision. A founder assessing their network should therefore ask where the current problem sits rather than immediately increasing the number of contacts.
What the Danish measures show—and what they leave out
The first paper does not measure network size directly. It measures networking intensity as the average frequency with which entrepreneurs talk to people across seven role relations, including personal ties, colleagues, acquaintances, and advisers. Frequency is a behavioral measure. It indicates that a founder is taking network-related action, but it does not reveal the total number of people known, the diversity of expertise, the strength of each tie, or the quality of the interaction.
This difference is important when interpreting a finding that networking intensity is related to advice. A founder may speak frequently with a small circle or interact often across a broad range of roles. The measure can register both patterns without telling us which one occurred. It therefore supports a conclusion about contact activity and its association with advice outcomes, not a conclusion that adding a specific number of contacts will produce a predictable return.
The study also relies on role-level self-reports rather than a record of individual exchanges. Advice availability and advice mobilization were measured across seven role relations, but the researchers could not follow a particular piece of advice from a particular person across time. That means the study can connect a founder’s overall sense of available advice with their later overall report of mobilized advice, while leaving the tie-level pathway partly hidden. We cannot tell from these measures whether the same adviser supplied the later advice, whether a weak tie supplied a crucial specialist insight, or whether several ordinary conversations accumulated into the reported result.
Self-report is not automatically a flaw. Founders are the people who know whether they believed advice was available and whether they experienced an exchange as good advice. Those perceptions are relevant to entrepreneurial action. But they are still perceptions. A founder’s confidence, memory, expectations, or definition of “good” may affect the measure. The result should be read as evidence about reported resource availability and mobilization, not as an audited inventory of objective network value.
The time structure improves the question without solving every problem. Networking intensity and advice availability were measured in one wave, while advice mobilization was measured a year later. That separation makes it more plausible to ask whether potential support precedes later reported advice than if everything had been measured at one moment. It does not prove that networking intensity caused the result. Entrepreneurs who network more may differ in experience, motivation, opportunity, or venture context in ways the controls do not fully capture. Nor does the design show the continuing feedback loop in which receiving advice changes later networking behavior.
For a founder, the practical translation is a short diagnostic conversation with themselves. First: What resource do I need, in terms specific enough to identify relevant knowledge? Second: Who could plausibly know this, and is that knowledge available through a current tie? Third: If it is available, what is stopping a clear request? Fourth: If it is not available, which new relationship or channel could reach the missing expertise? Only after these questions should “network more” become a candidate action.
The distinction also changes how progress should be judged. More conversations may be a useful leading indicator of future availability, especially when a founder is entering a new field. A response from a trusted adviser may be a better indicator that activation is working. A specific answer that changes a decision is closer to mobilization. These indicators belong to different stages and should not be used as substitutes for one another.
The central lesson is therefore not that network size is irrelevant. It is that size is too distant from the resource exchange to carry the whole explanation. Formation creates possible routes. Availability tells us whether a relevant route may exist. Action activates it. Mobilization records what arrives. The next question is how founders can move through those states when the route is available but the interaction itself remains difficult.