Your top post got 12K views once. 95% of followers saw nothing.

Recycling surfaces the evergreen winners sitting in your back catalog, generates AI variants with a new hook and shape so each recycle reads fresh, and queues them across the months ahead. Auto-stop the moment engagement drops below your floor, so nothing turns into spam.

Surfaces evergreen winners from your back catalog
New hook, new caption, same idea: rewrites per recycle
Per-post cadence, weekly through every 90 days
Auto-stop when engagement drops below your floor
What a recycle queue actually looks like

One winner. Three variants. Spread across the quarter.

Real shape of a recycle: the original post on top, three AI-generated variants below, each measured against the engagement floor you set on the queue.

Source post
LinkedIn·Mar 12, 20261,840 engagements

Most launches die on Tuesday because the people who would have shared them are still catching up on their inbox.

AI generated 3 variants
Recycle queue
1Variant 1·Shipped Tue, Aug 5 · 9:00am
completed

Why your Tuesday launch is dead on arrival, and the 3 days that work better.

Landed at 1,410 engagements77% of the original. Queue keeps running.
2Variant 2·Wed, Sep 3 · 9:00am
scheduled

5 reasons launching on Tuesday is the worst day of the week. A thread.

Floor: 920 engagementsBelow this, the queue pauses itself
3Variant 3·Thu, Oct 9 · 9:00am
scheduled

The Tuesday launch myth, debunked with 6 months of analytics from solo founders.

Floor: 920 engagementsBelow this, the queue pauses itself
AI rewrites per variant. Fresh hook every time.
Auto-stop guard rails. Nothing turns into spam.
Every recycle measured against the original.
The cost of writing every post from scratch

You only show up for 5% of your followers. Then you move on.

The post that hit 12K views in March was seen by 5% of your followers. The other 95% missed it. You wrote it once, the algorithm showed it once, you moved on.

You spent 3 hours writing the launch tweet that landed. You wrote another from scratch the next quarter when you could have reshipped the winner with a new hook.

The thread that earned your biggest week of new subscribers is buried 200 posts deep. You forgot it existed. It is still sitting there, still relevant, still unseen.

Is this for you?

Is recycling for you?

For you if

  • You write evergreen content (tips, frameworks, case studies, how-tos)
  • You have a back catalog of 50+ posts that earned real engagement
  • You're a solo founder and writing every post from scratch is the slow part
  • You ship to platforms where most followers see less than 10% of your posts (Instagram, LinkedIn, X)

Not for you if

  • You post mostly time-sensitive content (news, live events, real-time commentary). Recycling does not fit.
  • You post fewer than 20 times a month total. The back catalog has not built up yet, recycle later.
What's inside

Make your back catalog work for you.

Every post you ever shipped is sitting there. Recycling finds the winners, rewrites them, and re-ships them to the 95% of your followers who missed them the first time.

The recycler surfaces your evergreen winners

It ranks everything you shipped more than 30 days ago by engagement, then sets aside anything that reads as time-bound (dates, months, "today", "breaking", deadlines) so tips and frameworks rise instead of last quarter's news. You see the top 20 with one click.

AI variants per recycle

Each recycle is a fresh draft: new hook, new opening line, same core idea. Powered by Brand Voice and the original post's transcript. Reads like you wrote it twice.

Per-post cadence

Weekly, every two weeks, every 30, 60, or 90 days. Each winner gets its own queue, so you set the spacing from that post's shelf life instead of one global rule.

Auto-stop guard rails

Set an engagement floor (e.g., 600 engagements). The moment a recycle drops below it, the recycle pauses and you get a notification. Nothing turns into spam without you noticing.

One queue per winner

Every source post gets its own queue with its own cadence, floor, and stack of approved variants. Nothing is pooled, so two versions of the same idea never land in the same week by accident.

Recycle vs original tracking

Twenty-four hours after a recycle publishes, its engagement is measured against what the original earned. You learn which back-catalog posts are gold and which ran their course, and the queue acts on that answer without waiting for you.

How it works

Pick winners. Set cadence. Ship.

01

Ship through FoPost

Recycling reads the posts you published through FoPost, since those carry the engagement numbers a recycle gets measured against. Anything older than 30 days is a candidate.

02

Pick the winners

The recycler ranks your back catalog by engagement, sets aside the obviously time-bound ones, and surfaces the top 20. Tick the ones worth re-shipping.

03

Set cadence and guard rails

Per post: weekly, every two weeks, or every 30, 60, or 90 days. Per post: an engagement floor, which starts at 50% of what the original earned. Save.

04

Approve variants, the queue ships them

Generate up to 6 AI variants per winner, read them, approve the ones that hold up. Each time the cadence comes due, the queue takes your next approved variant and schedules it. It tells you when the approved stack runs low, and pauses itself if a recycle lands below your floor.

vs the alternatives

Why this beats manual reposting (or, more often, not reposting at all).

Three ways founders extend the life of a good post. Only one of them is a real recycle with AI variants, auto-stop, and performance tracking.

Do nothing

What most founders default to

  • 95% of your followers never see your best post.
  • Every new post starts from scratch. The talent has to keep producing.
  • Your back catalog earns dust.

Buffer or Hootsuite "Reshare"

What some schedulers offer

  • Same caption, same hook. Reads like a lazy repost.
  • No AI variant. Followers who saw it the first time notice immediately.
  • No auto-stop. Keeps recycling even when engagement craters.
  • Manual scheduling per post.
FoPost

FoPost recycling

What you actually want

  • AI variant per recycle. New hook, new caption, same idea.
  • Auto-detection of evergreen winners from the back catalog.
  • Auto-stop the moment engagement drops below your floor.
  • Recycle vs original tracking. You learn what holds up.

Publishes to all major networks

Frequently asked questions

Will my followers notice the same post?

Most will not, because (a) only 5 to 10% of your followers see any given post on most platforms, and (b) the AI variant changes the hook and shape so even the followers who saw the original read it as a fresh take. The core idea is the same, the delivery is not.

Is recycling considered spam?

Not when done thoughtfully. Recycling an evergreen tip every 3 months is normal practice (many top creators do it). Recycling the same announcement daily is spam. Default cadence is conservative (quarterly or longer) and auto-stop pauses anything that loses traction.

How does auto-stop work?

Set an engagement floor per post (default is 50% of the original post engagement). The recycler measures the new recycle 24 hours after publishing. If it falls below the floor, the next scheduled recycle pauses and you get a notification. You unpause manually or let it stay paused.

Which platforms does it work on?

Every platform you have connected. Recycling pays off most on fast-feed platforms (X, LinkedIn, Instagram, Threads) where reach decays in hours. It pays off less on slow-feed platforms (Mastodon, Bluesky) but still works.

Can I recycle posts I made outside FoPost?

Recycling reads the posts you shipped through FoPost, because those are the ones it can measure a recycle against. A winner you published elsewhere gets there the same way everything else does: run it through the composer once, and from that point it sits in the candidate list with the rest of your catalog.

How many variants per source post?

Up to 6 per source, and each one costs about 1 AI credit. Ask for fewer if you only want a couple. When the queue works through the approved stack it tells you, and you generate the next batch from the same source post.

Can I edit a variant before it ships?

Yes, and you have to: a variant is a draft until you approve it, and the queue only ever ships approved variants. Read them in the review dialog, edit the wording, approve the ones you like, delete the rest. Nothing you have not read goes out.

What's the recommended cadence?

For evergreen tips and frameworks, every 90 days is safe. For threads and longer-form, stretch it further by generating fewer variants so the queue runs out on purpose. Start conservative, watch the first recycle against the floor, then tighten it if the numbers hold.

Ready to try content recycling?

7-day free trial. 30 platforms. Unlimited posts on every plan.