How Agencies Manage Client Projects

Agency project management fails in a predictable way. The work for Client A and Client B sits on one board, a client is invited “to make updates easier,” and the hours live in a sheet the producers do not open. The fix is delivery structure: one project per client engagement, access that stops at that work, and time recorded on the tasks. It is not a ranking of agency platforms, and it is not an invoicing guide.

Estimates you send as quotes, invoices, retainers, and margin are a finance problem. This article does not cover them. A project tool can hold the work and the hours. Turning those hours into a bill happens somewhere else. If a product tour leads with profit dashboards, you are looking at a different category than the one described here.

One project per engagement

Give each client job its own project. The spring campaign and the autumn campaign can be two projects for the same client if they have different tasks, dates, and people. What you should not do is keep every client as a column on one internal board. Columns are statuses. Clients are not statuses.

A project gives you:

• A task list that does not mix two brands.
• Statuses that match that job.
• A place to attach the people who should see it.
• A channel for that project, if the conversation should stay next to the tasks.

A workspace can hold many of those projects when the same producers share them and there is no harm in those producers seeing the project names. When a freelancer or a client must not even see that another client exists, use a separate workspace. The organization can still be the same company. The workspace is the wall.

Do not link a task in one client’s workspace to a task in another. Cross-workspace links are not available. If work truly blocks across that wall, the tasks are in the wrong boundary, or the handoff stays in writing.

What the client is allowed to see

Unrestricted access is how internal comments and other clients’ names leak. Invite the client as a member on a role that cannot browse the workspace, then share the one project, or only a section or task, at view, comment, or edit.

View is the default for a buyer who wants status. Comment is for feedback on that item. Edit is for the rare person who should change tasks. Most clients should not edit dates.

This is not a client portal. There is no separate branded site and no link that works without a membership. Tell the client they are joining the project, not opening a portal. Read every task you share and remove internal cost notes first.

Keep the internal conversation in a channel the client is not in, or on tasks you did not share. A project channel is for the people on that project. A section channel is narrower. A custom channel with a chosen member list is for the producers’ side comments. None of those are a direct-message product. Do not promise private chat threads the tool does not have. Promise the channel you actually created and the membership on it.

Time on the tasks, not a second spreadsheet

Producers remember hours badly on Friday. The record that survives is a timer started on the task, or a manual entry added the same day. The entry is who, which task, and when. It is not an invoice line.

Use it for delivery questions: this round of designs took five hours; the revision took one. If you later bill, you can read those entries. The project tool is not doing the billing. Do not show a client a currency field and call it the fee. A currency field is a custom value. It does not calculate a rate or send a bill.

Attendance is a different record again. Whether a producer was on shift is an HR question. It does not split the day across Client A and Client B. Do not ask payroll’s punch report to explain a client’s hours.

Look at load before you say yes

Before you accept another job, look at who already has tasks due. A workload view that counts tasks due per person on each day of this month will show a designer with marks on most days and a writer with one. That is a reason to look at those tasks before you promise a new brand guide on Thursday. It is not a measure of hours, and it is not a margin forecast. Open the tasks. A day with four small reviews is not the same as a day with one campaign build.

If the view only includes one project, it will not show the other clients. Check the scope. Agency overload is usually cross-project. A single project’s board will look calm while the person is drowning on three others.

What to say in the proposal

Write the delivery scope in the same words you will configure.

“You will have comment access on your project” is accurate. “You will have a client portal” is not, if the setup is a membership and a share. “We will track hours on the tasks” is accurate. “The project tool will invoice you” is not. “We will watch workload” is accurate only if you mean who has tasks due, not a promise of a utilization percentage or a margin number.

Put those sentences next to the fee. The fee still comes from your finance process. The project system is how you will show status, collect feedback, and remember the hours. Clients accept a narrower promise more easily than they accept a portal that never appears.

When a producer joins mid-project, the same sentences are the tour. Here is the project. Here is the channel the client is not in. Here is where time goes. Here is the view of dues for this month, and it is not the invoice.

A week that stays coherent

1. Open or create the project for that client job. Do not add their tasks to a shared “all clients” board.
2. Add the internal team with roles that match the work. Producers edit. Leadership can view more broadly if their role says so.
3. Invite the client on a limited role and share only their project, at view or comment.
4. Put client-visible notes on shared tasks. Put staffing notes somewhere they cannot open.
5. Log time on the task the day it happens.
6. Before the next proposal, check who already has dues this month.

That sequence does not produce a profit and loss. It produces a project a new producer can open on Monday and understand.

How this works in Dayzen

Dayzen’s Project Management System can hold a project per client job, with tasks, statuses, and channels scoped to the project or a section. A client can be a workspace member on a low-privilege role, with a view, comment, or edit share on one project, section, or task. There is no client portal and no invoicing.

Time on a task is a timer or a manual entry. The workload view shows how many of a person’s tasks are due on each day of the current month. It does not show fees or utilization percentages. HR attendance, if you use Dayzen’s HRMS as well, stays a separate record under the same login. Use the project for delivery. Use a finance tool for the bill.