Write LinkedIn DMs that are easy to answer

Your first LinkedIn message does not need to explain your entire service. It needs to give the right person a clear reason to answer a reasonable question.

That sounds obvious until you read a typical sales DM. It introduces the company, lists several services, claims impressive results and asks a stranger to find time for a call. The recipient has to decide whether any of it matters before doing the work of responding.

Shortening that pitch helps only a little. The bigger repair is choosing an easier next step.

Harry the Marketer calls this respecting “inbox dynamics” in his ABCD message tutorial. The useful principle is direct: the person receiving your message owes you neither their attention nor a meeting. Design the message around that fact.

Earn the first sentence

“I love what you're doing” is not a reason to contact someone. Neither is inserting their company name into a sentence that could go to anyone.

Use a real connection between an observed situation and the work you do. That requires qualifying the prospect before writing. Otherwise personalization becomes decoration around the wrong offer.

Consider this illustrative message from a fictional design studio:

Hi Priya, impressive work at your company. We help ambitious brands stand out with websites, design and social media. Would you have fifteen minutes to discuss how we could help?

Priya still has to work out what the sender noticed, what problem they mean and why a call would be worthwhile. The compliment does not answer any of those questions.

Suppose the studio has genuinely reviewed a newly announced product page and noticed that the mobile comparison table is difficult to read. A more useful opening would be:

Priya, I looked at the product page you shared yesterday. The comparison table is difficult to read on a narrow screen. We work on product-page design. Would a short annotated example of a simpler mobile layout be useful?

That message has a fact, relevant commercial context and one offer. It does not assume the page is losing sales. It also leaves Priya free to say that the team already has a fix underway.

If you cannot identify a useful observation, do not manufacture one. A truthful explanation of the company's fit and a relevant question can be enough. “You run a regional accounting practice; we help that kind of practice explain specialist services” is less theatrical than a fake insight and more credible.

Separate an introduction from a request for calendar time

A meeting can be the right next step after someone asks for a supplier or explicitly describes an urgent need. For a cold introduction, it is often too much too early.

Harry's message-testing video makes this distinction: an opening should not require a long read and a substantial reply from someone who has no relationship with you. A specific useful offer can establish whether a conversation is welcome first.

That offer might be an annotated example, a short assessment, an answer to a question or a relevant piece of evidence. It must fit the observation. Do not send a thirty-page guide because the company happens to match an industry filter.

Keep the ask proportional to the relationship:

You can sell openly while keeping the pressure low. “No pitch” and “no agenda” are poor descriptions of a message whose purpose is to start a sales conversation. State the business context without making the recipient sit through the entire pitch.

A connection note is an introduction too

Harry often prefers sending an invitation without a note, then putting the substantive message after acceptance. He also recommends testing note and no-note versions in his sequence walkthrough.

That is an experiment, not a rule that blank requests always win. A truthful note can make the connection understandable after an event, a useful discussion or a shared project. A generic sales paragraph attached to every invitation can do the opposite.

For example, if you really answered someone's question during an industry discussion:

We were discussing onboarding documents under Lena's post. Your point about the handoff was useful; I'd like to stay connected around that work.

Do not imply a prior meeting, mutual relationship or job opportunity that does not exist. A recipient accepting because they misunderstood your identity is not evidence of a strong sales introduction.

If you compare approaches, use similar relevant audiences and record acceptance, subsequent meaningful replies and any negative response. Acceptance alone does not show that your offer is welcome. A blank invitation is not permission for a long follow-up sequence.

Use ABCD when the choices genuinely save effort

Harry's ABCD method makes a small menu out of the response. In the long-form explanation, the options separate someone ready to speak, someone wanting details, someone interested later and someone who wants no further contact.

The point is useful: let the prospect express a next step without composing a paragraph. The original uses profanity in its refusal option as a pattern interrupt. That can offend the person you are trying to reach. A clear, ordinary decline works without making humor a condition of understanding the message.

Here is an original adaptation for a fictional service helping consultancies improve project handoffs:

Elena, your post described project work arriving without a clear owner. We help small consultancies turn those handoffs into a short, usable process. If this is something you are considering, a letter is enough:

A: relevant, let's discuss the work.

B: send a little more detail first.

C: relevant, but later.

D: not relevant, please close this out.

This example depends on a real post and a service that can actually help. It is not a claim that every consultancy has the same problem.

A four-choice menu also adds length. For the designer's one-example offer, “Would that be useful?” is probably easier. Use ABCD when the different answers would lead to meaningfully different actions. Do not make every person decode your preferred sales framework.

Let people answer in their own words. “Our operations lead owns that” is useful information even though it contains no letter. “We already have a supplier” is not an invitation to put them into the later branch.

The reply changes what you should do

The sorting mechanism matters only if your behavior respects the answer.

If someone is ready to discuss the work, agree the purpose of the conversation and offer a sensible way to schedule. Do not send a pile of extra resources that delays the step they chose. Equally, do not repeatedly push a booking link because a person once expressed interest.

If they want details, answer the likely evaluation question. Explain scope, relevant evidence or how the service works. One well-matched example is more useful than an automated sequence of unrelated case studies. Ask what remains unclear before assuming they are now ready for a call.

“Later” needs interpretation. You can ask whether a check-back would be welcome and, if so, when. Save their answer and the context. A person saying that a project is paused until the next budget review has given you a different instruction from someone politely ending the exchange.

A refusal closes the solicitation. Record it so a colleague does not restart the same conversation. Do not switch to email to get around a LinkedIn decline or treat an unsubscribe as an objection to overcome.

Harry's source video proposes moving these groups into different email sequences. That is not an automatic consequence of a LinkedIn reply. Agree the channel and purpose before changing either. A useful CRM records what the person actually said, the date and the permitted next action; it does not just store A, B, C or D forever.

Follow up with something that changes the conversation

No response is ambiguous. The message may be irrelevant, badly timed, unseen or simply not worth answering. It is not a positive buying signal.

A follow-up can be appropriate when you have a legitimate reason to add something useful. Keep the context visible and choose a stopping point in advance. Repeating “bumping this” makes the recipient pay attention again without receiving anything new.

For the design example, a brief follow-up might explain that the observation concerned only mobile layout and offer to close the thread if it is already covered. It should not become a sequence that grows more urgent or guilt-inducing as silence continues.

Harry's automation walkthrough contains a useful operational detail: replies stop the planned sequence so a human can interpret them. Apply that principle however you manage messages. A reply may be a refusal, a question, a referral or an existing customer asking for something else. Sending the next prepared pitch before reading it can damage the relationship.

If you use software, verify its actual reply-stop behavior and the applicable account rules. LinkedIn's published policy does not make third-party automated activity safe because a tool stays below a claimed daily limit. You can prepare, review and track a small manual experiment before considering any further workflow support.

Measure whether the message starts the right conversation

The title of Harry's ABCD video claims an 85% reply rate. The transcript does not provide the conditions or a dataset that would make that a usable benchmark. A high reply rate can also contain many refusals.

Separate accepted invitations, replies, positive interest, qualified conversations, meetings held and suitable clients. Record where the process breaks. If nearly everyone who answers is the wrong kind of buyer, fix the list. If the right buyers do not understand the offer, fix the explanation. If people ask for details and disappear after receiving them, inspect the service, proof and scope before rewriting the opener again.

Test one meaningful difference at a time: a clearer observation, a smaller offer or one question instead of a menu. The winning message is the one that helps an appropriate buyer take an honest next step and leaves an uninterested person alone.