How to sell against ZoomInfo: the displacement playbook

Who owns the tool

The B2B data layer is almost always owned by revenue operations. In mid-market companies that is one RevOps manager or sales ops lead who administers seats, manages the integration into the CRM, and defends the line item at renewal. In larger companies ownership can sit with a dedicated data or enrichment owner inside RevOps, with procurement running the commercial side. Marketing ops is usually a secondary stakeholder because enrichment feeds their forms and routing. Your outreach target is the RevOps owner first and their VP or CRO second, because the admin feels the workflow daily and the executive signs the renewal.

The public signals that open the window

• Job postings that name the platform in the stackA RevOps or sales ops posting that lists the platform among the tools the hire will administer tells you three things at once: the account is a confirmed user, the role that owns it is being filled or expanded, and the posting date gives you a fresh anchor for estimating tenure with the tool. A req for the tool's admin also means the person who will influence the next renewal may not even be hired yet, which is the most open state an account can be in.
• Job postings that name a competing data skillsetWatch for reqs that ask for experience with a different data or enrichment vendor, or for generic skills like waterfall enrichment and data-quality operations that are not tied to the incumbent. A company hiring for a competing skillset while running the incumbent is publicly describing the stack it wants next. This is one of the cleanest evaluation signals available because the company wrote it down itself, in its own words, with a date on it.
• Turnover in the admin seatWhen the RevOps person who administers the data platform changes jobs, the vendor relationship resets. The renewal that used to be a rubber stamp becomes a fresh decision made by someone with no history with the account team and no personal investment in the original selection. LinkedIn job-change posts and team-page diffs surface this publicly. The window opens the day the departure is visible and stays open until the replacement settles into the inherited stack.
• A new CRO or VP of RevOpsNew revenue leaders audit the stack they inherit, usually inside their first quarter. A data platform is one of the larger line items in that audit, so an executive-hire announcement over the owning function is a timing signal even when nothing else has changed. The new leader has the authority to re-open decisions and a mandate to show early wins, and vendors who arrive during that first-quarter review get evaluated instead of filtered.
• Review and comparison research activityWhen people at an account start posting reviews of tools in the category, asking comparison questions in public communities, or engaging with head-to-head threads, that is evidence of active research regardless of what the posts say. Treat it purely as a timing signal: employees do not invest time comparing category options when the stack is settled. Never characterize the sentiment or attribute an opinion to the account. The fact of the research activity is the signal.
• Company events that force a data decisionSome events put every data contract on the table mechanically. A merger means two enrichment stacks and one surviving contract. A funding round that expands the sales team can push the account past its current seat tier, which forces a commercial conversation either way. A layoff round often triggers a consolidation review across overlapping tools. Each of these is public, dated, and creates a real decision moment that has nothing to do with anyone's opinion of the incumbent.

Public sources only. These are timing signals, not claims about the vendor.

When to reach out

The highest-value touch lands a full quarter before the estimated renewal, early enough that a real evaluation can fit before the deadline. The second-best moments are event-driven: right after the admin or champion departs, inside the first 90 days of a new CRO or RevOps leader, or immediately after an announced merger or team expansion. In each case you are arriving while the decision is genuinely open. Do not reach out on displacement framing when the account has just publicly signed or renewed and no other signal has fired; a fresh annual signature with a stable team means the window is closed for now, and the right move is to set a watch for next year's window rather than burn goodwill on an impossible ask. Log the estimated anniversary and come back on schedule.

How to frame it

Never trash the incumbent, by name or by implication. You do not know their experience with it, and disparagement reads as insecurity. Open on the public event you actually observed: the new leader, the stack-naming job post, the merger, the approaching anniversary you inferred. Then anchor to the workflow moment, not the vendor: renewal season is when teams re-check match rates, seat usage, and integration fit, and you are offering to make that check easy. Offer a side-by-side evaluation plan or a match-rate test on their own account list rather than a demo. Acknowledge switching costs honestly: migrating a data layer touches the CRM, routing, and every enrichment workflow, and pretending otherwise costs you credibility with the exact operator you are trying to win.

What to build in the first call

Use the first call to build a shared map, not to pitch. Sketch the current workflow around the platform: which teams consume the data, what feeds the CRM, where enrichment fires, and which integrations would move in a switch. Get the renewal date on the table, or at least the contract anniversary month, and the decision timeline working backward from it. Identify who actually owns the decision: the admin who runs it, the executive who signs, and whoever in procurement or security gets a veto. Then ask the honest question: what would have to be true for a switch to be worth the migration? Close by scoping a small, reversible pilot, one team running a parallel match-rate test against live records, with a defined end date and success criteria the account wrote itself.

Frequently asked questions

Related

Other playbooks