Documenting a process is one of those tasks everyone needs and nobody enjoys. You know the flow — the checkout, the onboarding, the backoffice approval — because you run it every day. But turning that into a clean BPMN diagram means stopping, reconstructing every step from memory, and dragging boxes around for an hour.
So I built Sevenda: a Chrome extension that watches you do the flow once and hands you the diagram.
What it does
Sevenda records a browser session and uses Claude to generate a real BPMN 2.0 process diagram out of it — the kind an analyst would draw by hand: multiple named pools, typed messages between participants, technical annotations on the side. You click through the flow; it produces the swimlanes.
It runs as a DevTools panel, so it lives right next to the app you're documenting.
How it works
- Record — open the Sevenda panel, hit record, and go through your flow like you normally would.
- Generate — Sevenda sends the captured session to Claude and builds the BPMN.
-
Export & edit — you get a standard
.bpmnfile you can open in any BPMN tool, plus an editable diagram right in the panel.
Same session, second output: GA4 / GTM analytics insights — a read on the tracking and events firing across the flow, for the analytics crowd.
A few things I'm proud of
- Analyst-grade diagrams, not toy output. Multi-pool, named message flows, send/receive typing for cross-participant exchanges, annotations outside the lanes.
- BYOK (bring your own key). You plug in your own Anthropic key. Your sessions and your key stay under your control, and you pay inference at cost — no middleman holding your data.
- Output in your language. UI and generated documents in English, Italian, Spanish, or French — and you can set the diagram's language independently of the interface.
Who it's for
Business analysts, QA engineers mapping test flows, product people documenting features, consultants capturing a client's as-is process, and devs who'd rather click through a flow than hand-draw it.
It's live
Sevenda is on the Chrome Web Store, tested and ready, with paid plans available (BPMN and Insights modes). You can try it today.
If you document processes for a living — or just dread it once a quarter — I'd love your take. What's the flow you'd point it at first? 👇
Top comments (3)
First flow I'd point it at: an internal refund approval that bounces between support, finance and a manager, and that nobody on the team has ever drawn the same way twice. Proper pools with message flows between participants, rather than one long lane, is what would make the output usable for something like that.
BYOK is the right call too. Anyone recording backoffice screens is going to care a lot about where that session ends up.
Thanks, this is exactly the kind of flow Sevenda was built for. A refund approval that bounces between support, finance and a manager is where a single long lane falls apart: what matters is who hands what to whom, and that’s what pools with named message flows make visible.
Sevenda follows page changes within a tab, so you can go through the support step, then the finance step, then the manager approval in one continuous recording, and it all ends up in a single diagram. Native merging of separate sessions into one BPMN is on the roadmap, but the single-tab approach already covers a flow like yours.
And agreed on BYOK: backoffice screens are exactly where people should care where the session goes.
One continuous recording across the three steps works for me. Merging separate sessions would be the next thing I'd want, since in real life the finance step usually happens a day later on someone else's machine. Good luck with the roadmap.