Displacement playbook
revenue intelligence and conversation intelligence platformHow to sell against Gong: the displacement playbook
How to sell against Gong on timing: the public signals that suggest an account is re-deciding its revenue intelligence layer, and how to run a respectful evaluation motion.
Who owns the tool
This category has an unusual ownership shape. The budget sponsor is typically the CRO or VP of Sales, because the platform's output feeds forecasting and deal inspection. But the daily operators are enablement leaders, who build coaching programs on the call library, and frontline managers, who run reviews from it. RevOps administers the integrations and often the renewal. That means displacement conversations have three doors: enablement feels the workflow, frontline managers prove or disprove adoption, and the CRO decides whether the line item survives planning. The most durable entry point is usually enablement, because coaching programs are where the platform is either woven into the org or quietly unused.
The renewal math
Platforms here are generally sold on annual contracts, frequently multi-year at enterprise scale, and priced per recorded seat, which ties the commercial shape to sales headcount. Public markers date the relationship: enablement job posts that name the platform, case-study appearances, conference sessions on the team's coaching program. Anniversary of the earliest marker is your estimate. Evaluation lead time runs 60 to 120 days, longer than a pure engagement swap because a fair test needs enough recorded calls to compare insight quality, and because security review is heavier when call recordings and their transcripts are involved; legal review of recording consent settings can add its own weeks at regulated companies. Headcount is the second clock: public sales hiring waves or reductions change per-seat economics at the next anniversary, and planning season is when the CRO weighs every line item feeding the forecast. All of it is standard process math, independent of any vendor's actual terms.
The public signals that open the window
- Enablement and manager reqs that name the platformPostings for enablement managers, sales coaches, or frontline managers that list the platform confirm the deployment and show where it lives organizationally. Read the emphasis: a req centered on building a coaching program from scratch suggests the current library is underused, while a req to administer and expand the platform suggests investment. Both are useful, and both carry dates that anchor your renewal estimate and your outreach calendar.
- Reqs naming a competing intelligence skillsetA hiring post asking for experience with a different conversation or revenue intelligence stack, at an account whose other markers show the incumbent, is a public statement of exploratory direction. So are vendor-neutral reqs asking someone to own the evaluation of coaching and forecasting tooling. Because job descriptions are drafted by the owning function, they reveal the internal conversation more reliably than any external inference can.
- Enablement leadership turnoverThe enablement leader who built the coaching cadence around the call library is the deployment's operational champion. Their departure, visible through job-change posts, decouples the platform from the program it powers. Successors rebuild coaching programs to their own design and often bring tooling preferences from their previous org, so the combination of a departure post and the incoming leader's background is one of the most predictive public reads in this category.
- A new CRO in planning seasonRevenue intelligence exists to serve the CRO's forecast, so a CRO transition puts the category under direct review by its own economic buyer. New CROs audit the stack in their first quarter and decide what survives the next planning cycle. The hire announcement is public and dated, the review window is short, and vendors who show up during it with a clear architecture point of view get evaluated rather than deferred to next year.
- Public comparison research activityEmployees of the account writing category reviews, asking comparison questions in revenue and enablement communities, or engaging with evaluation content are performing visible research work. The inference discipline matters: this establishes that the category is being examined now, and nothing else. Do not characterize sentiment, do not cite the posts in outreach, and do not frame the activity as dissatisfaction. Arrive on time; let the timing be the whole use of the signal.
- Headcount and consolidation eventsBecause pricing in this category tracks recorded seats, public headcount events move the commercial math directly: a sales hiring wave raises the stakes of the next anniversary, and a sales-function layoff commonly triggers a per-seat review across every tool billed that way. Mergers add a second dimension, two coaching cultures and two call libraries needing one owner. Each event is announced, dated, and forces a structural decision on the category.
Public sources only. These are timing signals, not claims about the vendor.
When to reach out
Open the conversation 90 to 120 days before the estimated anniversary, because evaluations in this category need recorded-call volume and security review time that shorter windows cannot fit. Move immediately on the event signals: an enablement leadership change, a CRO transition, an announced merger, or a public headcount event that changes per-seat math. Planning season adds a soft window even without an event, since the category's sponsor re-justifies the line item then. Do not run displacement outreach at an account that has recently expanded its deployment publicly, has stable enablement and revenue leadership, and shows no forcing event; without an open decision the touch spends credibility and buys nothing. Watchlist the account on the leadership pages and the anniversary, and let the next dated event set your calendar.
How to frame it
Anchor on the moment you can point to: the new CRO, the enablement transition, the sales-team expansion, planning season. Keep the frame architectural, not adversarial: at moments like these, teams re-examine how call data, coaching, and forecasting fit together, and you can make that examination fast and evidence-based. Say nothing negative about the incumbent, explicitly or by contrast; the enablement leader you are addressing may have built their program, and their coaching culture, on it. Offer an evaluation design rather than a demo: a parallel pilot on one team's calls with success criteria the account defines, or a migration-cost worksheet that honestly prices library migration, integration re-mapping, manager retraining, and program continuity. Being the vendor who told the truth about switching costs is a durable advantage in a category built on trust in recorded conversations.
What to build in the first call
Build the map before any pitch. Chart how the platform is actually used: which teams record, what the coaching cadence looks like, which reviews and forecasts consume its output, and where the CRM and calendar integrations touch. Establish the anniversary estimate, the security-review lead time, and the real evaluation runway between now and the deadline. Identify the decision unit by name: enablement lead, frontline manager voices, the RevOps admin, the CRO signature, and any legal gate on recording policies. Ask the gating question: what would have to be true for a switch to be worth re-platforming the coaching program? Record the answer as shared criteria. Then scope a reversible pilot, one team's calls analyzed in parallel for a defined period, with a pre-scheduled decision meeting so the evaluation ends in a decision instead of a drift.
Frequently asked questions
How do I find out when Gong contracts renew at a target account?
Estimate from dated public markers: enablement job posts naming the platform, case-study appearances, conference talks about the coaching program. Assume annual terms from the earliest marker and open outreach 90 to 120 days before the anniversary, since evaluations here need recorded-call volume and security review time. Sales headcount announcements are a second clock, because per-seat economics move with them.
Is it worth competing against an entrenched Gong deployment?
With a signal, yes. The category's windows are driven by people and planning: enablement leaders change, CROs transition, headcount events move per-seat math, planning season re-justifies every forecast-feeding line item. Gate your motion on those public events and the anniversary estimate, and skip stable accounts entirely; in this category an unearned touch reads especially poorly because the buyer's whole product is listening well.
What signals suggest an account is evaluating Gong alternatives?
Reqs naming a competing intelligence skillset or a tooling-evaluation mandate, enablement leadership turnover, a new CRO inside the first quarter, visible comparison research by employees, and headcount or consolidation events that change per-seat economics. One signal earns a respectful architectural conversation; two or more, especially near the estimated anniversary, earn immediate priority.
Gong and all other product names on this page are trademarks of their respective owners. Intakra is not affiliated with, endorsed by, or sponsored by Gong 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