An always-on campaign plan
built as a cycle, not a launch.

Storyflow is built for exactly this job: the weekly, monthly and quarterly rhythm, the creative in rotation, the refresh rule and every past cycle sit on one board, and its AI reads the last cycle before it drafts the next. Publishing the posts at a set time still takes a scheduling tool such as Buffer, Later or Hootsuite, and an email platform still sends the email.

It is marketing that runs all year with no end date: regular posts, emails, search and paid ads that keep a brand in front of buyers between launches. Because it never finishes, it is planned as a repeating cycle and not as a timeline. On a Storyflow board that cycle is three columns, weekly, monthly and quarterly, copied forward each month.

A burst campaign has a start, a peak and an end, and is built around one message or launch. An always-on campaign has a rhythm instead of a peak and is judged over quarters. Most teams run both: the cycle as the base, with bursts on top. In Storyflow a burst is marked across the weeks where it borrows slots from the cycle.

Weekly: the small regular pieces, such as three posts, one email and a check of the paid ads. Monthly: one anchor piece, an ad refresh and a short report. Quarterly: one theme, one flagship piece and a clear-out of stale work. That is 56 pieces a quarter. On a Storyflow board each one is a card with an owner.

Set a rule instead of a feeling. A common one for paid ads: replace when the click rate falls 30 percent below the average of its first two weeks, or after eight weeks, whichever is first. Review evergreen pages and videos once they have gone twelve months untouched. Write the rule on the Storyflow board above the creative, so everyone applies the same one.

Count it. In the worked example, weekly jobs take 10 hours, monthly jobs 7 hours a week and quarterly jobs 4, so 21 hours a week. For a team with 60 hours that is about a third. Put the jobs and hours in a table on the Storyflow board with a Sum in the footer, and agree the number before adding a channel.

They sit on top. A launch borrows some of the regular slots for a few weeks, then hands them back. Mark which slots and which weeks, so the cycle restarts on a known date and nobody has to ask when normal service resumes. On a Storyflow board the launch is a labelled card over those weeks, with its own brief beside it.

Storyflow supports it by keeping each cycle as its own column on one board, copied forward every month, with the creative and the refresh rule beside it and an AI that reads the last cycle before drafting the next. Project tools such as Asana or Monday repeat tasks on a timer, and scheduling tools such as Buffer or Later queue the posts themselves.

Yes, as a draft. Storyflow's AI reads the board it is opened on and up to three other boards you attach, so it can read last month's cycle, see what ran and what was retired, and lay out next month's cards. It does not know which pieces performed unless you paste the numbers in or attach the export, and you decide what stays.

No. Storyflow does not publish to social networks, send email, show a calendar month view or repeat a task on its own. It is where the cycle is planned and the creative is kept. Copy the cycle forward by hand each month, and publish from a scheduling tool such as Buffer, Later or Hootsuite.

Over quarters, not weeks. Track a few steady numbers, such as searches for your name, visits from people who typed the address, enquiries and cost per enquiry, and compare each quarter with the same quarter last year. Week to week the figures wobble for reasons that have nothing to do with the work. Paste the quarter's figures onto the Storyflow board and its AI charts them beside the cycle that produced them.

No. Storyflow runs in the browser and there are no native mobile or desktop apps. Open the cycle in any browser and share it by link. Leadership can read it with no account, and the freelancers and agency partners you invite to the board can comment and edit.