Displacement playbook
CRM platformHow to sell against Salesforce: the displacement playbook
How to sell against Salesforce on timing: the public signals that suggest an account is opening a system-of-record decision, and how to run a respectful, well-timed evaluation motion.
Who owns the tool
The CRM is the system of record, and its ownership reflects that weight. Day to day it belongs to a CRM admin or an admin team, usually inside RevOps but sometimes inside IT at larger enterprises. Above them sits a RevOps or business-systems leader who owns the roadmap, and above that a CRO or COO who owns the budget. At enterprise scale, solution architects and integration engineers form a whole internal practice around the platform. Displacement targeting must respect this depth: the admin team knows the real integration surface, the business-systems leader owns the architectural roadmap where a migration would live, and only the executive layer can sponsor a change this large. Start with the roadmap owner.
The renewal math
CRM platforms at this tier are sold on annual and, very commonly, multi-year contracts, and the migration weight makes the renewal calendar longer-fused than any other category in this playbook series. Date the relationship from public markers: admin and developer job posts naming the platform, case studies, conference appearances by the ops team. The anniversary of the earliest marker is your base estimate, with the caveat that multi-year terms mean the true decision point may be one or two anniversaries out. Serious evaluations of a system-of-record change start six months or more before the decision date, because they involve data-model mapping, integration inventory across every connected system, migration sequencing, parallel-run planning, and extensive security and procurement review. Consequently the realistic displacement motion here is less about catching a window and more about being present early in a long arc: the vendors considered in month one of a CRM evaluation are the ones still standing in month nine. Generic process math throughout, never a claim about actual terms.
The public signals that open the window
- Admin and developer reqs that reveal the footprintJob posts for admins, developers, and architects on the platform confirm the deployment and size it: the number of open platform roles approximates the internal practice built around the CRM, which is the single best public proxy for switching cost. Watch the trend line, not the snapshot. A shrinking platform-role footprint alongside growth in vendor-neutral data or systems roles suggests the internal center of gravity is moving, which is how CRM transitions look from the outside years before they are announced.
- Reqs naming a competing CRM skillsetA posting that asks for hands-on experience with a different CRM, at an account whose other markers show the incumbent, documents exploration at the system-of-record level, which companies do not do casually. Migration-language reqs are the strongest form: re-implementation, data-model redesign, CRM consolidation. Because these evaluations run long, a competing-skillset req is not a late signal; it is often your invitation to the beginning of a multi-quarter process.
- Business-systems leadership turnoverWhen the RevOps or business-systems leader who owns the CRM roadmap departs, visible through job-change posts, the roadmap itself goes up for review. Successors at this level are hired to have architectural opinions, and their first-year plan frequently includes a systems rationalization. The departure post, the successor announcement, and the successor's platform history together form a readable forecast of whether the system-of-record question will open, and roughly when.
- A new CRO, COO, or CIOSystem-of-record decisions need executive sponsorship, so executive transitions are the events that can actually open them. New operating and revenue executives audit core systems in their first two quarters, and CRM cost and fit is a standing item in those audits at any company where the deployment is large. The hire announcement is public and dated. Arriving during the audit with an architecture-level point of view is how a displacement vendor enters a CRM conversation credibly.
- Public research and community activityEmployees asking migration and comparison questions in ops and admin communities, posting category reviews, or engaging with platform-evaluation content are doing visible work on an open question. The discipline is the same as everywhere in this series: this signals timing, not sentiment. Never cite the posts, never characterize their tone, never present them as evidence about the vendor. Their only legitimate use is telling you the question may be live now.
- Mergers and multi-CRM consolidationThe single most mechanical opener of system-of-record decisions is a merger: the combined company holds two CRMs, and one must eventually absorb the other, a decision made on integration architecture, internal skills, and cost of change. Deal announcements are public and dated, and the systems-consolidation phase follows within a few quarters. Large public restructurings play a similar role, since they frequently trigger core-systems cost reviews with executive attention attached.
Public sources only. These are timing signals, not claims about the vendor.
When to reach out
Think in quarters, not days. Enter six months or more before the estimated decision point, and treat multi-year terms as meaning the next anniversary may not be a decision point at all. The event signals are what genuinely open this category: a new operating executive's first two quarters, a business-systems leadership change, and above all an announced merger entering its consolidation phase. When one fires, begin immediately, because being present at the start of a long evaluation is most of the game. The no-go is equally clear: an account that has publicly deepened its platform investment, with a stable admin practice and no executive or structural event, has a closed system-of-record question, and pressing it wastes years of future credibility. Watchlist on the leadership pages, the platform-role hiring trend, and merger news.
How to frame it
At this altitude, framing is everything. Open on the structural event: the merger, the new COO, the systems-leadership transition. Speak architecture, not product: the conversation an account will actually have at these moments is about integration surface, data model, internal skills, and cost of change, and your outreach should sound like a contribution to that conversation. Never disparage the incumbent; at many target accounts, dozens of careers are built on it, and the person reading your note may hold a certification in it. Offer decision-grade artifacts: a migration-cost model covering data, integrations, parallel running, and retraining; a phased evaluation plan that isolates one business unit; an integration-inventory template. Acknowledging that a system-of-record migration is expensive, slow, and risky, and structuring your proposal around exactly that truth, is the only framing that earns a seat in a CRM evaluation.
What to build in the first call
The first call in a CRM displacement is discovery for a long program, and it should feel that way. Map the deployment honestly: business units on the platform, the custom-object landscape, the integration inventory, the internal admin and developer practice, and which executive reports depend on which pipelines. Establish the contract shape as far as it can be inferred, the realistic decision point, and the multi-quarter timeline backward from it, including security, procurement, and parallel-run phases. Identify the full decision unit: admin team, business-systems owner, sponsoring executive, procurement, and any board-level cost review. Ask the gating question, what would have to be true for a system-of-record change to be worth it, and expect a hard answer. Then propose the narrowest credible pilot: one business unit or one region, parallel-run, bounded, reversible, with criteria the account authors.
Frequently asked questions
How do I find out when Salesforce contracts renew at a target account?
Date the relationship from public markers such as admin and developer job posts, case studies, and conference appearances, and treat the earliest marker's anniversary as a base estimate, remembering that multi-year terms are common at this tier and the true decision point may sit an anniversary or two out. Because evaluations run six months or more, early is the only kind of on-time in this category.
Is it worth competing against an entrenched Salesforce deployment?
Only when a structural signal says the system-of-record question is open: a merger entering consolidation, a new operating executive, a business-systems leadership change, or a visible shift in the platform-role hiring trend. Those events are infrequent but public, and gating on them turns an otherwise impossible displacement motion into a small portfolio of live, winnable, multi-quarter evaluations.
What signals suggest an account is evaluating Salesforce alternatives?
Hiring posts asking for a competing CRM skillset or containing migration language, a shrinking platform-role footprint alongside vendor-neutral systems hiring, business-systems leadership turnover, new executive sponsors in their first two quarters, employee research activity in admin communities, and, most mechanically, mergers that leave the combined company running two CRMs.
Salesforce and all other product names on this page are trademarks of their respective owners. Intakra is not affiliated with, endorsed by, or sponsored by Salesforce or its parent company. This page describes public-signal methodology and general sales process; it makes no claims about the vendor, its product, its pricing, or its customers. Verify anything about the vendor directly with the vendor.
Related
Other playbooks