One pillar piece.
A whole system drawn around it.

A pillar is the substantial piece everything else is cut from: the long video, the podcast episode, the essay, the webinar. It carries your actual thinking, took the most effort, and contains far more usable material than one post can hold. Planning around pillars beats planning around platforms because it fixes the economics of creation: the expensive thing gets made once and the cheap derivatives multiply its reach, instead of every platform demanding its own original idea. It also keeps the derivatives coherent, since everything traces back to a piece with a real argument. On a canvas this is literal: the pillar sits at the center and the derivatives radiate out from it, connected to the moments they mine.

No, and it is worth being plain about this. Storyflow does not cut video, auto-generate derivative posts, or publish to any platform. Clipping and editing live in tools like CapCut or Descript, and scheduling lives in tools like Buffer or Later. Storyflow covers the step before both: deciding what each pillar should become, which moments get clipped, which platform each derivative feeds, and tracking status as the pieces move through your actual production tools. That deciding step is the one most repurposing workflows skip, and skipping it is why so much repurposed content is the first ninety seconds of the video rather than the best ninety seconds.

Not during early access. Storyflow is paid-only right now, with plans starting at $9.99 a month, and a Free plan for solo use launches before the end of 2026. Anyone a paid member invites to a board joins free today, so your editor or VA can work on the map without paying. If you need a free option this minute, Trello's free tier will run a simple derivative pipeline honestly, and Notion's free tier can hold a content database with per-platform views if you are willing to build the structure yourself. What neither gives you is the drawn fan-out map or frame grabs from the source video.

As many as its genuinely strong moments support, and no more. A dense hour-long episode might honestly carry five clips, a thread, a carousel, a newsletter section, and several quote posts; a thin one might support three pieces total. The map is what keeps you honest in both directions. A pillar with two spokes next to pillars with eight is probably under-mined, and worth another pass. A pillar being stretched into fifteen derivatives is producing filler, and the weak spokes are usually visible on the board before they are visible in the metrics. The useful discipline is counting moments first and derivatives second, because the moment count is the real ceiling.

Look for self-contained beats: a claim that provokes on its own, a story with its own arc, a demonstration that shows something happening, a before-and-after. A clip fails when it needs the surrounding context to make sense, so the test is whether a stranger dropped into that moment would stay. In Storyflow you grab frames from the source video on YouTube or Vimeo and pin them to the board at the moments that pass the test, which does two things: it forces you to actually rewatch and choose rather than defaulting to the intro, and it turns each choice into a visual brief your editor can cut from without a call.

No. Storyflow's AI structures the plan; it does not ghostwrite the derivatives. Describe your cadence and it lays out the board: pillar slots, derivative cards, platform lanes. Prompt against the map and it can suggest derivative angles for an episode, point out which pillars look under-mined, or rough out how a thread might be structured from your moment cards. Because it uses the whole board as context, the suggestions fit your actual system. But the words that get published, the clip that gets cut, the caption that goes out, those are made by you in your writing and editing tools. The AI's job is to make sure they were planned from the pillar's best material.

A calendar answers when; a map answers what and from where. Calendars are organized by date, so they show you slots to fill, and they are genuinely the right tool for the final scheduling step. But a calendar cannot show lineage: it does not know that Tuesday's clip and Thursday's thread both come from last week's episode, or that the episode has six more strong moments nobody assigned. The map holds that structure, the pillar at the center with derivatives fanned out and connected to their source moments, and the calendar or scheduler takes over once each derivative is drafted. Most workflows need both; the mistake is using the calendar as the planning surface.

On a queue, you find out when the channel goes quiet. On a map, you see it in advance, because derivatives are grouped into platform lanes and an empty lane is an empty stretch of canvas. If the LinkedIn lane has nothing in idea or drafted status while Instagram runs three weeks deep, that imbalance is visible the moment you look at the board, and the fix is usually sitting right there: an under-mined pillar with strong moments that suit the starving platform. Status per card sharpens this further, since a lane full of ideas and empty of drafts is starving too; it just does not know it yet.

Yes, and it is one of the better reasons to keep the map in a browser. Share a view-only link and your editor sees the entire fan-out with no account: the frame grabs marking clip moments, the format per derivative, the lane each piece feeds. That is a complete brief, and a much better one than timestamps pasted into a chat. If you want them updating the map rather than just reading it, invite them to the board, and invited collaborators join free during early access. They can mark clips done, comment on a card when a moment does not cut cleanly, and the plan and its execution status stay on one surface instead of drifting apart across tools.