A cancellation email that was months in the making
The notice arrives on a Tuesday: an agency with five branches will not renew. The reason given is budget. When your team looks back, the signs were all there. Two branches had barely logged in since the spring. The lettings manager who championed you left in the summer. Support tickets from the agency had stopped, which everyone took as good news. The last invoice was paid late for the first time.
None of this was hidden. It was spread across your product database, your help desk and your billing system, and nobody was looking at all three together.
Why agency churn arrives without warning
Agencies rarely complain before they leave. They are busy, and changing software feels like a problem for later, until a renewal date forces the decision. Several things common in the property sector make drift hard to see.
- Usage is looked at per agency, not per branch, so one strong branch hides three weak ones.
- Champions move between agencies often, and nobody notices their account going quiet.
- Agencies are bought and merged, and the new owner has its own preferred software.
- Negotiators go back to the CRM or a spreadsheet for tasks your product does, and your data only shows less activity, not why.
- Customer success works from a list of renewal dates, not from how customers are actually using the product.
What quiet churn costs
Losing an agency you could have saved is the most expensive churn there is, because the fix was often simple: retraining a branch, introducing a new champion, or showing the new owner what the product does. Each lost agency also takes local reputation with it, and in property, agencies in the same town watch what each other use.
It also distorts your view of the business. Revenue looks steady until renewals land, and then several leave in one month and the forecast changes overnight.
How we build early warning for agency churn
What we build combines signals you already have into a single view of each agency's health, down to branch level.
- Activity measures per branch that match what the product is for: listings managed, viewings booked, tenancies progressed, reports opened, compared with that branch's own normal level.
- People signals: the champion or admin not logging in, admins leaving, new users not being added when staff change.
- Support signals: tickets stopping suddenly, or a rise in frustrated ones.
- Billing signals from Stripe or your billing tool: late payments, downgrades, removed users or branches.
- External signals where available, such as news of an acquisition or a branch closure, added by your team or from a data source you choose.
- A health score per agency and branch, with the reasons shown, and alerts to customer success when a score falls or a key signal fires.
| Signal | Example | Suggested action |
|---|---|---|
| Branch activity drop | One branch well below its normal use | Call branch manager, offer refresher |
| Champion inactive | Admin not logged in for weeks | Find out if they left, find a new contact |
| Support silence | Tickets stopped after steady flow | Check in, look at usage |
| Billing change | Late payment or branches removed | Account review with directors |
| Ownership change | Agency bought by a group | Early conversation with the new owner |
The score is a prompt for a conversation, not a verdict. The reasons behind it matter more than the number, so they are always shown alongside it.
A Tuesday alert instead of a Tuesday cancellation
In the summer, your customer success person gets an alert: the agency's admin has not logged in for three weeks and two branches have dropped well below their normal activity. A call reveals the lettings manager left and nobody took over. Your team runs a short session with the branch managers, sets up a new admin and fixes a setup issue that had pushed one branch back to its spreadsheet. By renewal, the conversation is about adding a branch, not leaving.
Could an agency be drifting right now?
- You look at usage by agency, not by branch.
- Your team finds out a champion left when a renewal is at risk.
- Support, billing and product data are never viewed together.
- Cancellations often surprise the customer success team.
- You do not track which agencies have been bought or merged.