Alright, let's be real. Every tool in this space promises to be the visual workflow savior until you hit about 20 seats and realize you're paying for a glorified sticky note system that charges per head. My team's been through three in the last 18 months. The "budget" part is key here—most scale by punishing you for collaboration.
For a 30-person design team, you're not just tracking tasks. You need:
* Asset linking & review stages baked into the cards
* Client feedback loops without giving everyone an editor license
* Decent version history on attachments
* Granular permissions so interns aren't moving the "Launch" column
The usual suspects and where they fall apart at 30 users:
* **Trello:** Becomes a money pit. Power-Ups are a la carte and the per-user business class is $10/month. That's $300/month before you even add the essential integrations for proofing. The free plan is a non-starter with that many people.
* **Monday.com:** Their "visual" appeal is strong, but their pricing model is a classic bait-and-switch. To get timeline views and time tracking (which design teams need for sprints), you're forced into the Pro tier. That's $16/user/month minimum. Do the math: $480/month. And their automations are counted separately, so you burn through them.
* **ClickUp:** Feature-rich to the point of chaos. The "Unlimited" plan looks good on paper ($7/user), but the learning curve is steep. Designers just want to move cards and annotate images, not configure custom fields for two days. Stability can be iffy.
My current, somewhat reluctant, recommendation is **Plutio**. It's not perfect—the UI feels a bit 2018—but it's a flat project/month rate, not per-user. You can get 30 people in for about $50/month if you pay annually. It bundles invoicing and proposals too, which is overkill, but you can ignore that. The kanban is solid, it has built-in file proofing with comments, and client access is controlled.
Anyone else forced into a budget kanban for a midsize creative team? I'm already eyeing the next quarterly migration when Plutio inevitably removes a key feature.