-to-listen ratio is a side benefit. Gong's revenue intelligence benchmark puts top B2B reps at 43% talk, 57% listen on discovery. Once you have a diarized transcript, that ratio is a one-line calculation per call — a coachable metric without buying Gong.
CRM integration patterns
We don't ship automatic CRM logging out of the box. You wire the integration. Three patterns work, in increasing order of engineering effort and decreasing order of fragility.
1. Copy-paste (zero integration)
The rep gets a transcript + structured summary by email or in the dashboard, copies the seven fields into Salesforce or HubSpot manually. A couple of minutes instead of 12-plus. Fine for a five-rep team where nobody wants to maintain a Zapier zap. Also the right starting point for any pilot — you'll learn which fields actually matter before automating anything.
2. Zapier / Make middle layer
The transcription job completes, fires a webhook, Zapier catches it, parses the structured JSON, creates or updates the Salesforce Opportunity or HubSpot Deal. Field mapping happens in the Zapier UI, so RevOps owns it without engineering.
Seams: webhook triggers can be near-real-time, but polled steps, downstream actions, and CRM rate limits can still add minutes, and complex field logic (e.g. "if MEDDIC champion is filled, update the Contact role to Champion") gets ugly in a no-code editor. Budget roughly $20–$100+/month on top of transcription, depending on task volume and plan.
3. Direct webhook to your CRM API
Our completion webhook posts the transcript JSON to your endpoint. A small Lambda or Cloud Function maps fields and calls the Salesforce REST API or HubSpot CRM API. You own the code, you own the logic, you own the failures.
This is what we'd recommend for any team above 15 reps. The payload is documented on our meeting-notes integration page — fields include transcript_url, diarized_segments, speaker_labels, and (if you turned on summarization) a structured summary object.
For Salesforce specifically, you'll likely write to the Task object (for the call record itself) and the Opportunity object (for the structured fields). HubSpot is similar — Engagement for the call, Deal for the fields. Both have rate limits worth reading before you go to production.
Where Gong, Chorus, and the natives win
Be honest about this — dedicated revenue intelligence platforms exist for reasons.
Gong does coaching at scale. It indexes every call in your org, lets a manager search "every call where a prospect mentioned Competitor X in the last 90 days," tracks objection patterns across reps, and surfaces deal risk from language signals. Vendr's 2024 benchmark puts Gong at $1,200–$1,600 per user per year plus a $5,000+ platform fee. For a 50-rep team that's $65,000–$85,000/year, and the value is real if your sales org runs on call coaching.
Chorus (now part of ZoomInfo) plays a similar game with tighter ZoomInfo integration. Salesloft Conversations is bundled with the cadence tool — if you already pay for Salesloft, marginal cost may be lower depending on your package.
HubSpot Conversation Intelligence ships with Sales Hub Professional ($90–$100/user/month) or Enterprise ($150/user/month) per HubSpot's 2024 pricing. If you already have those seats, transcription is "free" — quality and depth are below Gong, but it's in the CRM where you already work.
Salesforce Einstein Conversation Insights is included with Sales Cloud Unlimited ($330/user/month) or a $50/user/month add-on for Enterprise. Same logic.
Mid-market AI notetakers sit between full RI and general transcription. Fathom AI offers a free tier with CRM-syncing Team plans at $24/user/month (2024 public pricing). Fireflies.ai Business with Salesforce/HubSpot integration sat around $19/user/month in 2024. Verify current packaging before you compare — contract minimums and tier structures move every quarter.
Where general transcription is enough:
- Teams under ~20 reps with no full-time enablement person doing call review.
- Founders running discovery themselves who want a record + summary, not a coaching platform.
- Solutions engineers and CS doing "discovery-adjacent" calls (renewals, expansion) that don't justify a Gong seat.
- Anyone already paying for Sales Hub Professional/Enterprise or Sales Cloud Unlimited (or Enterprise with the ECI add-on) who wants supplemental coverage on calls the native tool misses — one-off Google Meet calls, in-person recordings, phone bridges.
Our Pro plan at 600 audio-minutes + 900 bot-minutes per month (as of May 2026) covers a working rep doing roughly 20 discovery calls of 45 minutes. Business at 5000+3500 covers a small team. Details on the pricing page. That's a Gong-alternative price point — not a Gong replacement.
Privacy: don't skip this section
Recording a sales call is a regulated act. The rules differ by who's on the call and where they sit. Build your consent map around participant location, not your HQ address.
Two-party (all-party) consent US states: commonly treated all-party states include California, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, and Washington. Connecticut and Delaware have stricter or mixed rules, and Oregon and Michigan are context-dependent — get legal review. If any participant sits in one of these, as a conservative working rule, get explicit consent from everyone. "This call is being recorded for note-taking and quality purposes" followed by an affirmative response is the working norm.
One-party consent states: most of the rest of the US. The rep can record without disclosing, in theory. Don't rely on this. Disclose anyway — the reputational cost of a prospect feeling spied on is bigger than the convenience of skipping a sentence.
EU and UK (GDPR): recording is processing of personal data, and special-category processing if health, religion, or political views come up. You need a lawful basis, a retention policy, and a deletion path. Once the transcript lands in your CRM, the CRM is part of the data footprint too — scope access accordingly.
A practical rule: don't dump full verbatim transcripts into broad-access CRM objects. If a prospect mentioned employee health data, an active security incident, or internal financials, that belongs in a restricted field or attached to a need-to-know record — not in the Activity Timeline anyone with read access can scroll.
What we do: meeting bots join under a configurable name