The LeanScale Podcast · Episode 25

The End of Sales Guesswork

Christina Brady on how Luster diagnoses and predicts sales-team skill gaps before they erode revenue

Christina Brady · Co-Founder & CEO · Luster Hosted by Anthony Enrico
Published Updated 00:38:50 40 min read 8,051 words
Executive Summary

The one-paragraph brief, extended

Why this conversation matters — and who should spend the hour.

Christina Brady spent 18 years in go-to-market — a full-cycle AE who climbed into C-suite roles, and a trainer for 15 of those years, certified in seven methodologies and personally responsible for upskilling more than 30,000 revenue professionals. Luster, the company she co-founded and runs as CEO, is by her own description 'a culmination of my pain.' The pain is specific: as an operator she could watch KPIs decline, sales cycles stretch, and churn climb without ever being able to see, in advance, which reps were about to 'step in mud' on a call — and so, like everyone else, she made customers the collateral damage of a team whose competency she couldn't measure until after the deal was already lost.

Her core argument is that the enablement industry runs the sequence backwards. Tools that claim to be 'predictive' mostly extrapolate CRM data entered by sales reps — 'the furthest thing from analysts' — or grade past calls subjectively, then hand leaders a stale 'problem plop' months later. The alternative Brady builds toward is diagnosis before enablement: map every rep against an atomic skill matrix for each stage of the sales process, score proficiency objectively, and only then prescribe. She frames the status quo as a doctor who asks each patient to self-diagnose, treats everyone for the most common answer, and PIPs the ones who don't get better. Luster's loop is diagnose, predict, prescribe.

The middle of the episode is a live product tour. Luster ingests real customer conversations through Zoom and Teams integrations, proficiency-maps each rep at the skill level, and — connected to the calendar — scans upcoming meetings to warn a rep that tomorrow's discovery call is a revenue-impacting risk, then auto-schedules a tailored AI 'dress rehearsal' that mimics that exact call, even role-playing an AI version of the real person on the invite. It can generate custom battle cards, persona docs, and discovery questions per meeting; run full-call simulations or focused 'skill drills' (the golf metaphor: play a round, or just practice your swing); and send every manager a weekly per-rep coaching report that flags which calls a manager should personally join. Brady demos a generative cold-call sim with an AI buyer named 'Candice,' underlining that nothing is scripted and Luster treats 80–85% as the proficiency bar.

The back half turns to how it's built and why that matters. Brady contrasts 'quick tech' — a user interface bolted onto a shared LLM instance that ships fast and risks leaking customer context — with the 'platform' approach Luster chose: a per-customer, closed-off, trained instance sitting behind a proprietary trust-and-security layer she nicknames 'Pearl.' That architecture is model-agnostic (Luster can swap OpenAI, Claude/Anthropic, or any model on cost, performance, or security), let the company clear SOC 2 Type 1 and Type 2 plus a penetration test, and costs it the feature velocity she's willing to trade for stability. She was disciplined enough to turn down a $500K enterprise deal because the product wasn't yet enterprise-ready — refusing to let a big customer control her roadmap.

The final movement is the hiring and ramp use case, which Brady calls one of Luster's core plays. A bad go-to-market hire that turns over inside a year costs north of $300,000, and the best rep at one company is no guarantee at another — so run candidates through a role-calibrated simulation to get an objective pre-hire proficiency map, then use those gaps to drive prescriptive onboarding that, she says, has halved ramp times and given companies a real definition of 'ramp.' Crucially, she insists Luster is 'not a performance-management platform; it's meant to avoid performance management' — a safe place to make mistakes, try new talk tracks, and fail forward. Who should listen: sales and enablement leaders constrained by manager bandwidth, RevOps and revenue executives who own ramp and capacity plans, and founders building AI products who want a clear-eyed take on wrapper-versus-platform and data security.

Key Takeaways

12 things worth stealing

The load-bearing ideas, each with the business implication and who should care.

01

Diagnose before you enable — or you're just guessing

Brady's central thesis is that enablement without an objective diagnosis is wasted money. Most orgs skip straight to 'let's retrain everyone on everything,' because they never accurately measured what each rep is actually deficient in. Deploy learning or development against an unknown gap and it will not stick.

Why it matters: Stand up an objective proficiency diagnosis before you spend on training, consultants, or content. The order is diagnose, then prescribe — the reverse guarantees a low-adoption, one-size-fits-all program that treats everyone the same and helps almost no one.

Sales LeadersRevOps LeadersFounders
02

'Predictive' tools built on CRM data aren't predictive

Brady is blunt that most tools claiming prediction just extrapolate CRM data entered by reps — 'the furthest thing from analysts' — or grade past calls subjectively. Reps also can't self-report their own skill gaps; in thousands trained she never met one who could accurately name where they were losing deals.

Why it matters: Discount vendor claims of 'predicting revenue' from CRM fields. Real prediction requires objective proficiency signal captured from actual behavior, not self-reported pipeline data or retroactive call reviews.

RevOps LeadersRevenue ExecutivesSales Leaders
03

The 'problem plop' is why consultant-led skill audits fail

Best-in-class before Luster meant building competency maps in spreadsheets with no way to measure them, or paying a firm hundreds of thousands over three-to-four months to analyze the team on bad CRM data and interviews — then delivering the 'problem plop': last quarter's problem, with no mechanism to fix it, handed back to the same team that caused it.

Why it matters: A point-in-time audit is stale the moment it lands, especially in a scaling startup. Favor a continuous, self-serve diagnostic that also prescribes the fix over an expensive one-shot assessment.

RevOps LeadersSales LeadersFounders
04

Point-in-time prediction is the differentiator — train the gap 24–48 hours before it bites

Even a correct diagnosis fails if the timing is wrong: train a rep on a gap they won't face for two weeks and ~80% is forgotten. Luster scans each rep's proficiency map against calendared customer meetings and flags a revenue-impacting gap 24–48 hours out, then schedules practice right before the call so it ingrains.

Why it matters: Enablement value is a function of timing, not just content. Deliver the right micro-practice immediately before the moment of use rather than in a quarterly training block.

Sales LeadersRevOps Leaders
05

Measure proficiency at the atomic skill level, per role and stage

Luster breaks the diagnostic down to the specific critical skills a rep must master at each stage of that org's sales or support process, customizable per role — not high-level feedback. It snapshots the whole team's proficiency and drills to an individual score so a manager knows exactly what to coach.

Why it matters: Build a skill matrix specific to your process and roles, then measure against it. 'Ask more questions' is uncoachable; 'your discovery pain-funnel proficiency is 62%' is.

Sales LeadersRevOps Leaders
06

An auto-scheduled AI dress rehearsal removes the manager bottleneck

The binding constraint on most enablement is the bandwidth of the management team. Luster lets a rep self-serve: get an independent assessment from prior-call data, then practice a simulation that mimics tomorrow's call — even against an AI persona scraped from the real attendee's metadata — with no one else required. Managers can't role-play a buyer persona they've never been anyway.

Why it matters: You can enable a 10-, 20-, or 30-rep team without proportionally scaling manager or enablement headcount. Route the repetitive rehearsal work to the tool and reserve human coaching for judgment.

Sales LeadersRevOps LeadersRevenue Executives
07

Two ways adults learn: full-call sims and skill drills

Rooted in behavioral and cognitive psychology, Luster offers full-call simulations (prospecting, discovery, QBR, proposal, negotiation) and isolated skill drills with a built-in AI coach that keeps throwing objections, product questions, or security questions. Brady's golf metaphor: play a whole round, or just practice your swing.

Why it matters: Design practice for both modes — end-to-end reps for flow and confidence, and targeted drills for the one objection or skill a rep keeps biffing. One without the other leaves gaps.

Sales LeadersRevOps Leaders
08

Build a platform, not a GPT wrapper — data isolation is the moat

Brady contrasts 'quick tech' (a UI on a shared LLM instance that ships fast but leaks context and can't guarantee latency or security) with a 'platform' where every customer gets their own trained, closed-off instance behind a proprietary trust-and-security layer. Luster never shares customer data with the LLM, which is how it cleared SOC 2 Type 1 and Type 2 and a pen test.

Why it matters: For AI products handling sensitive data, the durable advantage is architecture and data isolation, not feature speed. Expect to trade some velocity for a build you can fully control and secure.

FoundersRevenue Executives
09

Be model-agnostic so you can swap LLMs on cost, performance, or security

By building custom layers on top of the model rather than being 'stuck on' one provider, Luster can swap OpenAI, Claude/Anthropic, or any LLM without impacting the core product — abstracting the fast-moving model layer behind its own stack ('Pearl').

Why it matters: Don't hard-wire your product to a single foundation model. An abstraction layer lets you ride each model's improvements and renegotiate on price, reliability, and security as the market moves.

FoundersRevenue Executives
10

Hire on objective proficiency — a bad GTM hire costs $300K+

The average cost of a frontline revenue hire who turns over within a year is over $300,000, and sales reps are good at selling themselves — the best rep at one company isn't guaranteed to be the best at yours. Run candidates through a role-calibrated Luster simulation to get an objective pre-hire skill map, which also protects you from HR risk on the no-hire decision.

Why it matters: Replace gut-feel interviews and role-plays with a measurable proficiency benchmark. You de-risk the hire and, for those you do hire, walk in already knowing their gaps.

Sales LeadersRevOps LeadersRevenue Executives
11

Prescriptive onboarding halves ramp — and finally defines what 'ramp' means

Instead of one-size-fits-all onboarding, Luster meets a new hire 'back at their desk' and up-levels them on their specific deficiencies while classroom training covers product. Managers know from day one where to coach and which calls to join. Brady says this has cut ramp times in half and lets companies actually measure and standardize ramp.

Why it matters: If you're heading into a heavy hiring year for AEs, SEs, SDRs, and CS, tie onboarding to each hire's diagnosed gaps and instrument ramp as a measurable curve rather than a number six people guess at differently.

Sales LeadersRevOps LeadersFounders
12

It's not spyware — make it a safe place to fail forward

Brady insists Luster is 'not a performance-management platform; it's meant to avoid performance management' for reps who belong at your company. The pitch to reps: make your mistakes here, try new talk tracks, do weird stuff, fail — the alternative is being measured only after performance has already declined and you're on a PIP. Teams even share their worst calls and laugh, building a culture of learning.

Why it matters: Position practice tooling as a rep benefit — self-coaching to hit quota and make more money — not surveillance. The right reps embrace an objective, private space to improve; framing it as spyware kills adoption.

Sales LeadersRevOps Leaders
Frameworks Discussed

6 named models

Every framework Jimmy names, defined and time-stamped.

Diagnose, Predict, Prescribe

11:50

Luster's core operating loop: first diagnose proficiency at the atomic skill level, then predict where a lack of proficiency is about to impact performance in the next 24–48 hours, then prescribe the specific practice or content to close that gap in real time.

It inverts the industry default of prescribing training first. Diagnosis makes the enablement accurate; the point-in-time prediction (scanning calendared meetings against the proficiency map) makes it stick, since a gap trained two weeks early is ~80% forgotten.

Diagnosis Before Enablement

06:37

The principle that you must objectively measure a team's competency gaps before deploying any learning, development, or training — otherwise the enablement is a waste of time and money.

Brady dramatizes the status quo as a doctor who asks patients to self-diagnose, treats everyone for the most popular answer, and blames the ones who don't improve. Sales orgs do the same by relying on rep self-reporting and then training everyone the same.

The Problem Plop

04:58

The failure mode of the consultant-led skill audit: after three-to-four months and hundreds of thousands of dollars analyzing the team on poor CRM data and self-reported interviews, the firm 'plops' a diagnosis with no mechanism to fix it — and it's already last quarter's problem.

It captures why one-shot, subjective assessments don't work in scaling companies: the data is bad, the finding is stale on arrival, and the same team that created the gap is left to close it with no tools.

Two Ways Adults Learn (Full Calls vs. Skill Drills)

15:10

Grounded in behavioral and cognitive psychology, Luster offers two practice modes: full-call simulations that mimic an entire sales conversation (prospecting, discovery, QBR, proposal, negotiation), and isolated skill drills with a built-in AI coach that repeatedly tests one skill such as objection handling.

The golf metaphor: you can play a whole round or just practice your swing. Full sims build flow and confidence; drills hone the specific skill a rep keeps missing. Adults need both.

Quick Tech (GPT Wrapper) vs. Platform Approach

19:53

Two ways to build an AI product. 'Quick tech' is a user interface layered on a single shared LLM instance — fast to demo, but unable to control data sharing, latency, or per-customer context. The 'platform' approach builds a trained, closed-off instance per customer behind proprietary layers, trading feature speed for control, security, and stability.

Luster deliberately chose the platform path and launched later than point-solution competitors, but with a more robust, secure, model-agnostic product. Brady's view: companies want the most stable tool, not the fastest one.

Pearl — Luster's Layered Discourse Engine

24:19

Luster's proprietary stack that sits between the raw LLM and the user interface. Layered bottom-up: a per-customer trust-and-security layer, a custom ingestion model of the org's people and behavior, a company-specific insights/persona/goals layer trained on first-party plus third-party web data, a conversational-AI layer (latency, personality, context), and an output layer of predictive skill insights and prescribed actions.

This is the 'everything in between' that separates a platform from a GPT wrapper. It isolates each customer's data, hardwires call goals so sims are measured properly, and makes the model swappable underneath.

Best Quotes

15 lines worth clipping

Pulled verbatim. Copy or share any of them.

“We make our customers collateral damage to our inability to really measure the competency of our team and address a lack of competency before it erodes your revenue.”
Christina Brady 01:19
“So many tools advertise the fact that they are predictive. They're like, we're gonna predict your revenue. I'm like, no, you're not — because you're using CRM data, which is input by sales reps who are the furthest thing from analysts.”
Christina Brady 02:34
“That would be like a doctor saying, I've heard your symptoms, what do you think your diagnosis is? And the patient's like, oh, I don't know. And they go, interesting, and write it down.”
Christina Brady 05:27
“Then you get what I call the problem plop: you plop the problem and say, based on research constructed on poor data and self-reporting, this is the problem that you have. So welcome.”
Christina Brady 04:58
“We diagnose, we predict, and then we prescribe the solution.”
Christina Brady 11:50
“We'll look at your map and say, hey, based on that discovery call you have tomorrow, you're about to make a revenue-impacting mistake. So we're gonna custom-create a practice session that mimics that call and proactively schedule it on your calendar.”
Christina Brady 11:15
“To use a golf metaphor, you can either play an entire round of golf or you can just go and practice your swing.”
Christina Brady 15:43
“This is not a scripted conversation. This is true generative AI. So every conversation is going to be different.”
Christina Brady 17:39
“We're not built on OpenAI and stuck on OpenAI. We're not built on Claude or Anthropic and stuck on them. We can actually swap that out, which is really nice because we can be dynamic.”
Christina Brady 25:21
“At the end of the day, what companies want is not the fastest tool, but the one that's gonna be the most stable.”
Christina Brady 22:11
“The cost of a bad hire that turns over within one year is over $300,000 — and it's probably larger than that.”
Christina Brady 31:51
“Luster is not meant to be a performance management platform. It is meant to avoid performance management for reps who should be at your organization.”
Christina Brady 35:34
“Make your mistakes in Luster, try new talk tracks here, do weird stuff here, fail.”
Christina Brady 35:34
“Sometimes we don't have the time to stop and take the pebble out of our shoe because we have to keep running the marathon. So let's not get to the finish line with bloody feet.”
Christina Brady 29:51
“When we're inside doing revenue operations for high-growth VC-backed startups, we say it all the time: the growth model is won or lost on hiring and enablement.”
Anthony Enrico 37:57
Practical Advice

What should you actually do?

The playbook, split by the seat you sit in.

Sales Leaders

  • Diagnose before you enable: get an objective, atomic-skill proficiency map of the team before you spend a dollar on training, or you'll retrain everyone on everything and change nothing.
  • Deliver practice at the point of use — a tailored dress rehearsal 24–48 hours before the actual call — because a gap trained two weeks early is ~80% forgotten.
  • Use both practice modes: full-call simulations for flow and skill drills for the specific objection or competency a rep keeps missing.
  • Frame the tool as a rep benefit, not spyware — a private place to make mistakes and self-coach toward quota — so adoption is organic.

RevOps Leaders

  • Stop trusting rep self-reporting and stale CRM-based 'skill audits'; the diagnostic has to be objective and continuous, not a one-shot 'problem plop.'
  • Instrument ramp as a measurable proficiency curve so 'what's our ramp time?' has one answer, not six.
  • Free manager bandwidth by routing repetitive rehearsal and coaching-report generation to tooling, reserving human time for judgment calls.

Revenue Executives

  • De-risk hiring with an objective pre-hire proficiency simulation — a bad GTM hire that churns within a year costs $300K+, and interview performance doesn't predict on-the-job performance.
  • Tie onboarding to each new hire's diagnosed gaps to cut ramp; generic onboarding wastes the fastest-decaying window of a new rep's tenure.
  • In a heavy hiring year, make enablement and ramp a top-of-plan capacity input, not an afterthought.

Founders

  • If you handle sensitive customer data, build a platform with per-customer data isolation, not a GPT wrapper on a shared instance — it's how you clear SOC 2 and pen tests and win enterprise trust.
  • Abstract the model layer so you can swap LLMs on cost, performance, and security instead of being stuck on one provider.
  • Be honest about your product's current fit and say no to deals you're not ready for — Brady turned down a $500K deal rather than let a big customer control her roadmap.
AI Takeaways

How AI actually changes GTM

LeanScale's signature read on the AI-in-GTM question this episode wrestles with.

The thesis

AI sales-enablement is only as good as its diagnosis and its data isolation. The durable product is not a fast UI on a shared model — it's a secure, per-customer, model-agnostic platform that objectively measures proficiency and prescribes practice at the exact moment of need.

Predictive ≠ CRM regression

Most 'predictive' tools extrapolate rep-entered CRM data or grade past calls subjectively. Real prediction needs objective proficiency signal from actual behavior, mapped to upcoming calls on the calendar.

Wrapper vs. platform

A UI on one shared LLM instance ships fast but can't guarantee data isolation, latency, or per-customer context. Luster builds a closed, trained instance per customer behind a proprietary layer ('Pearl').

Model-agnostic by design

Abstracting the LLM behind a trust-and-security layer lets Luster swap OpenAI, Claude/Anthropic, or any model on cost, performance, or security without touching the core product.

Latency as a feature

Luster measures each user's natural human latency and tunes the model to it, so simulated calls feel like real conversations instead of a one-size latency set product-wide.

Data isolation is the enterprise gate

Never sharing customer data with the LLM is how Luster cleared SOC 2 Type 1/2 and a pen test. In this category a breach is catastrophic, so architecture beats feature speed.

Agent & automation ideas

  • Proficiency-diagnosis agent that maps every rep to an atomic, per-stage skill matrix from recorded Zoom/Teams calls and outputs an objective team and individual score.
  • Calendar-watching agent that scans upcoming meetings, flags a revenue-impacting skill gap 24–48 hours out, and auto-schedules a tailored AI dress rehearsal that mimics that exact call.
  • Meeting-prep agent that scrapes meeting metadata plus third-party web data to generate a custom battle card, buyer-persona doc, and discovery-question list per call.
  • Weekly manager-coaching-report agent that summarizes each rep's proficient and deficient skills with concrete examples and flags which calls the manager should personally join.
  • Hiring-screen agent that runs candidates through a role-calibrated simulation to produce an objective pre-hire proficiency map and de-risk the hire.
Operations Takeaways

By function

The same conversation, filtered for RevOps, pipeline/marketing ops, and customer ops.

Revenue Operations

  • Diagnosis before enablement. Objectively measure atomic-skill proficiency before spending on training; skipping the diagnosis guarantees low-adoption, one-size-fits-all enablement.
  • Kill the 'problem plop'. Replace stale, consultant-led, CRM-based skill audits with a continuous diagnostic that also prescribes the fix in real time.
  • Instrument ramp. Turn 'ramp' from a number six people guess at differently into a measurable proficiency curve you can standardize and manage.
  • Scale enablement without scaling headcount. Route repetitive rehearsal and coaching-report generation to tooling so a thin management team can enable a large field.
  • Objective hiring signal. Use a role-calibrated pre-hire simulation to measure competency before an offer — cheaper than a $300K+ bad hire and safer from an HR standpoint.
Metrics Mentioned

The numbers, with context

18 years
Christina Brady's GTM tenure

From full-cycle AE up through multiple leadership and C-suite roles across technology.

15 years, 7 methodologies
Training experience

Certified trainer across seven sales methodologies.

30,000+
Professionals trained

Revenue professionals Brady has personally trained and upskilled.

~12% max
Traditional training adoption

Brady spent hundreds of thousands on training at prior orgs for at best ~12% adoption — if it could even be measured.

~80% forgotten in 2 weeks
Skill decay after training

Train a rep on a gap they won't use for two weeks and ~80% is gone — why point-in-time practice matters.

80–85%+
Luster proficiency bar

The score range Luster treats as demonstrated proficiency on a skill or full call.

>$300,000
Cost of a bad GTM hire

Average cost to the business of a frontline revenue hire who turns over within one year.

$500K ARR / ~1,000 reps
Enterprise deal declined

Brady turned down the deal because the product wasn't yet enterprise-ready and she refused to let it control her roadmap.

Cut in half
Ramp time impact

Prescriptive, gap-based onboarding via Luster has halved ramp times, per Brady.

July 2024
Launch

Luster launched, deliberately not enterprise-ready at first, then built up the infrastructure.

SOC 2 Type 1 & Type 2, passed pen test
Security posture

Achieved by custom-building a closed instance per customer and never sharing customer data with the LLM.

Entities

Companies, people & tools mentioned

Auto-extracted and linked into the knowledge graph.

Companies

People

Tools & software

ZoomVideo Conferencing

One of Luster's two core call integrations; Luster ingests prior Zoom conversations to proficiency-map reps and grades live customer calls after they happen.

Microsoft TeamsVideo Conferencing / Collaboration

Luster's other core call integration alongside Zoom; together they 'pretty much cover all of that' for pulling in and grading customer conversations.

LinkedInSocial Platform

Surfaces both as a demo signal (an AI buyer 'paying attention to AI enablement tools on LinkedIn') and as a way to reach Christina and Luster's go-to-market team.

Frequently Asked Questions

Straight answers

Generated from the conversation, marked up for search and AI extraction.

What does Luster do?

Luster is a predictive sales-enablement platform built by Christina Brady. It diagnoses a rep's proficiency at the atomic skill level for each stage of the sales process, predicts where a lack of proficiency is about to cause a revenue-impacting mistake in the next 24–48 hours by scanning calendared customer meetings, and prescribes tailored AI practice — including auto-scheduled dress rehearsals, battle cards, and personas — to close the gap before the call happens.

Why isn't CRM data enough to predict rep performance?

Because CRM data is entered by sales reps, whom Brady calls 'the furthest thing from analysts,' and reps generally can't accurately self-report their own skill gaps. Tools that claim to predict revenue from CRM fields or subjective past-call reviews are extrapolating unreliable, self-reported data. Real prediction requires objective proficiency signal captured from actual behavior and mapped to upcoming interactions.

What does 'diagnosis before enablement' mean?

It's the principle that you must objectively measure what each rep is deficient in before deploying any training, or the enablement will be wasted. Brady likens the status quo to a doctor who asks patients to self-diagnose, treats everyone for the most common answer, and blames the ones who don't improve. Luster diagnoses first, then prescribes, so training is specific to each rep rather than one-size-fits-all.

How does Luster's AI dress rehearsal work?

Luster continuously scans a rep's proficiency map and connects to their calendar. When it sees a meeting the rep isn't proficient enough for — say tomorrow's discovery call — it warns them of a likely revenue-impacting mistake, custom-creates a practice session that mimics that specific call (even role-playing an AI version of the actual attendee scraped from meeting metadata), and schedules it on the rep's calendar so they rehearse right before the real conversation.

What is the difference between a 'GPT wrapper' and Luster's platform approach?

A GPT wrapper is a user interface built on top of a single shared LLM instance — quick to demo but unable to fully control data sharing, latency, or per-customer context, with all customers added to one instance. Luster's platform builds a separate trained, closed-off instance for every customer behind a proprietary trust-and-security layer, never shares customer data with the LLM, and can swap the underlying model. It trades feature speed for control, security, and stability.

How does Luster help with hiring and ramp?

Candidates run a role-calibrated Luster simulation to produce an objective pre-hire proficiency map, so you can measure whether they walk in with the critical skills for the role — reducing the risk of a bad hire, which costs over $300,000 when it turns over within a year, and providing HR-safe documentation for no-hire decisions. For those you hire, Luster drives prescriptive onboarding against their diagnosed gaps, which Brady says has cut ramp times in half.

Is Luster a performance-management or surveillance tool?

No. Brady is explicit that Luster is 'not meant to be a performance management platform; it is meant to avoid performance management' for reps who belong at your company. It's designed as a private, safe space to make mistakes, try new talk tracks, and fail forward before a rep is in front of a real customer — a rep benefit for self-coaching to quota, not spyware.

How does Luster keep customer data secure?

Luster custom-builds a closed, trained instance for each customer and never shares that customer's information with the large language model. Its architecture puts a per-customer trust-and-security layer between the model and the product. This is how the company achieved SOC 2 Type 1 and Type 2 clearance and passed a penetration test, at the cost of moving less quickly on new features.

Full Transcript

The whole conversation

Broken into chapters, searchable, verbatim from the audio. Speakers inferred (not diarized).

00:00Meet Christina Brady & the origin of Luster

0:00 (logo whooshing) - Christina, thank you so much for being here. Really excited. We have the co-founder, CEO of Lustre here to walk us through the product. I think what you've built is absolutely incredible. I can see a lot of use cases we could have at LeanScale and any go-to-market team, scaling a sales team, any one customer facing, this is an incredible platform. So I'm curious, I think, I always love to kick these off. What gave you the inspiration to start Lustre? And what gave you the courage to get it going and bring it to where you are now? - Yeah, first, thank you and thank you for having me. That kind of feedback makes my go-to-market heart

0:39 very, very happy 'cause that's what I wanted to build. And I would say this company is sort of a culmination of my pain (laughs) and making sure that nobody else has to feel it again. And so if you look at my background, I spent the last 18 years of my career in go-to-market. So I started my career as a full cycle AE, worked my way up to multiple different leadership positions, some C-suite positions across technology. I've also been a trainer for the last 15 years, so I'm trained and certified in seven different methodologies, I know. - Oh, wow. - I know, it's wild. And I've been lucky enough to train and upskill over 30,000 revenue professionals.

01:19Customers as collateral damage: the competency blind spot

1:19 And the one thing that was very, very clear, not only as I was working with individuals, but also being an operator at various organizations, is this idea that we make our customers collateral damage to our inability to really measure the competency of our team and address a lack of competency before it erodes your revenue. And that's how every single go-to-market function. And that was frustrating for me to constantly feel like I was behind the eight ball, I couldn't see the proficiency of my team, my KPIs are declining, the sales stages are increasing, churn is going up, and then we look and we say, what's going on, what's happening,

1:59 who's the problem, is it the person, is it the product, is it our ICP, is it a lack of product market fit? I don't know. And so you go through this reactive fire drill exercise where then you say, you know what, I know what we'll do, we'll just retrain everybody on everything. And then that will work. And then we stay in this tumble cycle. And so I said, there has got to be a way for me to identify that my team was gonna step in mud on these calls or these processes. Like, how did we not know that we were gonna biff that deal until after it happened? How did we not know that? So I started looking for technology

02:34Why 'predictive' CRM tools aren't actually predictive

2:34 that would allow me to be predictive instead of reactive. And it didn't exist. And what's crazy is so many tools advertise the fact that they are predictive, right? They're like, we're gonna predict your revenue. I'm like, no, you're not. You know why? Because you're using CRM data, which is input by sales reps who are the furthest thing from analysts. I know because I was one and I've managed hundreds of them. So, okay, we could use their subjective data to try to identify their proficiency gaps. But of the thousands of people I've trained, I've yet to meet a single revenue professional that is like, no, I'm actually keenly aware

3:12 of these skill gaps that I have and where they're impacting my performance. And I know exactly what I have to do to overcome that, right? Like that level of awareness doesn't exist. And so using things like CRM data or previous customer calls to subjectively identify where you're going wrong is just a non-starter. And so there wasn't a tool that did this. And I said, I have to build one. And then I look at my background and I was like, I'm probably one of the people best positioned to do that because I've lived this pain for so long, but I've also seen what works to up level people and why the tools that exist today

03:45Best-in-class before Luster: skill matrices & the 'problem plop'

3:45 are just inherently broken or incomplete. So that's the long and short of just kind of why I said, okay, I'm gonna do it. - Yeah, that's really interesting. And like you said, you're an expert in this. So that goes a long way. What was best in class process before Lustre? I always like to get into like what the comparable was in the market. - Right, because the, I mean, before you go into that, it's kind of a two-sided coin. One, do the people know what their skill gaps are? And then in order to bridge the gap, it's a massive burden on the organization to do training and role-playing and making sure that, and do they even have the skills to train properly?

4:27 That's a big part of it too. - It's not their fault that they don't. The best, what best in class looked like, and I've seen this done and I participated in it probably hundreds of times, is first we say, okay, we have to skill matrix the entire team. So we're either gonna do that ourselves internally in spreadsheets. So first we're gonna get together and we're gonna build our own competency maps based on what good looks like. And we're gonna have no way to measure those, but we're gonna put them on paper, or we're gonna hire a firm to come in and spend hundreds of thousands of dollars for them to come in and they're gonna analyze our team.

4:58 They're gonna analyze our team on CRM data and previous customer conversations and interviewing the sales reps, which would be the same way that you would do it if you wouldn't hire somebody from the outside. This process would take probably three or four months, and then you would get what I call the problem plop, which is you plop the problem and you say, based on the research that we did, which was constructed on poor data and self-reporting, this is the problem that you have. So welcome. And then you go, okay, first of all, that was the problem that we had four months ago, but if you're working in any kind of scaling startup,

5:27 it's probably not the problem that you have anymore, but then you're still left with now what do we do about it? Because the same team that caused these problems is now tasked with no way to actually be able to overcome them. And so inherently we rely on asking the revenue professionals what they think their competency gaps are. That would be like a doctor saying, yeah, I've heard your symptoms, what do you think your diagnosis is, right? And the patient's like, oh, I don't know. I mean, I think maybe this, and they go interesting, and they write it down, and then they say, okay, you can go. And the patient goes, well, what about my treatment?

6:02 And they say, well, what I'm actually gonna do, I'm gonna ask every patient that I have today what they think their diagnosis is, and then based on the most popular answer, we'll just treat all of you as if you have that, right? And the 10% of you where that is actually an issue, you might get better. The rest of you are gonna get worse, and then you know who's gonna get blamed for that? The sales rep that you now put on a PIP because you never properly diagnosed them, and then prescribed them based on their needs. And so the way that we've done it before, the diagnostic is completely missing. Predicting where the diagnostic

06:37Diagnosis before enablement

6:37 is about to erode your revenue, completely missing. The prescription of what you specifically need to not make those mistakes in erode revenue, completely missing. We just do everything subjectively and then treat everyone the same anyway. So it's a waste of time and money. It doesn't work, and it candidly will never work. - Yep, and I've seen you say diagnosis before enablement. So I think that's an interesting way. That's what best-in-class look like, is like, let's actually do diagnosis, and then we'll enable. The shortcut was like, let's just do enablement. - Yeah, do everything. - But, yeah, so, yeah, that's really interesting, really interesting.

07:14Demo: diagnostics at the atomic skill level

7:14 - Well, I know you prepared a demo for us today. I'm really excited to see Luster's approach to getting salespeople, anybody in front of a customer, to be the best version they can be, and dive in and see how we went from hundreds of thousands of dollars of consultants that aren't really even helping. Hundreds of thousands, probably millions, of time and expense of enablement is something that's actually tailored to the salesperson and scalable. - Yeah, I mean, to that point, I've spent hundreds of thousands of dollars on other training at previous organizations to get maybe a max 12% adoption, and that's if you could even measure it. So it's meaningful.

7:55 So I have prepared, I prepared something to show you. So basically here, we can kind of look at the back end of Luster, and the first thing to note that is really unique about this tool, and we talked about it a little bit, is what Luster is going to do first is it's gonna provide that diagnostic, which is critical. If you deploy any kind of learning or development or training, and you have not been able to accurately diagnose the needs of the team, it will be a waste of time. The other thing is you could even address a skill gap that somebody might have, but the prediction and point in time is also important. If you are addressing a skill gap that I have

8:30 that I don't have to perform against on a customer call for two weeks, you're training me on that today, two weeks from today, I've forgotten 80% of what you've trained me, and so it doesn't ingrain and it doesn't stick. And so the whole idea of Luster is first diagnose, right? So here you'll see, this is basically what we have for the entire team, and then also for every individual rep. So you'll see here that we break down your diagnostic at the atomic skill level. So whatever the skills are that are critical for your organization, your specific sales roles, is what we break it down. So it's not this high level feedback.

9:04 In order to get a diagnosis, it's every stage of your sales or your support process, there are critical skills that you have to show a level of mastery in order to kind of get through that process. And so all of these are customizable, and the first thing that we do is take a snapshot of what your entire team looks like. So where's your entire team's proficiency? We can also do that down to an individual, right? So if I am an individual performer here, we'll look at somebody who has completed something recently. I don't wanna pick on anybody, but we might. So we can look at an individual, right? So any individual on my team,

9:41 I can actually also see their individual proficiency score so that I understand exactly where they are and where I need to coach them. So now we basically start with this level of diagnosis. Now we can get this in two different places. Place number one is you can practice in Lustre, and we will proficiency map you because the simulations that we'll go through are gonna mimic a customer interaction exactly. The other thing that we can do is we can look at all the previous calls that you have had and proficiency map you immediately to identify where the gaps are based on what good looks like for your organization, right? So now-- - That's pretty big.

10:12Integrations, and grading real customer calls

10:12 I just wanna make sure. What's the best way to get that data into Lustre? What tools are you integrated with? And what's the best format for somebody interested in bringing that data into the platform? - Yeah, so Zoom and Teams pretty much cover all of that. And so we have an integration with Zoom. We have an integration with Teams. So we can automatically not only look at all of your previous conversations for an individual, but then we can also grade your existing customer calls after you have them. So we can say, here's how you're showing up in practice. Here is your proficiency after that training that your enablement team just did.

10:44 And now you wanted a customer call that mimic that training session. What's the delta between those two? So we can actually see, again kinesthetically, how is it sticking, right? So we can actually now measure what's gonna happen before the call, what happened on the call, what are the gaps, and now what data do you need to continue to up level? So we're looking at kind of the full picture there to again, get a proper diagnosis. So then we talk about what is the point in time piece being so important? So let's say that this is my proficiency map. What Lustre is gonna do is Lustre is gonna consistently scan this proficiency map.

11:15Predict: auto-scheduling a dress rehearsal

11:15 We are then gonna also connect to your calendar to look at the actual customer interactions that you have scheduled on your calendar. And we're gonna look at your map and say, hey, based on that discovery call that you have tomorrow, you're about to make a revenue impacting mistake. So we're gonna custom create a practice session for you that mimics that call that you're about to go on, proactively schedule it on your calendar for you so that you can go in and practice and have a dress rehearsal of an actual call before you have it. So these are kind of some of those more magical pieces. And again, are all in the diagnose what's wrong,

11:50 predict where your lack of proficiency is about to impact your performance in the next 24 to 48 hours, and then you continue to do that in real time. And so we diagnose, we predict, and then we prescribe the solution. - I think something, so Joe is a big fan of doing the dress rehearsal. I know a lot of sales teams don't even do that as a process, but to have that baked into your product and predict when they'll need a dress rehearsal and schedule that for them, and they don't even need anybody else on the team, they can do it on their own, that's huge. - That's a big part. I mean, we're working with teams where I think the biggest constraint

12:27 is the bandwidth of the management team to be able to do the training. So it seems like this could be guided by a rep, and they can go on this journey of getting this assessment from an independent system based on previous data, and then go through this process of improving themselves without needing anyone there. And I think that's crazy 'cause that's a huge time suck. If you're managing 10, 20, 30 reps, you cannot do that. - No, you can't. And are you the right person to do it as well? We can scrape the metadata of an actual person on your calendar and truly create a dress rehearsal for you to practice a conversation with an AI version of that person.

13:06An AI version of your actual buyer

13:06 So like, whereas a sales manager can't necessarily do that, right? Like if you've never been the persona of the person your team is selling to, then are you the right person to help them overcome the skill gaps? Like it's just, it's too much onus put on sales management and enablement versus the other thing about the diagnostic is we're not just gonna diagnose practice for you. The diagnostic could be we're gonna diagnose AI custom created content that Lustre's gonna build specifically for you for a specific call. So Lustre's gonna scrape the metadata of that meeting and say, hey, here's a custom battle card for that meeting.

13:37Battle cards, personas & weekly manager coaching reports

13:37 Here's a persona documentation that'll help you understand how to talk to this person or what they care about. Here's a list of discovery questions that you should ask to really learn how to pain funnel. So Lustre is not just prescribing AI role play. Now practice is a huge part of testing. Are you ready before you do it? But it's not the only thing. Lustre will even send every single sales manager every single week a custom coaching report for every person on their team. Based on the critical skills, where are they proficient? Where are they deficient? Here's examples of that. And here's how you as a manager can up level them.

14:08 So then we're also celebrating the human managers by getting them out of the mud and showing them how to coach their people and helping the manager improve and like be better at their job. Which again, I've been a sales manager for 15 years. So like having that kind of insight and not going into every one-on-one and being like, so, what do you think you need to work on? Like it's like, it allows you to say like, I know exactly what you have to work on. I have examples, you have that call tomorrow, right? Lustre will also identify to a manager when a rep still is not at proficiency before a call, tag the manager and say,

14:41 this would be a good call for you to attend. The rep is not proficient enough to handle this call on their own. So when managers are looking at saying, what calls should I join? They're not gonna have data that tells them, I know for a fact that this rep is not proficient on this call. This is a good opportunity for me to jump on the call and Lustre will proactively tag managers and say, you might wanna join this call, right? Because they practice they're not getting there. It's not ingraining. This is where you need some leadership support. So it's a tool for managers to up level too. So this is basically what the backend looks like

15:10Two ways adults learn: full calls vs. skill drills

15:10 and these are kind of examples of exactly what different simulations that are custom created might look like. You'll see there's two ways to practice. And so this is also rooted in behavioral and cognitive psychology. So there's two ways that adults learn. And one is sort of doing a full call simulation where I'm practicing the entire thing. And the other is focused on an individual skill, right? So these are examples of different types of full calls that are created to mimic your sales process, right? Is it a prospecting call? Is it a discovery call? Is it a QBR, right? So anybody having any kind of customer conversations, Lustre can mimic those.

15:43 Is it a proposal call? Are we negotiating today? But then also skill drills. So to use a golf metaphor, you can either play an entire round of golf or you can just go and practice your swing. And so if you're having a difficult time overcoming certain objections, you go into the skill drill environment, which comes with a built-in AI coach. The coach is gonna give you objections relevant to your role. You overcome them and that's gonna give you feedback on what you could have said differently. You just keep getting hit with objections or product questions or security questions, whatever skill is identified that you need help honing in on.

16:13Live cold-call simulation with 'Candice'

16:13 So we can see here what an actual session will look like that has been prescribed. (phone ringing) - Hi, this is Candice. How can I help you today? - Hi, this is Christina calling from Lustre. It is a cold call. Do you have a few minutes for me to tell you why I'm calling? - Hi, Christina. Honestly, I'm a bit swamped right now. Can you give me a quick idea of what this is about? - Yeah, Candice. I was actually noticing that on LinkedIn, you were paying a lot of attention to a lot of different AI enablement tools. Is that something that you're shopping for right now?

16:49 - Oh, AI tools, huh? I'm always on the lookout for things that can genuinely help our sales teams perform better. But I'll be honest, it's got to really address some key pain points we have. Can you tell me more about how your tool could help us out? - Absolutely. The first question I have for you is, do you have capability today to measure the skilled efficiencies of your customer-facing team and then use that data to prevent revenue-impacting mistakes? Can you do anything like that at all today? - Mm-hmm. - We do have some tools in place for tracking skill levels, but getting a clear, consistent picture across the whole team has been tricky.

17:25 And those insights aren't always directly linked to preventing revenue-impacting mistakes. So how does Lustre handle this differently? - Well, I guess I would ask, how do you currently measure skill proficiency today?

17:39 - Right now, we primarily rely on performance reviews, manager feedback, and some analytics from our CRM. But like I said, it's not always, it can be hard to connect those dots directly to revenue impacts. Does Lustre offer a more integrated or automated? - So we'll kind of continue to have that conversation. And the thing to say is like, this is not a scripted conversation. This is true generative AI. So every conversation is going to be different. We didn't prompt Candice to say that like, that's how skill mapping is traditionally done. She learned that 'cause that's how it's done. And then at the end of the call too,

18:10Scoring & the 80–85% proficiency bar

18:10 the feedback again is critical, right? Like what kind of feedback am I gonna get? Is it gonna be high level, super generic, or we'll kind of walk through here what the feedback at the end of a call actually looks like. So scored an 80%, typically Lustre looks at proficiency being between an 80 and an 85% or higher, and that is showing proficiency. So I'm feeling good going into this call block, but you'll also see that it gives me feedback on every individual skill that it heard me deploy. Now keep in mind, what I needed to work on was discovery and call prep. So I'm doing well here in the practice session. I may wanna do one or two more

18:43 because every single one of them is different, but I could listen to this call and I could review the transcript. So essentially that would be an example of how- - So there you go. That's a little bit of kind of what the actual practice session might feel like in the feedback. And then all of that scoring kind of goes into kind of the mass dashboard that CROs can see, enablement can see, and it kind of feeds into your proficiency overall. And then this tool just kind of keeps doing that. Reading where you are, prescribing custom practice, measuring that, looking at practice versus the actual call. So what it would do then after this

19:16The tech stack behind the simulation

19:16 is then it would look at the actual call block that I went on and compare that to the practice sessions and then continue to prescribe more prescriptive training based on what your gaps still are or move on to something else since we've addressed that gap today. - Wow, there's a lot of technology behind the scenes of that. I mean, you're transcribing what someone's saying, you're using text to speech, you're using language models to respond. There's a lot of latency considerations. I mean, how has building a product and a simulation like that been with the current AI? And where do you kind of see that going in the next couple of years?

19:53Quick tech (GPT wrapper) vs. the platform approach

19:53 - I would say it's interesting building AI right now because there's really two ways that it happens. And way number one is really quick tech, which can very quickly turn a bit into vaporware, right? And that quick tech is I can build a user interface directly on top of a large language model and I can give the illusion of building a lot really, really fast. And that's sexy for AI startups because you wanna look like you have this huge robust tool that can do all of these things, but what you can't necessarily control for is your information being shared with the large language model. Do you have the capability to really make it feel

20:30 like it is specific and contextual to the organization that you are giving it to? You can't really control the latency, right? One of the things that Lustre does is as users are using Lustre, it's gonna measure your natural human latency and amend the product to fit you so that you feel like you're having natural conversations versus being more beholden to whatever latency that you set your entire product at. So when you're doing a custom build, you have the capability to do things like that. So the experience learns with the user. So you've got that kind of quick tech, which is that sort of GPT wrapper. And then you have more comprehensive tech

21:03 that is a more platform approach. One of the other main differences between those two things is the quick tech is sort of one instance and then all customers are added into that one instance and then sort of separated out in the user interface versus something like Lustre. Every single customer gets their own trained closed off instance. So it is a custom build for every single customer, but then we can control the information. We can protect it from a security standpoint, right? Like Lustre's not sharing your information with a large language model ever. It's how we've been able to get SOC 2 clearance type one and type two and pass the repent test

21:35 is because we're custom building every single model. The downside is we can't be as feature fast, right? Like we can't keep building new features super quickly because every new feature, because it's AI, you have to look at the security, the infrastructure, the stability, the operation, the performance. And so that's why we have a larger engineering team than a lot of other startups our same size. And it's because we don't wanna move slower, but we wanna move responsibly. And so that quick tech versus platform approach, we made a very deliberate decision to go platform approach. So a lot of other folks just building sort of point solution in this space,

22:11 started building the same timer after us and all launched really fast, right? And then we finally launched, but then we launched a better, more robust, secure product that we can completely control. And at the end of the day, that's what companies want is not the fastest tool, but the one that's gonna be the most stable. And they wanna trust a founder that's not settling on their product roadmap. And so that's the other thing is like, I will tell you what the tool has today and what it has tomorrow. And if the limited use case that we have when we launched isn't a good fit for you, then don't buy it now. And if it is, then buy it now.

22:41Enterprise-grade security; saying no to a $500K deal

22:41 And that's also how we've kind of gotten ahead in terms of go to market and build. We've built some really good customer loyalty, so. - Well, and I think the idea of security is becoming more and more important, especially when there's more AI companies concerned about where their data is going as well. So I think building something that's actually enterprise grade, production ready, which this is a great fit. I could see amazing fit for small teams, but you really, really get the benefits of the enterprise space. - That's right. - So if you have large teams, the efficiency and effectiveness that this could drive,

23:17 and you need to be enterprise ready for them. - Right, and that's what we've been building for from the beginning. And so when we launched the product in July of 2024, it absolutely was not enterprise ready. And we had enterprise customers, even people, CROs who were in my network that were like, we'd love to buy this, we have a thousand reps. It's like, I would love to go back to my investors and say that I have a $500,000 ARR deal, but I'd be doing you a disservice and the product a disservice, and then you're gonna be controlling my roadmap instead of building the infrastructure that I need. And so we said no to some of those large enterprise customers.

23:48 Well, not no, we were like, wait. Wait until we are enterprise ready, and that takes a lot of things, not just in the product itself, but again, in the infrastructure. And I can't talk about enough, the security of the product. You have a breach in one of these products. It's really, really, really bad. And so we take security probably more serious than a lot of folks in our space. But again, I come from 18 years of go to market. I've been a company, so there's been a data breach before. I've seen what happens when this goes south and when you build sloppy tech, and I just refuse to do it. And so what we mean by kind of a more robust model

24:19Inside 'Pearl': Luster's discourse engine

24:19 is if you look at this, this is a little bit of the luster platform. So what you would see in more of a GPT wrapper would literally be like the user interface at the very top, which is like, hey, the insights and the coaching and the role play, the actual product, which is this piece up here. And then underneath this security layer, it would be the large language model that's powering the tool. For us, everything that exists within here is what we've just kind of affectionately called our, you know, Pearl is our discourse engine. The lustery Pearl, we had to be on brand. But this is sort of where we have multiple layers

24:50 of custom proprietary coded information that simply belongs to luster. And this is what we build for every single customer. So the first thing that we do is every single customer gets their own trust and security layer. So we build that on top of large language model first. Building like this also makes it so that we are not beholden to an individual large language model. So we can actually swap out large language models based on the performance or the cost or even their element of security without impacting the core product. And so that's nice as well as we're not built on open AI and stuck on open AI.

25:21 We're not built on Cloud or Entropic and stuck on them. We can actually swap that out, which is really nice because we can be dynamic. On top of that is where we build a custom model to actually ingest the behavior of your people and then how we want luster to behave, right? The persona of the people, the latency of the model, what we want your user interface to look like, the types of simulations that are gonna be custom created. So then we kind of build that ingestion engine to be specific for every individual company. On top of that is then where we kind of build in your specific insights. So we do a combination of taking your company information

25:55 and then third party metadata that exists on the web to train the model on how to be an exact replica of your customer or prospect conversations. And that's who are the personas that you're selling to? What are the critical skills or methodologies or processes that you wanna make sure that your people based on their role are following? What kind of knowledge does the tool have to have to give proper feedback? So it feels like you're getting feedback from a sales manager or somebody in enablement at your organization and not just like, you didn't ask enough questions, ask more questions sometimes. And then goals, right?

26:25 Every single conversation that you have as a sales rep or a CSM, there is an end in mind or a goal at the end of that call. We hardwire those goals into every single simulation so that it's actually measured properly. On top of that is in the conversational AI, right? The latency, what's the persona gonna look like? What is their vibe gonna be? The personality of the person. You can give the person that you're selling to like 45 different personality attributes. You can give them context like, you're selling to a VP of sales who needs to buy a tool before they go on maternity leave in the next two weeks and they haven't started yet, right?

26:57 Like you can give it that specific level of kind of conversational intelligence so that it really feels like a real call. And then on top of that is what is the output that then comes after that? The output would be the predictive skill insights and then the action that is prescribed to it. So like, this is the difference between just seeing like a large language model and a user interface. And then everything in between is the custom coded piece of more of a platform type company like Lustre. - That's really helpful to see because I think the tech you're building is pretty, it's pretty deep into what language models and speech to text and tech.

27:32 I mean, you're kind of using it all to the fullest extent. And I think it's at that point, we were talking about this a little earlier where it's about to get really, really good. I mean, it's already really good, but we're getting to that point where even trying to build this tech five years ago would have been really hard just based on the quality of the model's AI, what was available. So your timing and the infrastructure you built with where the market's going, I feel like you're just gonna keep getting better and better and better. So I'm really excited to see what the next couple of years are like. - Like it's a great point because if you also look

28:08 at every bit of infrastructure, each of those are gonna be improved in their own unique and specific way based on larger advancements in the market. And so by building this way, we have so many more points of being able to provide a more delightful product for our customers because we can impact it positively in so many different ways. So building it the right way first allows you to catch the upswing of technology without having to say, we didn't build the product right in the first place. And so now that we have customers in the system, we're gonna go back and build the plane while it's in flight. And I get, look, I've been in tech for a long time.

28:41 I've worked at companies that do that. So I'm not dogging on it, but also I am. Because that, again, that then makes your customers kind of more collateral damage to you not building the product that you told them that you were gonna build and then not being able to keep up to date on the new advancements that are made, which is also credit for customers. - 100%. - No, I think you need to make it build to last. And I think it's such a natural experience. And the way you've done it is really, really intentional and elegant, so I appreciate that. It's not feeling like you're interacting with an AI bot. It feels like a real scenario,

29:21What if you have no training docs?

29:21 which I think is important for adoption and making sure you're getting organic interaction with it too. - Yeah, absolutely. Well, that's another thing that we hear is you'd be surprised at the size, or maybe you wouldn't, the size of companies when we say like, hey, give us your training documentation. Give us your persona information. Give us the skills that you're measuring your people on. And they're like, so here's the thing. We don't actually have any of that, right? And I was like, you guys are living on the edge. That is reckless. But been there, right? Sometimes we don't have the time to stop and take the pebble out of our shoe

29:51 because we have to keep running the marathon. I get that. And so like, let's not get to the finish line with bloody feet. And so one of the things that Lustre can also help with is let's say that you don't have any of that information. That's where that third party ability for it to train itself really comes into play. So we can say based on the industry that you are in, the personas that you are selling to, the role that they have, what does good look like for other sales reps on teams like this selling to these industries. And we can actually custom train or even build a methodology for you based on what is already proven to work for your industry.

30:22Hiring & ramp: the manager and exec use case

30:22 And so if you have that information, great. If you don't, we can then actually custom build that and measure it for you. Or we can look at what you already have and say, hey, based on the skills that you're currently measuring your people against, it might not be industry best practice. Like we can actually give you that information. So it's helpful to give a directing light to people on what good looks like as well. - 100%. I think one last quick piece I was hoping we could talk about is just the manager and exec use case. Because one thing we come into a lot is just teams building out a really intense growth plan.

31:04 And they have to hire and build capacity plans for so many AEs, SEs, customer success, SDRs, I mean, the whole list. So if you're someone who's going into a year of heavy hiring, enablement is a very top of mind thing. How would they work with Lustre? What are some of the ways that they could leverage the platform to get a really firm grasp on the talent, the ramping, and how it could improve some of those ramp times too? - This is such a good question. Because the last time I checked it, the cost of a bad hire and go to market of a frontline revenue producer, account executive, on average, the cost of a bad hire that turns over

31:51 within one year is over $300,000. Like the cost to the business. And it's probably larger than that. And so what you're actually honing in on is another one of our core use cases. The reason why we get hiring wrong so often is one, we have to take people's word for it. Two, people don't know how to actually hire. And three, sales reps, if we're talking about that persona, are really good at interviewing. Like sales reps are usually pretty good at selling themselves. And the problem is the best sales rep at another company does not mean that they are gonna be the best sales rep at your company because everything is so different.

32:23 And so no matter how much you interview people, put them through in-person role plays, competency map them, put them through panel interviews, you are still taking a wild guess. And then when we do hire them, we don't know how to ramp them anyway, right? You go to six different people at an organization, you're like, what's your ramp time? And they're like, ugh, they all kinda look like, there's no common denominator. So the first thing that you can use Lustre for is instead of doing that kind of weird, choogie interview role play that you do, you can actually have them role play and do that interview in Lustre.

32:56 So now I can actually get a skill proficiency map for you before you even start. So now I can see, are you walking in the door with the critical skills needed to be successful at this company and in this role? So then you can say, hey, based on what good looks like for a new employee, and you can amend a simulation to measure a new employee, right? They're not gonna have the product context, all of that. But then you can build a simulation that measures what are the core competencies that you currently have and what kind of product knowledge do you actually have that? So then you can either say, hey, we're not gonna hire you

33:24 because now we can actually measure your skills and we know that you're not a great fit. And that also keeps you safe from an HR standpoint 'cause you're not saying, I just don't feel like you're the right hire. It's, hey, we have an objective measurement for this. And then if you do decide to hire them, instead of doing this one size fits all onboarding for everybody, I now know the skill gaps that you have that are gonna slow you down from producing revenue. So I can now do prescriptive onboarding with Lustre. So while you're going in a classroom setting and learning all things about the product, Lustre's then gonna meet you back at your desk

33:51 and actually help to up level you where you have those deficiencies. And so that's where we have seen the ability for enablement to really shine in onboarding managers to know where to coach their new reps for the first time. They know based on Lustre when they should get on a call or when they should not. And so we've cut those ramp times in half and we're actually helping companies define what ramp looks like, right? Like what is your ramp time? We can actually measure the proficiency of your team increasing when they are hired. So you can now have a standard denominator of what does ramp look like? How do we measure people and not continue

34:25Not spyware: a culture of failing forward

34:25 to pick amazing employees that you should sit and up level properly from the get go. - Right, yeah. Well and I think for the right rep too, a rep that you'd actually want in your company, they would look at this as a positive. So this isn't just like spyware, something to like put you through unnecessary steps. - That's right. - They care about hitting quota, making money. And if you're giving them tools where they can coach themselves and they can improve their own skills so they can make more money and crush their quota every single quarter, the right rep will look at that as a positive. So I think, I don't know if some managers

35:01 or some reps are listening to this and thinking like, oh, I don't want to have to put somebody through all these steps, then they're probably not a good fit anyway. - Right, well and the thing is, is you're going to be measured based on your performance in one of two ways. Either by your performance itself once it's already declined and you're not making any money and on a performance improvement plan, or the capability for you to proactively identify before it erodes your KPIs and your metrics that you have things to work on and do that in a safe space so that you can only shine or you now know when to go and ask for help and what you need help on.

35:34 And so we tell folks like, Lustre is not meant to be a performance management platform. It is meant to avoid performance management for reps who should be at your organization. So we say like, make your mistakes in Lustre, try new talk tracks here, do weird stuff here, fail. Right, we have reps using this tool and they will actually share horrible calls they've had and be like, this guy was like Bowser, I could not get through time and procurement, right? And they share and everybody laughs about it, right? It also then creates this culture of learning and failing forward versus the culture so often, which is, I don't want my manager to know

36:07Who it's for & how to get started

36:07 that I have any issues. I don't want my manager to know that I'm not ready to do this job. And so then you get on a call and you're terrified, you can take all of that away by providing a real area for your team to play in and actually enjoy getting better at their job and see the results on paper. - Yeah, I think that's awesome. That is awesome. CS teams too, solutions engineering teams, sales engineering teams, VDRs. So there is applications for all of those people. And yeah, I think it's awesome what you've built. If you're watching this and you're interested, how do I get going, test out Lustre, get in touch with you. What should they do?

36:47 What's the quickest way to get on the platform? - So you can, I mean, if you're like, we want to kick off a POC right now, love it. Email me christina@lustre.ai. You can go on our website and fill out a demo form. You can find me on LinkedIn. Anywhere that you can find Lustre, anywhere on the open web is gonna eventually get you to me or somebody on our broader go-to-market team. And so we are very, very buyer friendly. We don't believe in holding our buyers to rigid processes. And so whatever way that you need to be delighted and feel really confident buying a new tool is something that we're gonna make sure that we do for you.

37:25 And we're also not afraid to let you test it and pilot it and try to break it first 'cause we're confident in the tech. So customers have come to us and said, like, we're just gonna sign up for a year out the gate. I'm like, great. Others are like, will it do what you say it will do? And I'm like, test it. 'Cause it will, and then you'll buy it, you know? So however you need to buy for your organization, we've got you, we're just in the business of delighting customers and keeping them. - Well, Christina, this has been great. I think it's something we're probably thinking might be a good fit for lean scale. I know it's definitely a good fit

37:57 for a lot of the companies that we work with. You know, when we're inside doing revenue operations, go-to-market operations for high growth VC-backed startups, they're, we say it all the time, the growth model is one or lost on hiring and enablement. And I think this is the most elegant and intentional way to make sure people are getting the tailored training that they need and getting it diagnosed in the first place of where they need help and where they can increase their performance. So I'm so excited about what you're building, what you're doing. Can't wait to see what you do next, especially like Joe is alluding to,

38:34 as just the foundational technologies continue to improve. I know you're gonna take advantage of them and can't wait to have you back when you do. - Oh my gosh, I can't wait either. Thank you so much. Music to my ears.