[ RESOURCES | CONNECTOR GUIDE · GONG ]

Extract feature requests and competitor mentions from Gong calls

To extract feature requests and competitor mentions from Gong, pull transcripts with the account attached, sample and build a taxonomy, tag requests and mentions apart, count per account and review weekly. Gong records and transcribes sales and customer success calls. Inside those transcripts sit the two signals product and marketing teams most want and least often get: what customers asked for in their own words, and which competitor they said they were looking at. The method below works with an export and a spreadsheet, and it is the method HyperOrbit’s agents run continuously once Gong is connected.

5 STEPS · 3 PITFALLS · WORKS WITHOUT HYPERORBIT · UPDATED SEPTEMBER 2026
[ 01 | THE METHOD ]

Five steps, by hand, from call recordings and transcripts

Do it once by hand before you automate it. You will learn what your customers call things, and you will know what a good automated read looks like.

01

Pull the transcripts

Export or query transcripts for a fixed window, say the last 90 days, with the account, the deal stage and the date attached to each. Without the account you cannot price anything later.

02

Sample and build the taxonomy

Read 30 to 50 calls end to end before you tag anything. Write down the requests and competitor names you actually hear, group them, and freeze a first taxonomy. Revisit it monthly, not daily.

03

Tag requests and mentions separately

A feature request is a customer describing a job the product does not do. A competitor mention is a name, a price or a feature attributed to someone else. Keep the two lists apart; they answer different questions.

04

Count per account, not per call

One account raising a request on five calls is one account. Count distinct accounts, attach their ARR and renewal date, and rank by revenue rather than volume.

05

Review weekly, with the quotes

Bring the ranked list to the product and marketing owners with the quotes behind each line. A request without its quote gets argued with; a request with three quotes and the ARR gets scheduled.

[ 02 | PITFALLS ]

Three ways the manual read goes wrong

Keyword search is not tagging

Searching transcripts for “pricing” finds the word, not the meaning. Most requests are phrased as problems, not features.

The lag hides the cause

A rise in competitor mentions usually follows a competitor move by days or weeks. If you only count mentions, you will notice the effect and miss the cause.

Sales calls skew to prospects

Gong hears deals more than renewals. Pair it with support and review sources or you will build a roadmap for people who have not bought yet.

[ 03 | WITH HYPERORBIT ]

The same method, run continuously by three agents

OVER THE GONG CONNECTORConnect Gong once over OAuth and Chorus reads every new transcript, clusters requests into themes and sub-themes with the quotes and the ARR behind each, and keeps the read current. Recon flags each competitor mention, ties it to the competitor move that preceded it where one exists, and drafts a battlecard for the moves that matter. Atlas adds the account’s health and renewal window, so a mention on a call from an account renewing in 60 days lands in front of its owner that night.

Chorus, the voice-of-customer agent

Clusters reviews, calls, tickets and surveys into ranked themes and sub-themes, each with the quotes behind it and the ARR of the accounts that raised it.

Recon, the competitive intelligence agent

Watches competitor sites, changelogs, pricing pages and reviews every day, scores each move, and drafts a battlecard for the ones that matter, held for review.

Atlas, the account intelligence agent (beta)

Fuses what Chorus and Recon find with usage, support and CRM data into one health score per account, then watches every churn and renewal window you set.

[ 04 | GO DEEPER ]

Related on hyperorbit.ai

[ 05 | FAQ ]

Questions people ask

Does HyperOrbit integrate with Gong?

Yes. Gong is one of the 76 connectors on the integrations page. It connects once over OAuth and is read continuously.

Can I do this without HyperOrbit?

Yes. The five-step method above works with an export, a spreadsheet and a weekly hour. HyperOrbit is the way to run it continuously across every call.

How are competitor mentions linked to competitor moves?

Through the shared signal layer: Recon logs each competitor move, Chorus logs the mentions, and the two are placed on one timeline so the lag between a move and the reaction is measured rather than assumed.

What does it cost to start?

Starter is free and includes Chorus on one feedback source, 50 signals and 10 insights a month. Gong can be that source.

Every signal, on one orbit

Connect your first source in an afternoon. The first pass lands before your next standup.

Book a demo