Early access Mash is live with a small group of early adopters. Apply for Early Access →
← All case studies

Case study · Rootly

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.

Rootly accelerates sales velocity and customer response times with Mash

  • 45%faster responses to customer inquiries
  • 50%less time on prospect research and proof-point prep
  • 15%faster onboarding for new GTM hires
  • Published: 4 March 2026
  • Industry: Incident management
  • Where it ran: Slack

About Rootly

Rootly is an AI-powered incident management platform built for high-growth, engineering-led organizations. It helps engineering, SRE and operations teams detect, manage, learn from and resolve incidents faster, with structure, automation and real-time coordination brought into Slack- and Microsoft Teams-native workflows.

As product complexity grew, knowledge became the bottleneck

Rootly was expanding into a multi-product platform in a fast-moving, competitive market, and the complexity of sales conversations rose with it. Each deal needed a deep technical understanding of how the products worked together, where Rootly fitted a customer’s needs, and how the platform mapped onto very different customer environments across a large and diverse addressable market.

New features were shipping faster than static documentation could follow. Knowledge lived in Slack conversations, internal threads, product updates and the heads of a few subject-matter experts. The consequences landed on every role:

  • Account executives needed fast, accurate answers to win competitive cycles.
  • Customer success managers needed reliable product detail to support customers.
  • Sales engineers had become the bottleneck for routine technical questions.
  • New hires took longer to ramp because product knowledge was not centralized.

Every specific product question was answered by hand, by some of Rootly’s most senior revenue people and product experts — sometimes including the company’s co-founders.

“As we’ve grown, the biggest bottleneck wasn’t pipeline – it was the flow of technical knowledge. Mash removes that completely.”
Andre King · VP of Sales, Rootly

What Mash built

Mash brought real-time product knowledge into Slack, where the revenue team was already spending its time searching for technical answers. Because Rootly is itself a Slack-native product, the fit was natural: Mash was deployed to capture evolving product knowledge and surface it instantly, without asking anyone to change how they worked.

The loop mattered as much as the answers. When Mash replied in a thread, a product expert could confirm or correct it right there, and that correction fed straight back into Rootly’s tuned knowledge engine. Knowledge had to be written once — in the Slack conversation where it came up.

A Slack thread. Chris asks why he keeps getting an error setting up a customer’s
        account, and whether similar customers have had the same issue with the feature. The Mash app
        replies underneath with an overview and four cited sources drawn from Slack, Notion, Google
        Drive and Salesforce, with a button to view the source detail.
A question answered in the thread it was asked in, with the sources it came from.
“Before Mash, every answer depended on my team responding. Now we get one accurate answer that’s always updating based on our conversations.”
Gideon Lapshun · Head of Support, Rootly

How Rootly used it

  • AEs researched prospects and pulled proof points during live sales cycles.
  • Product and technical questions were answered automatically in Slack, reducing the dependency on sales engineers.
  • Sales engineers validated or improved answers, reinforcing accuracy without slowing deals down.
  • Knowledge was written once — in the Slack conversation — and Mash kept learning from those interactions.

The results

Customer response times dropped by 45%. Reps stopped pausing conversations to say “let me get back to you” and answered detailed questions in the moment, even in competitive situations. New and existing reps had immediate access to accurate product context, which shortened onboarding and raised the technical credibility of every conversation.

Rootly reported two further numbers against that. Time spent on prospect research and proof-point preparation fell by 50% — AEs pulled proof points mid-cycle rather than assembling them beforehand — and new GTM hires reached productivity 15% faster, because the product knowledge they used to get from a colleague was answerable in the channel they were already working in.

“With Mash, all my reps are now product experts. We’re seeing meaningfully higher close rates with shorter deal cycles.”
Andre King · VP of Sales, Rootly

What Rootly and Mash did next

Rootly and Mash continued to deepen the engagement by:

  • Expanding Mash to additional GTM roles and Slack channels.
  • Capturing more nuanced product and customer knowledge.
  • Tightening feedback loops to further improve answer quality and coverage.

As Rootly scaled its platform and customer base, Mash was meant to remain the knowledge foundation that let every team member, from new hire to leadership, work with the same technical clarity, speed and confidence.

“Rootly is scaling fast. Mash is helping us do that — from ramping new hires quickly, reducing interruptions, and automating internal answers.”
Gideon Lapshun · Head of Support, Rootly

About Mash, as it described itself then

The paragraph below is how Mash described its own product during this engagement. It is reproduced for the record and does not describe what Mash is today.

“Mash is the Slack-native knowledge agent platform that helps complex and multi-product revenue teams get the information they need, when and where they need it. Designed for revenue teams, Mash’s platform automates answers, surfacing contextually relevant information, and managing complex organization workflows in real time. They are the foundation for bringing client, technical, product and tribal knowledge to the entire organization.”

Next: Triple Whale — Six knowledge tools, thirty minutes a question, and three or more people interrupted to answer it. Or see what Mash is today.