The CRM decision every advisor gets wrong
The debate is always Redtail versus Wealthbox versus the new AI systems. The real problem is what happens between reviews, and no migration fixes that. Ember works with the CRM you already run and does the client contact itself.
Switching CRMs is the most expensive way to change nothing
Every advisor knows the cycle. The current CRM feels stale, a new one promises a fresh start, and three months later the practice has spent a quarter migrating households, re-keying custodian data, retraining staff, and getting workflows re-approved. Then the first busy week arrives, the data entry slips, and the new system starts aging exactly the way the old one did.
The migration never fixes the thing that made you want to leave, because the thing that made you want to leave was never really the software. It was the quiet feeling that clients slip between reviews, that referrals go to whoever stayed in touch, and that the follow-up you meant to send after that good meeting never went out. A different database does not send it either.
A record of a relationship and the tending of a relationship are two different jobs. Advisor CRMs, old and new, do the first. Ember was built to do the second, on top of whatever does the first.
Touch cycles are why clients can tell
The standard answer to client contact is a touch system: a birthday letter, a quarterly newsletter, a check-in task that fires every ninety days. Practice management calls this discipline, and it is better than silence. But a client can feel the difference between a scheduled touch and a real one. The birthday letter with four signatories reads like what it is. The ninety-day check-in that opens with "just checking in" tells the client the calendar prompted it, because nothing else did.
A real touch references something true. The concern they raised on the last call. The college deadline they mentioned in passing. The question about the trust that never got a full answer. Those touches build the kind of trust that holds a household through a down market and brings in referrals. They are also precisely the touches no cadence engine can produce, because a cadence engine does not know what your client said.
Ember does know, because it reads the relationship: the email threads, the meetings, the notes. When it proposes reaching out, the reason comes from the client's world. When it drafts the message, the substance comes from what was actually discussed. You review it, adjust if you want, and approve.
Keep your CRM. Add Ember.
Ember connects to the inbox and calendar your practice already lives in, Gmail or Outlook, and works alongside whatever system of record you keep. There is no book migration, no staff retraining, and no weekend spent mapping custom fields. Advisors on Redtail, Wealthbox, or Salesforce keep them. Ember reads client context from Attio today to ground its drafts even deeper. HubSpot and Salesforce connections are in development.
This matters more than it sounds, because the inbox is the one system in an advisory practice that is always current. CRM notes trail reality whenever the week gets busy. The email record never does. By grounding itself in what was actually written and said, Ember stays accurate even when the CRM has not been touched since the last review season.
- Ember tracks the live state of every client and prospect relationship it manages: what was discussed, what was promised, whose turn it is.
- It surfaces the households going quiet before they become the review meeting where the client seems distant.
- It drafts each touch in your voice from the real history, and proposes the timing from context rather than a fixed cycle.
- You approve every message, and it sends from your own mailbox, threaded onto the real conversation.
- It keeps its own activity timeline of every touch, so you can see where each relationship stands without a data-entry session.
Side by side
| Dimension | Typical advisor CRM | Ember on top of it |
|---|---|---|
| Getting started | Migrate your book, retrain staff, re-map workflows | Connect your inbox; the record stays where it is |
| Between reviews | Clients hear from you when a task reminds you | Ember watches each relationship and prepares the touch |
| Client touches | Touch cycles: birthday letters, scheduled check-ins | A reason drawn from what the client actually said |
| Who writes it | You, from a template library | Drafted in your voice from the real history |
| Oversight | Depends on staff discipline | Every send waits for your approval, from your own mailbox |
| When the week fills up | Contact slips until the next review cycle | The work continues and queues for your sign-off |
Built for a practice where every send is supervised
Advisory work runs on oversight, and Ember was designed around a human approval loop from the first line of code. Every message it prepares waits in a queue until you sign off. By default nothing reaches a client without a person deciding it should. Because sends go through your own mailbox rather than a separate sending domain, the archiving and supervision tooling your firm already runs captures every message the same way it captures the ones you type yourself.
The approval queue turns out to be the part advisors like most. Reviewing three well-grounded drafts over morning coffee takes minutes. Writing those three messages from a blank page is the work that used to slip to next week. See how Ember works for the full loop, or the security page for how access and data scoping are handled.
Where this fits in your practice
Solo RIAs use Ember to keep a full book warm without an ops hire. Ensembles use it so a client who emails one advisor never gets dropped when that advisor is traveling, because the relationship state is shared. Growing practices point it at the prospect pipeline, where seminar attendees and referral introductions go cold fastest. In every case the shape is the same: the record stays where it is, and the follow-through stops depending on the busiest person in the building remembering.
Frequently asked
- Do I have to leave Redtail or Wealthbox to use Ember?
- No. Ember connects to your inbox and calendar, so it works alongside whatever CRM your practice runs. Your system of record stays exactly where it is. Ember handles the client contact your CRM was never going to do for you.
- Is Ember a CRM replacement for advisors?
- It can be for a solo advisor who wants one system, since Ember tracks the state of every relationship it manages. For most practices, though, Ember runs on top of the existing CRM. The record keeping stays put and Ember adds the layer that acts on it.
- How does Ember know my clients well enough to draft a real message?
- It reads the actual history: your email threads with each client, the meetings on your calendar, the notes you keep. Drafts reference what was genuinely said, so a follow-up after a review sounds like you wrote it, because everything in it came from your relationship.
- How does Ember fit a supervised, compliance-conscious practice?
- Every message Ember prepares waits in an approval queue until you sign off, and by default nothing sends without a human decision. Emails go out from your own mailbox rather than a separate sending domain, so the archiving and supervision tools your firm already runs see every message, the same as one you typed yourself.
- How is Ember different from the new AI advisor CRMs?
- Two ways. First, they are still CRMs, so adopting one means migrating your book, retraining your staff, and re-papering your workflows. Ember asks for none of that. Second, their follow-up runs on touch cycles: birthday letters and scheduled check-ins that fire on a calendar. Ember reasons from the relationship itself and reaches out when there is a real reason to.
- What if my CRM data is a mess?
- That is normal, and it is fine. Ember grounds itself in your inbox and calendar first, which are current even when the CRM is not. A practice whose CRM notes trail reality by weeks still gets accurate drafts, because the email record does not lie.
Keep reading
Your book deserves better than a birthday letter.
Keep the CRM you have. Ember reads every client relationship, drafts the next touch in your voice, and waits for your approval before anything sends.