How an Agency Organizes 20 Clients at Once Without Losing Its Mind

With five clients, an agency can get by on memory and a WhatsApp group. With twenty, memory fails: someone forgets a post, an approval gets lost in a chat, the hours spent on a campaign are never logged, and on Friday nobody knows what was delivered. The answer isn't more individual discipline. It's a structure that makes the right way also the easiest way.

The structure below rests on four ideas: one project per client with workstreams inside it, routines that repeat on their own, approval in a single place, and requests and hours recorded at the source. It works for a marketing agency and, with adjustments, for studios, production companies, and consultancies.

One project per client, workstreams by type of work

The first decision is how to separate the work. The rule that scales best: each client is a project, and inside it the work is grouped into workstreams (a workstream is a grouping inside the project).

Why one project per client? Because everything that belongs to the client stays together: tasks, documents, conversations, hours, approvals. When someone takes over the account, they open one place. When the client asks "how are we doing?", there's an answer.

Client (project)	Workstreams	Example tasks
Clínica Sorriso	Social media, Paid campaigns, Website, Reports	November post calendar; Adjust the bid on the implants campaign; Update the treatments page
Loja Aurora	Social media, Email marketing, Seasonal dates	Mother's Day artwork; Abandoned cart flow; Black Friday campaign
Construtora Vale Verde	Development launch, Social media, Printed material	Sales booth schedule; Launch ads; Model apartment brochure

The names above are fictional, for illustration. What repeats is the pattern: workstreams follow the type of service you sell, and almost always the same ones serve several clients. That lets you create a project template and copy it for each new client.

What to avoid

• One project per type of service, with all clients inside. Mixing clients makes it impossible to see what belongs to whom and gets in the way of closing out hours.
• Too many workstreams. Four or five per client are enough. Beyond that, nobody remembers the difference.
• A project with no owner. Each client needs someone in charge of the account. Without one, everyone assumes someone else is taking care of it.

Routines that repeat on their own

A large part of agency work is recurring: the monthly calendar, the results report, the campaign review, the alignment meeting. If someone has to remember to create those tasks, one of them will be forgotten in some month.

The way forward is to turn them into recurring tasks or automations that create the work at the right pace. Automations fire on triggers (date, status change, new task) and run actions, and they exist on every plan, with a monthly execution limit that varies by plan.

Routines worth automating

• Start of the month: create, for each client, the tasks for planning the calendar and collecting materials.
• Weekly: a task to review campaign performance, assigned to the account owner.
• End of the month: a results report task, due before the meeting with the client.
• Status change: when a post moves to "client approval," notify the owner and set the response deadline.

Before turning an automation on for real, it's worth simulating what it would have done over the last 30 days, and checking the history afterward. It's better to catch a rule that duplicates tasks early than to find out with twenty clients.

Client approval in one place

Approval is where an agency loses the most work. The artwork goes out by email, the client replies on WhatsApp, someone comments over a phone call, and three people have three versions of what was approved.

The remedy is a single place where the client sees what needs a decision, comments, and approves. In the client portal, the client follows the project, comments, and approves, and doesn't take up a seat on the account (they're a guest). That way, you don't pay for a seat for every contact at every client.

Rules that make approval work

1. Set a response deadline. Two business days, for example. Without one, approval stalls delivery and the agency takes the blame.
2. Define who approves. One name per client. When the business owner and the marketing manager weigh in at the same time, the artwork comes back four times.
3. Limit the rounds. Two rounds of revisions included, any further ones as additional scope agreed in the contract.
4. Record the sign-off. The date, the approved version, and who approved it are kept, so the "but I never asked for that" conversation ends in seconds.

WhatsApp requests become tickets

Every client thinks the agency is one person on WhatsApp. "Change the time of that post," "I need a banner today," "the website is down." Without a filter, these requests become the team's real agenda, run over the plan, and go unrecorded.

The solution is to give each request a destination: the conversation becomes a ticket or a task in the client's project, with a priority and a due date, and the person handling it doesn't have to remember anything. For requests that come in often, a request form asks for what the team needs (which piece, by when, where it will be used) and creates the task in the right project.

This changes the conversation with the client. Instead of "I'll see if it's possible," the agency answers with a deadline and a place in the queue, and urgent stops meaning everything. A request that cuts the line becomes a visible decision: what gets pushed back so this can go in?

Hours to bill

An agency that charges by retainer, by scope, or by the hour needs to know how much work each client consumes. Without time tracking, a retainer that looked profitable may be costing more than it earns, and nobody finds out until the end of the year.

Log hours on the task itself, when they happen. In Tasskee, hours can carry a rate per project and per type of work, and the client statement comes out as a PDF or CSV, with the invoice recorded (Tasskee doesn't issue the invoice). People paid by the hour, such as freelancers, get their own statement. The article how to bill by the hour without a spreadsheet details the method.

What time tracking shows

Question	How hours answer it
Is the client consuming more than they pay for?	Hours logged per project against the contract value
Which type of work takes the most time?	Hours per workstream or type
Is the team overloaded?	Hours per person in the period
Is it worth adjusting the contract?	A series of months, to tell a spike from a trend

The weekly routine that holds it all together

The structure only works with a short cadence. For twenty clients, the essentials fit into four moments.

• Monday, 15 minutes: each account owner shows what's due this week and what depends on the client.
• Daily, individual: each person looks at the day's tasks and adjusts what's late.
• Friday: review of open tickets and pending approvals, chasing the client when needed.
• End of the month: closing out hours, results report, and meeting with the client.

How to go from 5 to 20 without bringing the house down

1. Build a template project with the standard workstreams and the recurring tasks.
2. Migrate one client at a time, starting with the most organized one. Adjust the template before moving on.
3. Move approvals to the portal for new clients first; existing ones move over when the timing is right.
4. Turn on automations gradually, simulating first.
5. Start logging hours the same day the client enters the system, so you don't have to rebuild history later.

The goal isn't to control the team, but to take out of people's heads what the system can remember. As an agency grows, the first thing lost is whatever nobody recorded. Record the essentials in the right place, and growth stops being a shock.