Cold email vs LinkedIn message: which should you send first?

You have one person in mind, an email address, and a LinkedIn profile. Choosing a channel should be the last small decision before writing. It becomes a large one when the reason for contacting them is still missing.

Our recommended starting rule is to use the place where your reason will be easiest to recognise. Then adjust for what the person has asked for and whether you can actually reach them there.

This is a decision method for a founder, consultant, or small agency. It is not a claim that either channel produces a higher reply rate.

Should you email or message on LinkedIn first?

Start with a contact preference if the person has stated one. Otherwise, look at the source of your reason and choose the route that needs the least explanation. A LinkedIn comment points toward LinkedIn. A specific observation from a website or interview can point toward email. Neither source proves they want to buy.

The source is a starting point, not an obligation. Someone might write frequently on LinkedIn and explicitly ask for business enquiries by email. Follow that preference.

For help establishing the reason itself, use how to say why you are reaching out.

Two worked examples of choosing the first channel

These people and situations are hypothetical. The messages illustrate the reasoning; they are not customer results or quotes from real conversations.

A LinkedIn comment gives you a question

Maya runs an agency. In a LinkedIn discussion about client reporting, she describes having to reconcile totals from two reports before each review. You help agencies simplify reporting.

LinkedIn is a reasonable starting point because you can identify the discussion directly. A possible message is:

Maya, your comment on the client reporting thread mentioned reconciling two totals before each review. Are the reports using different date ranges, or are they counting different things? I help agencies sort out reporting differences and wondered which issue you are running into.

The message separates an observation from a hypothesis. Maya described the reconciliation. You do not yet know the cause, whether she owns the decision, or whether she wants help.

If Maya had only liked the post, that would not support this opener. Do not turn a reaction into a statement about her business. Our guide to finding leads in LinkedIn post comments covers that distinction.

A company page gives you an observable detail

Eli runs a consultancy. Its service page lists three packages, but the enquiry form does not ask which package a visitor wants. You build enquiry forms and can point to the omission.

Eli's contact page invites business enquiries by email. That preference and your specific observation make email the sensible route. You can describe what you noticed without inventing a LinkedIn connection:

Eli, your services page offers three packages, but the enquiry form does not ask visitors which one they mean. Do you sort that out in the first reply? I build forms for consultancies and wondered whether a package choice would save you that exchange.

You can verify what the form asks. You cannot infer lost revenue or frustrated customers from it. Eli may prefer the current process. That answer would be useful information, not a failed pitch to overcome.

What if you cannot message them on LinkedIn?

Keep channel access separate from the reason to contact someone. A connection request, an InMail, and an email are possible routes, not different levels of relevance.

Check the options available on the person's profile and your account. If a connection request makes sense, use it honestly. Do not imply that you have met. If email is the practical route, identify the LinkedIn discussion in the email so the origin is clear.

You can also wait. The existence of another inbox does not create an obligation to use it. This guide does not recommend bypassing messaging restrictions or treating public contact details as an invitation for any purpose.

When should you switch channels?

Switch when the move solves a specific problem. The person asks for email, a document belongs in an existing email conversation, or they tell you which route they prefer.

Silence does not explain what went wrong. It cannot distinguish a missed message from lack of interest or lack of time. Sending the same pitch somewhere else does not resolve that uncertainty.

Keep one contact history across channels: what you sent, where, when, and what they replied. Treat an explicit refusal as applying to your approach, not just the inbox where you received it. For a later follow-up, use the test in how many follow-ups to send: what useful information have you added?

A 30-minute outreach review

Use this as a time budget to try, not a promised output quota.

1. First ten minutes: review a short list. Save the source, date, and specific observation for each person worth considering.
2. Next five minutes: check contact preferences and existing conversations. Choose one first channel for each name.
3. Next ten minutes: write only the messages your evidence supports. Ask about uncertainty instead of presenting it as fact.
4. Final five minutes: record sends, replies, and the next action. Leave a name unsent if its reason does not survive review.

Judge the routine by the conversations it opens about a real problem. Record refusals separately from useful replies. A small set of hand-selected contacts is useful for learning, but it does not establish a general channel benchmark.

Where Trendle fits

Trendle gives you a ranked shortlist with the reasons behind each name, so you can review why someone belongs there before reaching out. That helps with the decision that comes before choosing email or LinkedIn.

It does not make an uncertain reason certain. If you already have well-researched names and only need to send the messages, work through those first. Personalizing cold email at scale covers how to preserve the reasoning as your list grows.