Deal reviews stalled across tools; Gong summaries with Salesforce and Clari captured decisions and owners in Salesforce

Overview

A cybersecurity vendor’s deal reviews dragged because call notes, pipeline context, and risk signals lived in different places. Reps pasted highlights from Gong into documents, managers opened Salesforce for basics, and Clari risk flags were referenced inconsistently. Intelligex delivered a deal review workspace that auto?summarized Gong calls, pulled live Salesforce opportunity and account data, and attached Clari risk signals under controlled access. Deal desk meetings shifted from hunting for information to making decisions, action items were captured with owners, and updates flowed back to the systems already in use. The solution leveraged Gong for conversation insights, Salesforce for CRM context, Clari for risk and forecast signals, and enforced role?based access aligned to NIST RBAC principles.

Client Profile

• Industry: Cybersecurity software and services
• Company size (range): Enterprise field and inside sales with global coverage
• Stage: Gong in place for call recording; Salesforce for pipeline and opportunity management; Clari for forecast and risk; deal reviews run in slides and docs with manual prep and scattered notes
• Department owner: Sales & Business Development (Revenue Operations)
• Other stakeholders: Sales Leadership, Account Executives, Sales Engineers, Deal Desk, Customer Success, Marketing Ops, Legal, Finance, IT/Identity, Security/GRC

The Challenge

Deal reviews started with a scramble. Reps copied excerpts from recorded calls into slides, managers asked for missing context in chat, and risk indicators lived in a forecast dashboard that not everyone opened. Basic facts—stage, ARR construct, competitive posture, technical blockers, security review status—were assembled by hand. The same questions were asked repeatedly because answers were in different systems or buried in email threads.

Meetings meandered. Time went to finding the latest notes or replaying call segments rather than deciding on pricing moves, technical validation, or executive outreach. When follow?ups were assigned, owners were unclear and updates were not linked back to the opportunity. Leadership wanted faster decisions, clearer ownership, and consistent use of the tools already adopted.

Access and privacy added friction. Recorded calls sometimes included sensitive customer details, so sharing raw links widely was discouraged. Reps hesitated to include security or legal notes in general documents, which meant critical risks surfaced late or not at all.

Why It Was Happening

Signals were siloed. Gong held conversations, Salesforce held deal data, and Clari flagged risk, but nothing stitched them into a single view for a live review. Prep decks varied by owner and region, and there was no template to capture decisions and owners in a way that flowed back into the CRM.

Governance lived outside the meeting. Role?based access was defined in each tool separately, notes were copied into shared docs without consistent controls, and there was no traceable path from a decision to the follow?up tasks it created. As a result, reviews depended on memory and manual synthesis.

The Solution

Intelligex built a deal review workspace that standardized prep, pulled context automatically, and recorded outcomes with owners. Prior to each review, the workspace assembled a brief for every opportunity: an AI?generated summary of recent Gong calls, Salesforce stage and key fields, open tasks and next steps, and Clari risk and momentum signals. During the meeting, the team viewed a single page per deal, captured decisions and action items with due owners, and synced changes back to Salesforce. Sensitive content remained under role?based access, and only authorized users could view call excerpts or privileged notes. The approach used Gong conversation intelligence (Gong), Salesforce data services (Salesforce), Clari risk insights (Clari), and enforced access via SSO and RBAC.

• Integrations: Gong for recorded calls and transcripts; Salesforce for opportunity, account, contact, and task data; Clari for risk and forecast context; calendar for agenda prep; collaboration (Slack/Teams) for notifications; identity/SSO for roles and access.
• Standardized brief: Auto?compiled snapshot with last call summaries, highlights and objections, stakeholder map, stage and forecast category, open tasks, mutual plan milestones, and Clari risk indicators.
• AI summarization: Key moments and themes extracted from Gong transcripts, with links to time?stamped call snippets; confidence indicators; human review during prep.
• Decision log: Structured fields for decisions, owners, due dates, and dependencies; sync to Salesforce tasks and next steps; reason?coded notes for exceptions.
• Risk and blocker mapping: Clari risk signals and historical trendlines surfaced; security/legal blockers flagged with required next action; optional escalation prompts.
• Access controls: Role?based views; counsel?only and deal?desk?only notes hidden from broader audiences; opt?in sharing of call excerpts; immutable audit of who viewed what.
• Dashboards: Review outcomes by team and region; action item completion; risk trend movement after interventions; meeting hygiene (deals reviewed, time spent on decision?making).
• Security and privacy: Minimal sensitive content in notifications; encrypted links back to source systems; retention aligned to policy; logs of edits, views, and syncs.

Implementation

• Discovery: Mapped current review cadence and prep artifacts; identified common information gaps and repeated questions; cataloged Gong call patterns and sensitive topics; inventoried Salesforce fields required for decisions; captured Clari risk usage patterns; gathered requirements from Sales Leaders, AEs, SEs, Deal Desk, Legal, Finance, and IT/Identity.
• Design: Defined the review brief template and per?stage variations; authored AI summarization prompts and guardrails; selected key Salesforce and Clari fields; designed decision log and action sync to Salesforce; set RBAC rules and counsel?only notes; outlined dashboards and audit logs; established change control for templates and fields.
• Build: Integrated Gong summaries and snippet links; connected Salesforce for opportunity, task, and activity data; pulled Clari risk and trend signals; configured the workspace UI and decision log; wired Slack/Teams reminders; enabled SSO roles, permissions, and immutable logs; set up dashboards and exports.
• Testing/QA: Ran in shadow mode alongside existing reviews; compared AI summaries to human notes; validated field mappings and action sync; exercised access controls and counsel?only notes; piloted with one region and deal desk cohort; tuned prompts, templates, and messages based on feedback.
• Rollout: Launched the workspace for scheduled deal desk meetings; added executive and regional reviews after stability; retained legacy prep decks as a monitored fallback early on; tightened access rules and made the decision log mandatory after cycles stabilized.
• Training/hand?off: Delivered quick guides for reps and managers on using the brief and decision log; trained deal desk coordinators on prep and exception handling; briefed Legal and Finance on counsel?only notes and approvals; updated cadences and SOPs; transferred ownership of templates and dashboards to Revenue Operations under change control.
• Human?in?the?loop review: Established recurring audits of AI summary quality, sensitive topic handling, and access exceptions; recorded decisions with rationale and effective dates; updated prompts, templates, and RBAC rules accordingly.

Results

Deal reviews became decisive. The team arrived with the same context—recent call themes, live CRM data, and risk signals—and used meeting time to choose pricing moves, align technical validation, and assign executive outreach. Notes converted into owned tasks in Salesforce, so follow?ups were visible and tracked without additional data entry.

Clarity and trust improved. Sensitive details from calls were viewable only by authorized roles, counsel?only notes stayed protected, and managers no longer asked for screenshots of disparate tools. Leaders saw which interventions moved risk trends, which teams needed coaching, and where escalations were warranted. The core stack stayed in place; the new layer stitched Gong, Salesforce, and Clari into a single, governed review flow.

What Changed for the Team

• Before: Prep decks varied and missed context. After: A standardized brief auto?compiled Gong summaries, CRM fields, and Clari risk signals.
• Before: Meetings rehashed facts. After: Reviews focused on decisions, with a clear decision log and owned actions.
• Before: Call links and sensitive notes were shared inconsistently. After: Role?based views protected excerpts and counsel?only notes.
• Before: Follow?ups lived in email. After: Actions synced to Salesforce tasks with owners and due dates.
• Before: Risk signals were referenced sporadically. After: Clari indicators and trends sat next to the deal, prompting targeted interventions.
• Before: Little visibility into impact. After: Dashboards showed outcomes, action completion, and risk movement by team and region.

Key Takeaways

• Bring signals together; put call insights, CRM context, and risk indicators in one workspace.
• Standardize the brief; a consistent template reduces prep time and closes common information gaps.
• Decide in the room; capture decisions and owners in a structured log that syncs to the CRM.
• Protect sensitive content; use role?based access and counsel?only notes to keep governance intact.
• Measure impact; track how interventions affect risk and momentum to coach and prioritize.
• Integrate, don’t replace; keep Gong, Salesforce, and Clari—add the review workflow and governance between them.

FAQ

What tools did this integrate with? The workspace pulled conversation insights and links from Gong, opportunity and account data from Salesforce, and risk and forecast context from Clari. Notifications ran through Slack or Microsoft Teams, and access was enforced via SSO with role?based controls aligned to NIST RBAC.

How did you handle quality control and governance? The review template, summary prompts, and RBAC rules lived under Revenue Operations change control with owners and effective dates. Every summary, view, decision, and sync wrote to immutable logs. Counsel?only fields protected privileged notes, and periodic audits tuned prompts and access rules based on observed issues.

How did you roll this out without disruption? The workspace ran in shadow mode during existing reviews. Teams compared the auto?compiled brief to their prep decks, then switched once accuracy and access controls proved reliable. Legacy decks remained as a monitored fallback early on and were retired after stable cycles.

How were call summaries generated and accuracy ensured? Summaries drew from Gong transcripts and markers for key moments. Prep owners reviewed highlights before the meeting, could attach time?stamped snippets, and corrected misclassifications. Feedback loops updated prompts and topic detectors to improve future summaries.

How did you protect sensitive information and privacy? Role?based views limited who could see call excerpts and counsel?only notes. Notifications contained minimal detail and linked back to the workspace. Access and exports were logged, and retention followed records policy and legal guidance.