Retainer use falls
Billed hours stay well below the agreed monthly amount across consecutive periods.
Agencies
The invoice still goes out, so the account looks fine. Meanwhile briefs slow down, unused hours pile up, and the next project lands somewhere else. ChurnRisk puts those changes on one client review.
Retainer and project revenue stay separate. Shared chat and project tools set the confidence limit.
How the work repeats
Agency revenue mixes a steady retainer with uneven projects. The client may reduce scope, bring a service in-house, or keep the retainer while another agency wins the campaign work.
Billed utilization can fade before the monthly fee changes. Fewer briefs, slower approvals, cancelled meetings, and a new marketing leader make that underuse worth a careful conversation.
Useful changes
The page keeps retainer value, use, project work, and client behavior distinct.
Billed hours stay well below the agreed monthly amount across consecutive periods.
The retainer continues while project revenue or one service line disappears.
Briefs arrive less often, feedback takes longer, and meetings keep moving.
A new marketing stakeholder appears, asks about notice periods, or never enters a thread with the agency team.
Warning examples
These examples use retainer, brief, and approval language from the agency pack.
The retainer covers 40 hours a month. The client used 11 in June and 8 in July.
The monthly retainer continues. Project revenue stopped after regular project work in the prior cycle.
Approval times lengthened across recent rounds. The new marketing leader has not appeared in a connected thread.
Illustrative warning copy. Figures and events are sample data from the industry pack.
False alarms
A quiet month needs the campaign plan and client calendar beside it.
A project can complete exactly as planned and should fall out of the next baseline.
A client's budget calendar can create a temporary project gap around year end.
Campaign volume may return in the same window each year instead of every month.
A product delay or internal change can stop a campaign without reflecting the agency relationship.
ChurnRisk does not turn unused hours into billing pressure. It waits for the existing contact to introduce a new stakeholder and blocks outreach during an active escalation.
Connector limits
Agency confidence stays low to medium while those systems sit outside the product.
QuickBooks can show retainer value, project revenue, service-line exit, and payment changes. Connected mailboxes can show briefs, approval delays, meeting changes, and contract questions.
ChurnRisk does not connect to shared Slack channels, Asana, Monday, Basecamp, or design review platforms today. A client can be active in those places while email looks empty.
Shared chat outside email caps confidence at 55%. Project management tools cap it at 60%, and design review platforms at 70%. The warning stays below those ceilings until the account owner checks the missing workspace.
Read the current connection boundaries for QuickBooks and Gmail or Outlook. The How It Works page explains how missing data becomes an unknown instead of a healthy reading.
Monday workflow
The conversation starts with value and context, not a utilization accusation.
Put the agreed hours, billed hours, service mix, and project revenue on the same client view.
Remove completed projects, planned pauses, and ordinary budget seasonality from the warning.
Look in the client channel, project board, and review tool before treating an empty inbox as disengagement.
Prepare a retainer-use conversation or pre-renewal review. The account owner edits and approves the message.
See the full product workflow, including evidence, confidence, and approval before any customer contact.
Related industries
For recurring agreements where project work can move to another partner.
For campaign work that repeats on a client's calendar.
Compare plans on Pricing, or use the demo to test one account with labeled sample data.
Start with your fee and project history, or bring one underused client to a walkthrough and test the blind spots together.
Shared chat, project boards, and design review tools are not connected. Their absence caps confidence.