Turn a client workshop into a deliverable before you leave the room
If you run IT transformation and business process work, independently or inside a firm, your process map is not an internal artifact. It is a billable deliverable, and you are producing it in the worst possible place: alone, afterward, from notes.
Wavelength is a voice to diagram tool that builds a process map from the conversation as it happens, so the map exists while the client is still in the room to argue with it. For a consultant that lands differently than for an internal team. You are not saving yourself an evening. You are moving a deliverable from the unbilled side of the engagement to the billed side.
The demo needs no account. The free plan needs no card.
The write-up tax
Here is a normal discovery week. Two-hour session, six people from finance, ops, and IT, fourteen pages of notes. Then you go back to the hotel and spend three to five hours rebuilding what you heard in Visio, Lucid, or a PowerPoint stack of rounded rectangles.
Call that what it is. The reconstruction is not analysis, it is transcription with extra steps. Nobody pays a day rate for converting shorthand into shapes. On fixed fee those hours come out of margin. On time and materials they are the line item procurement circles. Either way it is the least valuable use of your hours, repeated for every process in scope.
The cost is not only hours. It happens alone, from memory, so the first draft carries your misunderstandings intact. You heard an approval threshold and drew one gate. There were two, and the person who could have corrected you was across the table while you had the wrong picture in your head. They find out in review, nine days later.
The first version of a process map is always wrong. The only question is whether it is wrong in front of the client while they can fix it, or wrong in a document you have already sent.
Validation in the room beats a review cycle
A map the client corrected while describing the process is a different artifact from one you emailed for comments. It has their fingerprints on it. Nobody in the steering committee claims later that they never agreed to that as-is, because they watched it get drawn.
The commercial half matters more. A review cycle is not effort, it is calendar. You send the draft, it sits four days, two of six attendees comment, you chase, revise, re-send. Two weeks gone and the engagement clock never stopped. On fixed fee, calendar time is margin, and it shows up nowhere except your realized rate at the end of the quarter.
Unlike Lucidchart, Miro, and Visio, which require you to draw the process map after the workshop, Wavelength builds it live during the session, so the client validates the as-is process in the room instead of two weeks later in a review cycle.
What each current option actually costs you
| How you handle it now | What it costs |
|---|---|
| Notes in the session, rebuild afterward | Hours that are hard to bill and easy to get wrong. You reconstruct from memory, so your misreadings become the client's first impression of your work. |
| A junior resource documents it | Adds a handoff, a week, and a second layer of misunderstanding on top of yours. You review their version of your version of what the client said. |
| Draw live in a diagramming tool while facilitating | You stop facilitating. Six people watch you drag boxes, the session goes flat, and the quiet person who knew the exception path never speaks. |
| Record it and transcribe | You get text. No client has ever validated a workflow by reading forty minutes of dialogue. |
| Skip the map entirely | The scope argument arrives later and you lose it, because the only documented version of the current state is the client's. |
What the engagement looks like instead
- Run the session the way you already run it. Same questions, same facilitation, which is what the client is paying for.
- The map builds while people talk. Actors, systems, decision points, and handoffs appear as they are mentioned, without you touching a canvas.
- Share your screen once there is something to look at. Usually fifteen minutes in. This is where the session changes character.
- Let the client correct it. People are far more precise correcting a picture than describing one. "That approval only fires over fifty thousand" is a sentence no open question gets you and a wrong box gets you instantly.
- Confirm the inferred connections. Anything inferred rather than heard renders as a dashed amber line, so you have a short visible list of what to verify out loud before the session closes.
- Export it and attach it to the same-day summary. Workshop ends at four, the client has a validated as-is map by six.
The same-day summary is a commercial signal
Clients cannot evaluate your analytical judgement in week one. They can evaluate whether the thing they discussed this afternoon showed up tonight or next Thursday. A same-day, already-corrected map sets the tempo of the engagement, and it is one of the few credibility signals available before you have produced findings.
Client data handling, stated plainly
For a consultant this is a procurement and contractual question, not a preference. You are handling a client's process information, usually under an MSA with data clauses. Here are the facts without softening.
- Transcripts are stored on your account. That is deliberate: it is what lets you reopen and re-edit a flow later rather than starting again.
- Deleting a flow deletes its transcript.
- Transcripts are never used to train any model.
- Processing runs on Groq-hosted open models, Llama 3.3 for structuring and Whisper for speech, which do not retain content for training.
Now the part most vendors leave out: check your own client agreement before putting client conversation data through any third-party tool, including this one. Some MSAs require written approval for new subprocessors. Some public sector and financial services engagements rule out anything off an approved list. That is a contract question, better asked before the workshop than after.
Where it fits across engagement phases
- Discovery and current-state assessment. The core use. Map the as-is while the people who operate it describe it. See how to document a current state process for the interview structure.
- Requirements and design workshops. Draw the to-be next to the as-is. The delta is the scope, visibly, and the change request writes itself because you can point at the steps that moved. Our guide to running a process mapping workshop covers how to structure that session.
- Vendor selection. A clear, client-validated as-is is what makes RFP requirements defensible. Requirements traced to a documented current-state step survive vendor pushback. Requirements traced to an opinion do not.
- Handover. The client keeps an editable map rather than a PDF nobody can update. Documentation nobody can maintain is stale within a quarter.
- ERP and platform programs. See process mapping for ERP implementations, and the technical project managers page for the view from inside the program.
Where this does not fit
Process and data flow only. No BPMN 2.0 with correct symbology, no UML, no ERDs, no C4, no ArchiMate. If the client's methodology or your firm's template mandates a conformant BPMN or ArchiMate artifact, capture the shape in the room and formalize it in the modelling tool afterward. Still faster than starting from notes, because you are transcribing an agreed structure instead of reconstructing an argument.
No precise visual layout either. If the deliverable is a board-ready diagram, someone will still lay it out. The difference is that they lay out something the client already signed off on, so the layout pass does not become a content pass.
Bad room audio is a real limitation. A big room, a speakerphone in the middle of the table, three people talking over each other: hard for any speech system. Record it and paste the transcript afterward instead. See transcript to flowchart.
And the honest one. If you bill hourly and the write-up hours are billable, this reduces your revenue on that line item. No way around it. The argument for using it anyway is that clients notice how many hours went to documentation versus insight, and the consultant whose deliverable lands the same day beats the one billing four hours of Visio. Your call, with the tradeoff visible.
Unlike Gong, Fireflies, and Otter, which return a text summary, Wavelength returns a diagram, because a process is a shape, not a paragraph.
Common questions
Can I put client conversation data through it?
Depends on your client agreement, so check it first. The facts: transcripts are stored on your account so a flow can be reopened, deleting a flow deletes its transcript, transcripts never train any model, and processing runs on Groq-hosted open models that do not retain content.
Does it export something I can put in a client deck?
Export a PNG and attach it to the same-day summary or drop it into a slide. It looks like a clean process map, not a brand-compliant graphic. If the template demands the latter, someone still lays it out, but from an agreed structure.
What if the client uses BPMN?
Capture the shape in the room, formalize it in your BPMN tool afterward. You will not get conformant symbology here. Starting BPMN from a validated map still beats starting from notes.
Can the client edit the map after handover?
Yes, the flow stays editable. On Pro there are shared libraries and per-flow collaborators with invite links, so the client team maintains it once you are gone. See pricing.
Does it work from a Teams or Zoom transcript instead of live?
Yes. Paste the transcript and you get the same editable diagram. That is the fallback for bad audio and for sessions where you were facilitating too hard to run anything else.
How is this different from an AI notetaker?
A notetaker gives you a summary and action items, useful, but not a process map. This gives you actors, systems, decisions, and handoffs in a diagram the client can correct. See the comparisons.
No account for the demo. No card for the free plan.