How to give your product team Gong call context without buying them a Gong seat
You don't need to buy a Gong seat for every PM and engineer to get them what customers say on sales calls. Gong lets anyone view a full call recording and its AI-generated summary without a license, either by a shared link or by verifying their email on your company's domain, a setting an admin turns on once. That covers the "can they see one call" question for free.
What it doesn't cover is a feed. Sharing a call is something a rep does on purpose, one call at a time, when they remember a moment was worth passing along. Below is how the license-free sharing actually works, why Gong's per-seat pricing makes people reach for it in the first place, and the point past which relaying calls by hand stops keeping up with how many get recorded.
“we need SSO before rollout”
“any update on single sign-on?”
“SSO came up twice on this call”
Linear issue, quotes attached
insight report in NotionWhat a Gong seat actually costs
Gong's pricing page doesn't list a rate. It's licensed per user, with a separate platform fee sized to how many users you're supporting, and the only path in is a form asking whether your team is 1-50, 51-1,000, 1,001-9,999, or bigger, followed by a custom proposal. There's no self-serve tier and no published number to check against.
The closest thing to a published number comes from teams comparing invoices in public. A rundown of Reddit-reported Gong pricing puts the smallest deals around $12,000 a year for 3 seats, with 5-7 rep teams quoted $20,000 or more, and one 9-seat deal at $30,000 plus a $10,000 setup fee. A separate breakdown of Gong's pricing estimates the base tier at $1,400-1,600 per user per year, with bundled packages running $2,880-3,000 per user per year on top of platform fees that start around $5,000 for small teams. These are reported figures from public deals, not Gong's own rate card, but they're consistent with each other, and with what the pricing page's structure implies. Adding five more seats so product and engineering can watch calls is a five-figure decision, not a checkbox.
That's the real reason most companies ring-fence Gong access to reps and their managers. It isn't that Gong is hiding calls from the rest of the company on purpose. It's that a seat is priced like a sales tool, and nobody budgets for a dozen of them so an engineer can occasionally hear a customer's actual words.
Share a call without a license
Gong's own answer to this is call sharing, and it's a genuine native option worth setting up before you look anywhere else. Sharing a call works two ways: copy a link and send it to anyone, in or outside the company, or turn on domain-based access so that anyone with a verified email on your company's domain can open shared calls without a separate invite. The recipient gets a page with the recording, call details, and, if your admin has it enabled, the AI-generated highlights, outline, and transcript, all without ever logging into Gong or occupying a seat.
Two limits are worth knowing up front. If someone opens a shared link without verifying who they are, Gong shows the link as accessed but not by whom, so you lose the attribution that makes a call note useful later. And AI summaries are only available on full calls, not on a shorter snippet, so sharing a specific moment means sharing the whole recording around it.
Set domain-based access up once and it removes the "does this PM even have access" question permanently. What it doesn't do is tell a PM which of last week's forty calls they should watch. For that, someone still has to notice something worth sharing and act on it.
Trackers flag the moment, but only a seat holder sees it
Gong Trackers identify a phrase, keyword, or trained concept the moment it comes up in a call. Set one up for "onboarding time" or a competitor's name, and every future call gets scanned automatically. The aggregate view of how often a tracker fires lives at Insights > Team > Trackers, showing team members how often the concept comes up in their own calls.
That view sits behind a Gong login. A tracker firing doesn't message anyone who lacks a seat; it surfaces inside the product for whoever already has one and knows to look. In practice, trackers plus sharing become a two-step relay. A rep or manager with a seat sees a tracker hit or remembers a call, decides it's worth passing on, and shares the link with the product team member who doesn't have one. The relay works. It depends entirely on a human doing step one.
How Simone kept Solheim's product team looped in, until she couldn't
Solheim Diagnostics sells scheduling and billing software to independent imaging clinics, and its product org is three PMs, none of whom has ever held a Gong seat. Simone Balakrishnan leads that team, and for most of the first year the informal system held up fine. An account exec would hear something worth flagging on a call and drop the link in Slack on their own.
Deshawn (AE): Sharing this one, worth a listen around minute 12. Clinic ops director basically described our roadmap back to us. [gong link]
Simone: Got it, watching now. This is the third clinic asking for the same thing this month.
That third comment was the problem. Simone knew it was the third time because she remembered the first two, not because anything counted them. By the time Solheim had eleven reps and roughly 60 calls a week, the relay depended on whichever rep happened to think a comment was noteworthy enough to interrupt their day and share it. Requests that came up in a tone a rep didn't register as a "feature ask" (a customer saying "we just built a workaround for this ourselves") never got shared at all. Simone estimated she was seeing maybe a third of the calls where something roadmap-relevant came up, and had no way to check that estimate against the calls she wasn't seeing.
Where the relay breaks down
The share-link and tracker combination is genuinely enough for a small team watching a modest number of calls, and it costs nothing beyond an admin flipping on domain access. It stops working for three predictable reasons at once: coverage depends on a rep's judgment about what's worth sharing, nothing counts how many times a request came up across calls the product team never saw, and a shared link lands as an isolated moment with no memory of the last four times someone said something similar in a different call, or in Slack, or in a support ticket.
That's the point where a growing number of teams stop relying on the relay and add something that reads every call automatically. That's the category Modem is built for. Modem's Gong integration ingests transcripts from the workspaces you connect, starting from the moment you connect it (no backfill of older calls), and matches the people on each call to the same people and companies it already knows from Slack, support tickets, and email. A mention gets grouped into a topic with a running count, whether or not a rep thought to share it, and Modem's own pricing includes unlimited users on every plan rather than charging per seat, so the whole product and engineering team can see what came up without anyone provisioning a Gong license for them. It's an honest trade, not a replacement. Modem doesn't do deal coaching or call scoring, and it isn't a better way to review one call closely. It's a way to stop losing the calls nobody thought to share.
Two related guides worth reading: how to search every Gong call for a feature mention covers what happens once you do have Gong access and are trying to find every mention of one thing, and the six tools that mine product feedback from sales calls compares Modem's approach against Chorus, Productboard, and Enterpret directly.
Start with what's already free
Turn on domain-based call access in Gong's sharing settings so every PM and engineer at your company can open a shared call without asking for an invite. Then set up one Tracker for the request you keep hearing about secondhand, and ask the AE team to forward its hits to the product Slack channel as they come up. That costs nothing and closes the access gap immediately. It won't tell you what you didn't see, which is exactly the gap that shows up once the number of weekly calls outgrows what any one rep can keep track of.
