Three of the 4,200 teams planning in Flowzy, and the specific thing that changed for each of them. The numbers are theirs, not ours.
4,200 teams planning in Flowzy1.2M tasks shipped this quarter18% fewer missed deadlines after 90 days4.8/5 average review
Oripio · Product studio · 40 people
Ending the sprint-capacity argument
Oripio ran delivery out of a spreadsheet and a weekly meeting whose only purpose was to find out what had actually happened. Estimates existed, but nobody could see them against the days people were really available.
The workload view made the gap visible during planning rather than during the retro. The recurring argument about whether a sprint was realistic became a chart everyone could read, and the weekly status meeting was retired.
“The workload view ended a recurring argument. We could finally show that the sprint was 30% over capacity before anyone committed to it.”
Priya RamanDelivery Lead, Oripio
30%over capacity, caught before commit
6 → 1status meetings per week
Nyra · Consumer app · 120 people
One dataset, two very different readers
Nyra's designers worked on a board, its product managers worked in a calendar, and the two were reconciled by hand every Friday. The reconciliation was the job that nobody wanted and everybody distrusted.
Moving both groups onto the same records removed the reconciliation entirely. Neither team changed how they work; they simply stopped working from copies.
“Our designers live in kanban and our PM lives in the calendar. Same data, no export, no arguing about which board is current.”
Tom BergqvistHead of Product, Nyra
0exports between design and delivery
18%fewer missed dates after 90 days
Basalt · Operations · 60 people
Automation without a specialist
Basalt had wanted routing rules for two years. Every attempt died at the same point: the rule builder needed someone technical, and that person was always booked on something else.
Writing the rule as a sentence removed the specialist from the loop. The ops team now ships its own automation, and the execution log means a rule that misbehaves is diagnosed rather than switched off.
“I set up automation by typing a sentence. That is the whole story. Previously it was a flowchart builder and a support ticket.”
Hana SugiyamaOps Manager, Basalt
14rules live, written by non-engineers
2 daysfrom idea to running rule
And the shorter version, from everyone else.
“We moved 300 tasks over from Jira on a Tuesday afternoon and nobody
lost a comment. That was the whole migration.”
Marek DolejšíEngineering Manager, Halden
“Guests see their board and nothing else. I stopped keeping a second,
sanitised copy of the plan for clients.”
Ada NwosuStudio Director, Fenwick & Vale
“The slip warning gave us nine days’ notice on a launch date. We
moved two things and hit it.”
Ren TakahashiProgramme Lead, Sundara
Plan the next quarter before it plans you.
Free for up to three projects. No card, and your data exports whole if you leave.
Priya RamanDelivery Lead, Oripio
