FOR UX WRITERS
A button label is
never a single string.
It only makes sense given the screen before it and the screen after it. Storyflow gives UX writers and content designers one canvas for the flow itself: every step in order, the microcopy in place, the error and empty states nobody drew, and one terminology list the whole product can agree on. Storyflow is paid-only during early access, with plans from $9.99 per month.
Paid-only early access
Plans from $9.99/mo
Write to the flow
Used by creative professionals at:
Artlist
Pixar
Nike
Red Bull
The North Face
Porsche
Start from a ready-made template
Pick a board to see what you can build, then let AI fill it in. Every template is a real, editable starting point on the same infinite canvas.
Story Plan
Outline your plot, characters, and world in one connected view, then expand each thread as the story grows.
Content design is interface design done in words
UX writing, or content design, is the practice of designing the words inside a product so a person can finish what they came to do. It is not decoration on top of a screen and it is not persuasion. A UX writer decides what a button says, what a field asks for, what an error explains, what an empty state teaches, and what an interface calls each thing it contains. Those decisions carry more of a product's trust than any visual choice does, because they are the only part of the interface that answers a question directly.
The unit of work is the flow, not the page. A label like Continue, Done, or Save is meaningless in isolation, because its whole job is to describe the transition a person is about to make from where they are to where they are going next. Writing microcopy in a spreadsheet row, or in a Figma comment on one frame, hides exactly the thing that determines whether the word is right. Get four screens in a row and you can see the sentence the flow is speaking: three verbs that each promise something slightly different, a confirmation that repeats what the previous screen already said, a step where the user is asked to trust something nobody has explained yet.
Then there is the half of the job that never gets designed. The happy path always has a frame. The failed payment, the expired session, the search that returned nothing, the account with no data in it yet, the permission that got refused halfway through, those are the moments where the writing actually earns its keep, and they usually arrive as a ticket with the words TBD in it. An error message has two obligations, to say what happened and to say what to do next, and most shipped ones do neither. An empty state has one, to teach the thing the product does rather than apologise for a blank rectangle.
Storyflow is one infinite canvas for that whole practice, holding the flow mapped step by step, the microcopy written in the sequence a user actually meets it, the error and empty states listed and drafted rather than left as TBD, the voice and tone rules broken down by context so a delight moment and a failed payment are not asked to share a register, the single terminology list that stops four teams naming the same object four ways, and the localisation constraints that matter when English is often the shortest string you will ever get.
HOW IT WORKS
From a flow diagram to copy that survives the build.
Four steps that put the sequence, the states, and the vocabulary on the same surface.
01
Map the flow before you write a word
Lay the journey out as connected steps: entry point, each screen, each decision, each exit. Half the copy problems you were asked to fix turn out to be a step in the wrong order, and now you can point at it.
02
Write the copy into the sequence
Put the heading, the body, the field labels, and the button on the step where they belong. Read the flow left to right and you hear the sentence it makes, including the three verbs that contradict each other.
03
List the states nobody drew
Branch off every failure, empty, loading, and permission state from the step it belongs to. What happened, what to do next, in that order, in the tone that context deserves.
04
Pin the terminology and the tone rules
Keep one list of what each thing is called and one set of tone rules per context on the same board, so the whole team is arguing against a visible source rather than remembering different meetings.
The part of UX writing that is not the string.
The flow, the failure states, the vocabulary, and the tone, on one board instead of a spreadsheet and four Figma comments.
Write to the flow
See the sequence the copy has to work in
Map the journey as steps and write each label into its place. A button reads correctly only against what came before and what comes next, which a row in a spreadsheet cannot show you.
See the free user flow diagram tool →
The states nobody drew
Error and empty states, listed and written
Branch every failure, empty, and permission state off the step it belongs to, then write what happened and what to do next. The half of the product that has no Figma frame gets copy anyway.
See the user journey map tool →
One name per thing
A terminology list the whole product can see
Keep the agreed noun for every object, the rejected alternatives, and the reason, in one place. Four teams naming the same thing four ways is a content problem, and it is solved by a visible source.
See the AI brand voice generator →
Tone by context
Voice that shifts where the user's state shifts
A celebration screen and a declined card cannot share a register. Break the tone rules down per context and keep them beside the drafts, so the shift is deliberate rather than accidental.
See the customer persona generator →Paid plans from $9.99 per month.
Storyflow is paid-only during early access. A Free plan launches before the end of 2026, and anyone a paid member invites to a board joins free today.
Unlimited boards for flows, state inventories, and terminology lists
Basic AI usage to enumerate states and structure a flow
Pin screenshots, wireframes, and tone rules beside the copy
Share view-only with engineering and research, or invite collaborators free
BUILT FOR CONTENT DESIGNERS
Made for the way content design actually works.
Sequence, failure states, vocabulary, and the moment you get pulled in too late, on one canvas.
The flow is the unit
Stop writing strings, start writing transitions
Every step in order: Entry, screens, decisions, and exits laid out as connected cards, so the copy is judged against the journey rather than against a cell reference.
Read the flow out loud: Four steps side by side expose the verb that promises something the next screen does not deliver, and the confirmation that repeats what the user already read.
Count the steps, not the words: When the answer is fewer screens rather than better sentences, the map is the argument. You can show it instead of describing it in a comment.
Ask the AI to enumerate the branches: The assistant reads the flow and lists the paths and states you have not covered. It structures the inventory, you write the words.
The unglamorous half
Errors, empty states, and everything marked TBD
What happened, then what to do: Draft both halves of every error in the same card. A message that names the failure but not the recovery has done half a job and cost the user the whole task.
Empty states that teach: First-run and no-results screens are the best teaching moment a product gets. Write them as instruction, not as an apology for a blank rectangle.
A visible inventory: Every state hangs off the step it belongs to, so the gap between the twelve states that exist and the four that were designed is impossible to miss in a review.
One vocabulary
Four teams, four names, one object
The agreed noun, in one place: Workspace or project, member or seat, archive or delete. Put the decision somewhere everyone can point at instead of somewhere everyone half remembers.
Keep the rejected options: Record what you did not pick and why. It ends the same debate arriving from a new team every quarter, and it survives you leaving the company.
Write with translation in mind: Note the length constraints and the strings that will not survive translation. English is often the shortest version, and a label that only just fits in English will break elsewhere.
Brought in too late
Make the structural argument visible
The map is the pushback: When you are asked to wordsmith a flow whose real problem is its shape, a board showing the sequence is a far better argument than a comment saying this feels confusing.
Copy beside the screenshot: Pin the build screenshot or the wireframe next to the draft, so the two line limit and the truncated label are found now rather than at QA.
Review where the work is: Comments land on the specific step rather than in a thread, and a view-only link lets engineering, research, and legal see the flow without editing it.
Explore templates for your project
Every template opens as a real, editable board on the infinite canvas. Pick the closest fit and make it your own.
Story Plan
Outline your plot, characters, and world in one connected view, then expand each thread as the story grows.
COMPARED
How Storyflow compares for UX writers.
Storyflow is not a design tool, a localisation platform, or a string management system. Here is the honest split.
Storyflow
Recommended
Map a flow and write the copy into each step
Inventory every error, empty, and edge state
One terminology list with the reasoning kept
Copy attached to live design frames
Translation workflow and locale management
Structured string database with filters and views
Figma
Map a flow and write the copy into each step
Inventory every error, empty, and edge state
One terminology list with the reasoning kept
Copy attached to live design frames
Translation workflow and locale management
Structured string database with filters and views
Notion
Map a flow and write the copy into each step
Inventory every error, empty, and edge state
One terminology list with the reasoning kept
Copy attached to live design frames
Translation workflow and locale management
Structured string database with filters and views
Google Sheets
Map a flow and write the copy into each step
Inventory every error, empty, and edge state
One terminology list with the reasoning kept
Copy attached to live design frames
Translation workflow and locale management
Structured string database with filters and views
What creators are saying
Join early creators getting structured workspaces and AI that remembers their projects
“Storyflow has sped up my workflow by at least 3x, which means more flow state and more projects I can actually ship. It truly changed the way me and my team create.”
Reilin Joey
Director & YouTuber
“One prompt gets me a structured board. But the tactics are my favorite. I run my YouTube scripts through them and my intros and retention got better. It's amazing.”
Justkay
YouTuber & Freelance Filmmaker
“I used to juggle five apps to plan a project. Now I describe what I am making and get boards, lists, and a schedule. All in one place.”
George
@fernwehchronicles
UX writing questions, answered.
Including the ones where the honest answer is no.
A copywriter is trying to move someone toward a decision. A UX writer is trying to help someone finish a task they have already decided to do. That changes almost everything. Copy is judged on persuasion and memorability, and UX writing is judged on whether the person got through without stopping to think. A great headline can be surprising. A great button label is almost invisible. Both need craft, but they optimise for opposite things, which is why the same person often writes worse at one when they are deep in the other. Our page for copywriters covers the persuasion side.
Map the flow. Write the states. Then argue with evidence.
Open a canvas, lay the journey out step by step, and put the copy where the user will actually meet it. Plans start at $9.99 per month.