Skip to content
Demo only.

Project management for teams and workflows

Work moves when it’s actually ready.

Three teams, three methods, one workspace. Estimates, dependencies, checklists and sign-offs are checked by the server on every path that can move a card. Not a warning. A refusal, with the reason attached.

No card. Three teammates included.

01The board
Todo22pts
Rate limit the export job
API
high1/3Sep 25
Sara
Retry webhooks with backoff
Infra
low2ptsSep 30
Leo
Design15pts
Progress report
medium5pts4/4Sep 23
Mia
Build211pts
At WIP limit2 / 2
Board presence
API
urgent8pts3/5Sep 20
LeoMia
Column exit criteria
medium3ptsSep 27
Sara
Sign-off13pts
DPA rewrite for EU customers
Awaiting approval
high3ptsOct 2
Mia
Shipped15pts
Card dependency wall
medium5pts6/6Sep 16
SaraArun
Todo first, a WIP cap of two on Build, and an approval column that freezes a card until it is signed off.
02The interlock

Most tools warn you. This one says no.

Three refusals, quoted from the source. Same answer whether the card is dragged, bulk-edited, or moved by an automation.

Entry ruleEntry rule
This board requires estimates. Add one before moving the card into Design.
Sequential flowlib/columns
This board moves one stage at a time. You can’t skip ahead.
Sub-task gatelib/subtasks-shared
This card still has 2 of 5 sub-tasks unticked — finish the checklist before moving it to Done.
  • WIP limitA column already at its limit stops accepting work.Capped columns
  • Dependency wallA blocked card cannot move forward until its blocker closes.Every board
  • Sequential flowWork cannot skip a stage on the way forward.Governed boards
  • Entry ruleLeaving the backlog can require an estimate first.Per board
  • Sub-task gateUnticked sub-tasks keep a card out of any Done column.Every board
  • Approval freezeA card awaiting sign-off cannot move at all.Approval columns

Backwards is always free. A card can be pulled back down the route at any time, so getting unstuck never needs permission.

03The views

The same cards, read another way.

A board is one reading of the work, not the work itself. The list is where you triage. The calendar shows a crunch week before it arrives.

7 tasks1 overdue
Task
Status
Assignee
Progress
Due
Age
Tags
Rate limit the export job
Todo
Sara
1/3
Sep 25
API
Retry webhooks with backoff
Todo
Leo
Sep 30
Infra
Progress report
Design
Mia
4/4
Sep 23
Board presence
Build
LeoMia
3/5
Sep 20
API
Column exit criteria
Build
Sara
Sep 27
DPA rewrite for EU customers
Sign-off
Mia
Oct 2
Card dependency wall
Shipped
SaraArun
6/6
Sep 16
TodoDesignBuildSign-offShipped

Double-click a title to edit inline · Click a row to open

List: grouped by column, with progress, assignees and overdue dates in red.
Wed, Sep 16
Sun, Sep 20
Wed, Sep 23
Fri, Sep 25
Sun, Sep 27
Wed, Sep 30
Calendar: every due date on a month grid, while there is still time to move one.

Timeline, swimlanes and the flow report read the same cards. So do drafts, tickets and hand-offs.

04The methods

Three ways of working, one workspace.

Support runs continuous flow. Product plans in cycles. Compliance needs controlled stages and a signature. Three boards, one workspace, the same people and history.

Support

Continuous flow

Backlog
Doing
Done

No ceremony. A WIP limit of three keeps the middle column honest.

Product

Two-week cycles

Backlog
Build
Review
Done

Points, burndown, and cycles that start and end on their own dates.

Compliance

Approval flow

Draft
Legal
Sign-off
Filed

No skipping a stage. Sign-off freezes the card until someone signs it.

05The price
$6per seat / per month

One plan, everything in it. Five days free for up to three teammates. No tier hides the gates or the reports behind an upgrade.

No card up front. If it is not carrying your team by day ten, you have lost ten days and nothing else.

  • Boards, cycles and controlled stages in one workspace
  • The whole interlock, enforced server-side
  • Shared boards, flow metrics, five access levels
  • Tickets, drafts, hand-offs and an activity log
  • 500 projects, 5,000 boards, 20,000 cards a board