Two Routes from a Relationship to Advice
Entrepreneurs do not always reach useful advice in the same way. This chapter explains the two routes identified in research on nascent founders: building a pool of available advice through relationships over time, and reaching a new contact while asking for help immediately. The distinction supports a practical decision: when a founder faces a problem, should they deepen an existing tie, broaden the network, or do both?
The answer depends less on a general desire to “network” than on the fit between the problem and the knowledge already around the founder. A familiar question may be best handled by a relationship that has had time to develop. A specialized question may expose a gap that no amount of repetition within the current circle can fill. Treating these as the same route produces either wasted effort or an unrealistic expectation that every new contact will become an adviser.
The indirect route: build availability before you need it
The indirect route begins before the urgent request. Through repeated interaction, an entrepreneur creates or strengthens relationships that may later contain useful advice. The relationship is not valuable merely because it is old or frequent. It becomes more useful when the other person is relevant to the founder’s work, understands enough context to interpret a request, and is willing to respond when a challenge appears.
This is the logic behind the network formation problem. Founders operate under uncertainty, so they often do not know in advance which question will become important or which person will be able to answer it. Maintaining relationships across different roles creates a larger set of possible routes to knowledge. Over time, interaction can also create familiarity and norms of reciprocity. A future request is easier to make when it does not arrive as a completely unexpected demand from a stranger.
Consider a founder who is repeatedly discussing customer discovery with an experienced operator. At first, the conversations may be exploratory rather than transactional. Later, when the founder must decide whether a pattern in customer feedback justifies changing the product, the operator may be able to offer specific advice because they know the venture’s context and have seen the founder reason through earlier problems. The value of the relationship is partly accumulated. Availability has been built before mobilization is required.
This route explains why network work can have delayed returns. A conversation that produces no immediate introduction or answer may still make a future exchange more likely. The founder is building a resource pool, not collecting an instant payoff from every interaction. That does not mean every recurring conversation is productive. It means that the relevant outcome at this stage is potential access to suitable advice, not advice already received.
The Danish study gives this pathway an empirical shape. In a two-wave survey of nascent entrepreneurs, networking intensity—measured as the frequency of contact across several role relations—was positively associated with advice availability one year before advice mobilization was measured. In the reported regression, the unstandardized coefficient for networking intensity in predicting advice availability was 0.21, and adding it raised adjusted explained variance from 0.05 to 0.09. These numbers are not a promise that a particular conversation will create a particular resource. They indicate that more frequent networking was associated with a stronger pool of potential advice in this sample.
The indirect route is especially plausible when the needed knowledge is already represented in the founder’s relationships. A supplier may know the operational constraints of a product decision. A peer may recognize a familiar hiring problem. An adviser may have enough history with the venture to challenge a founder’s assumptions rather than offer a generic suggestion. In these cases, deepening a relevant tie can be more efficient than continually searching for another person who has no context.
But availability still has to be activated. A founder may know that someone would probably help but postpone the request, fail to articulate the question, or assume that the other person will volunteer the information. The existence of a resource-rich relationship makes mobilization more possible; it does not make it automatic. The indirect route therefore contains a transition from an available resource to an actual request and response.
The direct route: search when the current network does not fit
The direct route starts with a mismatch. A founder encounters a problem whose knowledge domain is poorly represented in their existing network. The relevant action is not to wait until current relationships become more embedded. It is to find a new contact and seek advice as the relationship begins.
Imagine a founder moving into a specialized market whose regulatory requirements differ from anything their close contacts have encountered. The founder’s existing network may be supportive, but its knowledge does not cover the new requirement. The founder can reach out to a specialist, ask a focused question, and begin a relationship through that exchange. Formation and action happen together: the contact is being created at the same time that a resource is being requested.
This direct route is not a rejection of relationship-building. It recognizes that a founder’s current resource pool can be misaligned with an immediate need. Networking intensity can help here because frequent engagement exposes the founder to more people and more possible knowledge domains. The benefit is not simply a larger list of names. It is a greater chance of encountering someone who can bridge the specific gap, whether through a direct answer or an introduction to another person.
The distinction between the routes is temporal, but it is also about the kind of uncertainty involved. When a founder knows the type of help they need and can identify a relevant relationship, deepening may be sensible. When they know the problem but not who possesses the answer, broadening is a search for fit. When the problem itself is still unclear, broad networking may generate useful context, but it may also consume time without creating a clear request.
The research paper describes this as a partial rather than purely sequential relationship between availability and mobilization. Networking intensity predicted advice mobilization overall, with a reported coefficient of 0.08. After advice availability was included, the coefficient fell to 0.06 and became only marginally significant. The indirect effect through advice availability was 0.03, with a 95% bias-corrected confidence interval from 0.01 to 0.05. Taken together, the results are consistent with both routes: much of the association runs through building available advice, while a smaller remaining association is compatible with mobilizing advice beyond the previously available pool.
The qualification matters. A remaining direct coefficient is not a recording of founders meeting strangers in real time and receiving an answer during that first interaction. The study did not follow specific ties or individual pieces of advice. The direct route is an evidence-supported interpretation of the model and mediation result, not a guarantee that just-in-time outreach works whenever a founder sends a message to a new contact.
A new contact may not respond. They may respond but lack the exact expertise. They may offer an answer that is too general, or refer the founder elsewhere. Direct outreach also carries costs. Instrumental networking can feel uncomfortable because the founder is asking a person to do something useful for them, and the founder may worry about seeming opportunistic or uninformed. The time spent searching can displace product work, customer conversations, or other commitments. Broadening is therefore a strategic response to a knowledge gap, not a virtue that should be pursued without regard to opportunity cost.
The two routes are complementary because founders’ needs change. A start-up may first rely on close relationships for general orientation, then seek a specialist when a technical or institutional problem appears. A specialist relationship may later become part of the founder’s available advice pool if the interaction is repeated and useful. A new contact can be a direct solution today and an indirect resource for tomorrow. Conversely, an established relationship can remain valuable for one class of questions while being irrelevant to another.
The decision tree should not be read as a rigid sequence. The “yes” and “no” branches describe the dominant problem at a particular moment. A founder can deepen one relationship while broadening elsewhere. They can ask an existing contact for an introduction, combining an available tie with a new route. They can also discover through a broad conversation that the supposed knowledge gap was misidentified. The model is useful because it makes the decision explicit, not because it eliminates judgment.
Choosing a route under startup constraints
A founder’s first constraint is usually attention. Networking has to compete with validating a product, serving customers, managing cash, and completing the work that makes the venture viable. The indirect route asks for time before the payoff is certain. Its advantage is that trust and context can reduce friction later. Its failure mode is maintenance without relevance: the founder keeps interacting but does not build access to knowledge that matters for the venture’s next decisions.
The direct route can be faster when the knowledge gap is sharply defined. Its advantage is access to a person the existing circle cannot supply. Its failure mode is search without conversion: the founder accumulates introductions, sends broad requests, and receives little that can be used. A new contact may also lack enough context to understand the problem. A narrowly framed request helps, but it cannot eliminate the basic uncertainty of a new relationship.
The trade-off is therefore not “quality ties versus quantity ties.” It is whether the founder is investing in future availability or solving a current fit problem. Deepening is more defensible when the needed expertise is already nearby and the relationship can support a precise exchange. Broadening is more defensible when the current network lacks the relevant knowledge. Both choices should be judged by what they are supposed to change: future access, immediate advice, or the founder’s understanding of the problem.
This framing also avoids retrospective founder mythology. If a venture eventually succeeds, it is tempting to describe every early conversation as an obvious step toward that outcome. The evidence does not support that kind of inevitability. At the time a founder chooses a route, the value of a relationship is uncertain. A conversation may lead nowhere, reveal a better question, or open a route that becomes important only later. A sensible strategy uses small, reversible tests: make a specific request to a relevant existing tie; if the knowledge is absent, seek one new contact through a credible channel; then assess whether the exchange produced information that changes a decision.
Networking intensity can support both kinds of action, but the research does not show that it should rise without limit. The study’s coefficients are modest, and the measure captures frequency of contact across role relations rather than the number or diversity of all contacts. The finding is therefore best used as a mechanism clue. Repeated activity can help create advice availability, and it may also expose a founder to new resources. It does not tell the founder how many interactions are optimal, which relationship should be prioritized, or whether the advice will be correct.
The strongest operational question is simple: What is the current network unable to provide? If the answer is trust, context, or willingness, a relevant existing tie may need attention and a clearer request. If the answer is expertise, broadening is necessary. If the answer is not yet known, the founder may need exploratory conversations, but should treat new information as a way to refine the problem rather than as proof that networking is working.
The two-path model replaces a single ladder—first build a network, then use it—with a branching system. Founders often build availability indirectly, but they can also mobilize advice directly while creating a tie. The next challenge lies inside both routes: even when relevant advice is available or reachable, the exchange still has to be activated. The question is no longer only which path a founder chooses, but what enables a potential resource to become advice that they can actually use.