How do you repurpose LinkedIn posts into a newsletter?
Keep the idea. Add the context, the link and the reply.
Which LinkedIn posts are worth repurposing?
Not the ones with the most likes. A like costs nothing and tells you little. The posts worth a second life are the ones that made people do something: write a real reply, save the post, send it to a colleague, or message you about it. Those actions mean the idea landed and someone wanted to keep it. That is the same reaction you want from a newsletter reader.
LinkedIn's own help page on relevance says the feed looks at how constructive or professional the conversation under a post is, alongside views and engagement. Its March 2026 note on the feed says it is reducing recycled, click-driven posts and favouring posts with genuine insight and thoughtful perspectives. Read that as a hint for your own filter: the posts that started a useful conversation are the ones worth expanding. The ones that only got a reaction are not.
| Signal | What it tells you | Repurpose? |
|---|---|---|
| Replies that add a story or a disagreement | The idea is specific enough to argue with | Yes, first choice |
| Saves and direct messages | People want to keep it or act on it | Yes |
| Reshares with a comment | Someone used your framing with their own audience | Yes, if the comment adds something |
| Likes only | It was easy to agree with | Usually no |
| Comments that are one word or an emoji | A hook worked, the idea did not | No |
What does the weekly flow look like?
Repurposing works when it is a routine, not a scramble on send day. Five steps, in order, once a week. For teams that send more or less often, scale the collection window to match; the cadence guide covers how to choose that schedule.
- Collect. Early in the week, copy every post from the last seven to fourteen days into one document, with the replies that mattered underneath. Do this from the post itself, not from memory.
- Pick. Run the filter above. Choose one post. If two are close, choose the one where a reply asked a question you did not answer.
- Expand. Write the newsletter section from the post, not around it. Add the setup the post skipped, the step a reader would take next, and the answer to the best question from the replies.
- Link. Add one link the post could not carry: a longer guide, a template, a case study, a calendar page. One, not three.
- Send. Write the subject line last, from the section, and end the section with a question readers can answer by replying. Then log which post you used so you do not repeat it.
If your newsletter has a fixed structure, the repurposed post usually becomes the lead section and the rest of the issue stays as it is. Our guide to running a B2B newsletter shows where that section sits in a full issue.
What does a post look like once it becomes a newsletter section?
Here is one worked example. The post is illustrative: we wrote it for this guide, about a renewal problem many B2B teams recognise. It is not a client post and the details are invented. The section that follows is the same idea, rewritten for email.
Before: the LinkedIn post
Illustrative LinkedIn post, about 130 words
We almost lost a renewal last quarter, and the warning sign sat in our inbox for six weeks.
The customer had stopped replying to our monthly check-in. Not angry. Just quiet.
Our account manager read it as "busy." It was actually "evaluating a competitor."
Here is what we changed:
1. Silence is now a trigger, not a non-event. Two unanswered check-ins open a renewal-risk task.
2. The task goes to someone other than the account manager. A new voice gets replies a familiar one does not.
3. The first message does not mention the renewal. It asks one question about the thing they bought the product to do.
The renewal closed. Smaller than before, but it closed.
Most churn does not announce itself. It goes quiet first.
What is your earliest warning sign for a renewal at risk?
After: the newsletter section
Illustrative newsletter section, lead slot
Quiet accounts: the renewal signal most teams misread
If you sell annual contracts and your customer success team is small, you probably run some form of monthly check-in: a short email asking how things are going. This section is about what to do when those emails stop getting answered.
Last week I posted about a renewal we nearly lost because a customer went quiet for six weeks and we read it as "busy." The replies were the useful part. Several of you said the same thing: silence is the most common early signal, and the one most teams treat as nothing.
The practical change is small. In your CRM, make two unanswered check-ins create a task. Assign that task to someone the customer has not been emailing, usually a founder or a product lead. Their first message should not mention the renewal at all. Ask one question about the outcome the customer bought the product for. You are not trying to save the deal in that email. You are trying to get a reply, because a reply gives you something to work with.
A few of you asked what the second and third messages look like. We wrote the full three-message check-in sequence, with timing and a note on when to hand it back to the account manager, here: the renewal check-in sequence.
Reply to this email with the earliest warning sign you watch for. I read every reply, and I will share the best ones, anonymised, in the next issue.
What changed, and why
| Change | Why |
|---|---|
| Opened with who it is for, not with the story | A post has to stop a scroll. An email reader already opened it; tell them in one line whether this applies to them. |
| Added the context the post skipped | The post assumed the reader knows what a check-in is and why a small team runs them. The email explains it in two sentences. |
| Brought in the replies | The best part of a good post is the thread. Quoting what readers said, without names, turns the section into a conversation, not a rerun. |
| Added the "so what" | The post listed three changes. The email says how to set them up, who should own the task, and what the first message is for. |
| Added one link | A post cannot carry a link well. The email points to the full sequence, which is the next step a reader would want. |
| Replaced the comment prompt with a reply prompt | A question at the end of a post asks for public comments. In email, ask for a reply and say what you will do with it. |
When we do this for a client, the post and the section are rarely the same length. The section is usually longer, because it has to carry what the post could only hint at.
What should you change when a post moves to email?
Three edits do most of the work. The others follow from them.
Cut the hook
Posts open with a line built to make people click "see more." In email, that line reads as bait, and the reader has already given you the open. Start with the point, or with who the section is for. Google's sender guidelines also ask that headers and content be accurate and not misleading, which rules out subject lines that promise more than the section delivers. Our subject line guide covers how to write one from the section rather than from the hook.
Add the "so what"
A post can stop at the insight. A newsletter section should say what to do with it: the step, the owner, the tool, the trap. If you cannot write the "so what", the post was an observation, not a lesson, and it is probably not the right one to expand.
One link
Choose the single link that is the natural next step. More than one and the reader has to choose, and most will choose nothing. If the obvious link does not exist yet, that is a sign of what to build next: the guide, template or case study the post keeps pointing at.
Keep the email side healthy while you do this. Google's guidelines ask senders to keep spam rates below 0.10% and never reach 0.30%, to support one-click unsubscribe on marketing mail, and, above 5,000 messages a day to Gmail, to authenticate with SPF, DKIM and DMARC. None of that is specific to repurposing, but a newsletter that grows from LinkedIn tends to grow fast, and those rules are where fast growth breaks.
What should you not repurpose?
Some posts do well on LinkedIn for reasons that do not survive the move.
- Posts that only work in the feed. A reaction to news from that morning, a reply to someone else's post, a poll. By the time the issue goes out, the moment has passed.
- Posts that are all hook. If the first line is the whole idea and the rest is restatement, there is nothing to expand.
- Personal updates. A new hire, a conference photo, a milestone. Fine on LinkedIn. In a newsletter the reader signed up for, it is a section they skip.
- Posts you already turned into an issue. Keep a log. Repeating an idea within a quarter is noticed, and not kindly.
- Posts with a claim you cannot back up in writing. A round number thrown into a post gets a pass. The same number in an email, with your name on it, gets a reply asking for the source. Expand only what you can support.
How does the newsletter feed LinkedIn back?
The flow runs both ways, and the return trip is where the list grows. Three ways to use it.
Replies become next week's post. The reply prompt at the end of a section brings in stories and objections you did not have. Write the next post from the best reply, with permission and without the name. It is specific, it is new, and it came from your audience.
The issue becomes the post's link. When you post the next idea, you now have somewhere to send people who want more: the issue, or the signup page. A post that says "the longer version went to the list on Tuesday" gives readers a reason to join. If you are using a lead magnet to do that, see how to promote a lead magnet on LinkedIn.
LinkedIn's own newsletter is a doorway, not a destination. LinkedIn Help says any member can create a newsletter on the platform, and that subscribers get push, in-app and email notifications when an edition is published. That reach is useful. But the subscriber list belongs to LinkedIn, not to you, and you cannot email those people yourself. Use a LinkedIn newsletter as a preview that points to the email list, where you own the relationship.
For a sense of what the finished issue looks like, see our B2B newsletter examples, several of which lead with a section that began as a post.
About this guide and its sources
This is Sawa's working method for moving ideas between LinkedIn and email. The worked example is invented for this guide and labelled as such. The numbers come from LinkedIn's and Google's own help pages, fetched on the date shown; they describe platform limits and sender rules, not results you should expect.
- LinkedIn Help: Post and share updates
States the 3,000-character limit for a post and that longer pieces should be published as an article.
- LinkedIn Help: LinkedIn relevance, optimizing the member experience
Lists the three signal types the feed evaluates (identity, content, activity), including how constructive the conversation on a post is.
- LinkedIn News: How LinkedIn Is Improving the Feed (March 2026)
LinkedIn's own statement that it is reducing recycled, click-driven posts and engagement bait in favour of posts with genuine insight.
- LinkedIn Help: LinkedIn Newsletters
Confirms any member can create a newsletter on LinkedIn and that subscribers receive push, in-app and email notifications per edition.
- Google: Email sender guidelines
Source for the 0.10% and 0.30% spam-rate thresholds, one-click unsubscribe, the 5,000-messages-a-day authentication rule, and the requirement that headers and content not be misleading.
Frequently asked questions
Put the repurposed section into a full issue
The newsletter issue template has a lead slot built for a section like the one above, plus the rest of the structure around it.
Need help with this? See how Sawa handles newsletters and LinkedIn content, or book an intro call.