One of the more common requests I get from founders sounds reasonable on the surface. “Can you introduce us to…?” Fill in the blank: a prime contractor, a government buyer, a program manager, an investor. The assumption is that access is the constraint—that progress depends on getting into the right room with the right people, ideally through someone who can vouch for you.
It’s not an unreasonable instinct. In most industries, access does matter. Networks act as accelerants, and a well-placed introduction can shorten cycles and open doors. But in the space business, that logic only holds at the margins. Founders who rely on it too heavily tend to misdiagnose the real problem, and as a result, they spend time solving the wrong constraint.
The issue is not that people are hard to reach in some structural sense. It’s that they are busy. And not generically busy—the kind of busy that comes with responsibility for programs where failure has real consequences. Their time is allocated, quite rationally, to the problems that are most urgent and most important to them. If you are not connected to those problems in a meaningful way, you will not be a priority. You may get a few minutes. You will not get sustained attention.
This is where the idea of the “warm introduction” starts to break down. It assumes that access is the gating factor, when in reality priority is. You can be introduced to a senior executive, have a perfectly cordial conversation, and still walk away having accomplished very little. Not because the interaction went poorly, but because you were not relevant to what that person needed to solve that day, that week, or that quarter.
There is also a second, quieter assumption embedded in the request for introductions. It assumes that credibility can be transferred—that if someone respected makes the connection, some portion of their credibility carries over to you. That may be true in the opening moments of a conversation, but it dissipates quickly. Once the discussion turns to specifics—your system, your processes, your ability to deliver—you are being evaluated on your own terms.
And this is where founders often reveal more than they intend to. If you arrive in that conversation trying to demonstrate how much you know, you tend to default to what is familiar. You explain your solution. You highlight its advantages. You try, in real time, to connect it to a problem you only partially understand. It feels like forward motion. In practice, it signals something else: that you are optimizing for appearing knowledgeable rather than becoming informed.
There is a quieter, more effective posture, but it requires a different kind of discipline. You show up trying to understand what you don’t know. That means resisting the urge to prove yourself early. It means asking questions where you do not yet have a good answer and being comfortable leaving space for the other person to shape your understanding. It also means accepting that, in the early stages, your role is not to persuade but to learn.
This is not just a philosophical point. It is how credibility actually forms in this industry. You are not taken seriously because you have answers. You are taken seriously because you demonstrate that you understand the problem space well enough to know where your understanding is incomplete—and that you are deliberate about closing that gap.
Spend enough time in technical sessions, program reviews, or even informal discussions at conferences, and a pattern becomes visible. The people who are consistently engaged are not the ones who speak the most or present the most polished narratives. They are the ones who ask questions that move the conversation forward—questions about constraints, edge cases, integration challenges, and failure modes. Questions that reveal they are thinking about how systems behave under stress, not just how they perform under ideal conditions.
Those questions do two things simultaneously. They contribute to the discussion in a meaningful way, and they signal that the person asking them understands the environment they are operating in. Over time, that signal accumulates. People begin to recognize it, and more importantly, to trust it.
Contrast that with the founder who shows up with answers before they have context. Confident, articulate, ready to explain—but explaining into a system they don’t yet fully understand. The gap is rarely called out directly, but it is noticed. Not because the content is necessarily wrong, but because it is premature. And in a domain where the consequences of being wrong are significant, premature confidence is often interpreted as a form of risk.
This is why early introductions can have unintended consequences. If you meet someone before you are ready to engage at their level—before you understand enough to ask useful questions—you are effectively using that interaction to test your own thinking. From your perspective, that may feel like progress. From theirs, it is time spent on something that is not yet relevant to their priorities.
And first impressions, like it or not, tend to stick. You are not categorized harshly, but you are categorized. If you give the impression that you are “not yet useful” that is a difficult position to move out of, particularly when people have limited time to revisit initial judgments.
It may be difficult to accept, but the alternative requires patience. You go to the conferences, the working groups, the technical sessions—not to be seen, and certainly not to pitch, but to understand. You ask questions that you cannot answer yourself. You listen carefully to how different stakeholders describe the same problem, paying attention to where their perspectives align and where they diverge. You begin to map not just the technical landscape, but the operational one—the pressures, constraints, and trade-offs that actually drive decisions.
This will not generate new orders in the short term, and it will not solve an urgent financial issue. But over time, your questions improve. They become more precise, more grounded, and more relevant to the real problems being solved. At some point, they stop being exploratory and start being additive. You begin to surface issues others have normalized or connect ideas across domains in a way that clarifies rather than complicates. When that happens, people notice—not because you are promoting yourself, but because you are contributing in a way that is useful.
This is how you become someone worth talking to. Not through proximity, but through participation. And once you are worth talking to, you are worth buying from or investing in. This is a pattern that I have seen over and over again. Founders resist the time and energy it will take to establish their reputation. But once they make the investment, they find that it begins to pay off in subtle and important ways that strip away friction and accelerate growth.
There is also a practical implication here that founders tend to underestimate. Every introduction you ask for is, in effect, a bet on your current level of readiness. If you are well-prepared—if you understand enough to engage meaningfully—an introduction can accelerate a conversation that was already likely to happen. But if you are not, it can do the opposite. It can consume an opportunity before you are in a position to make the most of it.
This is particularly true when approaching senior executives. Their time is constrained, and their focus is narrow by necessity. They are thinking about a small number of high-consequence problems—issues that affect schedule, integration, mission success, or organizational risk. If you do not understand what those problems are, you cannot position yourself as relevant to them. And if you are not relevant, you will not be a priority, regardless of how you were introduced.
Which leads to a simple but often ignored principle: you should not approach a busy executive until you have a clear view of what is keeping them up at night. Not a generic understanding of their sector, but a specific, grounded sense of the pressures they are managing. Without that, you are asking for time without offering value.
None of this means introductions have no role. They do. But their function is often misunderstood. A good introduction does not create interest; it accelerates it. It works best when the person on the receiving end already has some signal that you are worth engaging with—because they have seen you contribute, heard your name in a credible context, or encountered your thinking in a way that resonates with their own experience.
Without that foundation, an introduction is often just a forced conversation between two people who do not yet have a reason to talk.
So, when a founder asks me for a warm introduction, I usually pause. Not because I am unwilling to help, but because it is often the wrong intervention at that moment.
The better question is not “who should I meet?” It is “what have I done to be worth meeting?” And more specifically, “do I understand their problems well enough to be relevant to them?”
If the honest answer is still forming, then the most valuable work is not outbound. It is upstream.
In the end, this comes back to a dynamic that shows up repeatedly in the space business. You do not build momentum by increasing visibility. You build it by reducing uncertainty. And one of the most reliable ways to do that—long before your first contract or your first flight—is to demonstrate, consistently, that you understand the problems you are trying to solve better than you understand your own solution.
Do that well, and introductions become easier. More importantly, they become less necessary.