Tools
We do not sell a standalone CRM, so this is written without a horse in the race. Most advisors choose for the wrong reason.
We do not sell a standalone CRM, so this is written without a horse in the race. Our platform includes one, which matters at the end of this piece but not before it.
Most advisors choose a CRM for the wrong reason: features. Nearly every CRM in this category will hold a contact, log a note and schedule a task. The differences that actually change your week are integration depth, how much configuration it demands, and whether anyone at your firm will maintain it.
| Best fit | The real cost | |
|---|---|---|
| Redtail | Small to mid firms wanting something advisors will actually use | Depth ceiling — you outgrow the workflow engine before you outgrow the contact record |
| Wealthbox | Firms that value adoption over configurability | Simplicity is the feature and the limit |
| Salesforce | Firms with an admin, or budget for a consultant | It will do anything, which means somebody must decide what it does — forever |
Where does the client data live, and how many copies are there? A CRM that does not share a record with your portfolio system means someone re-keys households, and re-keying is where the errors your clients eventually notice are born.
Ask any CRM vendor how their integration handles a household that exists in both systems with different spellings. The answer is usually a sync that runs nightly and a conflict rule nobody has read.
A CRM that is not a separate product at all — built on the same records as trading, billing, reporting, planning and risk, so there is no integration because there are no two systems.
That sounds like a technicality. In practice it changes the day:
| CRM plus integrations | CRM on the same ledger | |
|---|---|---|
| The household record | Exists in two or more systems, kept in step by a sync | Exists once |
| Opening a client | Contact detail here, holdings there, risk score somewhere else | Positions, performance, risk profile and planning on the same screen as the notes |
| Preparing a review | Assemble from three exports | Already assembled, because nothing had to be assembled |
| Prospect becomes a client | Re-key into the portfolio system | One action — the record was already there |
| When something disagrees | Which system is right? | The question cannot arise |
| Cost | A licence, usually per seat, rising with headcount | No separate licence |
The reconciliation question is the one worth sitting with. Every integrated stack eventually produces a moment where the CRM says one thing and the portfolio system says another, and somebody has to decide which is true. That moment is where the errors your clients eventually notice are born — and on a single ledger it does not occur, because there is nothing to disagree with.
Honestly: configurability. Salesforce will bend into any shape your firm imagines, and a CRM that is part of a platform will not. If you have an admin and a process you have refined over a decade and you want the software to match it exactly, a native CRM will feel constrained. That is a real trade and it is worth naming before anyone sells you past it.
What you gain is that nobody at your firm becomes the translator between systems — and one fewer company holds a copy of your client list, which is a question worth asking every vendor now that every vendor is adding AI to their slice of it.
Questions this did not answer? Ask them directly — that is what the twenty minutes is for.
Book 20 minutes with Kyle