The most expensive sentence a sales leader can say is, "we should switch CRMs." The second most expensive is, "let's add another tool on top." There is a third option, less famous, and it is what we ship.
The bottleneck
Most "we need a smarter CRM" problems are actually "we need our CRM to do things it was never designed for." Lead scoring that adapts. Enrichment that lives on the record, not in a side tool. Drafted follow-up that sits in the activity feed. Forecasts the team trusts. None of these need a migration. All of them can be built as a layer that reads from your existing CRM and writes back into it.
The mental model that works: the CRM is the system of record. AI is the workflow on top. The CRM owns the truth. The AI does the thinking. The reps see both, in the same place, without learning a new tool.
What we actually ship
- Enrichment. Every new contact pulled through a firmographic + intent step. Stored on the contact record. The rep sees it without asking.
- Real lead scoring. Not the rule-based version your CRM ships with. Trained on your last 18 months of closed-won and closed-lost. Score updates daily, with the reason attached.
- Drafted follow-up. When a rep has not touched a deal in N days, an agent drafts the next email and parks it as a draft activity. The rep approves and sends.
- Account summaries. One-paragraph summary per account, refreshed weekly. Recent activity, risk signals, what to do next.
A real engagement
A healthcare DTC company asked us to "rebuild RevOps." Two weeks of diagnostic later, the bottleneck was not the CRM — it was that 60% of reps were not logging activity, so nothing downstream worked. We shipped the enrichment + scoring layer, plus a logging shim that surfaced missing data back into the rep's workflow. Pipeline doubled in nine weeks. Manual upkeep dropped 71%. No CRM migration.
A smart CRM is one where your reps do not know we are there. The CRM just got better.
The longer write-up of the integration pattern is in the field note The smart CRM: stop replacing it, start layering on top.
Why we do not migrate the CRM
The pitch from the new vendor sounds clean. Better data model. AI built in. Nicer UI. The problem is that the value of a CRM is not the software. It is the years of data, the rep behavior, the integrations with your billing and marketing stack, and the muscle memory of the team. Migrations break all of that.
We have watched a sales team lose an entire quarter to a CRM swap. By the time the new tool was running, half the reps were updating the old one out of habit and the forecast was a guess. Layering on top is 3–5 weeks and zero rep workflows changed. Migrations are 9 months and a bad year.
The best smart-CRM upgrade we have ever shipped is the one a sales rep noticed three weeks in and asked who built it. They thought it was a new feature.
Where the CRM stays the truth
Pipeline stage. Deal value. Forecast category. Anything the CFO sees on Monday morning. The AI layer can suggest changes to those, but it does not write them without a rep approving. The moment your forecast number disagrees between two systems, the entire org loses trust in the data.
Engagement shape
- Two-week paid diagnostic. CRM audit, rep interviews, the real reason the pipeline is not telling the truth.
- Build sprint, 4–6 weeks. Layered AI in your CRM, evals on every classifier, handoff to your sales ops lead.
- Optional retainer. Ongoing tuning + new agents as the motion changes. Most teams take it for one quarter, then own it themselves.
If you have a CRM that mostly works and a sales leader saying "we need to switch," the right next step is probably a diagnostic, not a vendor demo. Book one.