Personalize an outreach message by turning an observed signal into a reason for the recipient to care. Keep a profile detail when it changes the message you would have sent from a blank page. Connect the signal to a specific implication for the recipient, then ask a question that lets them confirm or reject it. Role, company, posts, and shared context are useful places to look when they can be reviewed before contact.1
Choose a signal
Start with a small research pass. Find one detail that gives you a credible reason to write. You do not need a full biography.
Review work experience or education on the prospect's profile.2 Check recent activity, including content the prospect has liked or interacted with.3 The company page is another place to find a relevant detail.4
Write the exact observation in plain language before drafting the message. If you cannot state what you saw clearly, you will probably fill the message with vague praise. Choose a signal that relates to the recipient's current work or gives you a natural question.
Test the signal
A signal earns its place if it supports a question about the recipient's situation. Ask what changed, why it might matter, and what the recipient could correct.
When a profile shows a recent promotion, congratulate the person and ask, "How is it going?"5 For shared context, use the prompt, "Compare my LinkedIn profile to [prospect's name]'s. What do we have in common?"6 A shared interest can also open the message naturally.7
Move on when the detail gives you both an observation and a reason to ask. Leave out a commonality that leads nowhere.
Write the bridge
Draft the message in this order: observation, implication, question. This keeps the personalization attached to a reason for contact.
Connect the event to a specific implication for the recipient.8 Reference the post or activity that prompted you. Keep the question focused on their situation and leave the pitch out of the opening.9 A strong note shows that you took time to understand something about the recipient personally.10
For a new connection, use a semi-tailored message: keep the structure stable and change the observation and question.11 A useful frame is, "I noticed [signal]. How is that affecting [area]?" Treat the brackets as prompts for your research, not text to send.
Match the message to the moment
Use different wording for the same signal depending on where the conversation stands. Use the invitation to earn a response, then use the accepted connection to continue the thread.
Reported reply rates were 9.36% for personalized requests and 5.44% for generic requests, a reported 71% lift from personalization.12 Use those figures as a reason to personalize the invitation, not as a promise of your own result.
After the connection, build the conversation around the post that brought you together.13 A simple message acknowledging the previous connection often generates immediate engagement.14 For an InMail, keep personalization to one relevant detail.15
If you use a post, comment, or shared context in the invitation, make the next message feel like a continuation of that thread. Do not introduce a new detail merely to prove that you researched the person.
Review before sending
Read the draft as the recipient would. Check whether the observation is recognizable, the implication is fair, and the question can be answered without decoding your intent.
If you use generated personalization, treat it as a draft that you must manually copy and paste into the message.16 Keep personalization blocks for this channel separate from email blocks because tone and formatting differ.17 Scan for unresolved variables such as {{industry}} before sending.18 Use an informal, conversational tone and preview the output for the specific prospect.19
Remove any detail that does not change the question or clarify the implication.
What not to do
A real detail still has to support the message.
- Use a personalized invitation instead of the default connection request whenever possible.20
- A hobby detail such as liking cats is insufficient personalization.21
- Do not send repeated direct messages without context, since that can lead to spam reports.22
- When using a post or technology signal, make a smooth transition to the product message.23