Drift-triggered client outreach for RIAs
Know who to call today.
Eclipse tells you a portfolio is out of tolerance. It does not tell your advisor what to do about it, and it does not write to the client. Trueband does that part, and only that part.
See the demoRead the security brief
The demo needs no signup and runs on fictional households. Nothing on this site sends an email.
- Priya Vantablack IRA+20.0pp StocksNeeds client approval first
- Marlowe Ashgrove Family Trust+15.0pp StocksRebalance, then tell them
- Thaddeus Windlemere Trustno numberNo discretion flag on file
- Rowan Fairweather Retirement+1.0pp StocksInside its band
The problem
Drift is quiet, and that is the whole problem.
By the time a 60/40 household is sitting at 75/25, nothing has alarmed anyone. Eclipse flags it. The flag joins six hundred other flags. The advisor who should pick up the phone has no way to tell which of their households moved this week and which have been sitting there since March.
The part that stings is not the trade. It is the client who read their own statement first and asked why nobody called. You cannot win that conversation afterwards, and every advisor in your firm has had it.
A client should hear from their advisor when their money moves, not at the next quarterly review.
Why listen to us
There is no AI in this product.
Drift is arithmetic. Your target allocation minus your current allocation, measured against the tolerance band you already set in Eclipse. The client email is a template your advisor edits before anything leaves the building.
We could have put a model in the middle of that and charged more for it. You would then spend a year explaining it to your CCO, and the answer at the end would still be a number you could have computed exactly.
This started as one firm's internal tool. Every awkward corner of the Orion and Eclipse APIs is handled in here because we hit it first, with a real book and a real advisor waiting on the answer.
The plan
Three steps, and one of them is a morning habit.
1
Connect Orion once
Onboarding tests your credentials against Orion core, the Eclipse token exchange and an Eclipse model read, then tells you which of the three you are stuck on. Most firms get stuck on the same one, and the screen hands you the support request to send.
2
Open one list each morning
Overnight, Trueband works out which households moved outside their bands and by how much. Worst breach sits at the top. Anything it cannot review, because a model is missing or a fund will not classify, sits in its own tab with the reason written out.
3
Record thirty seconds and send
The email is already written from that household's own numbers. Your advisor edits it, records a short explanation from their webcam, and clicks once. An unsent draft appears in their own Outlook with the video linked.
What it replaces
The spreadsheet somebody rebuilds every quarter.
Right now the answer to who needs a call lives in an export, a filter, and somebody's memory of which clients get touchy. That holds until the person holding it takes a holiday, or until the book grows past what one person can carry.
With this running, every advisor opens the same list at 9:15 and knows their five calls, each one with a draft already waiting on it.
The boundaries
Four things it will never do.
- It does not trade. Trueband reads Orion and Eclipse. It never places an order.
- It does not send. The draft sits unsent in your advisor's own mailbox until they read it and press send.
- It does not guess. Where the data will not support an answer you get a flag and the reason, not a number.
- It does not write to your book. Nothing Trueband holds is pushed back into Orion or Eclipse.
Before you get excited
What connecting actually involves.
Being straight about this up front saves everyone a bad week. Orion issues the Partner ID your firm needs through a support case rather than a settings page, and the Eclipse token exchange usually fails the first time until Orion associates your user with your Eclipse firm on their side. When we did it, that took several days of back and forth.
Onboarding tests all three tiers live and shows you exactly where you stand. If Eclipse comes back with the firm association error, the screen hands you the support request to send Orion, worded for them.
Drafting into your advisors' mailboxes needs a second approval, this time from your Microsoft 365 admin. Two consent flows, not one.
Who it is for
RIAs on Orion with Eclipse.
Specifically, firms where a portfolio moving is supposed to produce a phone call, and nobody has the time to work out whose. That is the whole qualifying test, and it pays for itself in the first month at a firm that passes it.
If you rebalance on a calendar and do not write to clients about it, this will not earn its keep, and we would rather you found that out here than three months into a contract.
See it on fictional households first.
No signup, no call, nothing sends. It runs on fictional households and the buttons in it do not reach a mailbox. Questions it does not answer go to a@ashkaan.me.