Day 1 to day 14: exactly what to comment on a prospect's LinkedIn posts during warm-up

Cold connection requests get ignored. The math is brutal: LinkedIn's own data shows the average user receives dozens of connection requests weekly, and most treat the inbox like a spam folder. A cold DM from a stranger selling something dies on sight.

The fix is not better copywriting. The fix is familiarity. When someone sees your name five, seven, ten times in their feed before you ever send a request, the request stops being cold. It lands warm because you are no longer a stranger.

This article is a 14-day comment script library. It shows exactly what to comment, day by day, on a prospect's posts during the warm-up window. Every example follows one rule: build familiarity, never pitch. The goal is mere exposure, not immediate conversion. By day 14, your name is recognizable, your eventual connection request gets accepted, and your first message gets read.

Why commenting works when cold DMs don't

The reason cold outreach fails is not poor targeting or weak offers. It fails because cold lacks context. A message from a stranger asking for 15 minutes triggers the same reflex as a telemarketer calling during dinner: instant rejection.

Commenting in the feed is different. It shows up where prospects already spend attention, it costs them nothing to see, and it signals you care about their ideas before asking for anything. The psychological mechanism is the mere-exposure effect: repeated, benign exposure to a stimulus increases positive feelings toward it.

Strategic commenting is not about being clever or memorable. It is about being present, relevant, and non-threatening. You want the prospect to see your name enough times that when your connection request arrives, their brain registers familiarity instead of suspicion.

What makes a comment strategic instead of spammy

Not all comments build familiarity. Generic praise ("Great post!") registers as noise. Obvious self-promotion ("We help with this, DM me") triggers spam radar. Both teach the prospect to ignore your name, the opposite of the goal.

A strategic comment has three qualities. First, it is specific to the post. It references a detail, a number, a claim, something that proves you read past the headline. Second, it adds or asks. It extends the conversation with a question, a related observation, or a contrasting data point. Third, it contains zero self-promotion. No links to your site, no offers, no "let's connect." The comment exists only to be useful or interesting.

The 14-day scripts below follow this structure. Each day's example is tied to common post types (wins, questions, rants, how-tos, industry news) and shows what to say when you have deep expertise and when you have only adjacent knowledge.

Days 1 to 5: Observational comments that build initial presence

The first five days are about showing up without demanding attention. Your comments should be low-commitment and post-specific. The prospect should not have to think hard about your reply; they should read it, nod, and move on. The goal is one thing: get your name into their feed.

Day 1: React to a specific detail. If they share a win (a closed deal, a product launch, a team milestone), call out one concrete element. Example: "The 90-day close cycle is impressive, especially in enterprise. What changed between month two and three?" You are not congratulating generically; you are pulling out the number and asking what others wonder.

Day 2: Ask a clarifying question. If they post a hot take or a contrarian opinion, ask for the boundary condition. Example: "Curious where this breaks down. Does the same hold for regulated industries, or is speed-to-market the main variable?" You are not challenging; you are showing you thought about edge cases.

Day 3: Add a parallel example. If they describe a problem or a lesson learned, offer a related observation without making it about you. Example: "Seen the same with annual contracts. The urgency disappears after Q1 unless renewal risk is visible to the exec team." You are pattern-matching, not storytelling.

Day 4: Extend the conversation with a follow-up question. If their post is already generating replies, read the top comment thread and ask something the thread has not covered. Example: "Everyone is talking about the tool; what did the internal rollout look like? Buy-in from the team, or mandated top-down?" You are adding depth, not noise.

Day 5: Acknowledge nuance. If they post something that has obvious tradeoffs, name one out loud. Example: "The speed is a win, but I imagine the error rate climbs when you compress onboarding that much. Worth the tradeoff, or did you build extra QA in?" You are showing you think in systems, not slogans.

Days 6 to 10: Pattern recognition and light expertise

By day six, your name has appeared five times. The prospect does not know you yet, but they have seen you. Now you can layer in light expertise and pattern recognition without sounding like a pitch. Your comments should signal competence, not availability.

Day 6: Reference a trend they are riding. If they post about a tactic, a tool, or a shift in their market, tie it to a broader pattern. Example: "This tracks with what we are seeing in SaaS: the RFP cycle is stretching, but the deals that close without one are moving 40% faster. Are you skipping RFPs entirely, or running them in parallel?" You are contextualizing, not selling.

Day 7: Contrast their approach with an alternative. If they describe how they solved a problem, mention a different path without claiming yours is better. Example: "Interesting. Most teams we talk to go the opposite direction and centralize intake to reduce noise. What made distributed ownership work in your case?" You are showing you know multiple playbooks.

Day 8: Add a data point (if you have one). If their post is about performance, process, or outcomes, add a relevant benchmark or stat. Example: "The 30% lift aligns with what LinkedIn's own data shows for video posts in B2B, though the comments-to-views ratio matters more than raw reach. Are you tracking that, or is reach the north star?" You are contributing, not lecturing.

Day 9: Ask about the next step. If they describe a milestone or a launch, ask what comes next. Example: "Congrats on the beta. What is the plan for the feedback loop? Structured interviews, usage data, or just watching support tickets?" You are showing you think past the announcement.

Day 10: Name a second-order effect. If their post is about a change (a new hire, a pivot, a market shift), ask about the downstream impact. Example: "Bringing SDRs in-house usually shortens the feedback loop, but it also surfaces how messy the ICP definition is. Did that hit you, or was the target already tight?" You are thinking like an operator.

Days 11 to 14: Opening the door to relevance

By day 11, you have been present for two weeks. The prospect recognizes your name. Now you can start to signal relevance by connecting their ideas to your world, still without pitching. These comments should make it obvious you operate in an adjacent or overlapping space, so when you eventually connect, the context is already there.

Day 11: Tie their post to a problem you solve (indirectly). If they post about pipeline, outreach, or sales process, connect it to the category without naming your service. Example: "The acceptance rate gap between warm and cold requests is the whole game. We have seen teams triple connect rates just by commenting for two weeks before sending. Are you doing anything to warm the list before reaching out, or is it straight to the request?" You are teaching the play, not selling the service.

Day 12: Share a contrarian take (respectfully). If they post a popular opinion, offer a different angle. Example: "I see the appeal of automation, but the more we automate the top of the funnel, the more buyers tune it out. The best results we have seen come from slowing down and being present in the feed before asking for anything. Have you tested that, or is speed the priority?" You are showing your thesis without attacking theirs.

Day 13: Ask if they have seen a specific outcome. If their post is about testing, experimenting, or trying something new, ask if they have measured a second-order metric. Example: "Curious if you tracked reply rates after switching to voice notes. We have heard everything from 'game-changer' to 'gimmick,' and the variance seems tied to ICP. What did you see?" You are showing you run experiments too.

Day 14: Offer a resource (not your service). If their post asks a question or describes a challenge, point them to a public resource, a framework, or a mental model. Example: "If you are rethinking outreach, the comment-led playbook from Well Met is worth a look. It is the opposite of cold DMs: you show up in the feed for two weeks, build familiarity, then connect. We run it for clients, but the method is public at getwellmet.com/method if you want to try it in-house." You are helpful first, commercial second.

What to do after day 14

On day 15, send the connection request. The message should acknowledge the prior two weeks without being awkward about it. Example: "Hi [Name], I have been following your posts on [topic] and your thinking on [specific thing they posted] resonated. I work on the warm outreach side of this (we help teams book calls from LinkedIn without cold DMs), and I would value staying connected as you build out [their initiative]. No pitch, just a relevant connection."

If they accept, wait two to three days before sending the first message. When you do, reference a recent post or comment thread. Example: "Saw your post on [topic] last week. You mentioned [specific thing]. Curious if you have thought about [related question]." You are continuing the conversation, not starting a new one.

If they do not accept within a week, keep commenting. Some prospects need 20 or 30 touches before they connect. The cadence should drop to two or three comments per week instead of daily, but the strategy stays the same: stay present, stay relevant, never pitch in the comments.

What should I comment if the prospect rarely posts?

If a prospect posts less than once a week, this playbook does not work. You cannot build familiarity in a feed that does not update. The fix is to expand your target list to include people who post at least twice a week, or to shift the strategy to engaging with posts they comment on (if LinkedIn surfaces that activity in your feed).

Alternatively, use comment-led outreach on the prospect's peers, partners, or team members. If the CFO never posts but the VP of Sales posts daily, warm up the VP. When you connect with the CFO later, mention the VP by name in the request. Borrowed familiarity works.

How do I avoid sounding like I am stalking their feed?

The fear is real: if you comment every day for two weeks, will they notice and find it weird? The answer is no, if your comments are substantive. People who post regularly on LinkedIn want engagement. They do not track who comments; they track whether the comments are useful.

The line between helpful and creepy is specificity. A generic comment every day ("Love this!") will pattern-match as spam. A specific comment every few days ("The 40% improvement in Q3 is notable; what changed between Q2 and Q3?") registers as genuine interest.

If you are worried, throttle to three to four comments per week instead of daily. The warm-up window stretches from 14 days to three to four weeks, but the outcome is the same: familiarity without suspicion.

Can I use these scripts word-for-word, or will prospects notice?

The scripts above are templates, not copy-paste text. If you use them verbatim across multiple prospects, two things will happen. First, your comments will sound generic because they are not tied to the specific post. Second, if two prospects compare notes (unlikely but possible in tight industries), they will see identical language and flag you as a bot.

The structure is reusable; the words are not. Take the Day 3 example ("Add a parallel example") and adapt it: read the post, find the parallel in your own experience or data, write it in your voice. The goal is to sound like a human who read the post and had a relevant thought, because that is what you are.

What if my prospect posts content I know nothing about?

If a prospect posts about a topic outside your expertise, you have two moves. First, ask a smart question. You do not need to know the answer to ask something thoughtful. Example: "I am not deep in supply chain, but curious how much of this is software versus process change. Is the tooling the bottleneck, or is it internal alignment?" You are showing intellectual curiosity, not faking expertise.

Second, skip that post and wait for the next one. Not every post is commentable. If they post about a conference you did not attend, a book you have not read, or a niche technical topic, move on. You need 10 to 14 touches over two weeks; you do not need to comment on every post.