Most Gong rollouts stall in the same place: the platform is live, calls are recording, and almost no one is using the insights. Adoption, not installation, is what separates teams that get a return on Gong from teams that simply pay for it. This playbook is the sequence we use to get to real adoption.
Why Gong rollouts stall
A Gong rollout is easy to switch on and easy to under-deliver. The failures we see are rarely technical. They are operational: the platform goes live without a clear reason for reps to open it, managers are not given a coaching rhythm, and the data never connects cleanly to the forecast.
- No clear reason for reps to use it, so Gong feels like surveillance rather than support.
- Managers handed a tool but no coaching ritual to use it.
- Trackers and scorecards left at defaults, so the insights do not match how you actually sell.
- Gong and Salesforce loosely connected, so activity and deal data never line up.
- Success measured by logins instead of changed behavior or moved numbers.
Step 1: Capture and data hygiene
Everything downstream depends on Gong capturing the right conversations and tying them to the right records. That means clean call and meeting capture, correct user and team mapping, and a tight connection to Salesforce so every conversation lands against the right opportunity. Get this wrong and every report and signal that follows is noise.
Step 2: Configure for how you actually sell
Out-of-the-box trackers and scorecards are a starting point, not an answer. Map your sales methodology, your stages, and the moments that matter in your deals into Gong's trackers and scorecards so the insights reflect your business rather than a generic template.
Step 3: Build the coaching ritual
Adoption follows value, and the fastest value is better coaching. Establish a weekly cadence where managers review a consistent set of calls against a shared scorecard and give each rep one specific behavior to work on. The ritual is the product; Gong is the instrument.
Step 4: Connect Gong to the forecast
Once capture and coaching are working, bring Gong into pipeline and forecast reviews. Use conversation and activity signals alongside CRM data to pressure-test the roll-up and catch at-risk deals while there is still time to act.
A 90-day rollout sequence
- Weeks 1 to 3: capture, user mapping, and the Salesforce connection. Verify data lands correctly before anyone relies on it.
- Weeks 4 to 6: configure trackers and scorecards to your methodology, and train managers on the coaching ritual.
- Weeks 7 to 9: launch weekly coaching and pick one team-wide behavior to track.
- Weeks 10 to 12: bring Gong signals into pipeline and forecast reviews, and measure changed behavior rather than logins.
Measure behavior, not logins
Login counts tell you who opened the app, not whether anything changed. Adoption that matters shows up as different behavior and better numbers. Track a small set of signals that connect Gong activity to outcomes, and review them in the same meetings where you review the pipeline.
- Coaching coverage: what share of reps got specific, call-based feedback this week.
- Behavior change: movement on the one tracked behavior you chose, rep by rep, over time.
- Deal hygiene: are at-risk deals being surfaced and acted on earlier than before.
- Forecast quality: whether conversation signals are improving the accuracy of the roll-up.
Common mistakes to avoid
- Treating go-live as the finish line. The rollout is where adoption work begins, not where it ends.
- Leaving trackers at default and wondering why the insights feel generic.
- Rolling out to everyone at once instead of proving the coaching ritual with one team first.
- Letting Gong and Salesforce drift apart, so activity and deal data never reconcile.
- Positioning Gong as oversight. Frame it as preparation and coaching, or reps will quietly route around it.
Where teams get the most leverage
The highest-leverage move is almost always tighter integration between Gong and Salesforce paired with a disciplined coaching rhythm. As a Gong services partner, that is where we concentrate the work, because it is what turns a Gong subscription into a measurable change in how a team sells.
Which team should get Gong first?
Start with the team whose manager will coach from it every week. A willing manager matters more than team size or revenue share.
After that first team proves the ritual, add teams in an order that reuses what you built. A typical sequence is below.
- A pilot sales team with a committed first-line manager, to prove capture and coaching.
- The rest of the new-business sales teams, using the same trackers and scorecards.
- Sales development, with scorecards tuned to discovery and meeting setting rather than closing.
- Account management and customer success, with trackers for renewal risk and expansion signals.
- Leadership and forecasting users, once enough deals carry reliable conversation data.
How should you set up trackers and scorecards?
Build trackers from the moments that change deal outcomes, and build scorecards from the behaviors you will coach. Keep both short enough that managers use them.
| Item | Use it for | Common setup mistake |
|---|---|---|
| Keyword trackers | Named things: competitors, products, pricing terms | Tracking too many words, so every call matches something |
| Smart trackers | Concepts phrased many ways, such as budget concerns | Skipping review of the sample calls used to train them |
| Scorecards | Rating calls against your methodology | Too many questions, so managers stop filling them in |
Link each scorecard question to a stage or behavior in your methodology. If a question does not tie to something a manager would coach, drop it. Name trackers in the words your reps use. Review them with managers after the first month and remove any that nobody looks at.
What data should flow between Gong and Salesforce?
Decide which system owns each piece of data before you switch on sync. Salesforce should stay the record for accounts, contacts and opportunities.
- Which call and email activities write back to Salesforce, and against which object.
- Which opportunity fields Gong reads, so deal boards match what reps see in the CRM.
- How contacts are matched to calls when email domains or names differ.
- Whether any Gong insight, such as a deal warning, should appear on the opportunity page.
- Who reviews unmatched calls, so gaps are fixed rather than ignored.
How do you know adoption is sticking?
Adoption is sticking when Gong shows up in routines nobody has to schedule. Look for habits, not only numbers.
- Reps share call clips with each other without being asked.
- Managers open pipeline reviews from Gong deal boards, not a separate spreadsheet.
- New hires study recorded calls as part of their onboarding plan.
- Scorecard questions change because managers asked for them to change.
Watch for the opposite signs too. If reps only open Gong in the days before a review, the tool is still seen as oversight. Go back to how managers frame it.
