LinkedIn shipped a Send button in July 2026. It sits right next to Like, Comment, and Repost on every post, and it does one thing: puts that post directly into someone's DM in one tap. No copy, no paste, no leaving the app.
Founders we work with mostly shrugged when they saw it. "Fine, another share option." That reaction misses what actually changed. This isn't a new way to share content — it's LinkedIn formalizing a behavior that used to be invisible and putting a name and a data trail on it. People have always screenshotted posts and pasted links into DMs for one specific colleague. That was dark social — real, constant, and completely unmeasured. The Send button takes that exact behavior and makes it a native, tracked, one-tap action inside the platform.
For founders writing on LinkedIn to generate leads, that shift matters more than the UI change suggests. It means there are now three distinct things a post can be optimized for, and most people are only writing for two of them.
Three currencies, not two
Every post you write is implicitly optimized for one of three reactions, whether you've thought about it that way or not.
Like-worthy content is broadly agreeable. It states something most readers already believe, states it well, and asks nothing of them beyond a tap. Cheap to give, cheap to get. Useful for warmth, useless for anything harder.
Comment-worthy content triggers a reaction strong enough that someone stops and types. An opinion, a mild controversy, a "here's where I disagree." We've written before about why comments carry outsized weight in the algorithm — they're a real signal because they cost more than a like.
Send-worthy content is a different animal entirely, and it's the one nobody has been deliberately writing for because until this month there was no native mechanic rewarding it. A send-worthy post isn't written for "readers" in the aggregate. It's written with one specific person in the sender's network already in mind. The test isn't "will this get engagement" — it's "is there someone right now who needs to see this."
That distinction is the whole post. Like-worthy and comment-worthy content is written outward, toward an audience. Send-worthy content is written toward a person — even though the writer doesn't know who that person will turn out to be. You're writing for the mental moment where a reader thinks of a specific name.
What actually makes a post send-worthy
Not every useful post gets forwarded. Sending costs the sender something — a little social capital, a small bet that the recipient will find it worth the interruption. A like costs nothing and proves nothing. A send says "I thought of you specifically, and I trust this enough to put my name on the forward." That's a higher bar, and it shows up as a handful of concrete markers.
Specificity that maps to one person's exact problem. "Amazon founders should watch their COGS" is like-worthy — everyone nods, nobody sends it. "If you're running a two-brand portfolio and still updating your search-term negatives by hand every Sunday, this is the hour you get back" describes one operator so precisely that a reader thinks of the exact person doing that exact task and forwards it to them.
A framework or tool a reader wants a colleague to have. Anything that functions like a small gift — a checklist, a naming convention, a decision tree — gets sent because handing someone a usable thing is a normal, low-friction reason to DM them. Abstract advice doesn't travel this way. A named system does.
A contrarian take the sender wants credit for surfacing. People forward takes that make them look sharp for having found it first. "Everyone in our Slack is going to be talking about this by Friday, you should see it now" is a real internal monologue. Write the kind of claim that rewards the forwarder with a little reflected credibility.
Something that saves the recipient time or makes them look smart in their next meeting. If reading your post lets someone walk into a call already knowing the thing, forwarding it ahead of that call is an easy, high-value favor. This is why tactical, specific posts outperform inspirational ones for sends — inspiration doesn't prep anyone for anything.
Notice what these have in common: none of them optimize for reach. All of them optimize for relevance to a person the writer will never meet. That's the mental shift the Send button demands.
The signal you can't see is the one that matters most
Here's the part that should change how founders think about this feature, not just how they write for it.
There is no public send counter. Likes show a number. Comments show a number and a thread. Sends show nothing on the post itself — no author will ever see "this was sent 340 times." From the outside, sending looks like it does nothing.
Internally, it's the opposite. LinkedIn's ranking system — the 360Brew architecture we've referenced before when we've written about the platform's reach-tier mechanics — absolutely logs every send. The platform can see exactly which posts get pulled out of the feed and pushed into a specific, named DM thread, even though the author of the post never gets that number.
That asymmetry is the interesting part. A like is nearly free and easy to fake — pods, bots, reciprocal tapping have all been tried. A comment is harder to fake but still gameable with a little effort. A send is expensive to fake, because it requires choosing a specific real person and spending a small amount of social capital on them. You can't engagement-pod a DM share the way you can a like — it would mean recruiting people to send posts to each other for no reason, which collapses under its own absurdity fast.
That makes a send close to the cleanest quality signal LinkedIn has: private, costly to give, nearly impossible to fake, and correlated with content that solved a real problem for a real person. A ranking system built to expand reach for posts that pass a test-pool check is exactly the kind of system that would weight a signal like this heavily — high cost, high honesty, low noise. You should expect sends to matter a lot to whether a post graduates past its early test pool, even though you will personally never see the number that's driving it.
Writing for "who would I send this to"
The practical shift is small to describe and takes discipline to actually do. Before you write, and again before you publish, ask one question: who would I personally send this to right now?
Not "would this perform." Not "is this on-brand." A single named person — a specific client, a specific peer, a specific operator you know is dealing with this exact problem this week. If you can't name someone, the post is probably too generic to be send-worthy, even if it's perfectly like-worthy.
That question changes the draft in a few predictable ways:
- The hook gets narrower, not broader. Instead of "here's a mistake ecommerce founders make," you write "here's the mistake I watched a three-person Amazon brand make with their PPC negatives last month." Narrow reads as more relevant, not less — the reader who fits the description recognizes themselves instantly, and the reader who doesn't fit thinks of who does.
- The close changes from a question to a handoff. Most advice says end posts with "thoughts?" to bait comments. That's optimizing for the wrong currency. A send-worthy close names the reader directly: "If you run a two-person Amazon brand and haven't automated your search-term hygiene, this is your Monday." That line does two things at once — it tells the actual target reader this was written for them, and it hands every other reader the exact phrase they'd use to forward it. You're writing the caption the sender will effectively paste into the DM.
- You keep both currencies in view, not just one. A post can still earn likes and comments while being built for sends — those aren't mutually exclusive. But if you're only checking "did people react," you'll keep producing content that performs on the metrics you can see and quietly loses on the one you can't.
FAQ
Should I stop writing comment-bait posts now that sends exist? No — comments still matter and we've written about why they're worth engineering for. The point isn't to abandon comment-worthy content, it's to recognize that a post can be built for a third outcome the algorithm can see and you can't. Strong founder content increasingly does more than one job at once.
How would I even know if my posts are getting sent, since there's no counter? You mostly find out secondhand — someone DMs you "so-and-so sent me your post about X," or a prospect opens a call with "I saw this from a colleague." Track those mentions loosely; they're the only visible trace of an invisible signal. A rising pattern of "someone forwarded me your thing" is a real data point even without a number attached.
Isn't this just the first-comment or reach-tier stuff again? No — this is specifically about the new native Send mechanic and what content gets built to trigger it, not about comment velocity or how the test-pool graduation process works generally. Sends are a distinct, higher-cost signal running in parallel to likes and comments, and they call for different writing choices than either.
Does this apply if I have a small following? More than most signals, yes. A send doesn't care about your follower count — it only requires one person in someone else's network deciding your post was worth forwarding. A tightly specific post from a 1,500-follower founder account can get sent around a Slack channel just as easily as one from a large account, arguably more easily, because specificity reads as more credible from a smaller, more focused voice.
Most founders are still writing exclusively for likes and comments because those are the numbers they can see. The Send button rewards a completely different move — writing narrow enough, useful enough, and pointed enough that a stranger thinks of one specific colleague and hands your post to them. That's harder to do consistently than chasing reactions, which is exactly why it's underused. If you want your content built around that standard instead of guessed at post by post, that's the system we run for ecommerce and Amazon founders at EcomGhosts — get in touch.