Content Plan Generator

Enter an account and get fourteen dated slots: which day, which hour, which format, and the measurement that put each one there. Nothing here is generated text or a rule of thumb, and where a network gives us less to work with, the plan says so on the page.

What the planner actually schedules

The PlayerSells content planner builds 14 days of dated posting slots for an account on X, Instagram, Bluesky, Telegram, YouTube, Kick and Twitch. It reads the account's own posting record, needs at least 8 timestamped posts before it will describe a rhythm, and schedules at most 1.5 times the cadence that account already sustains, capped at 4 posts a day on X.

On X, the format rules come from a catalog-wide comparison that pairs every scanned account against itself and applies a Benjamini-Hochberg correction before publishing a bucket. Attaching an image measures as the single largest format effect in that table. On Instagram the same paired comparison runs live across the stored post catalog and returns a result worth stating plainly: reels take fewer likes and comments per post than the same account's carousels and feed posts, while carrying far more views. Those are different outcomes and the planner keeps them apart.

An effect smaller than 5% is reported but never scheduled against, because a difference that size does not justify reorganising a week.

Figures recomputed daily from the PlayerSells directory catalog.

How the plan is built

The planner reads the account's own posting record first, buckets it into day and hour cells scored against that account's own median, and works out the cadence it already sustains. Relative scoring rather than raw engagement matters here: on a growing account, raw numbers rank the oldest posts last and call the result a schedule.

Then it asks what is known about accounts of the same size. On X that is a catalog-wide table that pairs every account against itself, tests each bucket and corrects for multiple testing before publishing anything. On Instagram the same paired comparison is computed live across the stored post catalog. On the other five networks no such table exists, and the plan is built from the account's own history alone and labelled that way.

The two sources do different jobs, because that is what the data supports. The account's own history picks the hour, since it is the only source that knows when this audience is awake. The catalog vetoes: what it holds for timing is a set of hours the whole cohort measurably loses on, so it pushes slots off those rather than choosing between the rest.

Why there is no AI here

A language model would happily write fourteen posts and a rationale for each. It would have no way of knowing whether any of it works, and neither would you.

Everything on this page is either a measurement or a real post that someone published. Where a rule says a format lifts engagement, the figure beside it is the median account's change, with a 95% interval and the number of accounts behind it. Where the page shows an example, it is a post that actually ran and actually beat its author's median.

What this cannot tell you

It cannot tell you what to say. Timing, format and cadence are the parts that are measurable across accounts; the subject is not, and a tool that claimed otherwise would be guessing in a confident voice.

A fortnight of slots is a forecast built on a sample, not a promise. Slot confidence tops out at 95 for that reason, and a plan built on a thin sample says so in its strength score rather than looking identical to one built on a deep one.

The Kick and Twitch schedules describe the last seven days, because that is the full retention on the concurrent-viewer sampling behind them. They are a reading of a week, not a habit.

Turning the plan into scheduled posts

Everything above stops at the decision. The plan names a day, an hour and a format, and then it is a document: nothing here connects to an account or sends a post. That last step is a different kind of tool, and CRM Solid's post scheduler for X is the one we point people at, with sibling schedulers for Instagram, YouTube and TikTok. It queues threads against a connected account and reports what each one did afterwards, which is the half of the loop this page deliberately does not try to own.

Frequently asked questions

Does this write the posts for me?

No. It decides when to post, what format to use and what the measurement behind each choice is, then shows you real posts from accounts your size that did well in that format. Nothing on the page is generated text.

Where do the numbers come from?

Two places, and the page always says which. Format rules on X come from a catalog-wide comparison that pairs every account against itself and corrects for multiple testing. Timing comes from the account's own posting record. On the other networks only the second source exists, and the plan says so instead of borrowing the first one's language.

Why does it schedule fewer posts than other planners?

Because it starts from what the account already sustains and adds at most half again. A calendar that jumps someone from one post a week to four a day is abandoned inside a fortnight, and a plan nobody follows measures nothing.

Why is TikTok missing?

Post timestamps for a TikTok account cost a paid API credit per lookup, because TikTok does not show play counts to a logged-out reader. Every other network here is answered from data we already hold or from a free public endpoint, and a free tool that spends a metered budget on every visit does not stay free.

What does the confidence number on a slot mean?

How strongly the measurements back that particular square, from 0 to 95. It is not a predicted engagement figure and not a probability. A slot placed on a corrected catalog finding scores higher than one placed on four of your own posts, even when your four posts looked better.

How often does the underlying data update?

The catalog comparison is recomputed daily. Posting history is read live when you run the tool. The concurrent-viewer readings behind the Kick and Twitch schedules are sampled every fifteen minutes and kept for seven days, which is why those plans describe a week rather than a habit.

Not affiliated with X Corp, Meta, Bluesky, Telegram, YouTube, Kick or Twitch. Figures are measured from public data and from our own directory catalog.