How to Start a LinkedIn Conversation Without a Canned Pitch

Write a relevant first LinkedIn message, make a modest request, and follow up with care using practical examples.

Published · Updated

A good first LinkedIn message answers two questions quickly: why are you contacting this person, and what are you asking them to do? If the recipient has to search for either answer, the message needs editing.

You do not need an elaborate icebreaker. A specific professional reason is enough. The challenge is making that reason honest and the request proportionate to the relationship.

Match the message to your actual connection

Start with the context you share. There is a difference between a colleague you met at an event, someone whose public article you read, and a person who simply appears relevant to your work.

Here are illustrative openings:

  1. After an event: “We spoke briefly after the panel about supplier onboarding. You mentioned a checklist for handling exceptions. Is that something you can share?”
  2. After reading an article: “Your explanation of contract handoffs helped clarify a problem I'm researching. Have you written more about assigning the final approver?”
  3. For a new peer: “I'm working on support reporting for a small software team and noticed your public work in the same area. I'd be glad to connect and compare approaches over time.”

Use the first example only if the conversation actually happened. Use the second only if you read the material. A fabricated shared interest is still fabrication, however smoothly a tool phrases it.

Keep the first request small

A new contact does not owe you a meeting, free consulting, a referral, or introductions to their customers. A narrow question or connection request is often more appropriate than a calendar link.

If the purpose is commercial, make that clear. “I wanted to connect” should not conceal a prepared pitch you send immediately after acceptance. Our service-pitch guide shows how to state an offer with enough context for the reader to assess it.

Avoid making the recipient do your research. “How do I succeed in your industry?” is a large request. “Which public resource explains the certification route?” is easier to answer. You should still look for that resource yourself first.

Remove decorative personalization

Job-title compliments, generic enthusiasm, and references to distant personal details can make a message longer without making it more relevant. Keep the detail that explains the professional fit and remove the rest.

An illustrative edit turns “Your inspiring career journey and outstanding leadership deeply resonate with me” into “Your article on onboarding new managers covers a problem my team is working through.” The revised version is easier to understand and does not exaggerate familiarity.

AI can help shorten a draft, but inspect every fact it adds. For a preparation workflow, see AI-assisted networking. Do not assume a tool that sends invitations or messages is permitted simply because its copy looks natural. LinkedIn restricts specified automated activity in its User Agreement.

Follow the reply, not a script

When someone answers, acknowledge the substance. If they share a resource, read it before asking the next question. If they say they are not the right person, thank them and avoid pressing for an introduction.

No reply can mean many things. It does not tell you the person needs a more persuasive sequence. One concise follow-up may make sense when you have a relevant addition or an agreed reason to reconnect. Repeating “just checking in” without new context creates work for the recipient.

Respect a decline or request to stop. The relationship may simply not be useful to them at this point.

Check the message before sending

Read it as a busy recipient. Can you identify the reason and request in one pass? Is the information true? Can you decline comfortably? Does the message sound like a person you could have a normal conversation with?

Draft one message for a person you have a specific reason to contact. Remove every sentence that does not clarify that reason, supply useful context, or make the next step easier.

Put a better reply into practice.

See how ReplyPilot works