Small agencies rarely lose control dramatically. What happens is quieter: a client asks where something stands, and answering takes twenty minutes of asking two colleagues and searching a chat history. Nothing is on fire. But that twenty minutes recurs several times a week, and it is the same twenty minutes that turns into a missed deadline the one time nobody checks.
The underlying condition is that the state of the work exists in people rather than in a place. Everything below is about moving it out of people.
The four questions you have to answer instantly
This is a better diagnostic than any process audit. Take your largest client and try to answer these four without asking anybody.
| Question | If it takes more than a minute |
|---|---|
| What is open for this client right now? | Work is organised by project, not by client |
| Who is the single person responsible? | Ownership is implicit, which means it is shared, which means it is nobody's |
| What are we waiting on them for, and since when? | Blocked work has no state, so it is invisible until it is late |
| What have we done for them this month, and is it billed? | Delivery and billing are in different systems |
Most agencies fail two of the four, and it is usually the second and third. Those two are also the cheapest to fix, because they are conventions rather than software.
Organise around the client, not the project
Most agency setups are built around projects, because that is how the work is delivered. But it is not how the relationship works. A client is not one project — it is a retainer, two small jobs, an unanswered quote, three open support requests and a conversation about next quarter.
When the client is the organising unit, "what is happening with them" is one page. When the project is the unit, that answer requires assembling five places, and the fifth is a Slack thread. This is the single structural decision that determines whether the first question above is answerable.
One named owner, and it is not the founder
Every client needs exactly one person whose job it is to know the answer. Not a team, not "whoever picks it up" — one name, written down, that the client also knows.
This is the fix people resist because it feels bureaucratic in a team of four. It is precisely at four people that it starts mattering, because with four people a request can plausibly be somebody else's and therefore is nobody's. Shared responsibility for a client is the mechanism by which a client is neglected while everybody is busy.
- One owner per client, one owner per project. They can be the same person; they cannot be zero people.
- The owner is whoever answers the four questions, not whoever does the most work.
- Write down who covers each account when the owner is away, before they are away.
Make blocked work visible
In agency work, more delay comes from waiting than from working. Waiting on content, on approval, on access, on a decision from someone who has not read the email. And in almost every setup, that state is invisible: the task sits in the same list as active work, or it sits nowhere.
Give it a state that records who you are waiting on and since when. Two things follow. You can chase from a list instead of from memory — and, more usefully, you have a factual answer when a client asks why something slipped. "We have been waiting for the product photos since the 4th" is a different conversation from "it took longer than expected".
The status question, and what it costs you
Every agency has clients who ask for updates more often than the work produces them. The usual responses are a weekly status call or a written summary, and both are the same mistake in different clothing: they turn a data problem into recurring human work.
The cheaper fix is to make the state visible without you assembling it. Sometimes that is a shared board the client can see; sometimes it is a monthly report generated from the work rather than written about it. Either way the aim is the same: stop paying a person to answer a question the system already knows the answer to.
The twenty-minute pass over the client list
Once a week, go through the client list rather than the task list. It is a different pass and it catches different things — most importantly the quiet client nobody has touched in three weeks, who is the one most likely to leave.
- Any client with nothing open and no next conversation scheduled. That is not a calm account, it is a lapsed one.
- Anything on the waiting list older than a week. Chase it today rather than noting it.
- Any project whose owner has been away or is overloaded. Reassign now, not after something slips.
- Any delivered work not yet invoiced. This is the one with an immediate cash-flow effect, and it is the one that gets skipped.
- Any quote sent more than two weeks ago with no reply. A follow-up wins more work than a proposal rewrite.
Twenty minutes, once a week, run by the person who owns the client list. It is not a meeting — a meeting turns twenty minutes into two hours across four people, which is exactly the cost this is meant to remove.
When the answer is to let clients see for themselves
The buying guide covers what a client portal actually needs to do — which records the client can see, whether they can approve things rather than just read them, and whether client access costs a paid seat.