Who Wavelength is for
Wavelength is built for five 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. The twenty minutes where the process is still being revealed is the same in all five.
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.
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 |
| 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 do UML, ERDs, network topology, BPMN 2.0 with correct symbology, or floor plans. If your deliverable is formal architecture documentation, that belongs in a general diagramming suite. See the comparisons for where each of those tools is the better choice.
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.