Your CRM stores what happened at settlement. It does not tell you which client to call today, which loan is about to runoff, or whether your trail is being paid correctly. That gap is where commission leaks.
Trail commission is the closest thing a broker has to recurring revenue. It is also the part of the income statement that receives the least scrutiny, because it arrives as a statement line rather than an invoice. The result is predictable: loans drop off, balances are reported incorrectly, and clients refinance away without anyone noticing until the trail simply stops.
The CRM problem is not a feature problem
A mortgage broker CRM is designed to be a system of record. It holds the contact, the settlement date, the lender and the rate at the time the loan was written. What it does not do is watch the live book and act on what it sees. It is a static snapshot, not a dynamic monitoring layer.
- It stores the rate at settlement, not whether that rate is still competitive today
- It records the maturity date, but does not rank clients by which conversation matters most this week
- It holds contact history, but does not prompt outreach at the exact moment a borrower is most likely to leave
- It captures the loan file, but does not reconcile whether trail is actually being paid on every loan
None of this means the CRM is wrong. It means the CRM is doing a different job. The gap between record-keeping and revenue protection is where trail commission leaks.
Where trail actually goes missing
- Settled loans that never appear on a trail statement at all
- Balances reported at an old figure, so trail is calculated on the wrong base
- Split loans where only one tranche is being paid
- Loans transferred internally by the lender and reattributed away from the broker
- Redraw and offset treatment applied inconsistently between lenders
- Rate tier changes that quietly move the loan to a lower trail rate
Individually these are small. Across a book of several hundred settled loans, a one to two per cent error rate is a meaningful annual number — and it compounds, because an unnoticed omission keeps not being paid every month for years.
Why attrition is harder to spot than underpayment
A missing payment line is at least visible on a statement. A client about to refinance is not. The warning signs are in live data: a rate gap against current pricing, a fixed term inside ninety days of expiry, equity growth that changes the borrower's options, or simply no contact for twelve months. A CRM stores each data point, but it does not connect them into a risk score.
"Retention is not a campaign. It is being the first person to raise the thing the client was about to Google."
The fix is a dynamic layer, not a CRM replacement
Replacing the CRM is expensive, disruptive and unnecessary. The better pattern is to supplement it: a layer that reads the settled book continuously, compares each loan against live market pricing and expiry triggers, and produces a short, ranked list of clients to contact this week — with the reason attached.
- It works on the book you already have, not a future migration
- It prioritises by revenue at risk, so the highest-value conversations happen first
- It drives regular, targeted engagement without generic email blasts
- It generates the compliance record as a by-product of the outreach
That is the difference between static data and dynamic book management. The CRM keeps the file. The monitoring layer tells you what to do with it.
What Kayotte does
Kayotte sits alongside your existing CRM and aggregator. It monitors your settled book for trail underpayments, repricing opportunities, expiry triggers and refinance risk, then returns a prioritised contact list with the rationale already attached. No data migration, no replacement of systems, no change to the way you originate new loans.
Commission structures vary by lender and aggregator agreement. This article is general information, not financial advice.