Plan the publication,
not just this week's issue.

No, and it is deliberately not trying to. beehiiv, Substack, Mailchimp, and the other sending platforms own delivery, subscriber lists, sign-up pages, and open and click stats, and they are good at all of it. Storyflow is the editorial brain upstream of whichever platform you use: the place where ideas accumulate, issues move through the pipeline, series get planned across months, and drafts get written beside the plan. When an issue is ready, you paste it into your platform and send from there. Keeping planning and sending separate also means you can switch sending platforms without losing your editorial system, which is worth more than it sounds the day beehiiv or Substack changes its pricing.

Separate the publication from the issue. First, build a backlog: capture every idea as a card the moment it occurs to you, without judging it. Second, set up a pipeline with four columns, idea, outlining, drafting, and sent, and move cards right as they mature. Third, plan series as arcs rather than one-offs: lay each multi-issue thread out as a track so you can see where it starts, develops, and pays off. Fourth, pin research beside the issue it feeds so drafting starts warm. Finally, keep the sent column visible as an archive so you repeat deliberately. The weekly session then becomes an editorial decision, choosing what to advance, instead of a scramble to invent something from nothing.

Plan themes further ahead than drafts. A useful working shape is: the next two issues outlined or in draft, the next six to eight sketched as chosen backlog cards, and any series arcs laid out to their conclusion even if that is months away. Planning full drafts months ahead usually backfires, because newsletters live on timeliness and your best issue next month probably has not happened yet. The backlog is what squares this: it holds forty rough ideas at various stages of ripeness, so you can stay responsive to the week while never depending on the week for material. If the pipeline's outlining column is empty two weeks running, that is the early warning worth acting on.

Yes, and it is one of the main reasons to plan on a canvas instead of in a list. Lay each series out as its own horizontal track, with one card per installment, running across the plan. You can see the arc's shape at a glance: where it opens, how the middle develops, where it pays off, and how it interleaves with your regular issues and any other series running at the same time. Gaps and collisions become visible, like two heavy series landing in the same fortnight or a thread going silent for six weeks. Since part one usually promises what the final part delivers, having the whole arc laid out before anything ships is what makes the promise safe to make.

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 a co-writer, editor, or client can join your planning canvas without paying. If you need a completely free option this minute, Trello's free tier gives you a perfectly serviceable idea-to-sent pipeline, and Notion's free plan can hold an editorial database with more structure. What they will not give you is the canvas: backlog, series tracks, and research on one surface, with AI laying the board out from a prompt.

You can draft in it, and many writers do. There is a built-in document editor, so you can write an issue beside the board with the outline, the series context, and the pinned research one glance away, which is a genuinely better drafting position than a blank document in another tab. What Storyflow does not do is send: when the draft is done, you paste it into beehiiv, Substack, Mailchimp, or wherever your list lives, and format and send from there. Some writers prefer to draft directly in their sending platform or in Google Docs for its tracked changes; the plan works the same either way, because the canvas is the map, not the mailbox.

No, and that is a deliberate boundary. Subscribers signed up for a voice, and a newsletter that stops sounding like its writer loses the only asset it has. Storyflow's AI is structural: it lays out the planning board from a description of your newsletter, suggests issue ideas that fit the themes already on your canvas, groups a messy backlog into series candidates, and drafts outlines for an issue you are about to write. Because it uses your whole board as context, its suggestions fit your publication rather than a generic one. The sentences your subscribers read remain yours to write, in the built-in editor or wherever you draft.

Yes, in two ways. A view-only link opens the whole board in a browser with no account needed, which is ideal for a client who wants to see the next six issues, a sponsor checking when their placement lands, or an editor reviewing the quarter's arc. It replaces the screenshot-and-status-call routine with a live view of the actual plan. If someone should contribute rather than just look, invite them to the canvas and they can add ideas to the backlog and move cards through the pipeline with you; invited collaborators join free. You can also export the board as a high-quality image or PDF for a deck or a client report.

Keep the archive on the same surface as the plan. In Storyflow, sent issues stay on the board in the sent column, so the record of what you have covered sits directly beside the backlog of what you might cover next. That adjacency does real work: you notice you have leaned on the same theme three times this quarter, you spot the March issue worth calling back to in a new series, and you can see the subjects you have somehow never touched. Newsletters that archive in one tool and plan in another lose exactly this, because nobody rereads their own archive on purpose. On a canvas, you do not have to; it is already in view.