Ad agency project management tool: how to choose one for multi-channel campaigns

An ad agency project management tool has to hold three kinds of work at once: creative production, media placement, and client approval. General task managers cover the first and ignore the other two. Media buying platforms cover the second and ignore the first. The real question is which gaps you can close with a convention you write once, and which gaps will cost you a launch date.

Most ad agencies that ask this question already own a board tool and are losing time at the seams: briefs arriving in email, final assets reaching media buyers as a Drive link with no spec, and client approval living in a comment thread nobody can point at. This guide works through the campaign as a unit of work, compares the three shapes of tool you'll be evaluating, and ends with a test you can run on one real brief.

What one campaign actually contains

Vendors sell you a board. Your campaign is a set of objects spread across departments. Count them before you evaluate anything.

Worked example. An 11-person agency runs one spring campaign for Northwind Outdoors. Assumptions: one quarter, three channels, one creative director, two editors, one media buyer, two client approvers (a brand manager and a performance lead). The campaign contains:

• 1 client-facing brief, approved once with a change recorded
• 9 creative deliverables: 3 video cuts, 4 statics, 2 landing-page sections
• 6 media placements across paid social, YouTube pre-roll and display
• 2 client approvers, approving different subsets of the 9 deliverables
• 1 delivery deadline per channel, not one per campaign

That is roughly 15 trackable objects and 15 delivery dates spread over 10 weeks. If your tool shows one card called "Northwind Spring Campaign," you have a task manager, not a campaign system. The three places this hurts: brief intake (who approved which version), the creative-to-media handoff (which file is final), and approval (which reviewer cleared which asset).

Campaign tracking vs task management vs both

You are choosing between three tool shapes, and each has a predictable failure mode. This is the comparison worth running first, because it eliminates options faster than a feature checklist.

The honest tradeoff: no single tool does both creative production and media buying well. If your agency runs two campaigns a quarter with one channel each, a general board plus a strict naming convention is genuinely enough, and the switch will cost you more in admin than it saves. The case for a production workspace gets stronger when campaigns are multi-channel, editors and clients both need to see work, and you're paying reviewers for seats they use twice a month.

For the broader agency comparison, project management software for creative agencies covers the category. The creative agency workflow from brief to delivery is the process side of the same problem.

The routing convention for creative-to-media handoff

Most missed launch dates are handoff failures, not production failures. The asset exists; the media buyer got a link to the wrong cut, or a file in the wrong aspect ratio, three days late.

Fix it with one rule: one card per deliverable, not per campaign. Nine deliverables means nine cards on the campaign board, each carrying the same handoff fields:

• The final approved version, attached to the card (not linked from someone's desktop)
• Spec: aspect ratio, duration, character count, file format
• The placement IDs it feeds, listed on the card
• Approval state and who cleared it
• Channel deadline, so the delivery date isn't hidden in a campaign-level note
• The named media buyer who is responsible for taking it live

Two details make this survive contact with reality. First, when a file is attached to a card it lands in the workspace Drive, so the same file can be reorganized in folders later without breaking the card link. Second, version history means uploading a new cut to the same file keeps the earlier one, and reviewers can switch between versions — which is what lets you answer "approved against which cut?" months later. That mechanism is described in Review and, in workflow terms, in how to use Review.

A comment saying "this one looks good, use it" is not a spec. Media buyers need the four numbers, and they need them on the card, not in chat.

Client approval chains across mixed campaign assets

A campaign has more than one approval chain, and they don't all move at the same speed. The brand manager signs off on copy and creative; the performance lead often reviews statics and landing pages separately; legal occasionally appears for claims.

Two design decisions matter more than any feature:

1. Where approval state lives. One place, per asset. If the state is "brand manager replied-all on Tuesday," you cannot report on it and you cannot onboard a second reviewer into it.
2. Sequential vs parallel routing. Run reviewers in parallel when their notes are independent (statics and video). Run them sequentially when one person's change invalidates the other's review — landing-page copy before landing-page design, for example.

For video cuts and PDF documents, timestamped comments and @mentions on the attached file beat a numbered email list, because the note is anchored to the exact frame or page rather than to a description of it. The role and routing design is covered in detail in content approval workflow roles and routing.

One caution worth writing into your process: an approval that arrived by email is not a recorded approval. If a client replies "fine, ship it" two days before launch, paste that into the asset's card or ask for it in the review, or the next campaign starts with two people believing different things about what was cleared.

Questions to ask about client seats and multi-stakeholder access

Seat models are where ad agency evaluations quietly go wrong, because a campaign can add four client-side reviewers who each log in twice a month. Ask these before you shortlist, and verify the answers in a trial rather than in a sales call.

• Does a client reviewer count as a billable seat? In kloudboard, guests are free and do not count as paid seats; owners and members count toward the billable seat calculation. A roster alone doesn't prove an invoice is correct — invoice adjustments and historic seat changes also matter. For the arithmetic, see free client seats vs paid user seats and the current pricing page.
• Can a client see only the assets they're reviewing? Card visibility is enforced server-side. A guest without the "view all cards" permission sees only the cards they are assigned to, and an unassigned card is invisible to them. That's how you keep an internal cut out of a client's view. The setup is described in giving clients access without exposing internal work.
• Can a board be restricted to a named list of people? Yes — per-board access is separate from per-member permissions.
• Which integrations exist? Social accounts (YouTube, TikTok, Instagram, X) for analytics and imports, board imports from common PM tools, and Google Calendar. There is no general public REST API; the supported programmatic surface is the remote MCP server for AI tools. If your agency has an internal dashboard, plan around that limit.
• What is not included? There is no external chat bridge (Slack, Discord, WhatsApp, Telegram syncing) and no in-app audio or video calls. Assume your media buyers and clients keep their own comms channels.

Run one real campaign brief through the tool in 45 minutes

Feature lists don't predict anything. A single test with real work does, and you'll know more after 45 minutes than after three demos. Use your last completed campaign — a real brief, a real cut, a real client reviewer — and treat this as a dress rehearsal you then delete.

45-minute campaign brief test

Run one real campaign through a candidate tool to find which steps need a manual workaround before you commit.

The result to watch for is not "did every step pass." It's which steps needed a workaround. If you had to describe the handoff spec in a chat message because the card had nowhere to put it, that's the gap you'll be patching by hand every campaign.

What to do next: run the test on two candidates, score them on the three failure points from earlier — brief version, final asset handoff, approval state — and pick the tool where those three live in the system rather than in your team's memory. If two candidates tie on workflow, choose the one that charges less for the reviewers who log in twice a month. And if your campaigns are single-channel and infrequent, the honest answer may be that your current board plus a written convention is still the cheaper system.