The message always arrives the same way. A screenshot, no caption, sometimes just a link. Then: "have you seen this."
It is a competitor publishing in the founder's lane. Sometimes it is a near-restatement of an argument our client made in March. Sometimes it is the same mechanic, explained slightly worse, to a bigger audience. Occasionally it is the client's own phrase coming back at them with somebody else's headshot next to it.
The founder wants to know what we are going to do about it.
Usually the answer is: keep publishing, go one level deeper, and stop reading it as an attack on your distribution. Because it almost never is. But there is a version of this that costs real money, and the difference between the two is worth understanding before you react — because the instinctive reaction is the expensive one.
What actually happens to your reach
LinkedIn distribution is topic-shaped. The platform builds an inferred picture of what your account is about and uses it to decide who is in the room when you publish. That is the whole basis of a lane strategy: publish narrowly for long enough and the system gets confident about who to show you to.
Here is the part founders get wrong. A lane is not a fixed pool of attention that a second publisher divides in half.
When another credible account starts posting about 3PL selection or Amazon creative or DTC unit economics, the practical effect on the interest graph is usually that more people get classified as interested in that subject. The topic gets fed. Readers who were never sorted into it now are. If you are also publishing there consistently, some of those readers land on you.
We have watched clients' reach hold flat or improve in quarters where two other people entered their subject. Nobody believes this until they see it in their own analytics, because it contradicts the reflex that says a shared topic is a split topic.
What genuinely does get worse is a different thing entirely: substitutability. If a stranger reads your post and a competitor's post in the same week and cannot tell which one required access to a real business, you have a problem — and you had it before the competitor arrived. They just made it visible.
That distinction decides everything about the response. Reach is fine. Interchangeability is the actual exposure.
Three shapes this arrives in
Not all of them mean the same thing.
The adjacent operator who just hired a writer. They have been in your category for years and were always going to have opinions about it. What changed is that they now publish them on a schedule. This is the most common version and the least threatening. They are producing at a level they can sustain, which for most founders means one or two posts a week of general category commentary.
The larger account swinging through. A generalist with 80,000 followers writes one post about your subject, gets four hundred reactions, and moves on. It stings because the numbers are bigger than yours. It means almost nothing. They will not be there next month, they have no receipts in your category, and the readers who engaged were engaging with the account, not the topic. Do not restructure anything around a visitor.
The direct competitor who is reading you. Rarer, and the only one that ever warrants a change in behaviour. The tell is not similarity of topic — it is similarity of sequence. You publish a mechanism, they publish the same mechanism eleven days later. You publish the boundary case, they publish the boundary case. If you can predict their next post from your last one, you are not sharing a lane, you are being followed.
Even then, the response is not defensive. It is faster and deeper. More on that below.
The three reactions that cost you
Founders reliably reach for one of these, and all three are worse than doing nothing.
The subtweet. A post about how "some people in this space are repackaging other people's frameworks." No name, careful phrasing, and every reader who does not already know the backstory reads it as an unstable founder taking a private conflict public. The people you want — the operator evaluating whether to hire you, the acquirer, the partner — cannot verify who was right. They can only see that you brought it to the feed. It costs more than the copying did.
The escalation. The instinct to answer with something bigger, hotter, more contrarian. This nearly always means moving up in altitude — a broader take, a bolder claim, less working detail. It performs, briefly, because broad takes are agreeable. Then it gets copied too, because a position is one of the easiest things in the world to adopt. You have spent your best week producing something with a two-week half-life.
The retreat. The founder decides the lane is crowded and starts casting around for a fresher subject. This is the genuinely expensive one. You are asking the distribution system to relearn who you are from a standing start, discarding whatever topic confidence you spent a year building, and doing it at the precise moment your subject was getting more attention, not less.
Nobody has ever won a lane by leaving it.
The four moves that work
Go one level down, not one level over. If a competitor is writing "why your return rate matters," you write what your return reason codes said, in which months, and which frame you built to fix it. The level below the one they are operating at is almost always the level where your access lives — and access is the one layer nobody can copy on a deadline. They can restate your conclusion. They cannot produce the derivation, because they were not there when you did the work.
Publish the boundary. Every framework is wrong somewhere, and the person who knows where it breaks is the person who built it. A post that says "this holds for discovery SKUs and falls apart on replenishment, here is why" does something a restatement structurally cannot. It separates the author from the repeaters in a single post, and it is one of the highest-converting formats a founder has available.
Date your work instead of claiming it. Do not write "I said this in March." Write, inside a normal post, "when we ran this in March." One clause. It puts a timestamp on your version without picking a fight, and readers who have been following the subject do the arithmetic themselves. Founders resist dating claims because it feels like weakening them. It does the opposite — an undated claim reads as an assertion, a dated one reads as a record.
Change the reader, not the topic. The same subject aimed at a different role is a different post. Write the version for the ops lead instead of the founder. Write the version for the person who has to execute it on Thursday. This is how you get depth without leaving the lane, and it is the move founders reach for last because it does not feel like doing anything new.
When it is genuinely a problem
Two cases, and neither is about topic overlap.
They have your access. A former employee, a former agency, a former contractor who now publishes about the account they used to work on. This is not a content problem, it is a contractual one, and it belongs with your counsel and not in your posting schedule. Do not litigate it on the feed.
They are publishing and you are not. This is the one we see most and the one nobody wants to hear. A founder gets rattled by a competitor's post, spends two weeks feeling bad about it, and publishes nothing. Six weeks later the competitor has twenty posts in the subject and the client has four, and the platform has drawn the obvious conclusion about who this topic belongs to.
The competitor did not take your lane. The gap in your calendar did. In every case we have seen where a founder actually lost ground in their own subject, the proximate cause was a publishing pause, not a rival.
What it means commercially
Here is the reframe we give clients, and it is not a consolation prize.
A subject with exactly one credible voice reads to a buyer like one person's opinion. A subject with two or three reads like a category — a real area of practice with real disagreements in it. Categories generate demand. Opinions generate readers.
The founders who have done best out of this in our portfolio treated the arrival of a second voice as evidence they had picked correctly, then out-specificed them for two quarters. Not out-posted. Out-specificed. There is a large difference and only one of them is sustainable.
FAQ
Should I ever name them? Almost never, and never in a post that is about the fact of them. If you are genuinely disagreeing with a published position — a stated claim, not a vibe — naming the argument is fine and naming the person is optional. If what you actually want is for them to know you saw it, send a message. That is what messages are for.
They used my exact phrase. Do I say something? Privately, once, if you want to. Publicly, no. An owned phrase working in rooms you are not in is positioning arriving, which is the outcome you were building toward. It is uncomfortable and it is also the thing succeeding. Keep using it, keep attaching receipts to it, and let the version with evidence behind it be the one people remember.
Do I need to post more often now? Only if you were under-publishing already. Increasing cadence as a competitive response usually means thinner posts, and thin posts are exactly what makes two authors interchangeable. Same frequency, more working detail, is the correct adjustment.
How long before this stops mattering? It does not resolve, it gets absorbed. Within a quarter of publishing genuinely deeper material, the comparison stops being available to make — a reader cannot swap you for someone who does not have your data. The founders still bothered by it at month six are usually the ones who spent months one through five watching instead of writing.
If a competitor showing up in your subject has you rethinking your whole content strategy, the content was probably too replaceable before they got there. That is a fixable problem and it is not fixed by picking a new topic. Talk to us about what it would take to publish the version nobody else can.