Process mapping with data simulation
See what a change will do. Then see what it did.
Spacious Pro is a process map that runs. Put volumes, staff and costs on the steps, try a change before you make it, and compare the month before with the month after.
In development. Pilot companies use it first.
| Before | After | Change | |
|---|---|---|---|
| Average lead time | 5.7 h | 3.1 h | 46% lower |
| Longest queue | 34 | 6 | 82% lower |
| Orders finished | 191 | 219 | 15% higher |
| Staff cost per order | €53.61 | €51.87 | 3% lower |
Some of what went in
- Volume, one week
- 232 orders
- Pick & pack
- 2 people, 20–36 min
- Back-order
- 12% of orders
Made-up inputs, really simulated: this page runs a small queue model and these are its results.
The problem
A diagram shows the route. It does not show the queue.
Most process maps are drawings: who does what, in which order. They cannot tell you what happens when volume grows, where work will pile up, or whether last quarter's change paid off.
Those answers sit in spreadsheets, one for each department, and they rarely agree. Spacious Pro puts the numbers on the map and runs them, so the questions on the right get an answer everyone can see.
- What if volume grows 20% in December?
- Would a third packer pay for itself?
- Did the new routing really cut the lead time?
How it works
From a drawing to a decision, in five steps.
Map the process
Draw steps, connectors and a lane for each department. It works like the whiteboard you know.
Put numbers on the steps
Volumes over time, routes and their shares, staff and cost rates. Give a range where you are not sure.
Run scenarios
Simulate a shift, a month or a year, at a time scale from seconds to months. See where work waits and what it costs.
Compare before and after
Set one scenario against another. Then play back real data: the month before a change against the month after.
Decide together
Every department works on its own numbers, live on the same board. Present the result straight from it.
Working together
Every department owns its numbers.
A process crosses departments, and so does the board. Each one works on the part it knows, at the same time, on the same map.
-
Operations
Volumes and staff. How much arrives, when, and who is there to handle it.
- Volume by day
- Staff on each step
- Time a step takes
-
Finance
Cost rates. What an hour, a step and a finished item cost.
- Cost of an hour
- Cost of an item
-
Commercial
Scenarios. What a new customer, a peak season or a new offer would do.
- Peak season
- A new customer
Who it is for
Any company that runs processes.
If work moves through steps, with volumes, people and costs, it can be mapped and simulated. The first templates cover three of these.
Manufacturing
Balance a line, plan a second shift, see what a changeover costs.
Logistics
Order to delivery, peak weeks, the capacity of a dock or a packing line.
First templateCustomer service
Ticket routes, self-service, the staff each hour of the day needs.
First templateIT and cybersecurity
Alert triage, incident response, the time it takes to contain.
First templateSaaS operations
Onboarding, support tiers, releases and what an incident does to them.
The board
A whiteboard underneath.
The basics you expect from a board are there, so the workshop and the analysis happen in one place, and nobody redraws the process in a second tool.
Sticky notes and frames
For the workshop before the numbers.
Swimlanes and connectors
Lines that route themselves round the steps.
Charts on the board
Results next to the process they describe.
Comments and voting
Discuss a step where it is.
An open process format Planned
A documented JSON format for a process and its data, which people, programs and AI can read and write.
A public API and AI-assisted building Planned
Describe a process and get a first map to correct.
Data protection
Your process data stays yours.
A map with real volumes and costs is sensitive. This is how Spacious Pro is built for its launch.
Stored in the EU
Boards are stored on Cloudflare in its EU jurisdiction, encrypted at rest.
Raw data stays in your browser
The files you import are read in your browser. By default nothing raw is uploaded; sending a file to the workspace is your own, explicit choice.
You set the retention
Each workspace decides how long history, deleted items and files are kept. What is past its time is deleted.
Private workspaces Planned
End-to-end encrypted workspaces, where we cannot read a board at all, are planned as a later option.
Said plainly: this is how the product is being built, not a certificate. It is not live yet, and we hold and claim no certifications. This page sets no cookies, runs no analytics and loads nothing from other sites.
Pilots
Bring one process. See its numbers move.
We are looking for pilot companies in manufacturing, logistics, customer service, IT and SaaS operations. Bring a process you want to improve and the data you have; we help you map it and run it.
Questions about pricing? Write to pilot@spacious.pro.