LinkedIn Message Templates for Buying Signals: 7 Sequences

These LinkedIn message templates for buying signals come as seven sets, one per signal: a connection note under 200 characters, a first message under 400, and one follow-up. Each set names the signal in its first line, asks one question and makes no pitch. Each also has a do-not-send rule, because the most common failure is a misread signal, not a bad sentence. Pick the signal you saw, fill the brackets, check the count, send. The weak signals you should not message at all are listed at the end.

Which LinkedIn message templates fit which buying signals?

A buying signal is something a person or company did that makes a purchase more likely than it was yesterday. On LinkedIn the ones you can actually see are posts, comments, reactions, follows, job changes and hiring. The definition and a one-minute test are in the lesson; the table below maps each signal to the set you need and to how long you have.

Every template below is written for a hypothetical company so the specifics are easy to swap. The brackets are yours to fill. The character counts are for the filled example, so recount after you edit; the counter in the invite box is the final word on the note limit.

Set 1: They posted about the problem you solve

This is the person telling you, in public, what hurts. The message quotes their own words back and asks what they have tried. Nothing else.

Connection note (164 characters)

Your post on month-end reporting taking three days is the clearest description of that problem I have read this year. Curious what you tried before the spreadsheet.

First message, after they accept (297 characters)

Thanks for connecting. Your line about the finance team re-keying numbers from four tools stuck with me. We work with ops teams of 20 to 200 on exactly that handoff. Before I assume anything: is the three days a people problem, a tool problem, or both? Happy to share what we have seen either way.

Follow-up, day 4 or 5 (187 characters)

One more thought on your reporting post. The teams that fixed the three-day close all changed the same thing first: who owns the export. Want the two-paragraph version, or is this closed?

Do not send if the post is older than two weeks (the problem may be solved, and you will look like you are working through an old list) or if it is a repost of someone else's text. Window: one day. The person who wrote about the problem on Tuesday is thinking about something else by the following Tuesday.

Set 2: They asked for recommendations or alternatives

A request for tools is the strongest signal on the platform, and also the one with the most competition, because every vendor in the category replies in the comments. The message does not compete in the comments. It answers the actual question, in private, and includes a reason to leave you out.

Connection note (164 characters)

Saw your question about alternatives to [current tool]. I have a short list with the trade-offs, including where ours is the wrong pick. Happy to send it if useful.

First message (258 characters)

Here is the list I mentioned. [Option A] if you need [thing]; [Option B] if budget matters most; ours only if [specific condition], otherwise skip it. What is driving the switch: price, a missing feature, or support? That changes which one I would try first.

Follow-up, day 3 (142 characters)

Did any of the three make the shortlist? If you already picked one, tell me which and I will stop. If not, I can get you a reference customer.

Do not send if a comment already names your product (you will look like you did not read the thread) or if they announced their choice. Window: the same day. In our experience the shortlist is made within a day or two of the question, and a private message that arrives after that is answering a closed thread.

Set 3: They commented on a competitor's or a leader's post

Do not name the competitor or the post. "I saw your comment under X's post" reads as surveillance and puts your competitor's name in your first line. Lead with the topic, which you know because you read the thread. The three ways to track competitor post engagers cover how to find these people at all; this is what you send once you have.

Connection note (172 characters)

Your point about onboarding breaking at the second location is one I hear from most [role] teams this year. I wrote up what we found on it. Happy to send it over if useful.

First message (260 characters)

Here is the write-up I mentioned, two paragraphs. The short version: the second location breaks onboarding because the checklist lives in one person's head. Does that match what you are seeing, or is your break somewhere else? Glad to compare notes either way.

Follow-up, day 5 (164 characters)

Following up once on the onboarding note. If the second-location problem is already handled on your side, good, and I will leave it there. If not, what did you try?

Do not send if the commenter works for the competitor (check the headline before you write), or if the comment is just a tag of a colleague with no opinion in it. Window: two days.

Set 4: They post or comment under your topic's hashtag, repeatedly

One post under a hashtag is noise. Three in a month is a person who thinks about the topic for a living. The message treats them as a peer, not a prospect, and the ask is a conversation, not a call.

Connection note (156 characters)

You and I keep showing up under the same [topic] threads. Your take on [their recurring point] is the one I agree with most. Would like to follow your work.

First message (262 characters)

Thanks for connecting. I run [company], where we work on [topic] for [type of company], so your posts are useful to me. One question your last post raised and did not answer: how do you handle [specific thing]? That is the step most teams I talk to get stuck on.

Follow-up, day 7 (133 characters)

Saw your new post on [topic]. The [specific point] matches what we see. If you ever want the numbers behind it from our side, say so.

Do not send if they sell in your category. A consultant or a vendor who posts under your hashtag is a possible partner and a terrible prospect, and the template above will read as a pitch to them. Window: a week; this signal does not go stale the way a post does.

Set 5: They started a new role that owns your problem

New leaders tend to replace or confirm their tools in their first quarter, which is why job changes are on every signal list. Most templates get the timing wrong. The congratulations message on day one lands with fifty others. Wait two to four weeks, until they have an opinion.

Connection note (155 characters)

Congrats on the [role] seat at [company]. A few weeks in is usually when the [problem area] setup shows its seams. Would like to connect and compare notes.

First message (266 characters)

Now that you have had a few weeks in the role: did you inherit a [problem area] setup you plan to keep, or one you are already reworking? I ask because most people in that seat at a [size] company decide in the first quarter, and the two paths need different advice.

Follow-up, day 5 (146 characters)

One more on the [problem area] question. If it is keep-and-fix, I have a checklist that saved one team a month. If it is replace, a different one.

Do not send if the post is a farewell ("after six great years...") rather than an arrival, a promotion in the same team, or an internal move; none of those reopens the tool decision. Window: two to four weeks after the start date, not the announcement day. The guide to finding decision makers on LinkedIn covers confirming that the role really owns your problem before you write.

Set 6: Their company is hiring for the role your product helps

A job post for the role your product assists, say a second SDR or a first RevOps hire, means budget exists and the process is being built. Write to the person who owns the hire, not to the recruiter.

Connection note (161 characters)

Saw [company] is hiring a [role]. That usually means [process] is being built out properly. Would like to connect; I spend most of my week on that exact problem.

First message (284 characters)

Thanks for connecting. The [role] hire is a good sign; most teams only make it once [process] stops fitting in one person's week. One question, not a pitch: is the new hire inheriting a stack, or choosing one? If choosing, I can send the three mistakes we see teams make at that size.

Follow-up, day 5 (139 characters)

Following up on the [role] hire. If the stack question is settled, good, and I will leave you to the interviews. If not, the list is short.

Do not send if you cannot name the person who owns the hire. "Hi, I saw you are hiring" to someone two levels away from the decision is a cold message with a flimsy excuse. Window: while the job post is open. The seven-step guide to setting up signal-based outbound shows how to set the LinkedIn search and alert that catches these posts.

Set 7: They only liked a competitor's post

A like is the weakest signal that still justifies a message, and only if the post was about the problem you solve. The ask drops to a connection, and the note does not mention the like.

Connection note (122 characters)

We are both following the [topic] conversation on here. I work with [type of company] on exactly that. Open to connecting?

First message (203 characters)

Thanks for connecting. Quick one: is [topic] something you are dealing with now, or just following? If now, I have a two-page note on what [type of company] get wrong first. If just following, ignore me.

Follow-up (none)

If the first message gets no reply, stop. The signal was not strong enough to earn a second message. Watch for a second signal instead; a like followed by a comment two weeks later moves the person to Set 3.

Do not send if the person reacts to dozens of posts a day (a serial liker is not a buyer), or if you have nothing on the topic to offer. Window: three days.

Which signals should you not message at all?

A new follower of a competitor's page, a funding announcement with no connection to what you sell, and a profile view are all on vendor signal lists and none of them earns a message on its own. A page follow tells you the person knows your category exists. Funding tells you money exists, not that your problem does. A profile view may be a recruiter or a mistake.

Treat these as list inputs. Add the person to a watch list, connect without a note if you want them in your feed, and send the message only when a second signal arrives: a post, a comment, a job change. Two weak signals from the same person inside a month are worth more than either alone.

Finding the second signal by hand means checking the same profiles every week, which is the part that stops happening after the first month. Intentsly watches LinkedIn for you: it tracks who engages with competitor and industry posts, who writes about your pain-point keywords and who follows competitor pages, scores each person against your ideal customer and queues the ones worth a message, so the LinkedIn signals feed does the weekly checking and you do the writing.

How to adapt the templates without breaking them

Four rules, in order of how often they get broken.

1. Keep the structure, replace every noun. Signal in the first line, one thing you learned from it, one question. If your filled template could be sent to anyone who did anything, you have replaced the structure, not the nouns.
2. Recount after you edit. The counts printed above are for the filled examples. The counter in the invite box shows your own limit, and the templates stay under 200 characters so they fit on any account type.
3. Keep the first message short. LinkedIn's own analysis of recruiter InMails sent between May 2021 and April 2022 found that messages under 400 characters got a response rate 22% above the average and messages over 1,200 characters 11% below it, with individually sent messages about 15% ahead of bulk sends (LinkedIn, Talent Blog). That is recruiting data, not sales data, but the direction is the one we see, and the first messages above all stay under 300.
4. Stop after one follow-up. The sequence is three touches for strong signals and two for weak ones. A fourth message does not recover a dead thread; it costs you the account's reputation.

For the sentence-level mechanics, the four-line method for a LinkedIn outreach message has the character budget per line and a ten-point pre-send check that applies to every template here.

What reply rate should these templates get?

Judge them against a measured baseline, not against the numbers on a vendor's homepage. Expandi's benchmark of 13,218,869 connection requests and 6,730,447 messages across 13,302 accounts, sent between May 2025 and April 2026, puts the platform-wide average at a 28.5% connection acceptance rate, a 3.0% reply rate to connection notes and a 10.4% reply rate to messages (Expandi, LinkedIn Outreach Benchmarks 2026). Those are automation-tool averages across every kind of outreach, so they are the floor a signal-based message should clear, not the target.

Our own first-hand number is from one campaign, so treat it as one data point. When we launched Intentsly we pointed our own signal tracking and AI SDR at founders posting about cold outreach burnout, let the AI hold the conversations, and booked 14 qualified demos in 14 days with no manual outreach, at a reply rate 4x our previous cold campaigns. Most of those leads came from signals caught in real time. The case study has the account; we have not run a controlled test of these exact templates against a cold control, and we would be guessing if we quoted one.

Whatever you measure, measure per signal. Set 2 and Set 7 should not be averaged together, and a month of sending at the caps we run (15 messages and 15 connection requests a day per account, 30 the hard maximum, two accounts per workspace) gives you enough replies per set to see which ones to drop.

What to do this week

Pick the two signals from the table you can see today without a tool, usually Set 1 and Set 3. Save the two sets with your nouns filled in. Send at most 15 a day from a real profile, log the signal next to each name, and after two weeks keep the set with the better reply rate and rewrite the other.

If the finding is the part you will not keep doing by hand, try the AI: it shows the LinkedIn buyers matching your profile right now, with no account, so you can see whether the signals exist in your market before you write anything. The free Buying Signal Playbook lists the 12 signals worth chasing and the 8 to ignore, with a script per signal, if you want the longer list.

FAQ

Should I mention the competitor's post in my message?

No. Naming the competitor puts their brand in your first line and tells the person you were watching their activity, which most people find uncomfortable even when it is public. Lead with the topic of the post instead. You know the topic because you read the thread, and the person will recognise it without being told where you saw it.

How soon after a buying signal should I send the message?

It depends on the signal. A recommendations request needs a same-day reply; a pain-point post or a competitor comment, one to two days; a plain like, within three. A job change is the exception: wait two to four weeks after the start date, when the person has formed an opinion about what they inherited and the day-one congratulations have stopped.

What if the person is not connected to me?

Send the connection note first and the first message only after they accept. Keep the note under 200 characters so it fits whatever limit your account type has; the counter in the invite box will tell you. If they accept without replying to the note, that is normal; the first message carries the conversation, not the note.

How many messages should I send before I stop?

Three for a strong signal (note, first message, one follow-up) and two for a weak one. Then stop and watch for a second signal. A person who ignores three messages about a problem they posted about has either solved it or does not want to discuss it with you, and a fourth message changes neither.

Can I automate these templates?

Partly. The finding and the queueing can be automated; the filled nouns cannot be, because the signal and the detail you learned from it are what make the message work. If you automate sending, keep the volume at the caps we run ourselves, 15 a day per account with 30 as the hard maximum, from at most two accounts, and never from a browser extension running inside your own session.

Do these templates work for InMail?

The first messages do, with one change: InMail has a subject line, so put the signal there ("Your post on three-day month-end") and start the body with the question. The connection notes do not apply, since InMail skips the connection step. LinkedIn's own data on InMail length, linked above, is the reason the bodies stay short.