The ai-native sales leader webinar recap
A recap of our latest webinar with Laura Keith, CEO of Hive Learning and Hive Perform.
Most sales teams have more data than they know what to do with. Call recordings, CRM entries, email threads, outbound activity; it's all there. So why do so many enablement teams still struggle to move the needle on revenue?
That was the central question Laura Keith tackled in our recent webinar, "The AI-Native Sales Leader." Laura has spent years rethinking how sales enablement works in an AI-driven world. Her conclusion: the problem is the gap between data and action.
The Moment That Changed Everything
Laura shared a turning point from her own career. She had just pitched her AI-powered sales training product to a former boss and felt confident going in. His feedback stopped her cold.
He told her he couldn't use what she was selling because she hadn't diagnosed his actual problem. He didn't know if he had a messaging issue, a skills gap, a pricing problem, or a process breakdown. And without that diagnosis, no technology could fix it.
That conversation sent Laura back to square one. She asked herself: if I let go of everything I've been doing for 20 years and rebuild from scratch, what would that look like?
The answer became a three-layer system that she believes is the foundation of truly AI-native enablement.
The Three-Layer System
Layer 1: Data
This is your starting point. Pipeline data, win rates, call recordings, email activity, deal stage timing, etc. Most teams already have access to this. If your CRM hygiene is poor, that's your first fix. Otherwise, the data layer gives you the raw material to work with.
Layer 2: Diagnosis
This is where most teams fall short. Looking at broad numbers like conversion rates is not the same as understanding why they're dropping. Is it one rep struggling with discovery? A group of newer sellers who aren't looping in legal and finance early enough? A top performer quietly discounting at the close?
Every seller has a different set of challenges. A one-size-fits-all training rollout might produce one good quarter, but it won't create consistent improvement over time. Individual diagnosis does.
Layer 3: Intervention
Once you know the specific problem for a specific person, designing the right support becomes much more straightforward. Targeted coaching, focused one-on-ones, or call reviews can all be pointed at the right issue instead of thrown at the whole team.
The Context Layer: The Missing Piece
One of the most practical parts of the conversation came from a question about Claude and AI tools running wild with bad data. Laura's answer introduced what she calls the "context layer."
Before an LLM like Claude can diagnose anything accurately, it needs to understand what "good" looks like inside your specific organization. Your pitch, your pricing, your competitive positioning, your sales methodology, your process frameworks. All of it needs to live in one accessible place that the AI reads from every time.
Without that context layer, you get inconsistent outputs and, worse, reps making decisions based on filtered or incomplete data. With it, you get a quality assurance layer baked into every interaction.
The context layer also needs to stay current. New product features, new competitors, updated positioning; all of it needs to flow back into that foundation so the system keeps learning.
A Real-World Example
Laura walked through a case study with a fast-scaling SaaS company called Phosphor. They connected their call recording software and HubSpot to a well-built context layer, then ran individual coaching initiatives for each rep over a rolling month.
The results after six months: reps went from handling 15 MQLs per month to 22, SQL-to-close rates climbed from 60% to above 80%, and revenue per rep more than doubled.
The Simple Test
Laura closed with a question worth asking your own team: if you removed all the AI tools you're currently using, would reps just do their jobs a little slower? If the answer is yes, AI is still a bolt-on. When the diagnostic and coaching loop disappears without it, you're getting somewhere real.