List
Every field as a column. Group by client, lead, or any field, and save the view for the team.
Phases, tasks, and dependencies pre-set. Templates, hierarchies, and dependencies that hold, built to run one project or two hundred.
Subtasks, dependencies, custom fields, and views that make sense to engineering, sales, and ops at the same time. The work atom done well.
Typed stages and SLA clocks that pause while you wait on the requester. A customer issue can become a fix, an epic, or a deal in one move.
Threaded by topic, not by channel. Decide things in writing, leave a trail, and never lose the reason behind a call you made in another time zone.
Views
List, board, calendar, and gantt are four lenses on the same task records, not four copies. Switch between them without losing your filters or grouping, so engineering can run a board while the delivery lead reads the gantt, and nobody re-teaches the team a new tool. Filter any list, save it, and share it, and the same saved view works for the sales, ops, and engineering people who all touch the project.
Every field as a column. Group by client, lead, or any field, and save the view for the team.
Drag work between statuses. Each task type brings its own columns.
Due dates on a month, so a crowded week shows before it arrives.
Dependencies drawn across time. When something slips, what slips with it is visible.
On every task
Projects
Pick a methodology per project, not per company. Engineering runs sprints, ops runs a board, delivery runs a gantt, all on the same task records and custom fields. Templates carry phases, tasks, and dependencies into every new project.
My Tasks & Today
Most tools show you a project and make you dig for your part. My Tasks gathers everything with your name on it across every project, Today pulls forward what is due, and Focus clears the rest out of view.
One list, every project, no digging.
What is due now, pulled to the front.
The repeating stuff schedules itself.
Requests
It becomes a ticket with its own stages and an SLA clock that pauses while you wait on the requester. If it turns out bigger than a reply, promote it to a task, a project, or a deal in one move, conversation attached.
What this removes
Re-typing a client conversation into a second tool, and the silent gap between what support promised and what delivery scheduled.
Discussions & notes
Discussions are threaded by topic and pinned to the record they concern, so the reason behind a call lives next to the work it shaped. Notes sit with the project or meeting, and action items extract into tasks.
Templates, hierarchies, and dependencies that hold. Built to run one project or two hundred.
A lane that spans projects, for the teams whose work never fits neatly inside one of them.
Fixed windows and repeating cadences, with carry-over, archive, and velocity handled rather than remembered.
Initiatives and objectives above the projects, with portfolio-level progress rolled up from the work itself rather than from a status meeting.
One workspace, so the records here are the records everything else reads.
Modules with their own pages
ProjectsCoreTasksCoreTicketsProCollectionsProNotesCoreDiscussionsProDocumentsCoreSwitching from another tool?
If it exports a CSV or a document, it moves. See how to migrate
Don't see your question? Contact us
Yes. Methodology is chosen per project, so a sprint-based build and a milestone-based retainer run side by side on the same records and roll up to the same reporting.
Yes. Subtasks, dependencies, milestones, priorities, due dates, custom fields, and per-type statuses, with list, board, calendar, and gantt views on the same data.
Yes. Recurring tasks arrive on schedule with their checklist attached, so the monthly close and the weekly report stop depending on memory.
My Tasks collects your work across every project, and Today pulls forward what is due. Focus clears everything else out of view when you need to ship.
Through the client portal, a branded form, live chat, or inbound email. Each becomes a ticket with routing and an SLA clock, and can be promoted to project work in one move.
Yes. Bulk import with validation, a full run history, and a recovery path if a file was wrong. See the migrate page for the supported sources.
Yes. Gantt is one of the four views on every task list, and dependencies block, follow, and roll up, so when one task slips the ones behind it show it.
Yes. Sprints and cycles are fixed windows or repeating cadences, with carry-over, archive, and velocity handled by the system rather than remembered.
Yes. Task types each bring their own statuses, fields, and rules, so a bug and a change request stop pretending to be the same object.
Yes. Through the client portal, clients see the real record, not a status report you rebuilt on Friday, and a request they raise there becomes a ticket on the same records.
Yes, on Pro and Business. A merged pull request links to its task, and Slack keeps the team informed where it already talks. Email and calendar sync ship on every plan.
Projects and tasks are on every plan, including Core. Tickets, workflows, and collections need Pro. See pricing for the full list.
Yes. Benny drafts the weekly status from the actual work: comments, completions, and risk shifts, so nobody assembles it by hand.