Most teams find out an account is in trouble the same way: the client says so. By then the relationship has already absorbed weeks of quiet friction, a missed deliverable, an invoice that sat too long, a message that went unanswered for three days. There is a cheaper way to find out, and it takes thirty minutes a week.
Why nobody schedules this on purpose
Account health tends to live in someone’s head. The account lead knows which clients are happy and which are drifting, but that knowledge rarely gets written down or shared, because there is no meeting whose entire job is to surface it. Status meetings cover deliverables. Sales meetings cover pipeline. Nobody owns the question “how is this relationship actually doing,” so it gets answered reactively, usually by the client, usually in a tone nobody wants to hear.
The teams that avoid this run a short recurring review across every open account, separate from project status, separate from sales. It is not a status update. It is a diagnostic, and it produces a different kind of output: a list of accounts that need attention this week, ranked by risk, before risk turns into churn or scope creep.
What the review is not
It helps to be precise about the boundaries, because this meeting gets absorbed into other meetings if you let it.
- Not a project status check. Deliverables, timelines and blockers belong in the project stand-up. This review only asks whether the relationship is healthy, not whether the work is on schedule.
- Not a sales pipeline review. New business and renewals belong somewhere else. This is about accounts you already have, including the ones with no active project this month.
- Not a venting session. The goal is a short list of named actions, not a general discussion of which clients are difficult.
The five signals worth tracking
Five inputs cover most of what account health actually looks like. None of them require a new tool, just a habit of checking the same things at the same time every week.
| Signal | What it tells you | Where to look |
|---|---|---|
| Response time | A client who used to reply same-day and now takes four is disengaging or frustrated | Email or message thread timestamps |
| Invoice age | Late payment is often the first honest signal something is wrong, before anyone says a word | Accounts receivable or invoicing tool |
| Scope drift | Requests outside the original agreement, unbilled, are quietly eroding your margin and their expectations | Project notes or change log |
| Meeting cadence | A client who cancels or reschedules the standing call twice in a row is telling you something | Calendar history |
| Last touch that wasn't work | If every conversation in the last month was about a deliverable, nobody is checking on the relationship itself | CRM or notes |
Running the thirty-minute version
This works with two people or twelve. The format stays the same regardless of team size, and the discipline is in keeping it short.
- Pull the account list Every active account, plus any paused or dormant one still under contract or expecting to renew. Not just the ones on your mind.
- Color code before the meeting Green, yellow, red, assigned by whoever owns the relationship. This is a five-minute prep task, not a group exercise.
- Spend the meeting only on yellow and red Green accounts get a nod and nothing else. The whole point is to protect attention for the accounts that need it.
- Name one action per flagged account A call, a check-in email, an internal conversation about scope. Vague concern without a next step is wasted time.
- Assign an owner and a date Not “soon.” A day. Untracked follow-ups from this meeting are worse than not having the meeting at all.
We used to find out an account was unhappy from the cancellation email. Now we find out three weeks earlier, from the fact that they stopped replying to the Tuesday check-in.
Operations lead at a 14-person creative agency
The scope creep case, in detail
Scope drift deserves its own attention because it is the signal teams most often miss, and the one that costs the most. A client asks for one small extra thing. It gets done, because saying no over a small thing feels petty. Three months later there have been eleven small things, none billed, and the account that looked profitable on paper is losing money in practice.
The fix is not a stricter contract. It is a habit of logging every out-of-scope request the week it happens, even the ones you decide to absorb for free. Reviewed monthly, that log tells you two things: which clients are consistently asking for more than they are paying for, and which of your own team members are saying yes without checking. Both are fixable once they are visible. Neither is fixable while they live only in someone’s memory.
Where the record needs to live
None of this works if the health signals live in five different places: invoices in one tool, messages in another, notes in a shared doc nobody opens. The weekly review turns into an archaeology exercise instead of a thirty-minute habit, and it stops happening within a month. Whatever system holds your client or member records needs to be the same one that holds the notes from this review, so a color code from six weeks ago is one click from the current invoice status and the last message thread. Studio’s client workspace keeps that history attached to the account rather than scattered across inboxes, which is the only reason a review like this survives past the second month.
What to do with a red account once you find one
Flagging risk is only useful if the next step is specific. A red account almost always falls into one of three buckets, and each one has a different fix.
- Communication has gone quiet. Send a direct, low-stakes check-in that is not tied to an invoice or a deliverable. Ask how things are going, not whether they’re happy with the last milestone.
- Scope has drifted past what they’re paying for. Have the internal conversation before the client one. Decide whether to absorb it, bill for it, or renegotiate, then bring a proposal rather than a complaint.
- The relationship has an unresolved friction point. Usually from a missed deadline or a misunderstanding weeks back that nobody addressed directly. Name it out loud rather than hoping it fades.
Key takeaways
- Account health needs its own meeting. Folded into status or sales reviews, it never gets a real slot and gets skipped first when the week is busy.
- Five cheap signals catch most risk early. Response time, invoice age, scope drift, meeting cadence and non-work contact, tracked weekly, surface problems before the client raises them.
- Unbilled scope creep is the costliest blind spot. A running log, reviewed monthly, turns a vague sense of overwork into specific numbers you can act on.
- The review only works if the record is centralized. Notes, invoices and messages scattered across tools kill the habit within weeks.
Common questions
How is this different from a client satisfaction survey?
Surveys ask the client directly and get filtered, polite answers. This review reads the behavioral signals, response time, payment speed, cadence, that show up before a client would ever put a complaint in writing.
What if we only have five accounts?
Run it anyway, just faster. Five accounts take about ten minutes to color code and review. The habit matters more than the scale.
Who should own this meeting?
Whoever has the most client-facing relationships, usually an account lead or operations manager, not the founder or the most senior person by default. Ownership should sit with someone who will actually protect the time slot.
Should the client ever know this review happens?
No need to announce it, but the actions that come out of it, a proactive check-in, a scope conversation, a faster response, are exactly the things a good client relationship should produce anyway.
