A livestream run of show
you can read while you are live.

Storyflow is the one built for exactly this job: a timed table of blocks with a running total, the sponsor's brief and your assets beside it, an AI that drafts the first version from a description, and a clip list that becomes dated cards afterwards. Mods read it from a link. Sending the stream, switching scenes and running overlays and chat still takes streaming software such as OBS or Streamlabs.

Seven columns: start time, minutes, block name, what is on screen, what you say or do, links and assets, and a clip marker. Keep each row to one line of notes so it reads at a glance. In Storyflow the minutes column is a number column with a Sum footer, and the assets sit on the board beside the table.

For a two hour stream, a pattern that works is 5 minutes of starting soon, a 3 minute cold open, 7 minutes of catch-up, a 35 minute main block, a 2 minute sponsor read, 18 minutes with the community, a 5 minute break, a 30 minute second block, a second read, an 8 minute finale and a 5 minute outro. A Storyflow table totals it at 120.

Where the most people are watching and the energy is good, which is usually just after the first main block and again before the finale. Avoid the first ten minutes and the last five. Check what the contract asks for first. In Storyflow each read is a row with its talking points, link and code, so it is on screen when its time comes.

Name three moments in advance: the hook, the peak of the main block and the finale. While live, type the time in the clip column whenever something lands. Afterwards, ask Storyflow's AI to turn each marked row into a card with a title, a platform and a due date, and work down the list across the week.

A short one helps. Five or six blocks with rough lengths are enough for a relaxed stream: an opening, two main blocks, a break, a community segment and an outro. It keeps the sponsor read and the ending from being forgotten without scripting anything. A Storyflow run of show for a casual stream fits on one screen.

Decide before you go live which block shrinks if you run over, and write it in the notes. Keep one flexible block, usually the community segment, that can lose ten minutes. In Storyflow the Sum footer shows the planned total. The start times are typed by hand, so change them if you move a block.

Yes, a first draft. Tell Storyflow's AI what the stream is, how long it runs and when it starts, and it builds the table of blocks with times and notes. Attach a sponsor's brief and it adds the reads with the talking points. It does not watch your stream or find clip moments in a recording; it works from what is on the board.

No. Storyflow does not send a stream, switch scenes, show overlays or alerts, run chat bots or drop stream markers. It does not cut clips or post them, and its tables do not work out start times or sort. It holds the run of show, the sponsor notes and the clip list. Use OBS, Streamlabs or your platform's own tools to go live.

Yes. Send a view-only link and they open the Storyflow board in a browser with no account. To work on it with you, invite them: anyone a paid member invites to a board joins free. Your editor can then relabel each clip card from to cut to posted, and mods can add notes during the stream.

A webinar is an hour with slides, a guest speaker and a producer reading cues, built for a business audience. A livestream is longer, looser and run by one person with chat, sponsor reads and clips to think about. Storyflow has a separate webinar run of show page for the first job, with the roles and the backup plan.

No. Storyflow runs in the browser and there are no native mobile or desktop apps. Open the run of show in a browser window on a second monitor or a tablet while your streaming software runs on the main screen. Mods and editors open the link you send them with nothing to download.