CommentiSign In

Comment Examples8 min read

What to Comment on a LinkedIn Post You Disagree With: 18 Examples

What to comment on a LinkedIn post you disagree with: 18 real examples that add a counter-case, question the sample, or push back on the advice without dunking.

Deepak Yadav

By Deepak Yadav, Founder, Ampliflow

disagree.

The short version

  • Concede the part that is right before you object; a comment that opens with agreement gets read, and one that opens with 'actually' gets defended against.
  • Disagree with the claim, never the person, and never write the comment for the audience instead of the author. Dunking wins the thread and loses the relationship.
  • Bring something the post does not have: a counter-example, a question about the sample, or your own opposite experience. Pure contradiction adds nothing.
  • The strongest disagreement often separates the principle from the prescription. You can accept why something matters and still reject how the author says to do it.
  • Skip the comment entirely if the post is personal news, if you are angry, if the author is junior with a big audience watching, or if your objection needs 400 words.

What to comment on a LinkedIn post you disagree with: concede the part that is right, then add one thing the post is missing, a counter-example, a different sample, or your own opposite experience. Disagree with the idea, never the person. Bring evidence or lived experience, and never write for the audience instead of the author.

Below are 18 examples, grouped by the kind of disagreement you actually have. The grouping matters, because "I think you are wrong" is at least five different comments, and reaching for the wrong one is how a reasonable objection turns into a fight nobody wins.

The rules that keep disagreement from costing you

Deciding what to comment on a LinkedIn post you disagree with starts with five rules, listed in order of how often people break them.

  • Concede first, and mean it. Find the part of the post that is genuinely right and say so before you object. This is not a politeness ritual. It proves you read the thing, and it changes how the rest of your comment is received.
  • Disagree with the claim, not the person. "This framework misses X" and "you clearly have not run a team" are different comments. Only one of them survives being screenshotted.
  • Bring something. A counter-example, a question about the sample, a story from your own work. Pure contradiction is noise.
  • Write to the author, not the gallery. The moment you are performing for readers instead of talking to the person who posted, you are dunking. Everyone can tell.
  • Leave room to be right. "I might be missing something" costs you nothing and keeps the exchange open. Certainty is the most expensive thing in a comment section.

Disagreement is the highest-skill comment there is, which is why we treat it as a separate move in our full LinkedIn commenting strategy rather than a variant of a normal reply.

Comments that add a counter-example

The most useful form of disagreement. You are not saying the post is wrong; you are showing where its rule stops applying.

  1. "Mostly agree, with one exception worth naming. We ran the opposite playbook at a 12-person startup and it worked, because the founder was the only person customers wanted to hear from. Small teams might be the edge case here."
  2. "This holds for enterprise. It falls apart in product-led growth, where the buyer and the user are the same person and the whole champion framing stops mapping to anything real."
  3. "Does this hold outside B2B? Every consumer brand I have worked on runs the opposite play and gets away with it."
  4. "Agree on direction. The case I keep hitting is regulated industries, where ship it and iterate still means a compliance review either way. Would you still run this in fintech?"

Why these work: each one hands the author a real object to think about instead of a verdict to argue with. Authors defend against opinions and engage with examples.

Comments that question the sample, not the conclusion

Often the claim is fine and the evidence behind it is thin. Say that, precisely, without implying dishonesty.

  1. "Genuinely curious about the sample. Is this across all your clients or the ones who stayed past 12 months? The second group would be selected for exactly the behaviour you are describing."
  2. "Useful data. One caveat worth flagging: everyone on this list already succeeded, so we are looking at survivors. The companies that did the same thing and died are not in the screenshot."
  3. "Strong claim, and I want to believe it. What was the denominator?"

Why these work: they question the method, which is impersonal, instead of the person, which is not. Example 7 is deliberately short. A single honest question can be the entire comment, and brevity keeps it from reading as an ambush. We get into the length question generally in how long a LinkedIn comment should be.

Comments that agree with the principle but not the prescription

The most underused move on the platform. You accept why something matters and reject how the author says to do it.

  1. "The principle is right. The prescription I would push back on: post daily works if you already have something to say daily. For most people it produces 300 words of filler and a slow unfollow."
  2. "No argument on the goal. The step I would not copy is doubling outreach volume, because volume and quality are different skills and this treats them as one lever."
  3. "Completely agree this is worth solving. Less sure about hiring a specialist at seed stage. We did that, and the specialist was good, but nobody in the room knew enough to tell whether the work was working. Took us a year to find out."
  4. "Right diagnosis, wrong medicine, I think. The problem you describe is a positioning problem. The fix you propose is a copywriting one."

Why these work: they split the post in half and reject only the half that deserves it. The author gets to keep their thesis, which makes them far more likely to actually consider the objection.

Comments that offer the opposite experience

Lived experience is the one form of evidence nobody can dispute. Use it plainly, and admit its limits.

  1. "My experience was the reverse. I did exactly this for a year and got nothing until I changed the audience, not the format. Same effort, different room."
  2. "Interesting, because the opposite happened to us. We cut posting frequency in half and inbound went up. Small n, obviously, and I still cannot fully explain it."
  3. "This did not work for me, and I gave it two years. I keep wondering if it is a category thing, because it seems to land much better for consultants than for people selling software."

Why these work: "here is what happened to me" cannot be argued away, only contextualised. Note that 13 volunteers its own weakness before anyone else can. That single phrase, "small n, obviously", buys enormous credibility.

Comments that ask the question the post did not answer

The quietest form of disagreement and often the most devastating, so use it carefully. Only ask if you would genuinely accept a good answer.

  1. "What would falsify this? Asking sincerely, because I cannot picture the result that would change your mind, and that usually means I am the one missing something."
  2. "How do you separate this from the thing that was already working? From outside it looks like both changed at the same time."
  3. "Where does this leave someone with no audience yet? The advice seems to assume distribution already exists."
  4. "One gap I keep tripping on: who absorbs the extra cycle time? In every version of this I have run, someone downstream pays for it, and the post does not say who."

Why these work: a real question puts the author in a position to look good by answering it. A rhetorical question does the opposite, and readers know the difference instantly.

When not to comment at all

Restraint is part of the skill. Skip it entirely when:

  • The post is personal. Grief, illness, a layoff, a health scare. There is no version of "well actually" that belongs there.
  • You disagree with the person, not the idea. If you would let the same claim pass from someone you liked, close the tab.
  • You have not read past the hook. LinkedIn truncates long posts, and plenty of objections turn out to be answered in the part you never expanded.
  • The author is junior and the audience is large. Correcting someone early in their career in front of a big audience costs them far more than it costs you. Send a DM instead.
  • You are angry. Wait an hour. The comment you write at hour one is almost never the comment you write at hour zero.
  • Your objection needs 400 words. Then it is a post, not a comment. Write it, and link generously to the person who prompted it.
  • The thread is already on fire. Once a comment section has turned into a pile-on, nobody in it is there to change their mind, including you.

For the situations where you do want to engage but disagreement is not the move, we keep a wider library of LinkedIn comment examples covering launches, milestones, hiring posts, and bad news.

Where automation fits here, and where it should not

We build Commenti, a tool that writes LinkedIn comments in your tone, so read our position with that in mind. Read it plainly too: LinkedIn's User Agreement prohibits third-party automation, ours included, and the risk is real. It grows with volume, speed, and generic output.

Our advice for this specific scenario is narrow. Do not automate disagreement. An AI comment can spot that a post makes a claim; it cannot know that you ran the opposite experiment in 2023 and watched it fail, and that missing detail is the entire value of the comment. A generated objection with no evidence behind it is just contrarianism with better grammar, and readers sort that quickly. Commenti's skip filters and approve mode exist for exactly this reason, alongside daily caps and human-like pacing that reduce, not remove, account risk. The broader tradeoff is covered in our take on whether AI comments on LinkedIn help or hurt.

The disagreement comment is the one you write yourself. Concede what is right, bring the thing only you have, ask the question you actually want answered, and let the author be a person rather than an audience. Everything else on your feed can wait its turn.

Frequently asked questions

What should you comment on a LinkedIn post you disagree with?

Name what the post gets right, then add the specific thing it is missing: a counter-example, a question about the evidence, or your own opposite experience. Keep it about the claim, not the author. End with a question or an admission of uncertainty so the comment reads as an invitation to talk rather than a verdict.

Is it bad for your reputation to disagree publicly on LinkedIn?

Disagreeing is fine. Dunking is not. Readers remember tone far longer than they remember who was right. A comment that concedes ground, brings evidence, and leaves the author room to answer usually improves how you are perceived. A snide one-liner does the opposite, permanently, in a searchable public thread.

Does disagreeing in comments help or hurt reach?

Substantive disagreement tends to generate replies, and replies keep a thread alive, so a thoughtful objection often gets more visibility than agreement. That is exactly why it is tempting to be contrarian on purpose. Manufactured disagreement is obvious to readers and costs more credibility than the extra impressions are worth.

When should you not comment on a post you disagree with?

When the post is personal news, grief, a layoff, or an illness. When you are angry and have not waited. When the author is early in their career and the audience is large, because that is punching down in public. When your objection needs several paragraphs, write your own post instead.

How do you disagree without sounding rude?

Use hedges honestly rather than decoratively: 'in my experience', 'small sample', 'I might be missing something'. Attack the strongest version of the argument, not a weaker one you invented. Ask a real question. And never use the phrase 'respectfully' as a delivery vehicle for something disrespectful.

Written by the team building Commenti on real LinkedIn growth data. Found an error? Tell us and we’ll fix it. Accuracy beats winning.

Deepak Yadav

Deepak Yadav

Founder, Ampliflow

Builds Commenti at Ampliflow, and has worked across 80+ startups as an AI micro-SaaS builder. Writes about what the product data actually shows, including the parts that are inconvenient. Commenti is the LinkedIn comment automation tool by Ampliflow.

Read next

autopilot.

Comments like these, written in your voice.

Commenti drafts comments that sound like you on posts from the creators and keywords you pick, then posts them within your daily limit or waits for your approval.

60 days free for the first 200 users · Cancel anytime

Try it on your feed