A content week stopped being "posts" a while ago. Mine currently includes a thread on X, a text post on LinkedIn, a Reel, sometimes a YouTube Short cut from the same clip, and a Story that deletes itself after a day. Five formats, five sets of rules, and until I fixed it, roughly five browser tabs to publish them all.
Full disclosure before we go further: Planpost is my product. I built it, I schedule my own content with it every week, and this post is a founder walking through his workflow, not a review. The tab-juggling above is the specific annoyance the composer exists to remove.
The formats, named properly
Planpost thinks in five post types: post, thread, reel, short, and story. It publishes to eight platforms: Facebook, Instagram, LinkedIn, Threads, TikTok, X, YouTube, and Bluesky.
One naming collision worth clearing up, because it confuses everyone at least once. Threads with a capital T is Meta's platform. A thread with a lowercase t is the multi-part format you post on X, on Threads, or on Bluesky. So yes, you can schedule a thread to Threads. I did not invent these names. I just build around them.
The types map to formats you already know. A post is the standard single unit and works everywhere. A thread is a chain of connected segments published in order. A reel is vertical video on Instagram or Facebook, a short is YouTube's version of the same idea, and a story is the 24-hour format that expires on schedule.
The reason these deserve separate types instead of one text box is that they do not accept the same shape of content. A thread needs segment breaks in sensible places. A reel needs a video and a caption that works without it. A story barely needs words at all. Any tool that pretends these are the same thing produces posts that feel wrong on at least half the platforms.
One idea in, five formats out
The workflow starts with the idea, not the platform.
Take a real example from my own calendar: a build update about a feature I have just shipped.
On X it becomes a thread. I split the update into segments, one point per segment, and write the first segment so it can survive alone, because most people will only ever see the first one. Bluesky gets a slightly shorter version of the same thread. On LinkedIn the same material works better as a single text post with a stronger opening line, so that is what it becomes. If I recorded a demo clip, the vertical cut goes out twice: as a Reel with a casual caption, and as a Short with a more searchable title, because people find video on Instagram and YouTube in completely different ways. The rough behind-the-scenes take that is not polished enough for the feed becomes a Story and quietly expires tomorrow.
The same routine works for evergreen material, not only news. An older blog post can become a full week: the core argument as a LinkedIn post, the practical steps as an X thread, one contrarian line from it as a standalone Threads post. Content sources in Planpost exist for exactly this. You connect a blog or a feed, and repurposing starts from something you already wrote instead of a blank page.
All of it lives in one composer and lands on one calendar. That is the actual feature. Not writing once and blasting everywhere, but seeing the entire mixed-format week in one place before any of it publishes.
What one composer deliberately does not do
It does not write one caption and reuse it five times. Identical text pasted across platforms reads as spam on at least three of them. The composer makes tailoring per platform the normal path instead of an advanced option. Why that tailoring matters so much is a topic of its own, and I went deep on it in the cross-posting playbook.
Some things also stay in the native apps on purpose. Interactive Story stickers, polls, collab posts: platforms keep sprouting format-specific extras, and I would rather the composer handle five formats properly than twenty superficially. When I need one of those extras, I open the app and do it by hand, and I am at peace with that trade.
It also does not manufacture your assets. A reel still needs an actual vertical video. A thread still needs to be written as a thread, where each segment carries its own weight; an essay chopped into 280-character pieces is not a thread, it is an essay with worse pacing. What the composer removes is the mechanical layer: the five tabs, the copy-pasting between them, the publishing by hand at the right hour, the remembering of which platform got which version.
Scheduling the week in one sitting
I batch this on Monday mornings. The drafts from my writing block become scheduled posts spread across the week: threads and LinkedIn posts on weekday mornings, video where it fits, Stories whenever, since they are casual by nature. Planpost can suggest posting times based on when your audience engages; I treat the suggestions as a starting point rather than gospel.
If you run more than one brand, account groups keep each brand's connections bundled, so you do not schedule a client's Reel to your own Instagram. I have not done that. I did come close once. And when someone else needs to sign off before publishing, you can submit a scheduled post for approval and they approve it from a link, without creating an account.
When a week belongs to a bigger push, a launch or a theme, I group the posts under a campaign, so the calendar shows the shape of the push rather than a loose pile of posts. That pays off later, when you want to know how the launch content performed as a set and not post by post.
There is also a lazier path I use more every month: the composer has an MCP server behind it, so Claude can create and schedule posts directly. On a busy week I hand it a blog post and ask for a thread version, then review the result in the composer before it goes anywhere. If that sounds appealing, the agent integration page explains the setup.
What it costs
Planpost has a 7-day free trial and two plans, Creator and Pro. Everything in this walkthrough is plain scheduling, which both plans cover; the Pro-only features live elsewhere in the product, in revenue attribution and brand voice. Details are on the pricing page.
The bar I hold the composer to is one specific hour. Sunday evening or Monday morning, one sitting: a thread, a couple of text posts, a Reel, a Short, a Story, all sitting on one calendar with times attached. When I started building Planpost, that hour was a full morning of tabs. Now the hour is the whole job.