You wrote a post that worked. Forty comments, a few DMs, two people you did not know saying "this is exactly my situation". Then you scrolled on and wrote another one.
That post was not content. It was a finished argument, tested on a live audience, with evidence of who it hit. And most consultants let it die in the feed.
Learning to repurpose LinkedIn content is not about reposting it in three formats. It is about taking one idea and letting it travel down three channels that each do a different job: the feed, the invitation, the conversation. Same idea, three shapes.
Start by picking the post that actually earned it
Not the one with the most likes. Likes are cheap and often come from peers.
Pick the post where the comments contained a problem. Someone wrote "we tried that and it stalled at the handover" or "my team does this and nobody reads the output". That is a post that found a nerve, which means the idea inside it is a diagnosis, not an opinion.
Three quick tests:
- Did at least two people describe their own situation in the comments?
- Did anyone send you a DM about it, even a vague one?
- Can you say the core idea in one sentence without using the word "strategy"?
If all three are yes, you have raw material. Reach numbers alone tell you less than you think — a post can travel wide and touch nobody who buys. Dwell time and the shape of the engagement tell you more about whether the idea landed than the like count on the front of it.
Now extract the spine. Write it down in this form: people like X keep running into Y, and the reason is Z. That sentence is the asset. Everything else in this article is a translation of it.
Channel one: the post, rewritten as a sharper version
The first channel is the feed again — but not a copy-paste repost.
The original post was you discovering the idea. The second version is you knowing it. Three ways to re-cut the same spine:
The example version. Original was the principle. New one opens with a single situation and lets the reader work out the principle. "A client sent me their onboarding doc last week. Eleven pages. Nobody on the team had opened it since March."
The counter version. Take the objection someone raised in the comments and build the post around it. "Three people told me X doesn't work when the team is remote. They're half right. Here's the half."
The list version. The spine broken into the five places Y shows up. Lists are weak when they are generic and strong when each item is something only a practitioner would notice.
That is three posts from one idea, spread over six weeks, without repeating yourself. The choice between them is not taste — it is what you want the reader to do next. Teaching, proving and inviting are different jobs, which is why it pays to choose the format by intent rather than by what is trending.
And do not put the link to your long-form version in the post body if you can avoid it. External links change how a post travels; the first comment is usually the better home for it.
Channel two: the invitation note
This is where repurposing earns its keep, and where almost everyone wastes it.
The post gave you a list of people who raised their hand. Commenters. Reactors. The people who viewed your profile the day after. These are not cold. They have read your thinking once, in their own time, with no pressure. That is the cheapest warmth you will ever get.
The invitation note is 300 characters. It has exactly one job: make the connection feel like a consequence of something that already happened.
Bad, because it is about you:
Hi Sarah, I post about operations for scaling teams, would love to connect and share more.
Better, because it is about her sentence:
Sarah — you said the handover is where it stalls for you too. That's the part I've spent two years on. Happy to connect.
No ask. No "I'd love to hop on a call". The note's only purpose is to get accepted and to leave a true reason in her inbox.
For people who reacted but did not comment, you have less to work with. Reference the post, not their reaction: "We crossed on the post about eleven-page onboarding docs — connecting in case it's useful." Thin, but honest, and it beats nothing. Whether to send a note at all depends on the segment, and the trade-off is real in both directions — worth reading the case for and against the note before you standardise it.
One warning that matters here. If you use software to send those invitations for you, including a Chrome extension running in your own browser, you are using automation that LinkedIn's User Agreement does not allow — it prohibits third-party tools that automate activity on the platform. BIZLINKED is exactly that kind of tool: its extension automatically sends invitations and AI-written messages inside your own session, within limits it sets itself (at most 100 invitations a week, 150 once more than 40% are accepted, business hours, random pauses). Those limits reduce the obvious footprint. They do not make it permitted, and an account can be restricted at any volume. If you use it, you are choosing speed and accepting that risk knowingly. If that is not a trade you want, do this list by hand — a post's worth of commenters is twenty or thirty people, which is an hour.
Channel three: the first message and the follow-up
The invitation gets accepted. Now what?
The mistake is to treat acceptance as permission to pitch. The other mistake is to say nothing and let the connection rot.
The first message is the post's question, not its conclusion. You already told them what you think. Now ask them the thing the post made you curious about.
Thanks for connecting. Genuinely curious, since you mentioned the handover — is it a documentation problem on your side or a nobody-owns-it problem? I keep seeing both and they need opposite fixes.
That works because it is answerable in one line, it is specific to something they wrote, and it has no commercial hook attached. You are not qualifying them. You are continuing a thought.
If they reply, you have a conversation and the rest is normal consulting. If they do not, you need a follow-up that adds rather than nudges. The post you wrote in channel one is that follow-up — but sent as a thing, not as a link to your own feed:
No reply needed — I wrote up the two versions of that problem and what separates them. Three paragraphs, no form. Want it?
Most of the people who ignored message one will ignore this too. Some will not. What kills the sequence is the third message that says "just bumping this up" — there is a better structure for the no-reply sequence that does not depend on persistence alone.
One more thing. When someone says "sure, send me more info", the post is the worst possible answer. A post is written for strangers. They are no longer a stranger. That request needs a different handling altogether.
What this looks like as a weekly habit
The whole system is one hour, once a week, and it only works if the order is fixed.
- Monday. Open your last four weeks of posts. Pick the one with problem-shaped comments. Write the spine sentence.
- Monday, same session. Open the reaction and comment lists. Copy the names into a document with their one line. Twenty to forty people is plenty.
- Tuesday. Send the invitations, each with a note built from their own sentence. Fifteen minutes if you do not overthink it.
- Thursday. Message whoever accepted. The question, not the pitch.
- Following Monday. Write the re-cut version of the post. It feeds next week's list.
The loop is the point. The post generates a list, the list generates conversations, the conversations tell you which idea to write about next. Without the loop, posting is a lottery and outreach is cold.
If you want one change this week, make it step two. Most people never open the reaction list on their own posts. That list is the only free warm audience you have, and it decays — a comment from six weeks ago is a weak reference, a comment from Tuesday is a conversation.
