How The Laurel Post-Sales Team Uses Sam's Conversation Intelligence and AI Sales Engineer
See how HeySam trains itself on Solution Engineering calls while delivering conversation intelligence—helping Laurel’s SEs save time and AMs delight customers
Laurel’s AMs relied too much on SEs, hurting scalability. Their call recorder was just a notetaker—never built for post-sales
SEs Stretched Thin: SEs sat through lengthy CS calls just to handle brief technical Q&A, draining valuable time
No SE Knowledge Base: As a fast-growing startup, most SE knowledge lived in calls, uncaptured and undocumented for enablementThey had plenty of AI notetakers, but needed call intelligence built for AI-native sales teams
Broken Call Intelligence: They lacked a way to gather deal insights across multiple calls, leaving insights scattered and missed
The Solution
They gave their AMs Sam to self‑serve technical knowledge, learned from shadowing their SEs, while delivering conversation intelligence Fathom and Gong couldn’t provide.
Tribal Knowledge Base
Like most startups, Laurel lacked a solid knowledge base. Sam built one by learning from the tribal knowledge their SEs shared on Slack and customer calls
AI Conversation Intelligence
Sam gave Laurel’s AMs call notes, automated follow‑ups, and AI‑powered Q&A spanning customer conversations across calls and Slack
Product Feedback, Supercharged
Sam helped Laurel automate the collection of product feedback, feature requests, and complaints across calls, turning scattered insights into actionable data
Scalable SE Ratio
With AMs and Sam handling routine calls, SEs reclaim 20% of their time, enabling a scalable AM:SE model
Watch the full video
“Given the ability to solve the crux of our original problem—scaling SEs—while also delivering an AI‑first call intelligence tool, it was a clear decision to explore HeySam”
Elliot Peterson
VP Customer Experience
I kept thinking
What if my call recorder also gave me sales enablement? It would capture my best SEs’ tribal knowledge—the stuff that never makes it to knowledge bases. That’s why I built Sam.
