Everything the plan needs, in one place
Six things Flowzy does that a spreadsheet and a group chat cannot. Every one of them reads and writes the same records — there is no second source of truth to reconcile.
Three views, one plan underneath
Move a card in kanban and the list, the calendar and the workload chart all update. There is no export step and no which board is current conversation, because there is only ever one plan.
Each person picks the shape they think in. A designer can live in the board, a delivery lead can live in the calendar, and neither has to translate.
- Kanban, list and calendar over the same records
- Per-project default view, per-person override
- Filters and grouping survive the switch
Describe the rule in a sentence
Type when a task hits review, ping the owner and Flowzy writes the trigger. Open it later and it is still a sentence, not a flowchart you have to re-learn.
Rules run on the server, so they fire whether or not anyone has the tab open, and every run is logged with what it changed.
- Plain-language rules, editable in plain language
- Runs server-side, logged per execution
- Dry-run a rule against last month before enabling it
Capacity you can see before you commit
Capacity is computed from real estimates and real days off, not from an assumption that everyone works five clean days a week. An over-committed sprint shows up while it is still a plan.
The forecast is the same number your delivery lead would work out by hand, which is why people trust it enough to argue with it.
- Estimates and time off feed one capacity line
- Per-person and per-team, week by week
- Over-commitment flagged before the sprint starts
The argument lives on the task
Every task carries its own thread, its files and the decision that closed it. No archaeology across three tools to find out why a date moved.
Decisions can be pinned, so the answer is at the top of the task six months later instead of forty comments down.
- Thread, files and decisions on the record itself
- Pin the decision, not the whole conversation
- Mentions notify once, not per reply
A warning while it is still fixable
Flowzy watches velocity per project and flags the date that is going to slip while there is still time to move something. A red date on the day it slips is not a feature.
Each warning comes with the two or three changes that would recover it, costed in days rather than in vague reassurance.
- Slip predicted from this project's velocity
- Fix options costed in days
- One digest per project, not one alert per task
Guests see one board, not your estimates
Invite a client to the board they are paying for and nothing else. They can comment on the work without seeing your internal estimates, your margins or your other clients.
Permissions are set per project, and the audit log records who changed them, which is the part procurement always asks about.
- Per-project roles, not one company-wide setting
- Guests can comment without seeing estimates
- SSO, SCIM and an audit log on the Company plan
Works with what you already have.
Import once and keep the tools your team refuses to give up. Nothing here is an upsell — integrations are on every plan.
Plan the next quarter before it plans you.
Free for up to three projects. No card, and your data exports whole if you leave.