Content Repurposing for Founders: Start With a Comment

Every content repurposing guide I've read starts in the same place: take your webinar, your podcast, or your 3,000-word pillar post and slice it into 20 social assets. That works if you have a content team. Most founders I know don't have a webinar. What they do have is a comment they wrote at 11pm in r/SaaS that got more replies than anything on their company blog.

That comment is the best thing to repurpose, and it usually gets forgotten. This is content repurposing for founders run in the other direction. Start from what already landed in a conversation, then rebuild it for the places it hasn't reached yet, without tripping the spam filters that make copy-paste cross-posting risky.

Cross-posting vs content repurposing

The two terms get used interchangeably. On discussion platforms the difference decides whether your post lands or gets removed.

• Cross-posting is the same text and the same link dropped in several places. That's fine for your own feeds. It's risky anywhere a moderator or a spam filter is watching.

• Repurposing keeps the idea and rebuilds everything else: a new hook, a new length, a new framing for a new audience. The X version and the Reddit version share an insight, not a sentence.

Identical titles and links showing up in several subreddits within hours is exactly the pattern Reddit's filters and moderators look for. The ban-avoidance side is covered in How to Promote on Reddit Without Getting Banned, so this post sticks to repurposing.

Start with the comment that already landed

Founders are bad at picking what's worth repurposing because they judge their own work. Let the replies judge it instead. Once a month, go through your last 30 days of posts and comments and look for:

1. Replies, not just upvotes. A comment that started a back-and-forth hit a nerve. An upvoted one-liner usually didn't.

2. "Saving this" or "can you share more?" People asked for the longer version, so write it.

3. A DM or chat request because of the comment. That's the strongest signal you'll get.

4. Evergreen over news. "How I set up our cancellation survey" still works in six months. "My take on this week's API drama" won't.

Next to each piece, write down where it already lives. That "covered" list keeps you from pitching the same idea twice to the same crowd, which is how repurposing turns into spam.

The founder repurposing matrix

Each platform gets the format its readers already like, whatever format the idea started in.

Text never goes straight to TikTok or YouTube. Those platforms want video, so the repurposed version there is a script you still have to record.

The platform rules that bite

Reddit: use Repost, or rewrite

Reddit renamed crossposting to reposting on June 4, 2026, per Social Day. It works the same as before. It shares a preview of your original post into another community and links back to it. If you want the same post in a second subreddit, the built-in Repost is the honest way to do it, because everyone can see where it came from.

If the second community needs a different angle, rewrite it for real. Give it a new title that states the takeaway for that sub, a new opening, and examples that fit its readers. Post it days later, not minutes later. If your posts keep vanishing, run the checks in Reddit Shadowban Check.

Hacker News: reposts are allowed, rarely

The HN FAQ is plain about it: "If a story has not had significant attention in the last year or so, a small number of reposts is ok. Otherwise we bury reposts as duplicates." A Show HN that sank isn't dead, but you get a few retries, not a weekly slot. A good idea usually does better as a comment in someone else's thread (more on that here).

X, LinkedIn, and Threads: put the value in the post

Feed platforms don't want to send readers somewhere else, so the repurposed post has to be complete on its own, with the link last or left out. The details are in X Marketing for Founders and LinkedIn Comment Strategy for Founders.

dev.to: set the canonical, and still publish at home first

When you republish a full article on dev.to, set canonical_url in the front matter to point at your blog. Just don't count on it working. Google's canonicalization guidance says the canonical link element "is not recommended for those who want to avoid duplication by syndication partners, because the pages are often very different." Publish on your own site first and let it get indexed. Better still, make the dev.to version a different post: the technical half of the story, with a link home for the rest.

Rewrite, don't reformat: one comment, three posts

Here's an example. Say you left a long comment in r/SaaS about the one cancellation-form question that finally explained your churn, and a dozen people replied asking for details.

• X post: lead with the claim, not the context. "The only cancellation question worth asking: what are you switching to?" Then three short lines on why. No link.

• Reddit post, a week later, in a different sub: a title that states the takeaway, and a how-to body with the exact wording, what you did with the answers, and what you'd change. Say you run the product. No link unless the sub allows it.

• LinkedIn post: the personal lesson. What you believed about churn, what the answers showed, and what you changed.

That's one insight in three formats with no sentence shared between them. If a rewrite still reads like the original with the line breaks moved, it's a cross-post. If it reads like a model wrote it, fix these six tells first.

Space it out

A niche founder's audience overlaps across platforms. Post five versions of one idea in a day and people learn to skip you. Here's a cadence that works:

1. Day 0: the original lands.

2. Days 2–4: the standalone post on X, Threads, or Bluesky.

3. Days 5–10: the rewritten Reddit or Indie Hackers post, in a community that hasn't seen it.

4. Weeks later: the long version, if the short ones pulled replies.

Stop as soon as a version flops. That audience has already told you the idea doesn't fit, and posting it again won't change that.

Where Social Cue fits

Social Cue is a Claude Code plugin plus a Chrome extension, and it runs on the Claude subscription you already pay for. There's no extra AI bill and no platform API to lose. Scheduling tools already handle posting. What they don't handle is reach, and that's the part Social Cue covers.

Two free commands run the loop above. /log-activity visits your own profile and replies pages on each platform you're logged into and records what you've posted and commented since the last run, including what you wrote from your phone. /suggest-crosspost reads that log and your Content Library, checks which platforms each piece has already reached, and pitches 5–10 ranked repurposings for the places it hasn't. Your picks become platform-native drafts. Nothing gets posted. You schedule what you like, or hand a subreddit, Indie Hackers, or Show HN post to the Pro /content-post command.

It's only as good as what you've logged, and it can't tell you a sub's rules changed last month, so read the sidebar before you post. Where it does help is the step most founders skip: remembering, a week later, that a comment was worth posting again somewhere else.

Your content repurposing checklist

1. Monthly: list the posts and comments from the last 30 days that drew replies.

2. Write each one's covered list.

3. Pick one or two new targets per piece from the matrix.

4. Rewrite each version from scratch, with no shared sentences.

5. Reddit: Repost, or a real rewrite days later. HN: repost rarely. dev.to: canonical, home first.

6. Space versions over days or weeks, and stop when one flops.

Your best marketing writing probably isn't on your blog. It's in a reply thread, under someone else's question. Rewrite it for a new audience and post it there.