// replaces: docs nobody reads
Capture how your team actually works — once.
Flowbook turns the docs you already have into living runbooks your team actually follows — step by step, so nothing gets skipped — with the same flows available to your AI agents over MCP whenever you want them.
// the walkthrough — a real flow, start to finish
How Flowbook works
Your runbooks live in stale Google Docs nobody reads, and the knowledge that matters is in three people's heads.
You never start from a blank page. Drop in the messy docs you already have and Flowbook turns them into structured, living flows — branches, decision points and all — or fork a proven one from the public marketplace (rated, with a count of successful runs) and adapt it to your stack. Your team works a flow step by step instead of half-remembering it, and when someone gets stuck, Flowbook suggests the fix — or they describe it in plain language — and the flow updates in real time with whichever option they take, so the next person gets it right. It's how new hires ramp without shadowing someone for a week, and it's the SOP you pull up and fix together the moment something breaks in a meeting — the fix lands in the flow, so it's solved for good. The same flows are open to your AI agents too: an MCP server lets Claude Code, Cursor, or your own agents work through them, proposing each step for a human to approve before anything risky. People first; agents when you want them.
what it does
- ▸Turn existing docs into living runbooks — no writing from scratch
- ▸Your team follows flows step by step, so nothing gets skipped
- ▸Stuck mid-run? It suggests the fix, and the flow adapts in real time
- ▸Captures conditions as real branches and decision points
- ▸Fork a proven flow from the marketplace — rated, with a successful-run count
- ▸Bonus: agents follow the same flows over MCP — they propose, you approve
$ claude > run flow "rotate-prod-secrets" (via MCP)
✓ 1/5 fetch current secrets · vault
✓ 2/5 generate replacements
⠸ 3/5 update k8s secrets… awaiting your approval
↳ gap reported by @maya last week → drafted step approved ✓
// the beta deal
A real deal for getting in early.
Flowbook is in beta, and the deal is built so it's an easy yes. No risk, no lock-in — just six months to find out if it earns a place in your workflow. Every Zannal tool ships under the same terms.
Six months free
Full access from day one. No card, no trial countdown, no feature gates — six months to put it through real work.
Your data is yours
Back out whenever you want and take everything with you. Full export, no lock-in, nothing held hostage if it's not a fit.
Shape what gets built
A direct line to the person building it. The features your team needs jump the queue — beta feedback drives the roadmap.
Founding price, locked
Stay past the beta and you keep the founding rate for good: $10/month per tool, flat — any team size. The price goes up when the beta ends; founding teams never pay the increase. Same deal on every Zannal tool you pick up.
// honest answers
Questions you should be asking
How is this different from Scribe?+
Scribe captures your screen into step-by-step documents — and does it well. The difference is what happens after: Scribe produces documents for humans to read (its AI integration is read-only lookup), while Flowbook produces processes that get executed. A Flowbook run carries step-level state — who ran each step, what got skipped, which risky action a human approved — not view-and-completion stats. Flows have real conditional branches, they repair themselves mid-run when a step is wrong, and your AI agents can actually execute them, gated by your approvals, reporting the run back. Dev work — deploys, incidents, onboarding — is terminal commands and judgment calls, which screen capture was never built for. If what you need is polished how-to documents from screen recordings, Scribe is genuinely good at that.
Isn't this just Notion/Confluence with extra steps?+
Notion stores documents you read; Flowbook runs processes you execute. The difference shows up in week three: a wiki page that's wrong stays wrong until someone feels guilty enough to edit it. A flow that's wrong gets fixed at the moment it fails, by the person it failed on, as part of the run — and the next run gets the fix. If nobody runs a process, it's a document and Notion is fine. If people run it, drift is the whole problem.
Who's going to write all these flows?+
Nobody starts from a blank page. Drop in the messy docs you already have and Flowbook structures them into flows. From there, maintenance happens during runs — hit a gap, describe the fix in plain language, approved in seconds. Capture from your AI coding sessions (do the task once, get a draft flow) is in active development.
What can the AI agents actually do — and what can't they?+
Flowbook exposes every flow over an MCP server, so Claude Code, Cursor, or your own agents can read flows and work through them step by step. The posture is: agents propose, you dispose. Risky steps are gated — the agent stops and waits for a human to approve the specific action. Gates can only be tightened by your org's policy, never loosened by a fork. Humans running flows by hand is the primary mode; agents are there when you want them.
Where does my data live? Could my runbooks end up public?+
Your flows live in your workspace, isolated per tenant. Nothing is ever published unless someone in your org explicitly publishes it — and publishing runs an automated secret-scan as a backstop on top of your own review. Full export anytime, deletion on request, and the beta terms mean you can walk away with everything. Details on the privacy page.
What does 'beta' actually mean here?+
It means the product is real and working, the edges are still being sanded, and you get a direct line to the person building it. Full terms are in the beta deal above — free period, no card, your data stays yours, founding price locked if you stay. It also means your feedback genuinely steers the roadmap, because there are a handful of beta teams, not a queue of ten thousand.
Try Flowbook on your team.
Drop your email and I'll reach out personally to get you set up. Spots are limited so each beta team gets real attention.
- 01
I reply personally
within a day — no autoresponder, no queue.
- 02
30-minute setup call
we load your real docs in together; no homework first.
- 03
Your team runs its first flow
that same week — then you tell me what's broken.
Joe Christianson
the developer building this — you email, I reply. No team hiding behind this form.
// different pain?