The company provides legal support and document services to law firms and corporate legal departments. Their sales team sells complex service packages \u2014 litigation support, e-discovery, managed review, and compliance consulting \u2014 to sophisticated buyers who expect precision.<\/p>\n\n\n\n
Their training platform scored every practice session on a 0\u2013100 scale. The score was a composite: tone, pacing, objection handling, product knowledge, and compliance language all collapsed into one number.<\/p>\n\n\n\n
The problem became visible when two reps finished practice sessions on the same day. Both scored an 88.<\/p>\n\n\n\n
Rep A had lost points on pacing and hesitation. She knew the products cold, but she sounded uncertain. Her coaching need was clear: confidence, delivery, and speed.<\/p>\n\n\n\n
Rep B had delivered a smooth, confident performance. His pacing was excellent. His objection handling was textbook. But he had stated a service capability that didn’t hold up \u2014 and the platform hadn’t flagged it because it wasn’t checking content.<\/p>\n\n\n\n
Two reps. One score. Completely different coaching needs.<\/p>\n\n\n\n
“The number told me they were the same. They weren’t. One needed help with delivery. The other needed to learn what our services actually include. Those are not the same conversation, and the score gave me no way to tell them apart.”<\/p>\n\n\n\n
The cost of collapsed scores<\/strong><\/h2>\n\n\n\nThe firm had been using the score-based platform for 18 months. In that time, the head of sales enablement had noticed patterns she couldn’t explain:<\/p>\n\n\n\n
\n- Reps with strong scores were still making factual errors on live calls<\/li>\n\n\n\n
- Managers struggled to give specific, actionable coaching \u2014 they knew a rep had scored low, but not what to fix<\/li>\n\n\n\n
- The same mistakes were showing up across multiple reps, but the score data couldn’t reveal the pattern<\/li>\n<\/ul>\n\n\n\n
The underlying problem was structural. The score collapsed everything \u2014 tone, pacing, product accuracy, compliance \u2014 into one number, and once it was collapsed, you couldn’t get the detail back out.<\/p>\n\n\n\n
When a rep lost points, the manager didn’t know whether they lost them on tone or on a product fact. And without that distinction, coaching was generic: “improve product knowledge” instead of “here’s the specific claim you got wrong, and here’s the citation.”<\/p>\n\n\n\n
The intervention: verdicts instead of just a score<\/strong><\/h2>\n\n\n\nThe firm replaced their score-only platform with EOS (<\/strong>akaeos.com<\/strong><\/a>)<\/strong>, which adds a second layer underneath the score: claim-level verdicts.<\/p>\n\n\n\nInstead of asking only “how well did this session go,” EOS asks, for each specific claim a rep made: was that claim actually accurate? Every claim receives one of three verdicts:<\/p>\n\n\n\n
\n- Supported<\/strong> \u2014 the claim matches current product and policy documentation<\/li>\n\n\n\n
- Contradicted<\/strong> \u2014 the claim conflicts directly with that documentation<\/li>\n\n\n\n
- Insufficient<\/strong> \u2014 the claim is too vague to verify as stated, or it’s missing a qualifier, exception, or required disclosure that changes whether it’s fully accurate<\/li>\n<\/ul>\n\n\n\n
The Insufficient verdict turned out to be where most of the real coaching value lived \u2014 and it’s also the category a plain score can’t represent at all.<\/p>\n\n\n\n
Why “Insufficient” changed everything<\/strong><\/h2>\n\n\n\nConsider a rep who says a service offers “full document review coverage.” The claim is directionally true \u2014 the service does include document review. But if it’s only true for certain case types, and the rep didn’t mention the limitation, the claim isn’t fully supported either. It’s something in between: right on the main point, incomplete on the detail that actually matters to the customer.<\/p>\n\n\n\n
A binary right\/wrong system has no good place to put that claim. It either gets marked Supported \u2014 which lets a real gap through uncorrected \u2014 or Contradicted \u2014 which overstates the problem and makes the rep defensive about something they mostly got right. Flagging it as Insufficient says exactly what happened: the core claim held up, and here’s the specific condition that got dropped.<\/p>\n\n\n\n
That distinction mattered even more for compliance language specifically. On several calls, EOS flagged claims as Insufficient not because the rep said anything false, but because a required disclosure \u2014 a standard scope-of-engagement caveat their compliance team requires on certain service lines \u2014 was never mentioned at all. That’s a different kind of gap than a wrong fact, and in a legal services firm, it’s often the more expensive one: a scope dispute six months into an engagement traces back to a caveat that was never said out loud.<\/p>\n\n\n\n
That’s a coaching note a manager can actually act on. “Always mention the case-type limitation” is a concrete instruction. “Improve product knowledge” is not.<\/p>\n\n\n\n
What they found in the first month<\/strong><\/h2>\n\n\n\nThe firm ran a pilot with 30 reps.<\/p>\n\n\n\n![\"\"](\"https:\/\/blog.themusio.com\/wp-content\/uploads\/2026\/08\/image-36-1024x423.png\")
<\/figure>\n\n\n\nThree patterns emerged:<\/p>\n\n\n\n
\n- Scores didn’t tell the full story.<\/strong> Several reps with high overall scores had a meaningful number of Insufficient claims \u2014 directionally right, but missing critical qualifiers. The old score-based system had been giving them passing grades without revealing the gaps.<\/li>\n\n\n\n
- The most common errors were in the middle category.<\/strong> Reps rarely made outright false (Contradicted) claims. They frequently made claims that were mostly right but Insufficient \u2014 missing a key exception, limitation, or disclosure. These were the errors most likely to surface later as client dissatisfaction or scope disputes.<\/li>\n\n\n\n
- Managers could finally coach specifically.<\/strong> Instead of saying “work on your product knowledge,” managers could say “when you discuss e-discovery coverage, always mention the data-volume limit.” Using EOS’s manager dashboard, the verdicts gave them the specificity they needed.<\/li>\n<\/ol>\n\n\n\n
“Before, I could see that a rep had room to improve. I couldn’t tell anyone what to improve. Now I can. ‘This claim came back Insufficient \u2014 here’s the condition you left out.’ That’s a coaching conversation that actually changes behavior.”<\/p>\n\n\n\n
\n- Is your training platform giving you a score \u2014 or a diagnosis?<\/strong> Our 12-page report, Beyond Roleplay: The Rise of the Sales Knowledge Engine<\/em>, covers claim extraction, the fact-grounded verification pipeline, and the verdict system that replaces vague scores with actionable coaching. [Download the whitepaper \u2192]<\/strong><\/a><\/li>\n<\/ul>\n\n\n\n
Why verdicts beat a single score<\/strong><\/h2>\n\n\n\nA score tells you how a session went. It doesn’t tell you why \u2014 and “why” is the only part that’s actually coachable.<\/p>\n\n\n\n
Two reps can land on the same score for completely different reasons. One lost points on delivery. The other lost points on product accuracy. Those are not the same coaching conversation, and a score alone gives a manager no way to tell them apart.<\/p>\n\n\n\n
Verdicts add the layer a score is missing. They don’t replace the score \u2014 they sit underneath it, providing the detail that makes coaching possible. For a legal services firm where precision matters and partial truths can create scope disputes, that distinction was everything.<\/p>\n\n\n\n
The takeaway for sales leaders<\/strong><\/h2>\n\n\n\nIf your training platform gives you a single number and nothing else, you have a problem you might not see until a coaching conversation goes nowhere.<\/p>\n\n\n\n
A score tells you that something needs improvement. It doesn’t tell you what. Verdicts \u2014 Supported, Contradicted, Insufficient \u2014 tell you exactly what a rep got right, what they got mostly right but incomplete, and what they got wrong outright. They turn “improve product knowledge” into “here’s the specific claim you missed, and here’s the citation.”<\/p>\n\n\n\n
That’s the difference between generic feedback and coaching that actually changes behavior.<\/p>\n\n\n\n
\n- Stop guessing what your reps got wrong.<\/strong> EOS replaces single scores with specific, actionable verdicts \u2014 Supported, Contradicted, or Insufficient \u2014 for every claim a rep makes. Start free with up to 5 seats at akaeos.com<\/strong>, or [download the full whitepaper]<\/strong><\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
The head of sales enablement had a dashboard that showed her exactly how every rep performed. Eighty-eights. Seventy-twos. Ninety-fours. The numbers were clean, comparable, and easy to report upward. She could see trends, track improvement, and identify who was struggling. But when she sat down with a manager to coach a specific rep who had […]<\/p>\n","protected":false},"author":1,"featured_media":11305,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3642,3640],"tags":[],"class_list":["post-11304","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-en","category-all-en"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
The underlying problem was structural. The score collapsed everything \u2014 tone, pacing, product accuracy, compliance \u2014 into one number, and once it was collapsed, you couldn’t get the detail back out.<\/p>\n\n\n\n
When a rep lost points, the manager didn’t know whether they lost them on tone or on a product fact. And without that distinction, coaching was generic: “improve product knowledge” instead of “here’s the specific claim you got wrong, and here’s the citation.”<\/p>\n\n\n\n
The intervention: verdicts instead of just a score<\/strong><\/h2>\n\n\n\nThe firm replaced their score-only platform with EOS (<\/strong>akaeos.com<\/strong><\/a>)<\/strong>, which adds a second layer underneath the score: claim-level verdicts.<\/p>\n\n\n\nInstead of asking only “how well did this session go,” EOS asks, for each specific claim a rep made: was that claim actually accurate? Every claim receives one of three verdicts:<\/p>\n\n\n\n
\n- Supported<\/strong> \u2014 the claim matches current product and policy documentation<\/li>\n\n\n\n
- Contradicted<\/strong> \u2014 the claim conflicts directly with that documentation<\/li>\n\n\n\n
- Insufficient<\/strong> \u2014 the claim is too vague to verify as stated, or it’s missing a qualifier, exception, or required disclosure that changes whether it’s fully accurate<\/li>\n<\/ul>\n\n\n\n
The Insufficient verdict turned out to be where most of the real coaching value lived \u2014 and it’s also the category a plain score can’t represent at all.<\/p>\n\n\n\n
Why “Insufficient” changed everything<\/strong><\/h2>\n\n\n\nConsider a rep who says a service offers “full document review coverage.” The claim is directionally true \u2014 the service does include document review. But if it’s only true for certain case types, and the rep didn’t mention the limitation, the claim isn’t fully supported either. It’s something in between: right on the main point, incomplete on the detail that actually matters to the customer.<\/p>\n\n\n\n
A binary right\/wrong system has no good place to put that claim. It either gets marked Supported \u2014 which lets a real gap through uncorrected \u2014 or Contradicted \u2014 which overstates the problem and makes the rep defensive about something they mostly got right. Flagging it as Insufficient says exactly what happened: the core claim held up, and here’s the specific condition that got dropped.<\/p>\n\n\n\n
That distinction mattered even more for compliance language specifically. On several calls, EOS flagged claims as Insufficient not because the rep said anything false, but because a required disclosure \u2014 a standard scope-of-engagement caveat their compliance team requires on certain service lines \u2014 was never mentioned at all. That’s a different kind of gap than a wrong fact, and in a legal services firm, it’s often the more expensive one: a scope dispute six months into an engagement traces back to a caveat that was never said out loud.<\/p>\n\n\n\n
That’s a coaching note a manager can actually act on. “Always mention the case-type limitation” is a concrete instruction. “Improve product knowledge” is not.<\/p>\n\n\n\n
What they found in the first month<\/strong><\/h2>\n\n\n\nThe firm ran a pilot with 30 reps.<\/p>\n\n\n\n<\/figure>\n\n\n\nThree patterns emerged:<\/p>\n\n\n\n
\n- Scores didn’t tell the full story.<\/strong> Several reps with high overall scores had a meaningful number of Insufficient claims \u2014 directionally right, but missing critical qualifiers. The old score-based system had been giving them passing grades without revealing the gaps.<\/li>\n\n\n\n
- The most common errors were in the middle category.<\/strong> Reps rarely made outright false (Contradicted) claims. They frequently made claims that were mostly right but Insufficient \u2014 missing a key exception, limitation, or disclosure. These were the errors most likely to surface later as client dissatisfaction or scope disputes.<\/li>\n\n\n\n
- Managers could finally coach specifically.<\/strong> Instead of saying “work on your product knowledge,” managers could say “when you discuss e-discovery coverage, always mention the data-volume limit.” Using EOS’s manager dashboard, the verdicts gave them the specificity they needed.<\/li>\n<\/ol>\n\n\n\n
“Before, I could see that a rep had room to improve. I couldn’t tell anyone what to improve. Now I can. ‘This claim came back Insufficient \u2014 here’s the condition you left out.’ That’s a coaching conversation that actually changes behavior.”<\/p>\n\n\n\n
\n- Is your training platform giving you a score \u2014 or a diagnosis?<\/strong> Our 12-page report, Beyond Roleplay: The Rise of the Sales Knowledge Engine<\/em>, covers claim extraction, the fact-grounded verification pipeline, and the verdict system that replaces vague scores with actionable coaching. [Download the whitepaper \u2192]<\/strong><\/a><\/li>\n<\/ul>\n\n\n\n
Why verdicts beat a single score<\/strong><\/h2>\n\n\n\nA score tells you how a session went. It doesn’t tell you why \u2014 and “why” is the only part that’s actually coachable.<\/p>\n\n\n\n
Two reps can land on the same score for completely different reasons. One lost points on delivery. The other lost points on product accuracy. Those are not the same coaching conversation, and a score alone gives a manager no way to tell them apart.<\/p>\n\n\n\n
Verdicts add the layer a score is missing. They don’t replace the score \u2014 they sit underneath it, providing the detail that makes coaching possible. For a legal services firm where precision matters and partial truths can create scope disputes, that distinction was everything.<\/p>\n\n\n\n
The takeaway for sales leaders<\/strong><\/h2>\n\n\n\nIf your training platform gives you a single number and nothing else, you have a problem you might not see until a coaching conversation goes nowhere.<\/p>\n\n\n\n
A score tells you that something needs improvement. It doesn’t tell you what. Verdicts \u2014 Supported, Contradicted, Insufficient \u2014 tell you exactly what a rep got right, what they got mostly right but incomplete, and what they got wrong outright. They turn “improve product knowledge” into “here’s the specific claim you missed, and here’s the citation.”<\/p>\n\n\n\n
That’s the difference between generic feedback and coaching that actually changes behavior.<\/p>\n\n\n\n
\n- Stop guessing what your reps got wrong.<\/strong> EOS replaces single scores with specific, actionable verdicts \u2014 Supported, Contradicted, or Insufficient \u2014 for every claim a rep makes. Start free with up to 5 seats at akaeos.com<\/strong>, or [download the full whitepaper]<\/strong><\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
The head of sales enablement had a dashboard that showed her exactly how every rep performed. Eighty-eights. Seventy-twos. Ninety-fours. The numbers were clean, comparable, and easy to report upward. She could see trends, track improvement, and identify who was struggling. But when she sat down with a manager to coach a specific rep who had […]<\/p>\n","protected":false},"author":1,"featured_media":11305,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3642,3640],"tags":[],"class_list":["post-11304","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-en","category-all-en"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
Instead of asking only “how well did this session go,” EOS asks, for each specific claim a rep made: was that claim actually accurate? Every claim receives one of three verdicts:<\/p>\n\n\n\n
- \n
- Supported<\/strong> \u2014 the claim matches current product and policy documentation<\/li>\n\n\n\n
- Contradicted<\/strong> \u2014 the claim conflicts directly with that documentation<\/li>\n\n\n\n
- Insufficient<\/strong> \u2014 the claim is too vague to verify as stated, or it’s missing a qualifier, exception, or required disclosure that changes whether it’s fully accurate<\/li>\n<\/ul>\n\n\n\n
The Insufficient verdict turned out to be where most of the real coaching value lived \u2014 and it’s also the category a plain score can’t represent at all.<\/p>\n\n\n\n
Why “Insufficient” changed everything<\/strong><\/h2>\n\n\n\n
Consider a rep who says a service offers “full document review coverage.” The claim is directionally true \u2014 the service does include document review. But if it’s only true for certain case types, and the rep didn’t mention the limitation, the claim isn’t fully supported either. It’s something in between: right on the main point, incomplete on the detail that actually matters to the customer.<\/p>\n\n\n\n
A binary right\/wrong system has no good place to put that claim. It either gets marked Supported \u2014 which lets a real gap through uncorrected \u2014 or Contradicted \u2014 which overstates the problem and makes the rep defensive about something they mostly got right. Flagging it as Insufficient says exactly what happened: the core claim held up, and here’s the specific condition that got dropped.<\/p>\n\n\n\n
That distinction mattered even more for compliance language specifically. On several calls, EOS flagged claims as Insufficient not because the rep said anything false, but because a required disclosure \u2014 a standard scope-of-engagement caveat their compliance team requires on certain service lines \u2014 was never mentioned at all. That’s a different kind of gap than a wrong fact, and in a legal services firm, it’s often the more expensive one: a scope dispute six months into an engagement traces back to a caveat that was never said out loud.<\/p>\n\n\n\n
That’s a coaching note a manager can actually act on. “Always mention the case-type limitation” is a concrete instruction. “Improve product knowledge” is not.<\/p>\n\n\n\n
What they found in the first month<\/strong><\/h2>\n\n\n\n
The firm ran a pilot with 30 reps.<\/p>\n\n\n\n
<\/figure>\n\n\n\nThree patterns emerged:<\/p>\n\n\n\n
- \n
- Scores didn’t tell the full story.<\/strong> Several reps with high overall scores had a meaningful number of Insufficient claims \u2014 directionally right, but missing critical qualifiers. The old score-based system had been giving them passing grades without revealing the gaps.<\/li>\n\n\n\n
- The most common errors were in the middle category.<\/strong> Reps rarely made outright false (Contradicted) claims. They frequently made claims that were mostly right but Insufficient \u2014 missing a key exception, limitation, or disclosure. These were the errors most likely to surface later as client dissatisfaction or scope disputes.<\/li>\n\n\n\n
- Managers could finally coach specifically.<\/strong> Instead of saying “work on your product knowledge,” managers could say “when you discuss e-discovery coverage, always mention the data-volume limit.” Using EOS’s manager dashboard, the verdicts gave them the specificity they needed.<\/li>\n<\/ol>\n\n\n\n
“Before, I could see that a rep had room to improve. I couldn’t tell anyone what to improve. Now I can. ‘This claim came back Insufficient \u2014 here’s the condition you left out.’ That’s a coaching conversation that actually changes behavior.”<\/p>\n\n\n\n
- \n
- Is your training platform giving you a score \u2014 or a diagnosis?<\/strong> Our 12-page report, Beyond Roleplay: The Rise of the Sales Knowledge Engine<\/em>, covers claim extraction, the fact-grounded verification pipeline, and the verdict system that replaces vague scores with actionable coaching. [Download the whitepaper \u2192]<\/strong><\/a><\/li>\n<\/ul>\n\n\n\n
Why verdicts beat a single score<\/strong><\/h2>\n\n\n\n
A score tells you how a session went. It doesn’t tell you why \u2014 and “why” is the only part that’s actually coachable.<\/p>\n\n\n\n
Two reps can land on the same score for completely different reasons. One lost points on delivery. The other lost points on product accuracy. Those are not the same coaching conversation, and a score alone gives a manager no way to tell them apart.<\/p>\n\n\n\n
Verdicts add the layer a score is missing. They don’t replace the score \u2014 they sit underneath it, providing the detail that makes coaching possible. For a legal services firm where precision matters and partial truths can create scope disputes, that distinction was everything.<\/p>\n\n\n\n
The takeaway for sales leaders<\/strong><\/h2>\n\n\n\n
If your training platform gives you a single number and nothing else, you have a problem you might not see until a coaching conversation goes nowhere.<\/p>\n\n\n\n
A score tells you that something needs improvement. It doesn’t tell you what. Verdicts \u2014 Supported, Contradicted, Insufficient \u2014 tell you exactly what a rep got right, what they got mostly right but incomplete, and what they got wrong outright. They turn “improve product knowledge” into “here’s the specific claim you missed, and here’s the citation.”<\/p>\n\n\n\n
That’s the difference between generic feedback and coaching that actually changes behavior.<\/p>\n\n\n\n
- \n
- Stop guessing what your reps got wrong.<\/strong> EOS replaces single scores with specific, actionable verdicts \u2014 Supported, Contradicted, or Insufficient \u2014 for every claim a rep makes. Start free with up to 5 seats at akaeos.com<\/strong>, or [download the full whitepaper]<\/strong><\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
The head of sales enablement had a dashboard that showed her exactly how every rep performed. Eighty-eights. Seventy-twos. Ninety-fours. The numbers were clean, comparable, and easy to report upward. She could see trends, track improvement, and identify who was struggling. But when she sat down with a manager to coach a specific rep who had […]<\/p>\n","protected":false},"author":1,"featured_media":11305,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3642,3640],"tags":[],"class_list":["post-11304","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai-en","category-all-en"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t
- Stop guessing what your reps got wrong.<\/strong> EOS replaces single scores with specific, actionable verdicts \u2014 Supported, Contradicted, or Insufficient \u2014 for every claim a rep makes. Start free with up to 5 seats at akaeos.com<\/strong>, or [download the full whitepaper]<\/strong><\/a>.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"
- The most common errors were in the middle category.<\/strong> Reps rarely made outright false (Contradicted) claims. They frequently made claims that were mostly right but Insufficient \u2014 missing a key exception, limitation, or disclosure. These were the errors most likely to surface later as client dissatisfaction or scope disputes.<\/li>\n\n\n\n
- Contradicted<\/strong> \u2014 the claim conflicts directly with that documentation<\/li>\n\n\n\n