A design feedback tool
that keeps every note beside the work.

Storyflow keeps every note beside the work: the brief, the references and every round sit on one board with the pieces themselves. The client opens a view-only link with no account and signs in to comment beside the specific piece, and a status column shows where each piece stands. Frame.io and Filestage still do what Storyflow does not: comments anchored to a point inside the file and timecoded comments on video.

Software that puts the work and the reactions to it in one place, so feedback arrives attached to the piece it is about instead of scattered across email, calls and chat. Some are proofing tools for markup and approvals on near-final files, such as Filestage. Some live inside the design tool, such as Figma comments. Storyflow is a shared board for the work, the brief, the references and every round.

Five things, visible at once. The directions under review, side by side. The brief and references, so notes are measured against what was agreed. The comments, next to the piece each one is about. Each round in its own frame beside the last, so progress shows. And a table of every piece with its round, owner, due date and status. In Storyflow all five sit on one board the client opens from a view-only link.

Not to view. A Storyflow view-only link opens in any browser with no account and nothing to install, so the client sees the board exactly as you arranged it. To comment, they sign in, which also puts their name on every note. Anyone a paid member invites to the board joins free and can work on it with you. View-only visitors see the latest version when they open or reload the link.

Roughly. A client who signs in can draw on the board to circle the spot and leave a comment beside it, but neither is anchored to a pixel of the file, and there is no proofing markup or version compare. When a round depends on exact pixels in near-final artwork, use Figma comments for design files, or Filestage and Frame.io for proofing. Storyflow suits the direction stage, where the question is which route and why.

No. There is no approve button, approval status or version comparison. Freelancers usually record the decision on the board instead: a status cell set to Done, a person cell naming who decided and a date cell for when, beside the chosen direction. If a client's process requires a formal, auditable sign-off, use a proofing tool such as Filestage or Ziflow, and keep the brief and earlier rounds on the Storyflow board.

Set the rules before round one. Name one decision maker, show two or three directions, and agree two or three rounds, each with a job: direction, then detail, then corrections. Ask for one consolidated set of notes per round by a date. Keep the brief beside the work, so a note that contradicts it is visible to everyone. In Storyflow each round sits in its own frame beside the last, so progress is visible too.

Get them onto one surface before asking them to agree. When every stakeholder comments on the same Storyflow board, each sees the others' notes, so contradictions surface in the review instead of in your inbox. Ask the client's decision maker to settle conflicts and send one consolidated list. Keep the brief beside the work, so a note that contradicts what was agreed is visible to the whole group, not only to you.

Use both, for different people. Figma is better for critique between designers inside the working file, with comments pinned to exact positions. Client feedback usually needs more than the file holds: the brief, the references, earlier rounds and competing directions. A Storyflow board carries that layer behind a view-only link, and the client signs in to comment. Many designers make the work in Figma and decide about it on a board.

Yes, at the direction stage. Upload a cut, grab the frames that matter and place them beside the script and the style frames, and a client who signs in comments beside them. For frame-accurate, timecoded notes on every moment of a cut, Frame.io is the specialist tool. Many editors share the direction board in Storyflow and the final cut in Frame.io, and link one from the other.

It sets up and checks the board, and you decide. Describe the project, such as three logo directions for two stakeholder groups, and the AI lays out a frame per direction with the brief and references. Before a round goes out, ask it for notes on what still misses the brief, and it reads the whole board. It can also draft the note that introduces a round. It does not design the work or approve it.

No. Storyflow is paid-only during early access, with plans from $7.99 a month billed annually ($9.99 monthly). A free plan launches before the end of 2026, and anyone a paid member invites to a board joins free. Clients who only view never need an account. If you need something free today, Google Slides with comment access handles a simple review with one stakeholder.