Customer story
Sprout Social
How Sprout Social gave its revenue team one place to find everything. $3M annual value · 36,000+ hours reclaimed · 95% close rate pattern discovered · 30× ROI
Sprout Social's revenue team had no shortage of tools. BDRs, AEs, and customer success managers worked with Highspot for content, Gong for conversation intelligence, and Salesforce for CRM — a best-in-class stack by any measure. Shannon O'Donnell, Sprout's AI and Sales Enablement Lead, wasn't looking to replace any of it.
The problem was simpler and more persistent. Every time a rep needed to prep for a customer call, answer a competitive question, or find the right customer story for a specific industry, they had to open five to eight different tabs, search each system separately, and manually stitch together fragments that had no way of talking to each other. The information existed. Getting to it was the tax.
For a $457 million company with 31,000+ customers and a global revenue organization, that tax was enormous — and largely invisible, because it was distributed across thousands of small moments every day.
Eight systems. One conversation.
In August 2023, Sprout partnered with Tribble to solve the accessibility problem without touching the underlying systems. The goal wasn't to consolidate tools — it was to put a single conversational layer on top of all of them.
Tribble connected Salesforce, Gong, Highspot, Google Drive, and internal documentation behind one interface in Slack. A rep preparing for a customer call could pull past account conversations, relevant customer stories by industry, competitive positioning, recent product updates, and pricing context in a single query — without leaving the place they already worked.
Shannon had been experimenting with ChatGPT for sales enablement before this, but ran into the walls every enterprise AI effort eventually hits: IT security concerns, no access to internal systems, and outputs generic rather than grounded in Sprout's actual customers, competitors, and institutional knowledge. Tribble solved all three from day one.
Within months, the platform had processed over 20,000 prompts. BDRs used it for account research. AEs pulled customer stories on demand. Managers inspected pipeline. Customer success teams prepped for renewals. None of it was mandated. Reps adopted it because finding an answer in Slack in thirty seconds was better than reconstructing it manually across eight tabs.
Sprout's revenue organization named it the most adopted AI tool in the company.
"We recognized $3 million in annual value from a $100K investment. When we had to decide what stayed in the budget, Tribble made the cut." — Shannon O'Donnell, AI and Sales Enablement Lead, Sprout Social
Putting a number on it
By October 2025, Shannon and Tribble's Customer Success lead analyzed 90 days of usage data to answer a direct question from Sprout's CEO: what's the actual business impact?
| Interaction Type | Previous Workflow | Time Saved |
|---|---|---|
| Knowledge retrieval | 5–8 tabs across Drive, Confluence, Highspot | 5 min per instance |
| Salesforce data access | Deal context, contacts, account history | 8–20 min per lookup |
| Content creation | Slides, email templates, customer stories | Editing vs. authoring from scratch |
| Meeting intelligence | Gong transcripts + Salesforce opportunity data | Cross-system synthesis |
| TOTAL ANNUAL VALUE — 36,000–51,000 hours reclaimed at $80/hr | $3M+ | |
The conservative calculation, adjusted for retry rates and learning curves: 36,000 to 51,000 hours reclaimed annually. Over $3 million in productivity value from a $100,000 investment. 30× ROI.
The pattern no one had seen
The productivity numbers were significant. The more important discovery came from somewhere else.
While connecting deal data across Salesforce, Gong, and rep activity logs, Tribble surfaced something no human analyst had identified: deals with three specific attributes closed at a 95% rate. The data had always existed. It was invisible because no one had ever been able to look across all three systems simultaneously at scale.
That finding changed how the team thought about what they were building. Shannon started asking strategic questions: which customer stories were moving enterprise deals, what objections were most common in lost opportunities, where the gaps were between top performers and the rest of the team. The platform wasn't just saving time. It was producing intelligence the revenue organization had never had before.
Built for each persona
Shannon built out custom workflows for each team — designed around the specific information need of each role.
| Persona | Workflow | What it surfaces |
|---|---|---|
| BDR | One-click account research | LinkedIn data, news, financials, past interactions — in seconds |
| AE | Customer story generator | Industry and use case filtered, approved logos and messaging only |
| Manager | Pipeline inspection | At-risk deals from activity patterns and MEDDPICC gaps |
| CSM | Meeting prep packages | Support history, product usage, renewal risk — combined automatically |
Usage grew because each persona experienced immediate, specific value — not because AI was a company initiative.
What comes next
Shannon is building automated workflows for MEDDPICC capture, pipeline risk assessment, and rep coaching insights — moving from a system that answers questions to one that surfaces recommendations before reps ask for them.
The company is exploring deeper analytics: which content drives the most engagement in late-stage deals, where knowledge gaps correlate with lost opportunities, and how AI usage patterns connect to individual quota attainment.
The 95% close rate discovery pointed toward a larger possibility — that the most valuable output isn't time saved, but patterns that change how a revenue organization decides to sell.