How to organize 15 agency clients without mixing files or approvals
Illustrative scenario
A practical setup for separating clients, campaigns, permissions, calendars, and approvals inside a marketing agency.
This is not a customer case study and the results are not measured Polimake claims. It is an operating scenario for a small agency handling roughly 15 active clients and trying to stop coordinating every account differently.
The problem appears when one client uses Drive, another approves through email, a third sends material over WhatsApp, and the master calendar lives in a sheet understood by one person. The agency keeps delivering, but every new account adds more coordination than production.
Establish a boundary around each client
Create a separate space for each client and use the same base structure:
- 00_Brand: approved logos, fonts, guides, and templates.
- 01_Briefs: requests and received material.
- 02_Production: working files and work in progress.
- 03_Review: versions the client can review.
- 04_Approved: closed, publication-ready assets.
- 05_Results: reports and campaign learning.
Do not copy every asset into several folders. Use states and metadata to describe where work stands.
Match permissions to responsibility
A collaborator should not automatically see or download every client's material.
| Person | Access |
|---|---|
| Account lead | Full client workspace |
| Freelance designer | Brief, production, and required brand assets |
| Client reviewer | Review and approved versions |
| Sales team | Approved presentations and sales material |
| Departing collaborator | Access removed when the engagement closes |
Review access when people join or leave and when a sensitive campaign ends.
Use one workflow with limited exceptions
Begin with five states:
Brief received → In production → Internal review → Client review → Approved
Add a state only when responsibility changes. “Pending”, “almost ready”, and “review later” do not explain who should act.
A regulated account may need legal review. Most accounts do not. The common template reduces learning, while exceptions reflect real work.
Give one person ownership of approval
Imagine a campaign receiving comments from marketing, product, and leadership. The agency should not reconcile three contradictory lists.
Appoint one client owner. Others can comment, but this person provides a consolidated list and decides what blocks publication.
Record the version and date, review purpose, required and optional comments, approver, response deadline, and consequence of late feedback. The client communication guide explains the system in detail.
Keep a global calendar and client views
Agency leadership needs all accounts visible to spot overload. Each client should see only its own work.
Use the global view to review weekly deliveries, items waiting for clients, shared shoots and resources, people over capacity, and campaigns without an approved brief.
The client view can show campaign, channel, date, and state without exposing the rest of the agency.
Measure the first month honestly
Do not promise an invented 80% reduction. Establish a baseline:
- Minutes required to find an approved file.
- Days from first review to approval.
- Revision rounds per asset.
- Deliveries moved by late feedback.
- Unbilled coordination hours.
- Assets recreated because nobody found the original.
Compare after four weeks. If the system does not improve a specific metric or conversation, simplify it.
Roll it out in order
- Test with two clients rather than fifteen.
- Migrate active campaigns and current brand assets only.
- Define owners and states.
- Invite the client after testing permissions.
- Teach review and approval using one real asset.
- Review friction after the first cycle.
- Copy the corrected template to the remaining accounts.
Polimake can keep planning in Studio and files in Media. The tool does not replace these decisions. It makes the structure, access, and history visible so each new account does not require another improvised system.