Case study · Triple Whale
Mash answered 65% of Triple Whale’s complex product and integration questions
From Mash’s knowledge-systems era, 2025 to early 2026. Before Mash became a Personal Relationship Manager, it built custom knowledge systems for a small number of technical B2B revenue teams: bespoke pipelines into each company’s own scattered sources, and answers delivered where those teams already worked. This is a record of that work.
It is not the product on sale today. What carried over is the engineering underneath — reading years of messy, scattered history and making it answer questions reliably. Mash now does that for the people in your own network instead of for a company’s product documentation. See what Mash is now.
- 65%+of difficult internal questions resolved without escalating
- 5 hourssaved per GTM person per month at full deployment
About Triple Whale
Triple Whale is an agent-powered intelligence platform for e-commerce brands, built on a fully managed data warehouse with proprietary identity resolution and tools for acquisition, conversion and retention. More than 35,000 brands used it at the time of this engagement.
The problem: the answer existed, and nobody could find it
Before Mash, someone on the Triple Whale GTM team with a technical or product question searched across Guru, Notion, Google Drive, Slack, Jira and both internal and external help-center material. That took around thirty minutes for a complex question — and more often than not still ended in an escalation.
New team members direct-messaged tenured colleagues or posted into large channels. Both routes interrupted the most experienced people in the business, at an estimated twenty minutes each, with an average of three or more people pulled in per question.
The compounding part: most of those answers already existed. The team estimated that sales engineers and solutions architects were repeating themselves on 90% or more of queries — answers already sitting in documentation, tickets, decks, bug reports or past conversations. The company was launching product faster than any one person could track alongside their actual job.
“I’ve spent 15-20 hours this week responding to technical questions from customers and other members of the sales team — and the majority of these had documentation and had already had an answer somewhere in one of our tools after I dug in for 30+ minutes.”
What had been tried
The team had run an incumbent knowledge-management system for two years, with active effort to keep it current. It was built on verified knowledge paragraphs, so every launch meant writing and re-verifying snippets across the product suite — a great deal of rework. It handled some high-level questions and failed on many pressing ones. Even “do we have an integration with Facebook/Meta” would miss.
What Mash built
Mash started with Triple Whale in January 2025. Rather than asking the team to curate clean source material, the approach was to embrace the mess and read the sources as they actually were.
The teams first identified the question types the platform could resolve directly and those that needed extending: product features, recent launch detail, integration and onboarding, demo and marketing material, and bugs affecting customers. From there they worked through which knowledge sources to connect and how to do it securely — some supported out of the box, others needing bespoke pipelines. Public web documentation, Jira, Notion, Readme, HubSpot and Google Workspace all went in.
Answers were delivered to account executives, account managers, sales engineers, solutions architects, support, product marketing and enablement.
The results
Q2 2025 was a hard quarter to test this in: the company was growing quickly and launching a completely redesigned platform to all its customers, which made knowledge dissemination and bug tracking harder, not easier. Triple Whale went ahead and widened Mash from the sales engineering team to the broader organization.
On the team’s own estimate, Mash was resolving more than 65% of the difficult internal questions it was asked — product capabilities, features, integrations, onboarding and technical issues — without an escalation. Against the thirty minutes a complex question used to take, plus the three or more colleagues interrupted at twenty minutes each, that came to an estimated five hours a month back per person on the GTM team at full deployment. Both figures are Triple Whale’s own estimates, made during the rollout rather than measured at the end of one: the deployment was still moving outwards from the sales engineering team when they were given.
“The initial results and continued improvement we’ve seen with Mash in ~5 months are leaps beyond what we’ve seen from other solutions over the course of multiple years.”
Next: Nevvon — State-by-state regulatory answers, on the call rather than after it. Or see what Mash is today.