This is a snapshot tool — build a flow now and then, drop in a set of numbers, and read the analysis. There's no live connection to keep running.
Where your flows live
localStorage) as
you edit, so it's here when you come back. It's per-browser/per-device, not synced across
machines.*.flow.json file there, saved as you edit; anyone who connects the same folder
browses and searches the same maps. A .flowbuilder/ sidecar holds the catalog
and search index — safe to delete, it rebuilds.The stats loop — fill a sheet, then import it:
StepID (its join key — editable in the
inspector as "Data key").Sheet columns (one row per step; add Segment/Period rows
if you want to compare):
StepID · StepName · NodeType · Segment · Period · TouchTimeAvg · WaitTimeAvg · WIP · Volume · Throughput · Capacity · People · HoursPerDay · ReworkPct
No sheet yet? Cards fall back to the values you type into the inspector — so a flow analyses fine before any import.
Turn source material — a meeting transcript, a Visio map, an Excel sheet, a job-aid, or several at once — into a flow. Copy the prompt below into any capable AI (Claude, ChatGPT, Gemini) together with your files, then paste its answer back here.
1 · Fidelity — how close to the source vs. reasonably enriched
2 · Copy the prompt — paste it into your AI, add your files/notes, run it
3 · Paste the result — the AI's answer (JSON, or a ```json block)
This builds a new flow you can then Tidy, re-rate and refine. Nothing is invented at import — the map is exactly what the AI returned.
Structure imports faithfully — types, labels, connections, lanes, positions. Timing and people numbers usually don't exist in a Visio file, so the map arrives structurally complete, metrically empty, flagged as an unreviewed draft. Nothing is invented.