Your client just asked which round you're on. ClickUp says Approved. The Figma file's been touched twice since Friday. You can't answer the question from the board.
If you run a design agency, this is the loop. The board looks tidy. The work doesn't live there.
This isn't a ClickUp takedown. It's a strong product and it earns the consideration. The point is more specific than "ClickUp is bad." A design agency's operating reality is mostly about the client layer, and that's not what task trackers are built for.
Where ClickUp earns the consideration
Two things, honestly.
Custom views and fields. You can build almost any tracker inside it. Kanban, Gantt, list, calendar, mind map, switchable from the same data. If your problem is "I have a stack of work and want to slice it five ways," ClickUp solves that elegantly.
Automation and integrations. The automation builder works well. The integration list is long. If your workflow is "task moves through statuses and triggers downstream events," it does the job.
For ticket triage, sprint planning, or internal ops routing, ClickUp is a strong default. That isn't the job of a design agency.
Five places it breaks
Deliverables move between hands. Get marked up. Get billed against contracts. Need to be reassembled into a story you show the client every Friday. ClickUp's model is task-shaped. The work isn't.
1. Approvals live on tasks, not on artifacts
"Approved" is a status on a task. "Design v2 ready for review." Someone moves it to Approved.
The deliverable, though, is a Figma file or a PDF. Approval in the real world means "the client signed off on this specific version." When the designer pushes a v3 the next morning to fix one thing, ClickUp's status stays Approved until somebody manually moves it back. Twelve weeks in, you've got a board of Approved tasks and no record of which version of which artifact the client actually said yes to.
What you actually need is the approval stamp attached to the file at the revision it was given on. So when a stakeholder asks in month three "wait, did we ever sign off on the secondary mark?" the answer is in the artifact itself, not in a task status that's been overwritten six times since.
2. No native count for contract-capped revisions
Most agency contracts cap revisions. "Three rounds included, additional rounds at $X." Every studio has been there: round four lands in Slack as "just one small thing," and nobody catches it.
ClickUp can count things. It cannot count contractually meaningful revision rounds without a custom-field stack somebody maintains by hand. No native concept of a round. No link between revision activity and the contract. The accounting falls to whoever remembers to update the spreadsheet.
What "a round" actually means in agency work is also messier than a status flip: a round opens when feedback comes in, closes when the next version goes out, and bills when it crosses the contract cap. Three events, all on the artifact, none of them naturally captured by moving a card from one column to another.
3. Annotation belongs on the artifact
When a client gives feedback on a logo, they don't write "the top-left curve feels off." They drag a cursor to the corner and say there. Spatial feedback is the actual primitive of design review.
ClickUp's comment system works on tasks. It is not built for marking up a specific pixel of a specific version of a specific file. The workaround is the universal one: clients screenshot, paste into the comment, draw a red arrow, write "this part." Now the feedback lives in three places — the screenshot, the comment, the Figma file — and stays in sync only as long as nobody changes anything.
Tools built for design review anchor comments to coordinates on the artifact, versioned to its revision. ClickUp doesn't, because that's a different product category.
4. Status assembly across surfaces
Friday afternoon. A client emails: "where are we on the brand refresh?"
To answer honestly you need: which deliverables are in review, which got signed off, what's blocked on client input, what round we're on, what's in scope vs. quietly added. In a typical agency stack those answers live in ClickUp (task status), Figma (latest version), Slack (the conversation where the client said yes), Dropbox (the signed contract), and somebody's head (the verbal "yeah we can include that").
ClickUp doesn't cause this. It also doesn't solve it. The status on the task is a thin slice of the actual project state. A person still assembles the real answer by hand, every week, for every active project.
5. Scope drift never becomes a change order
The most expensive sentence in agency work is "we can probably include that, yeah." Said in a call. Not logged. Six weeks later it's a half-built feature in the deliverable, the contract still says the original scope, and nobody wants to be the person who brings it up.
A task tracker captures this only if a human remembers to log it. ClickUp has no model for "verbal scope changes become written change orders." Neither does Asana, Monday, or Jira. They weren't designed for it because their buyer isn't an agency.
The software you actually want here makes the verbal "yeah we can include that" cheap to record (one button on the call, a short note, attached to the project) and expensive to ignore (it sits next to the scope-of-work, visible to anyone who looks). That isn't a feature. It's a different posture toward what the project record holds.
For an internal product team, scope drift is a planning problem. For an agency, it's a margin problem. They look the same on a board and feel completely different in the books.
What the alternative actually looks like
Building a better ClickUp doesn't fix this. Changing what the project record is does.
Picture a project record that is the deliverable. Current version of the artifact. Comment threads anchored to it. Approval state. Round counter against the contract. Scope log with verbal-becomes-written entries. All on the same surface. Status stops being a Friday-afternoon assembly job. It's the default state of the record.
Agency-native software starts here: the unit of work is a versioned artifact with a client relationship attached, not a task. The views, the integrations, the automation all follow. You can get close by gluing seven tools together and writing a runbook for keeping them in sync. Or you use software where this is the default.
When ClickUp is still right
If your studio runs significant internal-only work — ops, content production, recruiting, internal R&D — and that's what you want software for, ClickUp is good. It's also fine as a companion tracker for non-client work, even when client work lives elsewhere.
For most studios past the second hire, the client-layer answer is no.
A soft pointer
We built Oase as the agency-native version of the chassis above. We're biased about this. If the five breaks here sound like the week you just had, that's the surface you'd be replacing.