How it Works
Most process documentation lives in slides and spreadsheets and stays out of date the day after it's written. Quokka makes the map a living artifact your whole team can edit.
Drop steps on a canvas. Drag-connect them in the order they happen. Parallel branches that merge later are first-class — the math handles them.
Each step is a node with a name, an owner (BDR, AE, RevOps, whatever), a duration, and a description. Double-click to rename. Drag a node next to another to auto-connect. ⌘+N adds a step, ⌘+D duplicates one, Delete removes it.
Tag every step with the tools that power it. Quokka keeps a global library across all your flows — so 'Salesforce' tagged on one flow autocompletes in every other.
The library shows you usage counts: which tools touch the most steps, which are only used once, which are stranded after a deprovision. The first real artifact of an honest stack audit.
Sequential steps sum. Parallel branches that converge take the max. Quokka highlights the critical path — the actual gating chain that dictates total cycle time.
Total recomputes live as you edit durations. Hover a terminal node to see the total time for any path. Cycles and orphan steps surface as warnings in the top bar. You stop guessing where the bottleneck is.
Flag the steps that are repetitive, well-instrumented, and high-volume — the steps where a current-generation AI agent has actual leverage. Not the hard-once-a-quarter ones.
AI readiness is a function of clarity, not aspiration. If you can map it, you can score it. If you can score it, you can prioritize it. Quokka makes the map.
PNG snapshot for slides. JSON for downstream tools. Markdown summary — formatted with the steps table, the tech rollup, and a critical-path callout — for any doc or wiki.
The Markdown export is what you paste into Notion, Linear, your monthly review. The audit committee likes JSON. The board likes PNG. Quokka emits all three.
The math
Topological sort over your steps, longest-path DP to compute total time, backtrack to highlight which steps gate everything. Cycle detection in the top bar so you know if your graph is broken.
The data
Every flow saves to your account in our Postgres database. Auto-save on every edit. Sign-in is Google OAuth — no passwords for us to lose. JSON export gives you a portable copy any time.
The stack
React Flow on the canvas, server-rendered marketing for fast loads, dark mode by default. Designed for executives and operators, not for tutorials.
Sign in with Google. Start from the GTM template, or open a blank canvas. Hand it to your team when you're done.
Start mapping