Project management software built for marketing agencies

Open a task into a full drawer: description, several assignees, start and due dates, priority, tags, real file attachments, an estimate and logged hours, watchers, blockers and comments. A context strip names the client and the project it belongs to, and the project name links straight there.

Everything you touch is written down. The activity trail records status moves, reassignments, date edits, comments and custom-field changes against the person who made them, and a quiet chip reads Saving, All changes saved or Retrying, so nobody wonders whether an edit landed.

Break work down and each subtask is a genuine task: its own title, description, assignees, due date, priority, status, tags, attachments and comment thread. Open one in the same drawer, hand it to a different specialist, give it its own deadline — it still rolls up into its parent's progress.

The hierarchy is deliberately one level deep, and a subtask always stays in its parent's project and client account, so a breakdown never becomes a tree nobody can navigate. Views hide subtasks until you switch them on, and project stats count top-level tasks only.

When a step does not deserve a whole task, the checklist is still there: named items you tick off inside the task. Any checklist item can be promoted into a real subtask the moment it grows teeth, and deleting a task takes its subtasks with it under one undo.

Type @ in a task comment and a people picker opens over the composer, the same one your team uses in chat. Pick a name and the mention becomes a chip in the thread. Teammates who are not on the project are still offered, clearly marked, so you can pull in whoever knows the answer.

A mention notifies the person named; a new comment notifies the task's assignees and watchers. Both land in the header bell and the Activity Center, deep-linked to the exact task, and a mention outranks a plain comment so it files under mentions. Your own comments never ring your own bell.

That same thread is what a client sees on a shared project, with mention tokens rewritten to plain names on the server — so a portal never shows your internal member keys, and nobody keeps a second, sanitized conversation elsewhere.

Rename, recolor, reorder, add and delete status columns so the board mirrors your real pipeline — Backlog, In Progress, Client Approval, whatever your shop calls them — with one column marked as the done state. Priorities work the same way: keep Urgent, High, Medium and Low, add your own, or reset in a click.

Custom fields let a task hold what your process needs and no template ships with: single-line text, long text, a number, a date, a checkbox, a URL, or a single-select with your own options. Mark one required and an empty value is flagged on the task; a field created through the Projects API wears a From API chip.

All three lists live in one panel — Settings → Projects — so the vocabulary the columns, filters, groupings and API share cannot drift into three versions. Retiring a field hides it without deleting the values already stored, and deleting a status moves its tasks to the first column.

Every project belongs to a client, so selecting an account filters the board to that client's work and hides the rest — the structure a multi-client agency needs to stop twelve accounts blurring into one backlog. Nothing lives in a general bucket outside an account.

Switch to All Projects for one client's entire portfolio in any of the five views, grouped and badged by project: the view you open before a client call. Choose All Clients and the same views widen into a cross-client aggregate, every row badged with its client.

When a marketer submits a paid, social, email or SMS plan for approval, the console creates a real task in a per-client Marketing Plans project — assigned to the approver, due in a few days, tagged for marketing and deep-linked to the plan.

The reviewer approves or requests changes in Team > Approvals or on the plan itself; the task points there, and completing it alone approves nothing. The review task lives where the rest of the work lives — on the board, in the assignee's own list, surviving a reload — rather than in an email nobody can find later.

Flip a project to client-visible and its tasks come along, so a client sees a clean view of the program you run for them in their own portal — while a per-task override keeps anything internal out of sight. The default is private until somebody decides to share.

That double gate lets one board serve your team and your client without two trackers drifting apart. Clients comment on what they can see, and their replies land in the thread your team is already reading, instead of arriving as a screenshot in an email.

Projects is responsive to roughly 360 pixels wide. The sidebar becomes a drawer, the list stacks into readable cards, dense tables scroll on their own axis instead of pushing the page sideways, and the task drawer opens as a full-height sheet.

That matters because agency work does not stay at a desk. Reassigning a task between meetings, ticking off a subtask in a client's reception, answering an @mention on the train — the mention picker, the field editors and the composer are built for a thumb.

General-purpose work managers are good software, and plenty of agencies run on one. What they ask is that you rebuild the client dimension yourself: a workspace per account, a tag convention everyone has to remember, client access granted person by person, a separate portal bolted on later.

Here the client is part of the model. A project belongs to a client account that already holds that client's files, chat channel, meetings, notes, CRM pipeline, campaign plans and reports — so a task can point at the brief it came from, and sharing it with the client is a switch.

The honest trade: this is a project manager for agencies running client work, not a build-anything platform. No task automations, no recurring-task generators, no app directory — one workspace where the work, the approvals and the client are the same records.