Delivery
Never hear a cycle slipped from the client first
Delivery merges every in-flight Project and Cycle — and their Tasks — into one worklist sorted by urgency. Final-stretch and untouched work floats to the top, so the thing about to be late is the thing you see first.
One list, not two views
One-off Projects and recurring retainer Cycles sit side by side, not in separate tabs.
Sorted by urgency
Final-stretch and untouched work floats to the top — triaged the way a program manager would.
Cycles renew themselves
A new Cycle generates each billing period, pre-filled from a task template plus anything left over.
How it works
Projects and Cycles merge
Every in-flight one, and its tasks, in a single list across every client.
Urgent work floats to the top
Final-stretch and untouched work is surfaced first.
Cycles renew themselves
Retainer cycles regenerate each period from the label’s task template.
- Merges every in-flight Project and Cycle — and their Tasks — into one sorted worklist across every client
- Final-stretch and untouched work floats to the top, mirroring the same signals the Monitor watches for
- Company-less internal work is grouped under its own Internal section, not scattered or hidden
- Cycles auto-generate on schedule for retainers, pre-populated from a per-Label task template plus anything carried over incomplete
- A Cycle closes when its tasks are done — with or without a client-facing delivery Document — and the retainer keeps running regardless
- Tasks can be marked as blocking or blocked by other tasks, so dependency chains are visible before they cause a slip
- When a person’s task load crosses a capacity threshold, the worklist flags it — overload is visible, not discovered after the fact
Part of one workspace
Every part reads and writes the same records, so nothing has to be kept in sync.
Less paperwork. More business.
Seats open in small batches — join the waitlist and you’ll be first in line when yours is ready.