Project management with the structure your team needs.

Run one project or two hundred on records the rest of the workspace can read.

Try for freeSee pricing

What can you do with project management?

  1. Templates per project type

    Phases, tasks, and dependencies pre-set. Templates, hierarchies, and dependencies that hold, built to run one project or two hundred.

  2. List, board, calendar, and gantt on the same records

    Subtasks, dependencies, custom fields, and views that make sense to engineering, sales, and ops at the same time. The work atom done well.

  3. Tickets with their own stages and SLA clocks

    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.

  4. Decisions stay with the work

    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

How do you want to see the work?

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.

List

Every field as a column. Group by client, lead, or any field, and save the view for the team.

Board

Drag work between statuses. Each task type brings its own columns.

Calendar

Due dates on a month, so a crowded week shows before it arrives.

Gantt

Dependencies drawn across time. When something slips, what slips with it is visible.

On every task

  • Subtasks
  • Dependencies
  • Milestones
  • Priorities
  • Due dates
  • Custom fields
  • Per-type statuses

Projects

What if every team works differently?

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

What should you do next?

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.

My Tasks, across everything

One list, every project, no digging.

Today

What is due now, pulled to the front.

Recurring work

The repeating stuff schedules itself.

Requests

What happens to a client request?

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

Where do the decisions end up?

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.

Inside project management.

Works with

  • Claude
  • Slack
  • GitHub
  • Zoom
  • Gmail
  • Microsoft Outlook
  • Google Calendar
  • Forms

Explore integrations

Switching from another tool?

  • Asana
  • Monday.com
  • Trello
  • ClickUp
  • HubSpot
  • Harvest
  • Notion
  • Confluence
  • Google Sheets
  • Excel

If it exports a CSV or a document, it moves. See how to migrate

Questions people actually ask.

Don't see your question? Contact us

Can each project use a different methodology?

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.

Do tasks support subtasks and dependencies?

Yes. Subtasks, dependencies, milestones, priorities, due dates, custom fields, and per-type statuses, with list, board, calendar, and gantt views on the same data.

Can work repeat on a schedule?

Yes. Recurring tasks arrive on schedule with their checklist attached, so the monthly close and the weekly report stop depending on memory.

Is there one view of everything assigned to me?

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.

How do requests from clients enter the queue?

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.

Can we bring projects over from another tool?

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.

Is there a gantt chart with dependencies?

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.

Can we run sprints?

Yes. Sprints and cycles are fixed windows or repeating cadences, with carry-over, archive, and velocity handled by the system rather than remembered.

Can a bug and a change request have different fields?

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.

Can clients see progress without a status report?

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.

Does it connect to GitHub and Slack?

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.

Which plan includes project management?

Projects and tasks are on every plan, including Core. Tickets, workflows, and collections need Pro. See pricing for the full list.

Can Benny write the status update?

Yes. Benny drafts the weekly status from the actual work: comments, completions, and risk shifts, so nobody assembles it by hand.