VSM Builder

Value stream mapping that calculates.

Rother and Shook symbols, lead time and takt time live from your process data, future-state scenarios with payback. Not a drawing tool with VSM shapes, but a calculation tool that happens to draw a standards-compliant map.

Open the demo Get started free

The demo runs without signing up: a complete value stream with five processes, inventory and calculated metrics. Change one cycle time and watch the lead time respond.

A section of a current-state map: process boxes with C/T and OEE, inventory as triangles, and the timeline of wait and processing time below.

Every number shows its own arithmetic

Under each metric sits the formula with the values actually used. A surprising number therefore explains itself from its own inputs, instead of looking like a defect.

Lead time: WIP ÷ output; Little’s Law across every inventory point in the chain.
Takt time: Available min/day ÷ customer demand; Derived from annual demand and shift pattern, not estimated.
Process cycle efficiency: Value-added time ÷ lead time; The number that starts the discussion in the steering committee.
Actual output: Available min/day ÷ bottleneck; Effective cycle time including OEE, not the nominal one.

The tool pushes back

A value stream can be methodologically wrong and still look fine. The method check runs on every change and ranks by severity: first what invalidates a metric, then what only affects the drawing.

Metric affected
Capacity shortfall
If the line cannot meet customer demand, inventory grows without bound. Little’s Law no longer holds, and the tool says exactly that instead of claiming a lead time.
Methodologically unsound
Push upstream of the pacemaker
Everything upstream of the pacemaker needs a pull system. Where a connection still runs as push, it is named and counted.
Methodologically unsound
No pacemaker set
Without a pacemaker, the ERP schedules every process individually. The map shows it that way, and the note explains why that is rarely intended.

From current state to business case

Each future-state scenario is its own copy of the value stream. The comparison places them side by side and translates the lean metrics into the language budgets are decided in.

Metric	Current state	Scenario A
Lead time	18.4 days	9.1 days
Process cycle efficiency	0.41%	0.83%
Investment	–	€85,000
Payback	–	14 months
Risk	–	Medium

Example values, shown to illustrate the columns.

Built for the room where the value stream is created

A VSM is not filled in at a desk, it is worked out in front of the group. Afterwards it has to fit on a sheet that someone else reads.

Presentation mode: Hides import and renaming. Process boxes stay editable, because a value stream is created in the room with the team and is not finished beforehand.
Full screen: One movement space instead of three. For the projector in the meeting room and the laptop on the shop floor.
PDF export: Map and metrics on A4 landscape. The sheet that goes into the committee.
24 terms explained in context: Pacemaker, supermarket, FIFO, heijunka, EPEI. Explained where they appear, so green belts and operators can follow.

Where your data lives

A value stream describes your production: takt times, inventory, bottlenecks. Anyone working with it wants to know up front where that is stored.

Database: Supabase; EU, France region
Application: Vercel; EU, France region
Other recipients: None; No analytics or tracking service is embedded

Plans

Compare all plans →

Free: €0; One value stream, one scenario, two seats. Every metric, every method check, PDF export.
Starter: €12/month; Five value streams, three scenarios each, five seats. Plus importing process steps from a CSV.
Professional: €49/month; Fifty value streams, unlimited scenarios, 25 seats. Including the industry benchmark.
Enterprise: Price on request; No volume limits, for several plants.

Look first, decide after

The demo needs no account and no company address. Anyone who then wants to build their own value streams will find the same functions in the tool.

Open the demo