Executive search
A warm-introduction brief for executive search: context before the request
Prepare an executive-search introduction request with a clear purpose, permitted context, a forwardable note and separate confirmation from the people involved.
A colleague appears to know the person you want to reach. Before asking for an introduction, you still need to explain why the conversation would be relevant, what can be shared and what the colleague is being asked to do.
A warm-introduction brief is that small piece of preparation. It gives a relationship owner enough context to assess the request and, if appropriate, ask the other person whether they want the introduction. It should leave room for a comfortable decline.
The brief does not establish that the relationship is current, that an approach is permitted or that the recipient is interested in a role. Those remain separate questions. A useful introduction begins with an accurate request, rather than an assumption that a visible connection can be used.
Copyable warm-introduction brief
| Field | What to write |
|---|---|
| Purpose | The particular conversation being requested |
| Relevance | A concise, supportable reason the person may have useful context |
| Proposed connector | The colleague or contact being asked to consider the introduction |
| Relationship check | What is known, what needs confirmation and who checked it |
| Permitted disclosure | What can appear in the request and forwardable note |
| Restricted context | Information that must remain outside the introduction |
| Forwardable note | A short self-contained message for the intended recipient |
| Choice | Clear room to decline or suggest a different route |
| Next owner | Person responsible if an introduction is accepted |
| Status and date | Requested, awaiting answer, declined, agreed or completed |
Start with the purpose, then remove anything the relationship owner does not need. The internal briefing can reference controlled sources; the forwardable text should stand on its own without attachments that reveal more than intended.
For the wider assignment context, use the mandate kickoff checklist. An introduction request should be consistent with that mandate rather than become an informal way to expand it.
Separate a visible path from a usable relationship
A shared connection, historical email or CRM relationship score can suggest a route worth checking. It cannot tell you whether the person is comfortable making this particular request now.
Affinity describes relationship intelligence using communication patterns to surface relationship context. That is a supplier's account of its product, not evidence that every surfaced connection is suitable for an executive-search introduction. Ask the relationship owner to confirm the relevant context directly.
The useful questions are ordinary ones. Do you know this person well enough to consider asking? Is the relationship current? Would this purpose be appropriate? Is there a reason you would prefer not to be involved? The answer may be “I know them, but not in a way that makes this request sensible.”
Do not translate a colleague's reluctance into an adverse judgment about the recipient or the colleague. Record only what the team needs for the next action. A declined introduction is not evidence about candidate suitability, professional reputation or willingness to change roles.
Make the purpose specific enough to assess
“Can you introduce us?” leaves the relationship owner doing the hard work of explaining why. A clearer request identifies the conversation sought and the information that may be shared, while respecting any restrictions around the assignment.
The purpose might be a confidential discussion about whether an appropriately described opportunity is relevant, or a request for general market context. Those purposes are different. Do not describe a role approach as neutral networking to make the request easier to accept.
Check that the proposed wording is accurate. If you cannot identify the client yet, say only what you are permitted to say. If the recipient would reasonably need more information before deciding, acknowledge that limitation and agree a suitable next step instead of inventing certainty.
Use the candidate research-note method to keep the factual basis separate from the invitation. A public biography may support a relevance question. It does not support claims about private interest, availability or motivation.
Draft text that can be forwarded without editing
Keep two pieces of text separate: the internal request to the connector and the note they may offer to the recipient. The internal record can reference controlled evidence; the forwardable note should contain only the agreed disclosure.
For a fictional industrial-service leadership search, the internal request could read:
Would you be comfortable asking Rowan whether an initial conversation would be welcome? The permitted description is a regional service-operations leadership search. Please do not name the client or forward the internal research brief. I am asking whether you will consider checking, not assuming an introduction is agreed.
The separate forwardable note could read:
Our search team is reviewing a regional service-operations leadership requirement. Your published work on managing field-service teams prompted the question. Would a short initial conversation be relevant? We can share the permitted context directly if you would like to hear more. Please feel free to decline.
These invented details demonstrate specificity, not a real opportunity or assessed candidate. In a real request, verify the published work, permitted role description and recipient before using them. If the connector needs more disclosure to explain the purpose honestly, return that question to the assignment owner before forwarding anything.
Ask before connecting the parties
A practical approach is to ask the connector whether they are willing to consider the introduction, then allow them to establish whether the intended recipient wants it. This is a suggested professional workflow, not a claim that one etiquette rule determines every legal or contractual requirement.
Record the difference between “happy to ask” and “happy to introduce.” The first still leaves the recipient's answer unresolved. If the connector proposes a different route, check that route against the assignment's restrictions before proceeding.
Avoid deadlines that imply an obligation to help. If there is a genuine timing constraint, describe it accurately and allow the connector to say that the timing does not work. A polite request is weaker when its closing sentence makes declining feel like a failure.
Do not treat silence as agreement. The team can decide an appropriate, limited follow-up under its normal communication policy, but repeated messages do not convert an unanswered request into permission.
Worked example: two possible connectors, one appropriate request
In this fictional continuation, connector C1 confirms a recent professional relationship with Rowan and is willing to ask the agreed question. Connector C2 has only an older contact entry and cannot confirm the relationship's present context. Neither entry proves Rowan wants contact.
| Record event | Literal status | Next owner |
|---|---|---|
| C1 says “I can ask whether Rowan is open to it” | Connector willing to ask; recipient answer outstanding | C1 asks only the reviewed question through the agreed route |
| C2 cannot confirm current context | Historical route unused | Consultant retains the limitation without inferring a negative view of Rowan |
| Rowan later accepts an initial conversation in this exercise | Introductory conversation agreed; role interest and further disclosure unresolved | Consultant arranges the agreed conversation and records its scope |
The handoff reads: “C1 checked; initial conversation accepted; consultant owns scheduling. Do not send another introduction request through C2.” It avoids both a duplicate approach and an overstated “candidate interested” label.
This sequence is invented to explain the record. It supplies no response rate or evidence that a warm route outperforms another channel. The connection-evidence review addresses whether a suggested path is supported; this brief begins the separate task of preparing and tracking a particular request.
Check the message audience and attachments
An introduction can disclose addresses, identities and relationships before anyone opens an attachment. Review recipients and content together. Gmail's sending guidance explains that Cc recipients can see other recipients, while Bcc recipients still see addresses in To and Cc. Hiding some addresses does not make the message's content confidential.
Check that any linked document has the intended audience. Google Drive sharing guidance describes access inherited from folders. A carefully written email can still point to a document shared more widely than intended.
Do not attach the internal research brief by default. The recipient may need only the agreed introductory context. If further information is appropriate later, make a deliberate disclosure decision at that stage through the normal firm and assignment controls.
An assistant or drafting tool can help prepare text for review only within its actual permitted use. This workflow does not assume that Laisy or another product sends introductions, checks permissions or controls the recipient's subsequent actions.
Preserve the response without overstating the relationship
After a request, update the record with the dated response and next owner. Keep the status literal: “connector considering request,” “recipient declined,” or “introductory conversation agreed.” Avoid a broad “engaged” label that hides which person replied and what they accepted.
Contact history also needs interpretation. Google Contacts documents limits to available change history, including older contacts for which some history may not be available. A visible record update is not necessarily a conversation, and a missing update does not prove that no interaction happened.
When the assignment changes hands, the handover guide provides a place for the active commitment and unresolved next step. The receiving consultant should be able to tell who is waiting for whom without restarting the request or contacting the recipient twice.
Test the preparation rather than promising a response
A useful small experiment can focus on the quality of the brief: can a second consultant identify the purpose, permitted disclosure, outstanding question and next owner without a separate explanation? Review the text for accuracy and whether declining remains straightforward.
Use the pilot success criteria to define that task alongside existing tools, with selected permitted inputs and reviewed outputs. A good result would be a clearer request and record. It would not prove that a person will reply, that the relationship is strong or that the assignment will succeed.