What if every team works differently?
Each project runs its own way: sprints, a board, or a gantt. Templates set up the phases, tasks, and dependencies.
List, board, calendar, and gantt all show the same tasks. Switch views and your filters come with you.
Every field as a column. Group by client or lead, and save the view for the team.
See what is stuck at a glance, and drag it on when it moves.
Due dates on a month, so an overloaded week shows before it lands.
Show the plan across time, and what moves with it when a date slips.
Each project runs its own way, everyone sees what is next, and decisions stay with the work.
Each project runs its own way: sprints, a board, or a gantt. Templates set up the phases, tasks, and dependencies.
My Tasks gathers your work from every project, with what is due first. Recurring work schedules itself.
Discussions pin to the record they concern, so the reason behind a call stays with the work. Action items extract into tasks.
Templates, phases, and dependencies. Run one project or two hundred.
A lane that runs across projects, for work that never fits inside one.
Fixed windows or repeating cadences. Carry-over and velocity are tracked for you.
Goals above the projects, with progress rolled up from the work itself.
Subtasks, dependencies, and custom fields, in the view each team prefers.
Each type gets its own statuses, fields, and rules. A bug is not a change request.
Stages and SLA clocks that pause while you wait on the requester.
Schedule it once. The task arrives on time with its checklist.
Everything assigned to you, across every project, with today first.
Save any filtered list and share it. Search finds any task, note, or decision.
Build your own tables without a developer. Add fields, views, and automations.
Rich text that sits with the project, deal, or meeting it belongs to.
Threads by topic, pinned to the record. The reason behind a decision stays with it.
Versioned, searchable, and attached to the right record.
It becomes a ticket with an SLA clock that pauses while you wait. Bigger than a reply? Promote it to a task, project, or deal, conversation attached.
What this removes
Retyping a client conversation into a second tool, and the gap between what support promised and what delivery scheduled.
One workspace, so the records here are the records everything else reads.
Don't see your question? Contact us
Yes. Pick one per project. A sprint build and a milestone retainer run side by side and roll up to the same reports.
Yes. Subtasks, dependencies, milestones, priorities, due dates, custom fields, and per-type statuses, in list, board, calendar, or gantt.
Yes. Recurring tasks arrive on schedule with their checklist attached.
Yes. My Tasks collects your work across every project, and Today puts what is due first.
Through the client portal, a form, live chat, or email. Each becomes a ticket with routing and an SLA clock, and can turn into project work in one move.
Yes. Bulk import checks each file, keeps a history of every run, and lets you recover from a bad one. See the migrate page for supported tools.
Yes. Gantt is one of the four views. When a task slips, the tasks that depend on it show it.
Yes. Run fixed sprints or repeating cycles. Carry-over and velocity are tracked for you.
Yes. Each task type has its own statuses, fields, and rules.
Yes. The client portal shows them the live record, and requests they raise there become tickets.
Yes, on Pro and Business. Merged pull requests link to their task, and Slack keeps the team posted. Email and calendar sync come with every plan.
Projects and tasks are on every plan, including Core. Tickets, workflows, and collections need Pro. See pricing for details.
Yes. Benny drafts the weekly status from the real work: comments, completed tasks, and changes in risk.