Who it is for
Fifteen roles that map a process while someone explains it
Wavelength is built for fifteen roles that share one problem: your real job in the meeting is to understand a process someone else is explaining, and every minute you spend drawing it is a minute you are not listening. There is a page below for each role, and each one says plainly where the tool does not fit.
The roles differ in what happens to the diagram afterward. A sales engineer sends it as a recap. An architect puts it next to a future-state design. A project manager turns it into scope. A consultant bills it as a deliverable. An ERP team hands it to configuration. An operations manager turns it into an SOP. An automation builder exports an n8n skeleton. A business analyst exports BPMN. A customer success manager attaches it to the deal. A product manager turns it into a user flow. A compliance lead turns a control walkthrough into a procedure. An IT ops lead turns an incident process into a runbook. A RevOps lead maps routing rules before building them. An insurance lead finds the handoffs that eat cycle time. A franchise lead records the best location and gives every location the same steps. The twenty minutes where the process is still being revealed is the same in all fifteen.
Sales engineers
Map a prospect's data flow live on a discovery call, then send the recap with a picture instead of a paragraph starting "so if I understood correctly."
Solution architects
Capture an architecture review while it is happening, so the diagram exists by the time the review ends rather than a week later from memory.
Technical project managers
Leave the workshop with the process map already done, validated in the room by the people who actually run the process.
IT transformation consultants
Turn a client workshop into a deliverable before you leave the room, instead of writing it up on your own time afterward.
ERP implementations
Capture as-is processes during discovery rather than after, so the gap analysis starts from something the business already agreed to.
Operations and SOPs
Talk through a task once and get a process map plus a written SOP with roles, owners, steps, and decision branches.
Automation builders
Scope the client's process on the call, then export an n8n workflow skeleton with a trigger, If nodes, and a placeholder for each step.
Business analysts
Map the current-state process in the workshop, switch to swimlanes by role, and export BPMN 2.0 for Camunda Modeler or bpmn.io.
Customer success
Map the customer's workflow on the kickoff call, confirm it with the customer, and attach it to the HubSpot deal.
Product managers
Describe a user journey or upload an interview and get a user flow with screen nodes, decisions, and error paths you can export to draw.io, Mermaid, or PNG.
Compliance and audit
Talk through a control walkthrough once and get a process map plus a written procedure with owners per step, version history, and a review link for the control owner.
IT runbooks
Talk through an incident or change process once and get the flow plus a written runbook with lanes for on-call, service desk, and CAB, and metrics for wait time between handoffs.
RevOps
Map lead routing and deal desk approval rules with a decision branch for every rule, attach to the HubSpot deal, and compare current vs proposed routing.
Insurance and lending
Map claims and loan processes with active and wait time per step, a wait percent summary, Compare for current vs future state, and BPMN export for the loan file.
Franchise operations
Record how the best location does a procedure and give every location the same steps with a review link so location managers confirm or flag fixes before rollout.
Which page to read
| If your meeting is | Start here |
|---|---|
| A discovery call with a prospect | For sales engineers |
| A design or architecture review | For solution architects |
| A requirements or process workshop | For project managers |
| A client engagement with a written deliverable | For IT consultants |
| ERP as-is and to-be discovery | For ERP implementations |
| A process walkthrough you need as an SOP | For operations and SOPs |
| Scoping a client automation for n8n | For automation builders |
| An as-is process workshop needing BPMN | For business analysts |
| A customer kickoff call | For customer success |
| A user journey or interview walkthrough | For product managers |
| A control walkthrough needing a procedure | For compliance and audit |
| An incident or change process for a runbook | For IT runbooks |
| Lead routing or deal desk rules to map | For RevOps |
| A claim or loan file with slow handoffs | For insurance and lending |
| A franchise procedure to standardize | For franchise operations |
| Already over, and you have the transcript | Transcript to flowchart |
What is the same in every role
You hold the mic, or paste a transcript, and describe the process in plain language. Actors, systems, decisions, and data stores appear as they are mentioned, each with its own shape. Anything Wavelength inferred rather than heard is drawn as a dashed amber line, so you know exactly which connections to confirm out loud before the meeting ends. Then you export a PNG, share a link, or send an email recap.
The step that changes the meeting is sharing your screen once there is something to look at. People stop describing and start correcting, and a correction is far more precise than an answer to a question you had to think of first.
Where it does not fit
Wavelength does process and data flow. It does not draw UML, ERDs, network topology, or floor plans. It exports BPMN 2.0 with tasks, gateways, events, and lanes. Add timers and message flows in your BPMN modeler. It also exports draw.io, PowerPoint, and Mermaid on every plan, so the flow goes into the documents your team already uses. See the comparisons.
It also will not rescue a call with bad audio. If the room is noisy or the line is poor, record it and paste the transcript afterward. Same diagram, just not live.