Start an Executive Compensation Outreach With a Relevant Question
Build a discreet first outreach around an executive’s planning questions without assuming compensation details.
Executives receive generic messages built on guesses about a bonus, equity grant, career move, or planning need. Such outreach feels intrusive because the sender does not know the facts. A business development advisor earns more attention by using public or volunteered context, asking permission for an introductory conversation, and leaving room for privacy. The first contact should offer a simple choice rather than turn a public announcement into a claim about private finances.
Start by checking why you have a reason to contact one person now. A public leadership announcement, a conference conversation, or a referral with permission gives you a narrow opening. An internal database label, a job title, or a guess about compensation does not. Write one sentence describing your factual reason for contact. If your sentence contains an assumption, do not send outreach yet. A clear factual note helps you stay within what you know when drafting and when answering a question later.
For example, a contact record might say, “A public company release announced Devon Lee’s new role on Tuesday.” Such a note identifies a source and a date. “Devon likely received a major grant” does neither. The second sentence asks you to build a conversation around private information you do not have. A new title does not reveal pay, holdings, plans, family circumstances, or interest in a financial discussion.
Keep the first message short enough for a busy reader to understand on one screen. Mention the source of your awareness only when appropriate. Then ask a question with an easy no. A message from advisor Talia might read: “Hello Devon. I saw the public announcement about your new role and wanted to offer congratulations. Would a brief introductory conversation be useful if planning questions arise during the transition?” Devon does not need to reveal income, holdings, plans, or personal goals in order to decline.
Avoid broad promises about value. “I help leaders manage every financial issue” asks the reader to infer skill from a slogan. A quieter explanation gives a more honest reason for contact: “I work with people who want a conversation about planning questions during career change.” The sentence describes an available discussion without stating which questions Devon has. You are offering a conversation, not diagnosing a need from a headline.
Here is a fictional practice situation. A public release reports Devon’s new leadership role. Talia has never met Devon. Before writing, Talia saves the public source in the contact record and adds one factual note: role change announced Tuesday. Talia does not search for estimates about Devon’s compensation. Talia does not assume a grant, bonus, or equity award exists. Talia checks whether her firm’s outreach process permits a message based on the public announcement, then prepares one draft.
Talia reads the draft aloud. The first version predicts important planning deadlines from a new package. Talia deletes the sentence. No public source supports such a claim, and Devon should not need to correct an assumption in an introductory email. Talia’s final message says, “Hello Devon. I saw the public announcement about your new role and wanted to offer congratulations. Role changes sometimes lead people to seek an introductory planning conversation. Is such a conversation useful for you now, or would you prefer no follow up?” The final question makes permission explicit.
Devon replies, “Thank you. The company has not shared details yet, so I am not discussing anything related to compensation.” Talia answers, “Understood. I will not make assumptions or ask for details. I appreciate your reply, and I will leave space for you to contact me if a future conversation feels useful.” Then Talia records Devon’s boundary through the approved process and closes the outreach task. A second message with a different angle would convert a clear answer into pressure.
An executive’s title should never become a financial profile. Avoid phrases such as “People in your role usually have complex equity needs” or “Your new package creates important deadlines.” Both statements assume facts. They also place the recipient in a position where correction feels like disclosure. Public context provides a reason for a respectful hello. Public context does not provide evidence of a planning problem, a decision deadline, or a level of assets.
Referral outreach needs equal care. Suppose Jordan tells Talia, “Devon might welcome an introduction.” Talia first checks what Jordan agreed to share and whether Devon gave permission for Jordan’s name in an email. “Jordan suggested I introduce myself” belongs only where Jordan gave permission for such mention. “Jordan told me you are worried about your shares” does not belong in an introductory message unless Devon agreed to share such a detail. A referral opens a door. Privacy controls the conversation after you step through.
Choose one contact method and one follow up rule before sending. In Talia’s fictional practice plan, she sends one email and waits ten business days. If Devon does not reply, Talia closes the outreach task rather than stacking calls, direct messages, and forwarded articles. An unanswered message does not explain Devon’s silence. Devon might be busy, uninterested, travelling, or protecting privacy. You do not need a reason for no response in order to respect no response.
When a prospect accepts a conversation, prepare questions which let the person define scope. Start with, “What prompted you to accept this conversation?” Then ask, “What would make our time useful?” Devon says, “I want a place to think through changes without sharing details today.” Talia responds, “We will keep today at a general level and decide whether another conversation makes sense.” Talia does not rush toward specific accounts, income, documents, or a meeting calendar. A prospect who sets the scope has more reason to continue speaking.
Another prospect might ask, “Why did you contact me?” Answer with the factual reason: “I saw the role change in a public announcement and thought an introduction might be welcome. I do not know your compensation details or financial situation.” The response addresses the concern without inviting a debate. If the prospect sounds uneasy, offer to remove future outreach according to your firm’s process. Do not defend the message or ask for a chance to explain further.
Timing requires discipline. A public announcement on Tuesday does not require a message before lunch. Give yourself time to confirm names, source language, and permission status. Read the draft once with a simple test: does every sentence come from public or volunteered information? Then check whether a person wanting no contact has an easy reply path. Remove each prediction of a need or result. Short outreach often improves when one sentence disappears.
Practice with fictional executive Devon and two facts only: a role announcement appeared yesterday, and Devon has never met you. Write a sixty word email with a relevant greeting and one permission question. Role play Devon saying, “Please do not contact me about personal finances.” Write your final response, enter Devon’s preference in the approved system, and close the task before opening your next prospect record.
Practice these next
Coach business development advisors to honor a referral relationship without assuming a prospect’s needs.
Create a credible first conversation around employer equity without advice in outreach.
Practice concise, respectful outreach for a planning meeting without seeking confidential details.
Practice a business development response which preserves trust and earns permission for future contact.
Business development advisors reconnect with old contacts without treating an earlier conversation as an obligation.
Earn a first planning meeting from an attorney referral without seeking confidential details too early.