task-ops
An eight person studio is delivering for eleven clients. Four are monthly retainers with no end date, five are fixed projects with dates, and two are signed but have not started. No single piece of that work is difficult. What is difficult is answering, on a Monday morning, which client is waiting on the studio and which is waiting on themselves, and whether the designer everyone wants next week has any week left to give.
That is the gap the phrase creative agency management software is usually trying to close. The trouble is that the phrase covers at least four different kinds of product, and the pages that rank for it tend to list all four side by side as if they were interchangeable. They are not. Buying a suite built for a forty person agency and using a tenth of it is a familiar and expensive mistake, and so is running a studio on a board that has no idea who is busy.
Sorting the category first is worth more than reading another list of twenty tools. Every product in this space is built to answer one of four questions well, and the others adequately at best.
| What it is built for | The question it answers | Where it strains for a small studio |
|---|---|---|
| Professional services automation | Is this client profitable, to the hour | Setup assumes billable rates, timesheets and a finance owner |
| Delivery and task management | What is the state of every job right now | Money and pipeline live somewhere else |
| Proofing and approval | Which version was approved, and by whom | Only covers the review step, not the schedule |
| Resource scheduling | Who has capacity in week 34 | Weak on the detail of the work itself |
The suites that dominate this search are mostly in the first group. They are built around the idea that time is money, literally: hours go in, rates convert them, and profitability per client comes out. That machinery is genuinely valuable for an agency billing by the hour against retainers it needs to defend. It also carries a cost that rarely appears in the comparison tables, which is that the numbers are only as good as the timesheets, and timesheets are the single hardest habit to establish in a creative team.
The honest test is this. If invoices are calculated from recorded hours, the first group is the right category and the setup effort is unavoidable. If invoices come from fixed project fees or flat monthly retainers, the first group is being bought for reporting rather than for billing, and delivery plus scheduling is the pair that matters.
Advice written for product teams assumes one team, one product, one backlog. Agency work breaks that assumption in four specific ways, and every structural decision follows from them.
People are shared and projects are not. A designer touches five clients in a week. Any view organised strictly by project hides the only number that matters when committing to a date, which is how much of that person's week is already spoken for.
Confidentiality runs between projects, not around the company. Client A must not see client B's work, and sometimes must not know client B exists. Product teams work the opposite way, where everything internal is visible internally.
Most of the elapsed time is waiting. Feedback rounds, legal sign off, assets that never arrive. Work blocked by the client is not work in progress, and a board that shows them in the same column reports a fiction.
Work ends, and then arrives again. Fixed projects empty out and close. Retainers never empty, and repeat the same six tasks every month. One structure has to hold both.
The structure that survives contact with eleven clients is one board per client. Not one board per project, which produces thirty boards and buries the small jobs. Not one board for the whole studio, which makes client access impossible.
The structure only works if the boards are identical in shape, which takes three conventions agreed once and then defended.
If one board reads Brief, In progress, Internal review, With client, Approved, Done, then every board reads that. Someone moving across four clients in a day should never have to work out what a column means on this particular board.
The two stages studios most often skip are the two that pay for themselves. Folding internal review into in progress hides quality problems until the client finds them. Folding With client into in progress makes the studio look slow for time it did not spend, and destroys the only evidence available when a deadline slips because approval took nine days.
A card called Homepage is useless three weeks later. Project, then deliverable, then round works: Website relaunch, home page, round 2. It takes no longer to type, and it makes search function, which matters more than it sounds at four hundred cards.
Every studio loses hours hunting for a brand guideline, a font licence or the name of the person who signs things off. A single pinned card at the top of each board holding those links removes that cost permanently. Credentials belong in a password manager, and the card points at the entry rather than holding it.
One more board is needed and is almost always missing: an internal board for pitches, the studio's own site, hiring and invoicing. That work consumes real capacity, and leaving it off the boards is how a planning conversation concludes that everyone has two free days they demonstrably do not have.
A board per client does not answer the capacity question by itself, and capacity is the question that causes the damage. The mechanism is to view the same cards grouped by person instead of by stage. Whether a tool offers that as a dedicated view, a saved cross board filter or a personal assigned list, the requirement is identical: one screen showing what each person has in flight everywhere.
Two habits make that screen honest. Every card has exactly one owner, because a card owned by two people is a card neither will start. Every card in progress carries a date, because without dates a person holding nine cards looks equally busy whether those nine land this week or across two months.
The most useful single number on that screen is not the card count. It is how many cards sit in With client, because that is the work that will land back on the studio without warning, and it appears in nobody's estimate of the coming week. A timeline view of the same cards shows the other half of the picture, which is where two clients' deadlines collide, ideally before they do. Whether a timeline is included or sits behind an upgrade varies widely between products and is worth checking on the features page of anything shortlisted.
Three models work. Mixing them by accident is what produces the awkward conversation.
Nothing. The board is internal, the client gets a weekly note and a call. Least work, least transparency, and for clients who do not want to be involved it is the correct answer.
A shared board. The client is a guest on their own board and sees all of it. Efficient, and it demands that no internal remark about budgets or difficult stakeholders ever lands in a card.
A split board. The internal board carries the working detail, and a simpler client board shows what is with them, what is coming and what is approved. Most control, most maintenance.
Two commercial details decide which of these is affordable. Whether permissions are set per board or per workspace, because per workspace permissions turn client access into an all or nothing decision. And whether view only guests are counted as paid seats, because eleven clients with two contacts each is twenty two people who will never create a card. Products differ on both, and the difference is visible on a pricing page in a way that feature lists are not.
A fixed project has an end and its board empties as it completes. A retainer never empties, and running one as a stream of one off cards fills the board with hundreds of identical completed items.
Two arrangements hold up. Either a recurring set of cards regenerated monthly, where the month is part of the card name, or one long lived card per recurring duty with a checklist reset each month. The first gives a clean history at the cost of volume. The second keeps the board small and loses the record.
Whichever is chosen, a retainer board needs one thing a project board does not: a visible count of what has been consumed against what was sold. Fifteen days a month sold, and no shared view of how many have gone, is the mechanism by which retainers quietly lose money. The count does not have to be sophisticated. A number in the board description, updated weekly by the person who runs the account, outperforms an unmaintained report.
Most studios do not need to buy the suite. They need to close one specific gap, and the order that keeps the team on board is to start with delivery, because that is the tool everyone touches daily and therefore the only one where adoption is real.
A workable sequence is delivery and capacity first, on one tool everybody opens. Then proofing, but only if versions and approvals are genuinely getting lost, since a dedicated markup tool adds a second place to check. Then the money layer, once the delivery board is trustworthy enough that hours recorded against it mean something. Doing the money layer first is the common order, and it is the order that produces beautiful reports built on invented numbers.
One practical point about moving. Studios already on a card based tool can usually carry boards across directly rather than rebuilding, and the import route is worth checking before any manual re entry is planned. The unglamorous part of the move is deciding what not to bring. Columns that no one has updated in three months should not survive the transition.
Add the two missing stages, Internal review and With client, to every board this week, and agree that one person owns each card. That alone will show where the time actually goes, and it costs nothing to test on the free tier of a tool where the pricing only moves when the team and the board count grow, as with Pinateca. Buy the profitability machinery later, once the board is honest enough to feed it.
No. Agency management suites are built around money, meaning billable hours, rates, budgets and profitability per client. Project management tools are built around the state of the work. A studio that bills fixed fees often needs the second and is sold the first.
One board per client holds up better for a small studio, with projects distinguished inside the card titles. A board per project produces two or three times as many boards as clients, which makes cross client capacity harder to see and buries the small recurring jobs.
Either keep the client off the board entirely and send a weekly summary, or run a split setup where a simpler client facing board shows only status. Sharing the working board is workable too, but only if internal remarks about budget and stakeholders never go into cards in the first place.
Per user pricing is the norm, and the range across this category is wide. Two details change the total more than the headline number: whether view only client guests are counted as paid seats, and whether timeline or reporting views sit behind a higher tier. Both should be confirmed on the vendor's own pricing page before shortlisting.