Explain the situation, the specific experience you need and the small outcome a first conversation could produce. Include timing, what you can contribute and information that is safe to share. A useful brief lets an introducer judge relevance without implying that anyone has already agreed to help.
Describe the decision behind the request
Begin with the business question you are trying to resolve. A request for someone senior in technology gives an introducer little basis for assessing fit. A request for an operator who has coordinated onboarding across several customer locations is more actionable because it identifies the experience that could inform the next decision. Explain the practical context in a few sentences.
Distinguish the problem from your preferred solution. If you ask only for a particular vendor or job title, you may exclude someone with more relevant experience. State what is currently difficult, what you have already tried and which uncertainty remains. Keep confidential customer details out of the shareable version unless an appropriate arrangement permits their inclusion.
Specify the experience and contribution you need
Describe relevant context, such as customer size, operating model, delivery complexity or stage of development. Separate essential experience from preferences. The person does not need to match your business in every detail to offer useful perspective, but an introducer should understand which differences would make the conversation less relevant. Avoid replacing that judgement with a long list of prestigious employers.
Explain what you are requesting: a short discussion, feedback on a prepared question or an introduction to a specialist service. Be clear if you are seeking paid work, an adviser or a potential commercial partner. A request framed as a casual conversation should not quietly turn into an expectation of unpaid consulting or an immediate sales opportunity.
Make the first step small and prepared
Propose an outcome that can fit a first conversation, such as identifying two onboarding risks or checking which assumptions need testing. Say what you will prepare and how much time you are requesting. Give the potential contact room to suggest a different format or decline. The brief should make participation understandable without placing a commitment on someone who has not seen it.
Include what you can contribute when relevant: a concise account of a problem, permitted research observations or experience in a complementary area. Keep the exchange accurate and proportionate. Mutual value does not require pretending that every conversation offers equal commercial benefit; it requires respecting the other person’s time and being honest about the request.
Create a version another person can forward safely
Use a short standalone note containing the context, fit, request, timing and an appropriate contact route. Remove internal commentary, private addresses and attachments that the introducer should not distribute. Ask whether the note accurately represents your request before it is passed on. A person willing to consider an introduction may still need permission from the other side.
Keep the brief current as the decision changes. If the question is resolved or the timing no longer works, tell the introducer rather than leaving an old request circulating. Record the next action you own, such as preparing a one-page context note. A connection brief is successful when it supports an informed decision about relevance, not simply when it creates a larger contact list.
A fictional founder asks for relevant operational experience
A fictional scenario to explain the method, not a customer result or a market benchmark.
A fictional software founder is preparing to onboard customers with several regional offices. Their initial request asks a mentor for “someone senior who knows growth.” After reviewing the decision, the founder writes a short brief seeking an operations professional who has coordinated customer onboarding across multiple sites and can discuss handover ownership.
The note explains the current uncertainty, requests a twenty-minute exploratory conversation and offers a prepared synthetic onboarding map. It says that no customer records need to be shared. The mentor can now assess relevant experience and ask the proposed contact whether they are open to an introduction. The founder remains responsible for the preparation and follow-up. This invented case demonstrates a clearer request, not a guaranteed introduction or an improvement in onboarding performance.
TAKE THIS INTO YOUR NEXT CONVERSATION
A practical next-step checklist.
- Name the business decision the connection should inform.
- Describe the experience that matters and why.
- State the format, time request and first useful outcome.
- Prepare a shareable version without unnecessary private detail.
- Own the next action and update the request when circumstances change.
Common questions.
How long should a connection brief be?
Long enough to explain the situation, fit and requested next step without requiring a company history. A short note can link to relevant public background. The useful test is whether a third party can describe the reason for the introduction accurately.
Should I ask for a named person or a type of experience?
Either can be appropriate. Explain the experience you need even when naming a person, and allow the introducer to suggest a more relevant contact. Naming someone does not establish their availability or permission to share their details.
Further reading & source context.
These primary references provide background. They are not evidence for the fictional example above and do not endorse AccelerateLink.
Found an error or a missing qualification? Send an editorial correction.
Find my next move.
Use a practical tool to turn this idea into a clearer starting point.
Find my next move