FlowVisual · macOS & Windows

Describe it once. Four answers. On your own machine.

FlowVisual is the tool for the FLOWREFY method. You describe a business process, such as quoting, order handling or invoice approval, the way it’s told in conversation, and get the process manual, the workload per role, the automation case and the knowledge risk. The stress test exposes your most expensive bottleneck and works out what a change would bring in euros and time, before you switch a single piece of software.

macOS 12+ via the App Store · Windows 10/11 via the Microsoft Store

Guide: how to use FlowVisual in 45 minutes
Version1.2.1
PlatformmacOS · Windows
DataLocal only
Modellingfree
FlowVisual 1.2.1 — Canvas
FlowVisual, Model view: a process built from elements, service times as a range of 8 to 20 minutes instead of a single estimate
01Views

From a process on paper to a number you can defend

Four lenses on the same model (model, domain, IT, management) and one result: you see where it jams and what relieving it is worth.

01 / Capture

Describe it once, the way it’s told

  • One line per step: role, duration and pain point on the same line
  • Or from building blocks: steps, decisions, sub-processes, start and end
  • Whatever nobody said goes on the open-questions list, never in as a silent zero

Write the process down the way people tell it to you: what happens, who does it, with what, how often, how long, what goes wrong and who else can do it. One line per step, and the chain wires itself. If you’d rather draw, build the same steps from building blocks. No BPMN degree required.

FlowVisual, Model view: a process built from elements, service times as a range of 8 to 20 minutes instead of a single estimate
Abb. 1Describe it once, the way it’s told
02 / Test

Stress test instead of a guess

  • Load on the peak day (P90) instead of an average
  • Lead time as P50, P90 and extreme day, without false precision
  • Throughput, days over capacity, and the headroom that is left

A stress test across a few hundred random working days shows which step saturates first and where the bottleneck moves after that: with load on the peak day (P90), lead time as a range up to the extreme day, throughput, and the share of days over capacity.

FlowVisual, stress test over 400 runs: the bottleneck at the top with 141 per cent load on a busy day, next to it cycle time as P50 and P90 and the fragility curve
Abb. 2Stress test instead of a guess
03 / Domain

Make load per role visible

  • Utilization per role in percent, colour-coded
  • Overloaded roles spotted instantly
  • Evidence for re-distribution instead of gut feeling

Who is overloaded, who has room? The domain lens colours utilisation per role: comfortable below 85 %, tight up to 100 %, overloaded above. That is the basis for redistributing work before you think about new hires or new software.

FlowVisual, Operations view: load coloured per role, the overloaded step in red
Abb. 3Make load per role visible
04 / Fit for the digital world

Media breaks and automation potential in euros

  • Load per system, not only per person
  • Media breaks visible exactly where data gets retyped
  • Value per measure in euros per year, as a range rather than a point

The IT lens shows load per system and reveals the points where data is carried by hand into the next system. The options list computes what closing such a break would be worth in euros per year. Before the digitisation project, not after it.

FlowVisual, IT view: which systems a step touches and where a media break begins
Abb. 4Media breaks and automation potential in euros
02Why simulate

A process is not a sum.

Try it yourself: same process, four situations — normal operations, a demand spike, a supply shortage, staff out sick. Watch the bottleneck move, and watch whether a person or a system is the limit. That decision is the whole point.

How a simulation works
000/500 runs

Your bottleneck is not a property of the process. It is a property of the situation.

The same five steps, four situations. One run draws one duration per step — one possible day. Five hundred runs make a distribution. Switch the situation and watch the bottleneck move.

Situation

An ordinary month. Nothing unusual happens — which is exactly what every process is designed for.

Last run
  • Capture the order—
  • Technical review—
  • Material / supplier—
  • Approval—
  • Dispatch—
Total duration across 500 runs
Averages added up
Averages added up

3 h 03 min

The figure everyone calculates.

Actually the median

—

In 1 of 10 cases

—

This gap is where deadlines break.

Which step held things up?
  • Capture the order
    0 %
  • Technical review
    0 %
  • Material / supplier
    0 %
  • Approval
    0 %
  • Dispatch
    0 %
04Principles

Built for honest numbers

No false precision, no cloud requirement. A tool for decisions that hold up.

01

Ranges, not false precision

Every euro figure comes with a P10–P90 band. 5–10 minutes instead of a made-up 7.5. The way processes actually run.

02

Runs locally, no sign-up

No cloud, no account. Your files stay on your own drive. Ideal for sensitive process data.

03

Manual, proposal, work packages

The process manual with responsibilities (who decides, who does the work, who is kept informed), the proposal with its business case and the work packages all come from the same model. Free as PDF; Word and your own letterhead with Pro.

04

Mac & Windows

Native desktop app for macOS (Apple Silicon & Intel) and Windows 10/11. Fast, offline, no browser lag.

05 / Download

Download FlowVisual

Capture, calculate, save and PDF are free. No cloud, no account.

macOS 12+ (Apple silicon & Intel) · Windows 10/11

FAQ

Frequently asked questions about FlowVisual

No. FlowVisual runs entirely locally on your machine. There is no sign-up and no server. Your process files stay on your own drive.

No. You build a process from six building blocks or write it down as a table, without learning a notation. It gives you the flow diagram, the process manual and the responsibilities (who decides, who does the work, who is kept informed). Existing Visio files are imported directly.

You enter volumes, durations as ranges, capacities and cost rates. The Monte Carlo stress test turns them into ranges (P10–P90) instead of false precision. Every figure carries its origin: measured, estimated or not captured.

Capturing, stress testing, comparing variants, saving and the PDFs are free, with no account and no limit. The PDF then carries a trial mark. Pro adds PDFs without the trial mark, your own letterhead, Word, Visio export, draw.io and SVG, and the team project folder. Current prices are on flowvisual.app.

One process, captured in 20 minutes.

We capture your most important process with you and show you live in FlowVisual where it gets stuck and what that costs.

Book 20 minutes

Live in the tool, with your numbers.