How introductions work on LINKK — and why the recipient decides

A good introduction request gives the recipient enough context to make an informed choice without turning access into an obligation.

### The three-step model LINKK introductions are deliberately simple. **First, a member sends a request.** The sender chooses a person or organisation and explains why the conversation may be relevant. The request is private rather than a public call-out. **Second, the recipient decides.** They can accept if the proposed conversation is relevant, decline if it is not, or leave it for later. The decision belongs to the person receiving the request. **Third, an accepted request opens a private conversation.** The private space is for clarifying the question, sharing appropriate context and deciding whether a next step is worthwhile. Acceptance is not a commitment to a partnership, investment, referral or meeting outcome. This small amount of friction is intentional. It protects attention and keeps a professional introduction different from a broadcast message. ### Why this is better than cold outreach Cold outreach often asks the recipient to do the sorting. The message may be generic, the reason for contact unclear, and the requested action larger than the information provided. Even a well-intentioned note can feel like an obligation when the recipient cannot see why they were selected. A recipient-led request changes the first question from “How do I get this person to reply?” to “Have I given this person a fair basis for deciding?” That is a healthier standard for cross-border work, where a name alone may not tell the recipient enough about the sender’s role, geography, programme stage or purpose. The model also makes declining acceptable. A declined request is not a failed relationship. It may mean the timing, scope or fit is wrong. A professional network should make that boundary possible without public embarrassment. ### What a good request contains A useful request usually has five parts: 1. **The specific recipient:** name the organisation or role that is relevant. 2. **The reason now:** explain the decision, project or question that created the need. 3. **The connection:** say what you have in common or what you are trying to learn. 4. **The proposed conversation:** suggest a modest first step, such as a 20-minute exchange. 5. **The boundary:** make clear what you are not asking for, especially if the topic could involve confidential information. Keep the request short enough to understand quickly, but specific enough that the recipient does not need to investigate you before deciding. ### An example > Hello Maya — I’m part of a women-founder accelerator in North Africa. We are reviewing how to support alumni entering the Gulf and noticed that your organisation works with early-stage programmes in that region. We are not seeking an endorsement or a referral list. We would value a 20-minute conversation about what an initial soft-landing exchange should and should not include. If this is outside your current remit, no problem; please feel free to decline. The example works because it identifies the sender’s context, names the reason for contact, proposes a limited conversation and gives the recipient a clear way to say no. ### What to avoid Avoid “I would love to connect” without a reason. Avoid attaching a full deck before the recipient has accepted. Avoid implying that a mutual contact, shared geography or profile view means there is an existing relationship. Avoid asking for several introductions in the first message. Avoid promising outcomes that depend on people who have not agreed to participate. A request should also respect confidentiality. Describe the category of problem rather than sharing a company name, founder detail, investor discussion or programme data that you are not authorised to disclose. ### A quick sender checklist Before sending, ask: Can the recipient tell who I am? Can they see why I selected them? Is the first step small and clear? Have I stated the relevant geography or programme context? Have I removed any confidential detail? Would I be comfortable receiving this request on a busy day? If the answer is yes, send it. If not, edit before pressing the button. **Practical takeaway:** draft your request in 80 words or fewer, then remove every sentence that does not help the recipient decide. **Closing CTA:** Find a relevant organisation on LINKK GLOBAL and send a recipient-led introduction request when you have a clear reason to talk.