How ServiceNow Certified 8,000+ Sellers in Six Weeks With AI Roleplays
Every enablement leader with a global sales team knows the certification problem. You need every seller to deliver the same message well. You need proof they can do it. And the traditional way to get that proof, a manager watching each seller one at a time, doesn’t hold up once headcount gets into the thousands.
ServiceNow’s solutions enablement team solved sales certification at scale with Yoodli. Their director of solutions enablement shared the details in a 5-star review on G2 this week. The short version: more than 8,000 sellers certified in six weeks on a program that used to take a full quarter.
Where It Started
ServiceNow runs an annual mandatory certification on its Corporate Narrative, the core story every seller tells customers. Before Yoodli, completing it meant scheduling one-on-ones with a manager, in the office or over Zoom, for every seller.
That setup had three problems.
Time. A certification requiring a manager for every seller competes directly with selling time. At 8,000 sellers, the calendar math alone stretched the program across an entire quarter.
Consistency. Feedback depended on which manager did the grading. One manager’s pass was another’s “try again.” The review describes this as subjective manager-led feedback.
Depth. The team had tried another AI vendor before. The reviewer described that vendor’s feedback as thin. Sellers got scores but not coaching they could use.
What Changed
The team moved the Corporate Narrative certification onto Yoodli AI roleplays. Each seller practiced and certified against the same scenario, graded against the same criteria, in what the reviewer called a judgment-free practice space.
Three things changed at once.
The timeline dropped from a quarter to six weeks
With no manager scheduling bottleneck, sellers completed certification on their own time. The program finished in about six weeks.
Feedback became objective
Every seller got scored against the same rubric. Managers no longer had to be the grader, and sellers got specific feedback on what to improve before trying again.
Sellers could practice before they certified
A judgment-free space means reps can run the narrative several times before the attempt that counts. That’s how certification turns into skill building. For more on designing programs reps actually complete, see our guide to sales certification programs.
A Second Program: 6,000 Sellers on New Packaging
The team didn’t stop at the annual certification. When ServiceNow introduced new packaging tiers, it used Yoodli’s AI Tutor to help 6,000 sellers practice explaining them.
The detail that stands out: sellers practiced using their own specific customer instead of a generic mock account. A rep preparing for a renewal with a real account could rehearse how the new tiers applied to that customer.
That matters for product launch training. Generic scenarios teach the pitch. Scenarios tied to a seller’s real accounts prepare them for the next actual conversation.
Beyond Certification
The review also describes how far Yoodli has spread inside the enablement team’s work. The reviewer called out the breadth of use cases across the enterprise, including:
Coaching leaders through difficult conversations with team members
Preparing sellers for unscripted, slide-free customer conversations
Practice sessions for demo delivery
Storytelling practice
For a team supporting thousands of sellers, one platform that covers certification, launches, leadership, and demos means fewer tools to manage and one place to see progress.
What They’d Improve
The review is candid about one gap. ServiceNow runs an internal learning university, and the back-end integration isn’t fully tracking learners once they click out of eLearning and into a roleplay or Tutor session. The reviewer wasn’t sure whether the issue sits with ServiceNow’s side, Yoodli, or the connection between them.
It’s a fair callout and a common one for large organizations with an existing LMS. Tighter LMS tracking is active work on our side.
What Other Enablement Teams Can Take From This
You don’t need 8,000 sellers for these lessons to apply.
1. Remove the manager from the grading seat
Managers are the most expensive and least consistent graders in most certification programs. Move grading to a consistent rubric and bring managers back in for coaching on what the data shows. Our post on using AI coaching data in 1:1s covers that handoff.
2. Let reps practice before the attempt that counts
Certification that allows repetition builds skill. Certification that’s pass or fail on the first try mostly measures nerves.
3. Use real accounts where you can
ServiceNow’s packaging program worked because sellers practiced on their own customers. Where you can, build scenarios around real deal context.
4. Plan for your LMS early
If learners start in an LMS and move into roleplays, map how completion and scores flow back before launch.
5. Measure the timeline
Time to complete certification is one of the easiest results to show leadership. ServiceNow’s quarter-to-six-weeks shift is easy to explain in one sentence.
The Bigger Picture
ServiceNow joins a list of enterprise teams running certification on Yoodli, including Google Cloud with more than 15,000 people certified and RingCentral with a 90% reduction in call-center certification time.
If certification is a manager-hours problem on your team, start small. Pick one narrative or one product, build a single AI roleplay graded against your rubric, and run one cohort through it. Compare the timeline and the feedback quality to your last round. Our guide to faster onboarding and certification with AI roleplay covers the setup, and you can read the full review on Yoodli’s G2 page.
Yoodli G2 Reviews: What Enablement Leaders Say After Rollout
Yoodli holds a 4.9 out of 5 rating on G2 across 42 reviews, and ranks among the top AI sales roleplay platforms in the category. Most of those reviews come from people who run enablement, L&D, and sales training programs at mid-market and enterprise companies. They bought the product, rolled it out, and came back to report what happened.
This post pulls together what those Yoodli G2 reviews say. The goal is to save you the scroll. If you’re evaluating AI roleplays for your team, these are the patterns worth knowing before a demo.
The reviewer list reads like an enablement org chart. Directors of solutions enablement. Commercial enablement managers. Learning strategy managers. Principal sales enablement managers. Program managers who run training for thousands of employees.
There’s also a smaller group of independent coaches and consultants who use Yoodli with their own clients, plus a handful of investors who’ve evaluated many sales enablement tools and landed on this one.
Company size skews toward enterprise and mid-market. That matters because the problems these reviewers describe are scale problems. How do you certify thousands of sellers? How do you give every rep practice when managers don’t have the hours? How do you know a rep can actually deliver the message, and didn’t just click through a course?
Theme 1: The AI Roleplays Feel Real
Realism is the most common thread across the reviews.
A learning strategy manager at an enterprise company said tenured employees told her team the roleplays matched conversations they’d had on the job. Her team leans on that personalization to keep training relevant. A reviewer at a software company went further and described the realism as almost eerie, close enough to real customer conversations that reps get pulled in.
Several reviewers connected realism to adoption. When practice sounds like a real buyer, reps stop treating it as a checkbox. One mid-market reviewer said Yoodli is the first tool his salespeople actually like using.
The second theme is range. Reviewers don’t only use Yoodli for sales onboarding.
Use cases named across the reviews include:
Sales certification on new messaging and product launches
Leaders practicing difficult conversations with direct reports
Customer success training for customer-facing teams
Communication skills for technical employees
Solution engineers rehearsing demos
Branch staff at a bank practicing customer service conversations
Partner enablement, with one roleplay built for internal and partner audiences
Presentation skills training across a company
A director of solutions enablement described using Yoodli well beyond classic stand-and-deliver roleplays. Her team coaches leaders through hard conversations, preps sellers for slide-free customer meetings, and builds practice for demo delivery and storytelling.
For enablement teams trying to consolidate tools, that range is the point. One platform covers sales, CS, leadership, and partner and reseller enablement.
Theme 3: Outcomes Reviewers Report
This is the section buyers care about most. Reviewers shared specific results.
Certification in half the time
The ServiceNow review is the largest example. The reviewer’s team moved an annual mandatory certification for more than 8,000 global sellers onto Yoodli. The program used to take a full quarter with managers running one-on-ones. It finished in six weeks, with objective feedback in place of manager-by-manager variation. The same team ran a second program where 6,000 sellers used the AI Tutor to practice explaining new packaging tiers.
Ramp time down 30%
A sales enablement manager at an enterprise company reported that onboarding ramp time dropped 30% in the first quarter of a pilot after adding Yoodli AI roleplays. If ramp is your main metric, our post on whether AI roleplay can reduce ramp time covers how to measure it.
20+ new AEs certified every month
A principal sales enablement manager said her team certifies more than 20 new AEs a month with Yoodli. Before, reps completed roleplays live with the enablement team or submitted recordings that someone graded by hand.
Hundreds of manager hours saved
A reviewer at a software company said Yoodli has saved hundreds of hours of sales manager time. Another at a bank said it took load off both the training department and branch managers.
Those numbers match what we see across enterprise customers, including Google Cloud with 15,000+ people certified and RingCentral’s 90% reduction in call-center certification time.
Theme 4: Setup Is Fast
Ease of setup shows up in reviews from small businesses and large enterprises alike.
One small business reviewer said building a roleplay now takes minutes instead of hours. An investor who reviewed the product said he gave it a prompt and it generated the scenario. Another said he was practicing in under a minute.
Admins also get a lot of mentions. A commercial enablement manager said the platform is easy for end users and for the admins building content. She called it a no-brainer given the price and usefulness.
Theme 5: The People Behind the Product
Support comes up often enough to count as its own theme. Reviewers describe a team that helps design enablement programs, responds quickly on complex rubric setups, and ships requested features fast.
A principal sales enablement manager said the Yoodli team regularly sets aside time to help her think through programs. Several others mentioned the pace of new features, like Tutor and sidebar navigation updates, as a reason they stay.
What Reviewers Want Improved
The reviews aren’t all praise, and that’s useful for buyers.
The most common request is for richer, more customizable analytics. Reviewers want to choose which data goes into reports, build their own dashboards, and see metrics like max score next to average score in the same view.
The second is the admin model. A few reviewers said the relationship between groups, reporting teams, and roleplay organization takes time to learn. One noted that recent sidebar navigation changes already helped new authors.
A few enterprise reviewers also asked for tighter LMS tracking when learners move from an eLearning course into a roleplay. Both of these areas are active work on our roadmap.
How to Use These Reviews in Your Evaluation
If you’re comparing AI roleplay platforms, G2 reviews are one of the better signals available. A few ways to use them well:
Filter by company size. Enterprise reviewers describe different problems than small teams. Read the ones that match yours.
Look for numbers. Reviews that name a result (ramp time, certification timelines, hours saved) tell you more than general praise.
Read the dislikes. They tell you what to test in a pilot.
Match use cases. If you need leadership or CS training alongside sales, check whether reviewers mention those.
G2 lists Yoodli in its sales coaching software category alongside larger enablement suites. The reviews point to where Yoodli stands out: realism, range of use cases, and fast setup, backed by a team that works closely with enablement leaders.
If you want to see what reviewers are describing, the fastest way is to try a roleplay built on your own content. Start with the conversation your reps find hardest, whether that’s objection handling, discovery, or a new product pitch, and see how the feedback compares to what your managers give today.
Gong Alternatives: How Yoodli Compares for AI Sales Roleplay
Yoodli and Gong both help sales teams improve customer conversations through AI-powered coaching and roleplay, but they start from different places. Yoodli is an experiential learning and AI roleplay platform built around realistic practice, personalized feedback, repetition, and measurable readiness across sales and other professional conversations. Gong is a Revenue AI platform built around capturing and analyzing real customer interactions, with AI roleplay now integrated into Gong Enable through AI Trainer. Yoodli is likely the stronger fit when scalable practice and broader experiential learning are the priority. Gong is likely the stronger fit when an organization wants roleplay tightly connected to conversation intelligence, live customer data, deal execution, and forecasting.
Summary
Yoodli and Gong increasingly overlap in sales coaching and AI roleplay, but they are not interchangeable.
Gong historically focused on analyzing real sales conversations. In 2026, that changed: Gong Enable now includes AI Trainer, which builds practice scenarios from customer interactions already captured in Gong and scores them with the same scorecards used on live calls. Its Dry Run capability can also prepare a rep for a specific upcoming meeting using actual account context.
Yoodli approaches sales development from the practice side. Its AI Roleplays give reps realistic, repeatable practice with immediate feedback on communication effectiveness and organization-specific criteria, and extend beyond sales into leadership development, customer success, partner enablement, and broader experiential learning. That broader reach is one of the most important distinctions from Gong.
Yoodli is likely the stronger fit if you prioritize:
AI roleplay and repeated practice as the central learning experience
Communication feedback covering delivery, clarity, pacing, and effectiveness
Experiential learning beyond the revenue organization, including leadership and customer success
Multi-persona roleplays across 40+ languages
Gong is likely the stronger fit if you prioritize:
Conversation intelligence and automatic capture of real customer interactions
AI roleplays created from actual sales conversations, scored on the same scorecards as live calls
Deal intelligence, pipeline visibility, and forecasting in one unified Revenue AI platform
For some enterprises, the right answer may not be Yoodli or Gong. Yoodli now supports Gong-connected workflows, and its August 2026 release notes describe dashboards that compare practice with real-call performance for organizations using call intelligence integrations. That makes a complementary model credible: Gong provides customer conversation data, and Yoodli provides a specialized practice environment.
Yoodli vs. Gong at a Glance
Area
Yoodli
Gong
Core positioning
AI roleplay and experiential learning
Revenue AI operating system
AI sales roleplay
Yes
Yes, through AI Trainer
Dynamic AI buyer personas
Yes
Yes
Roleplays based on real customer calls
Via call intelligence integrations
Native strength
Upcoming-deal practice
Custom-built scenarios
Dry Run automates this with account context
Custom scorecards
Yes
Yes
Same scoring across practice and real calls
Via connected workflows
Native capability
Communication delivery feedback
Major focus
Within coaching and evaluation
Conversation intelligence
Via integrations
Core platform capability
Automatic call capture
Not core
Core capability
Deal intelligence
Not core
Yes
Forecasting
No
Yes
Sales engagement
No
Yes, through Gong Engage
Multi-persona roleplay
Yes
Supported, scope evolving
Broader non-sales learning
Extensive
Primarily GTM-focused
Languages for roleplay
40+ advertised
24 voice languages for AI Trainer
Individual self-service pricing
Yes
No comparable product
Enterprise pricing
Custom
Custom, per user plus platform fee
Best fit
Scalable experiential practice
Revenue teams needing conversation and revenue data
Gong separately supports more than 70 languages across its broader conversation capture, transcription, and analysis platform. Do not confuse that figure with AI Trainer’s language support, which currently lists 24 voice languages.
What Is Yoodli?
Yoodli is an AI-powered experiential learning platform built to help people practice high-stakes conversations before those conversations happen in the real world. Its AI Roleplays create dynamic conversations with customers, buyers, stakeholders, managers, and other personas.
For sales teams, common practice scenarios include discovery, objection handling, cold calls, product positioning, demos, negotiations, and multi-stakeholder meetings. After a roleplay, Yoodli gives immediate feedback so the learner can pinpoint what to improve and repeat the scenario, evaluating both organization-specific criteria and communication behaviors like clarity, pacing, and delivery, so the goal is demonstrated readiness, not a completed exercise. That model also extends beyond sales into leadership development, manager training, customer success, and partner enablement.
What Is Gong?
Gong is a Revenue AI platform built around customer interaction data. Its conversation intelligence technology captures and analyzes calls, meetings, and emails, then surfaces buyer signals, objections, and deal risk. The broader platform extends into revenue enablement, coaching, deal execution, sales engagement, forecasting, and account management.
Gong states that its models are informed by more than 3.5 billion sales interactions and that the company serves more than 5,000 customers. These are Gong-published figures, not independent measurements.
Does Gong Have AI Sales Roleplay?
Yes. Older comparisons describe Yoodli as the roleplay platform and Gong as pure conversation intelligence. That is no longer accurate.
Gong introduced Gong Enable in February 2026 as part of its Mission Andromeda launch, adding AI Trainer alongside AI coaching, lessons, call review, and coaching workflows. AI Trainer lets reps practice new messaging, pitches, discovery, objection handling, and negotiation against AI personas built from actual interactions already captured in Gong, scored against the same standards used for live calls.
Both Yoodli and Gong now provide AI roleplay. The real question is what type of system you want your roleplay program built around.
AI Roleplay: Yoodli vs. Gong
Yoodli’s core product is purpose-built around repeated AI roleplay practice: configure a scenario around buyer personas, objections, products, sales methodology, and scoring rubrics, then let the learner practice, get immediate feedback, and repeat until performance improves. Yoodli also supports multi-persona AI roleplays, multi-speaker analysis, and cross-organization scenarios.
Gong AI Trainer’s strongest differentiator is where the scenario data comes from. Because Gong already captures real customer interactions, it can build training that reflects actual customer behavior, grounded in what reps are encountering in the field.
Verdict: Both platforms now have credible AI roleplay capabilities. Yoodli is more fundamentally built around experiential practice itself. Gong has a powerful advantage when practice needs to emerge directly from customer interactions already contained inside Gong.
Real Customer Data: Gong’s Biggest Advantage
This is the clearest structural advantage Gong has: its starting point is actual customer interaction data. The conversation intelligence system captures calls, meetings, and emails, and Gong says it can surface objections, competitive mentions, buyer signals, and deal risk straight into the enablement process.
A sales organization that discovers through Gong that reps struggle when procurement raises implementation concerns does not have to guess what training should cover. Enablement can build roleplays around the real pattern. The loop becomes:
Real call -> observed behavior -> identified skill gap -> AI practice -> subsequent live-call measurement
A standalone roleplay product struggles to replicate that closed loop without access to conversation intelligence data.
Verdict: Gong has the stronger native data foundation for connecting real customer interactions directly to practice.
Yoodli’s Response: Connecting Practice With Real Calls
Yoodli’s approach is integration-oriented: connect practice and coaching with systems the organization already uses rather than become a complete revenue intelligence platform itself. Its integrations support CRM, call intelligence, LMS, HRIS, and other enterprise systems, including Gong. Yoodli’s August 2026 release notes describe Gong-connected dashboards and reporting that compares real calls with practice.
An organization already using Gong for conversation intelligence does not necessarily need it to become its sole training environment. It can use Gong to capture and analyze conversations and Yoodli to provide specialized AI roleplay, with the integration connecting real performance to practice performance.
Upcoming Meeting Practice
Gong’s 2026 Dry Run feature lets a seller launch a roleplay for an upcoming meeting using existing account information, automatically pulling in deal stage, customer persona, and conversation history. The rep practices a version of the actual meeting instead of a generic scenario.
Yoodli’s Builder can generate scenarios, personas, objections, and rubric goals from a description, but Gong has the stronger native advantage when the account and conversation history already live inside Gong.
Verdict: Gong currently has the stronger native workflow for automatically turning a specific upcoming sales meeting into a practice session.
Feedback and Sales Coaching
Both products provide automated feedback, but their underlying perspectives differ.
Yoodli: Yoodli evaluates both content and communication performance, with feedback covering clarity, pacing, filler words, delivery, effectiveness, and alignment with custom rubrics and sales methodology. Knowing the right answer does not automatically mean communicating it effectively, and Yoodli’s AI feedback model is built to catch that gap.
Gong: Gong’s coaching system is grounded heavily in observed selling behavior. Managers use actual conversations, scorecards, coaching workflows, AI Call Reviewer, and team insights to identify skill gaps, and AI Trainer applies the same scorecards used on live calls, so practice and real customer conversations are judged the same way.
Verdict: Yoodli has a particularly strong communication-performance orientation. Gong has a particularly strong connection between coaching and observed sales behavior.
The Same Scorecard for Practice and Performance
This is one of Gong’s most compelling enablement capabilities. AI Trainer evaluates roleplays with the same scorecards applied to real calls, avoiding the measurement disconnect that happens when a roleplay platform scores a behavior one way and the conversation intelligence platform scores live calls another. Yoodli addresses the same problem through custom rubric-based evaluation and, increasingly, call intelligence integrations.
Verdict: Gong has a strong native advantage when standardized scoring across AI roleplay and captured live conversations is a primary requirement.
Conversation Intelligence
Gong remains substantially stronger in conversation intelligence, a foundational part of the platform that turns unstructured calls, meetings, and emails into structured data: transcription, topic detection, objection and buyer-signal identification, deal-risk detection, CRM automation, and AI summaries. Gong says it captures 99% of customer interactions for organizations using its platform, a Gong-published claim rather than an independent benchmark. Yoodli can analyze uploaded recordings and increasingly connects with call intelligence systems, but replacing Gong as a full conversation intelligence system is not its core proposition.
Verdict: Gong is the clear choice if conversation intelligence itself is a major purchasing requirement.
Revenue Intelligence, Deal Execution, and Forecasting
The distinction widens once the evaluation expands beyond coaching. Gong’s Revenue AI platform covers workflows Yoodli does not attempt to replace: deal risk monitoring, buying-signal detection, pipeline management, forecast visibility, outreach personalization, and CRM automation. Gong Engage extends into sales engagement, and Gong Forecast handles forecasting and pipeline.
Yoodli stays focused on learning, practice, feedback, and readiness, so a raw feature comparison is misleading here. Buying Gong solely for AI roleplay means evaluating a much larger revenue platform, and buying Yoodli for forecasting makes no sense, since that is not the problem it solves.
Verdict: Gong is much broader across revenue execution and intelligence.
Gong’s revenue specialization creates the opposite advantage for Yoodli. Yoodli’s AI roleplays extend to leadership conversations, manager coaching, difficult feedback, customer success, customer support, partner enablement, and executive communication, alongside sales training. Its broader AI experiential learning model gives employees repeated opportunities to learn, practice, get feedback, and improve. Its enterprise platform also supports admin-defined personas and rubrics, methodology partners such as Sandler and Korn Ferry, multi-persona and screen-share roleplays, and SCORM/LTI, SSO, SCIM, and HRIS integrations for company-wide deployment.
That changes the buyer. Gong naturally fits within a revenue organization’s technology stack, while Yoodli may be purchased by sales enablement, L&D, leadership development, customer success, or HR, so a global enterprise can use Yoodli across far more employee populations than Gong.
Verdict: Yoodli is the stronger option when AI roleplay is intended to become an enterprise-wide experiential learning capability rather than primarily a revenue capability.
Multi-Persona and Complex Conversation Practice
Yoodli supports multi-persona roleplays, letting learners practice conversations with several stakeholders at once, each with different priorities: a CFO focused on financial value, a security leader focused on risk, a technical evaluator worried about integration, a champion who is supportive but politically constrained. The seller has to navigate the group, not just answer isolated objections. Yoodli also supports multi-speaker analysis and cross-organization scenarios.
Gong’s AI Trainer centers on customer personas grounded in existing conversations, but Yoodli’s published positioning makes complex multi-persona roleplay more explicit.
Verdict: Yoodli has the clearer published proposition for multi-persona and broader complex roleplay formats.
Building AI Roleplay Scenarios
Yoodli has a dedicated Roleplay Builder and Roleplay Agent. Admins describe what learners should practice, and Yoodli generates scenario context, personas, objections, goals, and rubric criteria to edit, test, and deploy.
Gong administrators can similarly create AI Trainer scenarios for onboarding, messaging changes, or customer personas, defining trainee background, objectives, and session length (5 to 30 minutes), and testing them with sales leaders before publishing. The major difference remains data source: Yoodli turns organizational knowledge into practice, and Gong turns captured customer conversations into practice.
Verdict: Both provide substantial scenario-building capabilities. Test the builder directly rather than assuming one will be easier based on feature descriptions.
Sales Onboarding and Certification
Both platforms support onboarding. Yoodli’s AI sales training lets organizations build standardized roleplays around product messaging, discovery, objections, competitive positioning, and certification, so enablement can assess whether a seller can perform the skill, not just whether they finished the course. Gong Enable takes a broader approach: alongside AI Trainer, it includes lessons, assessments, AI Call Reviewer, and team insights, and can use actual field behavior to identify where future training should focus.
Verdict: Yoodli is particularly compelling as a dedicated practice and certification layer. Gong is stronger when onboarding needs to sit inside a broader system connecting learning, live calls, coaching, and revenue performance.
Global Language Support
Language comparisons require care because Gong supports different language sets for different capabilities. Yoodli advertises 40+ languages for AI roleplays. Gong’s broader platform supports more than 70 languages across call transcription and analysis, but Gong AI Trainer lists only 24 voice languages in its June 2026 documentation, so those figures should not be compared as the same capability.
Verdict: Yoodli currently advertises broader language support specifically for AI roleplay. Gong has broader published language coverage across its overall conversation intelligence platform.
Security and Compliance
Both companies are positioned for large enterprise deployments. Yoodli is SOC 2 Type 2 certified and GDPR compliant, with enterprise capabilities including SSO, SCIM, data-retention controls, and additional administrative features.
Gong publishes a broader security and compliance portfolio, including SOC 2 Type II, ISO 27001, ISO 27017, ISO 27018, ISO 27701, ISO 42001 for AI management, CSA STAR, the EU-US Data Privacy Framework, PCI DSS-related controls, and HIPAA mapping within its SOC 2 report, per Gong’s own compliance documentation.
Verdict: Both should go through normal enterprise security review. Gong publishes more specific certifications, understandable given the volume of sensitive conversation and revenue data it captures.
Pricing: Yoodli vs. Gong
Yoodli publishes individual plans alongside custom Team and Enterprise pricing: a free Starter tier with five lifetime roleplays, Pro at $8 per month billed annually with up to 10 roleplays per week, and Advanced at $20 per month billed annually with unlimited roleplays.
Gong does not publish standard per-user dollar pricing. Its pricing page states that cost depends on team-specific factors, with licenses priced per user plus a platform fee, and that existing tech-stack integrations do not carry an extra fee.
Verdict: Yoodli is easier to evaluate independently and has transparent individual pricing. Enterprise buyers will need customized quotes to compare total cost.
Customer Evidence
Yoodli’s case studies report Google Cloud certifying more than 15,000 employees on a new go-to-market pitch, Snowflake saving more than 1,200 manager hours of coaching time per quarter with 94% participation across roughly 3,000 sellers, ServiceNow cutting seller ramp time by 50%, and Clari improving GTM conversation quality by an average of 36% across five core conversation skills, all using Yoodli AI roleplays. These are first-party case study results, not universal benchmarks.
Gong states that more than 5,000 customers use its platform and that its AI is informed by billions of sales interactions, and Gong Enable publishes customer examples describing faster onboarding and scalable AI practice scenarios. These figures and testimonials come from Gong’s own materials.
Do not compare these numbers directly. Yoodli’s case studies measure practice volume, readiness, and skill improvement. Gong’s evidence spans revenue intelligence, sales execution, coaching, and forecasting.
Where Yoodli Is Stronger
Yoodli is likely stronger when an organization primarily needs:
Dedicated AI roleplay and repeated conversational practice
Communication delivery feedback and multi-persona roleplays
Cross-functional experiential learning, including leadership development and customer-facing training beyond sales
Global roleplay across 40+ languages
Individual access alongside enterprise deployment
A practice layer that can integrate with Gong and other existing systems
Gong now has roleplay too. What sets Yoodli apart is that its entire platform is designed around practice and experiential learning across many forms of professional communication.
Where Gong Is Stronger
Gong is likely stronger when an organization primarily needs:
Conversation intelligence and automatic customer interaction capture
Revenue intelligence, deal insights, forecasting, and sales engagement
AI practice grounded directly in captured customer conversations, scored on the same scorecards as live calls
Upcoming-meeting practice using account context
One revenue data foundation across several sales workflows
Gong’s central competitive advantage is that practice sits directly beside the data showing what sellers actually do with customers.
Can Yoodli and Gong Work Together?
Yes, and this may be the most important conclusion in this comparison. Yoodli and Gong overlap more than they once did, but they can still play complementary roles.
A company could use Gong to capture real calls and track deal execution, then use Yoodli to run specialized practice programs, repeated AI roleplays, and multi-persona training, extending experiential learning beyond sales.
Companies already paying for Gong should not assume they need to replace it to use Yoodli, and companies using Gong Enable should check whether AI Trainer already satisfies their practice needs before adding another platform.
Yoodli vs. Gong: Which Should You Choose?
Choose Yoodli if your central question is how to give people scalable, realistic practice and feedback so they become ready for high-stakes conversations, especially when the deployment spans sales plus leadership, customer success, support, partners, or L&D.
Choose Gong if your central question is how to use real customer interactions to improve selling, coaching, deal execution, forecasting, and practice, all from one system connecting conversation data with the wider revenue workflow.
For sales teams evaluating AI roleplay specifically, run both platforms through the same scenario: the same buyer persona, product information, objection, methodology, and seller population. Then evaluate:
Realism: Does the AI behave like an actual buyer, and can the rep tell exactly what to change from its feedback?
Repetition: Does repeated practice lead to visible improvement, and can the organization tell whether practiced behaviors show up with real customers?
Administration: Can enablement teams create and update scenarios efficiently, and does the system make manager coaching more targeted?
Adoption and overlap: Will reps practice repeatedly without being forced, and which existing technologies could this realistically replace?
The final choice should not come down to which vendor has the longer feature list. Choose the system that best connects practice, feedback, real-world behavior, and the outcomes your organization actually needs to improve.
FAQ
Do you need a separate AI roleplay platform if your company already uses Gong?
Not necessarily. Gong now provides native AI roleplay through Gong Enable’s AI Trainer, so evaluate that first. A specialist platform still earns its place when you need deeper experiential learning, non-sales use cases, or a practice environment spanning multiple business functions.
Can sales teams use Yoodli without giving it every customer call?
Yes. A roleplay program can be built from approved buyer personas, methodologies, messaging, objections, and training materials, without giving the platform unrestricted access to customer conversations.
Should companies let AI automatically create training from weak sales calls?
Not without human oversight. Real calls can reveal genuine gaps, but enablement leaders should validate recurring patterns before turning one unusual conversation into standardized training.
Is practice based on real account data always better than generic roleplay?
Not always. Account-specific practice is useful before an important meeting, but standardized scenarios compare readiness across employees more fairly, since everyone faces similar conditions. Mature programs use both.
Should live-call scores and roleplay scores be identical?
The framework can be consistent, but expectations should differ. Practice exists partly so learners can experiment and make mistakes.
Can Gong and Yoodli both be used in the same sales enablement stack?
Yes. Gong provides conversation intelligence and field-performance data, while Yoodli provides dedicated AI roleplay and experiential learning, and Yoodli’s Gong-connected dashboards let organizations compare practice with real-call performance.
Which platform is better for leadership training?
Yoodli, generally, since its experiential learning platform extends beyond revenue use cases into leadership, manager, and professional communication development. Gong stays oriented around revenue teams and customer-facing execution.
What Is a Sales Battlecard, and Why Reps Stop Using Them
A sales battlecard is a short reference document that tells a rep how to position against a specific competitor or handle a specific deal situation. Most teams have them, and plenty of reps stop opening them after the first few weeks. The card gets read at a desk, the competitive objection shows up mid-call, and nothing in between trains the rep to get from one to the other.
This guide covers what a battlecard is, what belongs on one, why adoption drops off, and how enablement teams can make the content usable on a live call.
What a Sales Battlecard Is
A battlecard is a one-page or one-screen summary built for speed. A rep should be able to scan it in under a minute before a call, or glance at it during one. It is narrower than a sales playbook and more tactical than a full competitive analysis. HubSpot’s guide to sales battle cards shows several common layouts if you want visual examples.
There are three common types:
Competitor battlecards cover one named competitor. They explain where that competitor wins, where it loses, what its reps say about you, and how to respond.
Objection battlecards cover one recurring objection. Price, timing, and “we built this in-house” are typical examples, each paired with a clarifying question and a response.
Persona battlecards cover one buyer role. A CFO card or an IT security card lists what that person cares about, what they ask, and what proof they need.
Competitor cards usually come out of competitive intelligence work, so product marketing tends to own them. Enablement often owns the other two types. On smaller teams, one person owns all of them.
What Belongs on a Good Competitive Battlecard
A battlecard earns its place by being shorter than the alternative. The strongest ones share a structure:
When to use it: The first line names the trigger, such as “the prospect mentions they are also evaluating X” or “the buyer asks for a discount before seeing pricing.”
What they will hear: The card lists the claims the competitor makes, in the words the competitor’s reps actually use.
Where we win: Two or three differentiators appear here, each tied to a buyer outcome instead of a feature.
Where we lose: Reps trust a card more when it admits weak spots, and they get blindsided less often.
Landmines: These are questions the rep can ask to surface a competitor’s weak spots without criticizing them.
Responses to the top objections: Each answer is short and written in spoken language, because a line that reads like a press release never gets said out loud.
Proof: Every claim gets one customer story or data point, with a link to the full asset.
Anything past that belongs in a linked doc. A battlecard that scrolls has turned into a whitepaper. The response section usually draws on your team’s objection handling framework, so keep the two aligned.
Why Reps Stop Using Sales Battlecards
Adoption falls off for predictable reasons, and each one has a fix.
The content goes stale
A competitor changes pricing or ships a feature, and the card still describes last year’s product. One outdated claim repeated on a call costs the rep credibility. After that, they stop trusting the card.
It lives in the wrong place
If the card sits three folders deep in a shared drive, it does not exist during a call. Teams that surface cards inside the CRM or the tools reps already have open see better usage. Our post on integrating sales practice into your CRM workflow covers how to put both the content and the practice where reps already work.
Reading a response differs from saying one
This is the big one. A rep can read “acknowledge the concern, ask what is driving it, then reframe around total cost” and agree with every word. The first time a buyer says “your competitor is cheaper,” the rep may still discount, ramble, or get defensive. Knowing the answer and delivering it under pressure are separate skills, and the card only covers the first.
The “already using a competitor” objection is a good example. Most reps know the right response on paper. Far fewer can deliver it calmly when a buyer raises it in the first five minutes.
Nobody checks whether it worked
Enablement ships the card, marks the project done, and has no signal on whether reps use the talk track or whether it lands with buyers. Without that loop, the card never improves.
How to Make Battlecards Usable on a Live Call
The fix for the first two problems is operational. Assign an owner, set a review cadence, and put the cards where reps work. The third and fourth problems need practice.
Turn each card into a practice scenario
Every competitor or objection card describes a moment in a conversation, and that moment can be rehearsed. Take the trigger, the objection, and the buyer persona from the card and build a short roleplay around it. The rep hears the objection the way a buyer would say it, responds out loud, and gets feedback on whether they hit the points on the card.
A rep who has handled the “you’re more expensive” objection ten times in practice sounds different on the eleventh, live one. They skip the pause, the filler, and the instinct to discount.
Practice the landmine questions
Landmine questions are the most underused part of most battlecards because they feel awkward to ask. Reps worry they will sound like they are attacking the competitor. Practice fixes this faster than any wording tweak. Once a rep has asked the question a few times and heard how a buyer responds, it becomes a normal part of discovery.
Score against the card
If the practice scenario is scored on the same points the card lists, you get the feedback loop battlecards usually lack. You can see which reps hit the differentiators, which responses they skip, and which talk tracks fall flat. That data tells product marketing which parts of the card to rewrite.
Where AI Roleplay Fits in Sales Battlecard Training
Traditional battlecard practice means a manager or a peer plays the competitor’s champion. It works well in small doses. Most managers do not have time to run it for every card and every rep, so the practice rarely keeps pace with the content.
AI roleplay platforms like Yoodli let enablement teams build practice scenarios from existing content, including battlecards. Our guide on training AI roleplay on your company’s sales content walks through that setup. Reps rehearse on their own schedule inside AI roleplays, where the AI plays the buyer, raises the objection, and pushes back when the answer is weak.
Reps get AI feedback right after each attempt. Enablement leaders get analytics and reporting on how the team performs against each card, all inside Yoodli.
Before you ship your next card, check each of these:
The card fits on one screen.
The trigger appears in the first line.
The responses use words a rep would say out loud.
The card admits where you lose.
It includes at least one landmine question.
Every claim links to proof.
It has a named owner and a review date.
It has a matching practice scenario.
Most teams skip the last item, and it decides whether the card gets used.
Frequently Asked Questions
What is the difference between a battlecard and a sales playbook?
A battlecard covers one competitor, objection, or persona and is built to be read in under a minute. A sales playbook covers the full sales process, including stages, qualification, messaging, and plays. Most teams link battlecards from the playbook so reps can move from the big picture to the specific situation in front of them.
Who should own sales battlecards?
Product marketing usually owns competitor battlecards because that team tracks the market. Enablement often owns objection and persona cards because they connect to training. Whatever the split, each card needs one named owner and a review date, so someone is accountable when a competitor changes pricing or positioning.
How often should battlecards be updated?
Competitor battlecards should be updated whenever a competitor makes a material change in pricing, packaging, or positioning. Outside of those moments, a fixed review cadence keeps cards from drifting, and quarterly is common. Update the matching practice scenario at the same time so reps rehearse the new response before they need it.
Do battlecards work for new reps?
Battlecards help new reps, and they work best when new hires practice the card before using it live. Reading the card gives them the content, and rehearsing it in a roleplay builds the delivery. New reps then walk into their first competitive call having already answered the objection several times.
Making Sales Battlecards Stick
A sales battlecard works when reps trust it, can find it, and have already said its lines out loud. Keep cards short and current, and give each one a practice scenario. Yoodli AI roleplays turn the cards your team already has into practice that shows up on live calls.
What Is Buyer Enablement, and How It Changes the Sales Conversation
Buyer enablement is the practice of giving buyers the information, tools, and support they need to make a purchase decision inside their own organization. Where sales enablement prepares your own reps, buyer enablement prepares the champion who has to win internal approval in meetings your team never attends.
Most B2B purchases are decided by a group, and much of that group’s discussion happens without the vendor present. A good program accepts that and designs for it. This guide covers what buyer enablement means, how it compares with sales enablement, what it asks of reps, and how enablement leaders can prepare their teams for it.
What Buyer Enablement Means for B2B Sales Teams
The idea is simple. A buyer who likes your product still has to convince finance, IT, legal, and at least one senior leader. Each group brings different questions. Your champion usually answers those questions alone, in internal meetings, with whatever material your rep left behind.
This approach treats that internal selling work as part of the sales process. The vendor’s job expands from convincing the champion to equipping the champion to convince everyone else. Marketing researchers call this group the buying center, and its size is a big reason deals stall after a strong first call.
In practice, it shows up in four ways:
Content is built for internal use. A one-page business case the champion can forward, a security summary IT can review without a call, and a pricing explainer finance can read in two minutes all fit here.
Buyers get decision support. Reps share how similar companies evaluated the product, who was involved, and what each group needed to see.
Buyers get tools they can use alone. ROI calculators, comparison frameworks, and implementation timelines answer questions before they turn into objections.
Reps coach the champion. The seller helps the champion anticipate pushback and plan the internal conversation.
Buyer Enablement vs. Sales Enablement
The two terms get confused because they share a word. They serve different audiences, and each one depends on the other. Our breakdown of revenue enablement vs. sales enablement covers a related distinction that comes up in the same planning conversations.
Sales enablement
Buyer enablement
Audience
Your reps
The buying group
Goal
Help reps run better conversations
Help buyers make and defend a decision
Typical assets
Playbooks, talk tracks, battlecards, training
Business cases, ROI tools, security docs, internal pitch decks
Who owns it
Enablement and sales leadership
Usually shared across marketing, sales, and enablement
Success looks like
Faster ramp and higher win rates
Fewer stalled deals and shorter internal approval cycles
Content for buyers is only useful if reps know how to introduce it, when to send it, and how to coach a champion through it. That part is a sales enablement job. Many teams run both programs from the same sales enablement solution and training calendar for that reason.
How Buyer Enablement Changes the Sales Conversation
A rep running this motion has a different job on every call. Three shifts stand out.
Discovery goes past the champion
Standard discovery asks what the buyer needs. Discovery in this motion also asks who else needs to agree, what each of those people cares about, and what stalled past purchases at this company. Reps who skip those questions tend to learn about the procurement review or the security questionnaire weeks into the deal.
Useful questions include:
“Who else will weigh in before this gets approved?”
“When your team bought something similar, what slowed it down?”
“What will your CFO ask you first when you bring this to them?”
Reps build this habit faster when they rehearse it before live calls. Our guide to discovery call practice shows how teams run those reps on a regular schedule.
The rep coaches the champion
The most valuable conversation in the deal is the one where the rep helps the champion rehearse their own internal pitch. What will the VP push back on? What number will finance care about most? What happens if IT raises a data residency concern?
This is a coaching conversation, and many reps have never been trained to run one. They know how to pitch the product. Helping someone else pitch it takes a different set of questions and more patience. A strong champion in B2B sales is worth that effort because they carry the deal into rooms the rep never sees.
Every stakeholder gets a tailored message
A CFO and an enablement lead hear the same product very differently. This motion asks reps to adjust their message for each person in the buying group, often in the same week and sometimes on the same call. That flexibility comes from practice, since a single talk track rarely fits every stakeholder.
Harvard Business Review’s article on the new sales imperative describes how consensus gets harder as more people join a purchase. Reps who can speak to each role keep that consensus moving.
New Skills Reps Need for Multi-Stakeholder Deals
This work raises the skill bar for sellers. Reps need to do five things well:
Map the buying group early. Reps should keep updating that map as the deal moves and new names appear.
Speak each stakeholder’s language. Finance hears cost and risk, IT hears security and integration, and leadership hears strategy and outcomes.
Coach without overstepping. Good reps help the champion prepare without scripting them or making them feel managed.
Handle multi-threaded calls. A call with three or four stakeholders stays on track only when the rep can balance what each person wants.
Know when to send what. A business case sent too early gets ignored, but the same document sent at the right moment goes straight into the approval meeting.
Each of these is a conversation skill. Reps build them by saying the words out loud to a realistic buyer, many times, before a live deal depends on it.
How to Build Practice Into a Buyer Enablement Strategy
Teams that take this seriously usually find the content is the easy part. Getting reps comfortable with the new conversations takes longer, so the practice plan deserves as much attention as the asset library.
Practice the stakeholder calls before they happen. Build scenarios where the rep presents to a skeptical CFO, answers a security lead’s questions, or handles a procurement contact pushing on terms.
Practice the champion coaching conversation. Have reps walk an AI champion through how to present the business case internally, including the objections that champion is likely to face.
Practice group calls. A call with a buying committee is harder than a one-on-one. Reps need practice managing multiple voices, redirecting side conversations, and making sure each person leaves with what they needed.
Yoodli supports this kind of practice with AI roleplays built around your own deal scenarios. Teams can also run multi-persona roleplays where a rep presents to several AI stakeholders at once, each with their own priorities and objections. Reps get feedback after each session, and enablement leaders can see which conversations need more work through analytics and reporting in Yoodli.
Teams treat it as a content project. Publishing a business case template does nothing if reps do not know how to use it in a deal.
One asset gets built for everyone. A 20-page deck serves nobody in the buying group well, and short, role-specific assets travel further.
The champion gets left alone. The champion is doing the vendor’s selling internally, so reps who check in, coach, and prepare them lose fewer deals to silence.
Stakeholder discovery gets skipped. If the rep only knows the champion’s priorities, every other stakeholder becomes a surprise late in the deal.
Frequently Asked Questions
Is buyer enablement the same as customer enablement?
Buyer enablement and customer enablement are separate programs that run at different stages. The first happens before the purchase and helps the buying group reach and defend a decision. Customer enablement starts after the contract is signed and helps customers adopt the product and get value from it. Some content overlaps, but the goals and owners differ.
Who owns buyer enablement?
Ownership is usually shared across marketing, sales, and enablement. Marketing builds much of the content, sales runs the motion in each deal, and enablement trains reps on the conversations. Some companies assign a single owner, often in revenue enablement or product marketing, to keep assets current and consistent across the buying journey.
How do you measure buyer enablement?
You measure it by tracking how deals move after the champion is engaged. Common signals include time spent in late deal stages and the share of deals that stall after a strong first call. Teams also watch the number of stakeholders engaged per deal and win rates on multi-stakeholder opportunities. Practice scores show whether reps are ready for those conversations.
Does buyer enablement matter for mid-market deals?
It matters in any deal where more than one person has to approve the purchase. Even mid-market deals often involve a manager, a finance contact, and someone from IT. The same principles apply at a smaller scale, with fewer assets and shorter approval cycles, and the champion still needs help making the case internally.
Making Buyer Enablement Stick
The approach works when content and conversation skills grow together. Give champions short, role-specific assets. Then give reps regular practice on the stakeholder calls and coaching conversations those assets support. Yoodli AI roleplays let enablement teams build those conversations into everyday training, so reps walk into multi-stakeholder deals already prepared.
Most managers learn to deliver a hard performance conversation the same way. They do it a few times with real people on their team and learn from what goes wrong. That is an expensive way to build the skill, because a conversation that misses can cost a manager an employee’s trust for months.
These conversations also tend to arrive with little warning, after a missed target or a concern raised by a peer. This guide covers why performance conversations are hard, what a good one sounds like, and how managers and L&D teams can build practice in before the stakes are real.
Why a Hard Performance Conversation Goes Wrong
The content of a performance conversation is rarely the hard part. Most managers know what they need to say. They struggle with saying it clearly, staying steady when the employee reacts, and reaching an agreed next step.
These are the most common patterns:
Burying the message. The manager opens with ten minutes of small talk and positive feedback, then mentions the real issue briefly at the end. The employee leaves thinking the meeting went well.
Over-explaining. A nervous manager justifies the feedback at length, which reads as uncertainty and invites debate.
Reacting to the reaction. The employee gets defensive, upset, or quiet, and the manager softens the message or drops it.
Leaving without a plan. The conversation ends with shared discomfort and no clear agreement on what changes next.
Each of these is a delivery problem. Knowing the right framework does not stop a manager from rushing, hedging, or backing down when the person across the table pushes back. Delivery improves with practice, which is why the rest of this guide focuses on how to rehearse.
What a Good Performance Conversation Sounds Like
Frameworks vary, but the conversations that work tend to follow the same shape. Many managers already know a version of it from the SBI feedback model, which ties feedback to a specific situation, behavior, and impact. SHRM’s guide to managing employee performance is another useful reference for the policy side.
1. State the purpose early
Name the issue in the first minute or two. For example: “I want to talk about the last three client deliverables. Each one went out late, and I want to understand what is happening and agree on a fix.” The employee knows why they are in the room, and the manager avoids a long buildup.
2. Describe behavior and impact
Stick to what happened and what it caused. “The Q3 report reached the client two days after the deadline, and they escalated to their account lead.” Avoid labels like “careless” or “not committed.” Describing behavior keeps the conversation on something the employee can change, and labels tend to start an argument.
3. Ask, then listen
Ask the employee for their view and give them room to answer. “What is getting in the way?” works well. The goal is to learn something. Sometimes the answer changes the conversation, such as a workload problem, a process gap, or something outside work.
4. Hold the line calmly
If the employee disagrees, acknowledge their view without dropping the point. “I hear that the timeline felt unrealistic. The deadline still matters, so let’s talk about how we flag that earlier next time.” This is the step that most often slips when a manager has never rehearsed it.
5. Agree on a next step
End with something specific: what will change, by when, and when you will check in. Write it down and send it after the meeting. A short written summary keeps both people working from the same plan.
Why Practice Helps More Than Preparation
Most manager training covers a framework like the one above in a workshop. Participants read the steps, watch a demonstration, maybe try a short roleplay with a peer, and go back to work. A few months later, when a real conversation comes up, much of that has faded.
Preparation helps. Writing down the key message, anticipating the employee’s response, and planning the next step all make the conversation better. Still, preparation alone does not get a manager ready for how it feels when the employee pushes back, goes quiet, or gets emotional. That part improves with repetition.
Repetition is hard to get. Managers do not want to practice on their team. Peer roleplay in a workshop is useful but awkward, and it usually happens once. Most managers never get a chance to rehearse the specific conversation they have to hold next week. The same is true for other crucial conversations at work, from peer conflict to delivering a change in role.
Generic scenarios like “an employee is underperforming” are easy to write and easy to forget. Scenarios built from the situations your managers actually face work better. Think of missed deadlines, a strong performer with a poor attitude, a peer conflict, or a promotion the employee expected and did not get. Each one has its own emotional texture and its own likely pushback.
Vary the employee’s reaction
The same conversation plays out very differently depending on the response. Practice each scenario against several reactions: defensive, emotional, silent, and agreeable but noncommittal. Managers who have heard all four are much less likely to freeze on any of them.
Give feedback on delivery
Managers need to hear how they came across. Did they state the issue in the first two minutes? Did they describe behavior or use labels? Did they talk more than they listened? Did they end with a clear next step? Specific feedback after each attempt makes the next attempt better. Gallup’s research on how effective feedback fuels performance makes the same case for frequent, specific feedback at work.
Make practice available on demand
The most useful moment to practice is the day before a real conversation. A manager who can rehearse privately, on their own schedule, is far more likely to do it than one who has to book time with a coach or a colleague. Private practice also lowers the pressure, which is the idea behind judgment-free coaching.
Where AI Roleplays Fit for Performance Conversations
AI roleplays give managers a private place to rehearse a hard performance conversation. The AI plays the employee, reacts the way a real person might, and pushes back when the message is unclear or the manager backs off. Managers can run the same conversation several times, try different openings, and get feedback on each attempt without anyone on their team knowing.
Yoodli supports this kind of practice for leadership and manager development. L&D teams can build scenarios around their own management frameworks. Managers get real-time AI feedback on pacing, conciseness, and how well they covered the key points.
Do you have two or three specific examples of behavior and impact?
Have you thought through how the employee is likely to respond?
Do you know what outcome you want from the meeting?
Have you said the opening out loud at least once?
The last item is the step most managers skip, and it makes the biggest difference. Saying the first two sentences out loud is the fastest way to find out whether the message is clear.
Performance Conversation FAQ
How long should a performance conversation take?
Most performance conversations run 20 to 45 minutes. That is long enough to state the issue, hear the employee’s view, and agree on next steps. A conversation that runs much longer usually means the core message has gotten lost. Plan the opening and the closing ask in advance so the middle has room to breathe.
Should HR be in the room for a performance conversation?
For routine performance feedback, HR usually does not need to be in the room. The manager owns the conversation and the follow-up. For formal performance improvement plans, follow your company’s HR policy, which may call for HR involvement or documentation. When in doubt, check with your HR partner before the meeting.
What should you do if the employee gets emotional?
Pause, acknowledge the emotion, and offer a short break if the employee needs one. Stay calm and keep your tone steady. If the conversation needs to continue another day, schedule the follow-up before the meeting ends. The issue still needs to be addressed, so make sure there is a clear time to return to it.
Can you really practice a hard performance conversation?
You can practice a hard performance conversation, and it helps. The exact words and the employee’s reaction will differ in the real meeting. Rehearsal gives a manager the chance to state the issue clearly, try out responses to pushback, and plan the close. In the real meeting, they have already heard themselves say the hard part once.
Practice Before the Stakes Are Real
A hard performance conversation is a skill, and skills improve with practice and feedback. Managers who rehearse the opening, hear a range of reactions, and get specific feedback walk into the real meeting steadier and clearer. Yoodli AI roleplays give L&D teams a way to offer that practice to every manager, on demand, built around the situations they actually face.
What Is Transfer of Training? Why Skills Don’t Show Up on the Job
Every enablement and L&D team has seen the same pattern. A program gets strong completion rates and good survey scores. Three months later, managers report the same habits on calls, in meetings, and with customers. The training happened, and the behavior on the job stayed where it was.
Researchers call this transfer of training. It is one of the most useful ideas an enablement leader can bring into planning, because it points to where the next training dollar will do the most good. This guide covers what it means, what drives it, how to measure it, and how to design programs where new skills carry over to real work.
What Transfer of Training Means
Transfer of training is the degree to which people apply what they learned in training to their actual work, and keep applying it over time.
Generalization. The learner uses the skill in real situations that differ from the training setting.
Maintenance. The learner keeps using the skill after the program ends.
Picture a rep who nails a pricing conversation in a workshop and then discounts on instinct during a live deal. That is a generalization problem. Now picture a rep who uses the new discovery framework for two weeks and then drifts back to old habits. That is a maintenance problem. Both are common, and both are fixable with the right design.
The Three Factors That Decide Whether Training Transfers
Baldwin and Ford grouped the inputs to transfer into three buckets. Each one maps to decisions a training team already controls.
Trainee characteristics
This covers ability, motivation, and how relevant learners believe the content is to their job. A seasoned AE who sees a module as remedial will not carry it into their calls. Relevance is something you can design for, by building content around the deals and conversations people actually run.
Training design
This covers how closely the training resembles the real task, how much practice is built in, and how specific the feedback is. Content-heavy programs with little practice tend to score well on knowledge checks and less well on the job.
Work environment
This covers whether managers reinforce the new behavior, whether people have time and opportunity to use it, and whether anyone notices when they do. A skill with no reinforcement fades over a few weeks.
Most programs put the bulk of their effort into content. The research points to training design and the work environment as the places where transfer is won.
Why Training Transfer Is Hard to Measure
Transfer lives at the behavior level, which is the hardest level to see. The Kirkpatrick Model calls this Level 3, whether people perform the critical behaviors on the job. Kirkpatrick Partners describes it as the degree to which people perform those behaviors and are supported and held accountable in doing so.
Levels 1 and 2 are easy to capture. Surveys measure reaction, and quizzes measure knowledge. Level 3 requires watching people do the work. Most teams do not have the manager hours to watch every rep, agent, or new manager handle real conversations.
So transfer often gets assumed. High completion and good quiz scores lead to a program being marked a success. Teams that want a clearer answer need a behavior signal, which is why many now look at how to measure the effectiveness of sales roleplays alongside completion data.
How to Design Training That Transfers
The following practices come straight from the three factors above. None of them require a new curriculum. They change how existing content gets practiced and reinforced.
Make practice look like the real job
The closer the practice setting is to the real situation, the more likely the skill carries over. For customer-facing teams, that means practicing the actual conversation. Think of the discovery call with a skeptical buyer, the renewal with a frustrated champion, or the escalation with an upset customer.
Specific scenarios produce specific skills. Build practice around your own products, your own buyer personas, and the objections your team hears every week. Yoodli lets teams train AI roleplays on their own sales content, so practice reflects the deals your team actually runs.
Build in repetition after the program ends
Maintenance depends on practice continuing after the session. A one-day workshop with no follow-up runs straight into the forgetting curve. Schedule short practice reps in the weeks after training. Tie them to real moments like an upcoming launch, a new competitor, or a quarter-end push.
This is the core idea behind moving from information to capability. People need repeated chances to use a skill before it becomes a habit.
Give specific feedback on the behavior
Generic praise gives a learner nothing to change. Feedback that names the moment works better, for example “you answered the pricing question before confirming the budget owner.” That gives the learner something to fix on the next attempt. The faster that feedback arrives, the more practice cycles a learner can fit into a week.
Get managers involved without adding hours
Managers have the most influence on the work environment and the least spare time. The goal is to let managers see who is practicing and where each person is struggling. Their coaching time then goes to the right conversation. Practice analytics and reporting give managers that view in one place.
Harness used Yoodli AI roleplays to cut sales training review time by 75%. Managers spent that time coaching the reps and moments that needed them most.
High completion and quiz scores, with no movement in the metrics the program was meant to change
Managers describing the same skill gaps before and after training
New hires who pass onboarding and then need the same coaching as hires who skipped it
Reps who can explain the methodology in a meeting and rarely use it on calls
Any one of these points to a design or environment issue more than a content issue. That is good news, because design and environment are both within the training team’s control.
Where AI Roleplays Fit
AI roleplays address the two factors that content-heavy programs tend to underweight. On design, they give every learner realistic, repeatable practice with immediate feedback. That happens at a volume that live roleplay with a manager cannot match. On environment, they give managers visibility into practice and progress, so reinforcement happens without hours of call review.
Managers stay at the center of coaching. AI roleplays give them better information about who needs help and with what. They also give learners more chances to use a skill under realistic conditions, which is where transfer is decided. You can see the full picture on the Yoodli AI roleplays platform page, or explore how teams use Yoodli for learning and development.
Frequently Asked Questions About Training Transfer
What is transfer of training in simple terms?
Transfer of training is whether people use what they learned in training on the job, and keep using it over time. A program with strong transfer changes behavior in real conversations, meetings, and customer interactions. A program with weak transfer produces good quiz scores and little change in how people actually do the work.
What are the two types of training transfer?
The two types are generalization and maintenance, as described by Baldwin and Ford in their 1988 review. Generalization means applying the skill in real situations that differ from the training setting. Maintenance means continuing to apply the skill after the program ends. Strong programs plan for both with realistic practice and ongoing reinforcement.
What affects transfer of training the most?
Training design and the work environment have the biggest influence on whether skills show up on the job. Realistic practice, specific feedback, and manager reinforcement all raise the odds that a skill carries over. Learner motivation matters too, and it rises when content clearly matches the conversations and situations people face in their own roles.
How do you measure training transfer?
You measure it by looking at behavior on the job, which is Level 3 of the Kirkpatrick Model. Performance-based certification, observed practice, and manager assessments of real conversations are strong signals. Surveys and quizzes measure reaction and knowledge, so they tell you less about whether the skill shows up at work.
Making Training Stick
Training transfer depends on design and environment as much as content. Programs that build in realistic practice, specific feedback, and manager visibility give people a real chance to use new skills on the job. Yoodli AI roleplays help enablement and L&D teams build that practice around their own content, so skills show up where they count.
What Is the 70-20-10 Model, and Where Practice Fits In
The 70-20-10 model shows up in almost every L&D strategy deck. It is also one of the most misread ideas in corporate training. Teams quote the ratio, trim formal programs, and then wonder why new managers and new reps still struggle in the conversations that matter most.
This guide covers what the ratio says, where it came from, and what teams get wrong about it. It also shows how enablement and L&D leaders can use it to plan practice for customer-facing and leadership teams.
In plain terms, most growth comes from doing hard things. A smaller share comes from the people who coach you and give you feedback. The smallest share comes from formal training.
The idea sits close to the broader case for experiential learning. People retain more when they do the work themselves, which is why experiential learning outperforms passive learning in most skill-based programs.
Where the 70-20-10 Learning Model Came From
CCL describes the rule as an outgrowth of more than 30 years of its Lessons of Experience research. That research studies how executives learn, grow, and change over the course of their careers. Successful leaders were asked to reflect on the experiences that shaped them, and the ratio summarizes their answers.
That origin shapes how you should use it. The model records where executives said their development came from. Treat it as a description of how people learn, and use it to decide where practice and feedback belong in your program. It works poorly as a budget formula.
What People Get Wrong About 70-20-10
Treating the numbers as precise
The ratio is a guideline. ATD has published a piece examining the evidence behind 70-20-10, and practitioners have long debated how literally to read the numbers. The useful takeaway is the direction. Experience and feedback do most of the work.
Using it to justify cutting formal training
Some teams read “only 10% from training” and conclude that formal programs can shrink. A better reading is that formal training works best when it sets people up for the 70 and the 20. A workshop with no follow-up application or feedback will underperform whatever share you assign it.
Assuming on-the-job learning happens on its own
Challenging experiences only build skill when people get to repeat them and learn from them. A new manager who has one hard performance conversation per quarter gets very few reps. A new AE who runs three live discovery calls in the first month learns from each one, but every mistake costs a real opportunity.
The Practice Problem Inside the 70
For customer-facing and leadership teams, the 70 is where the tension sits. The experiences that develop people the most are also the ones where mistakes are expensive. Here are a few examples:
A rep’s first pricing negotiation with a strategic account
A support agent’s first escalation with an upset enterprise customer
A new manager’s first conversation about underperformance
A partner rep’s first pitch of a product they learned last week
Organizations want people to gain experience. They would rather that experience not come at the customer’s expense. Realistic practice gives people a place to build that experience first.
Where Practice Fits in the 70-20-10 Model
Realistic practice gives people more of the 70 without the risk. It also gives them more of the 20, because feedback comes with every attempt. Teams using Yoodli build this practice around the exact conversations their people face on the job.
Practice extends the 70
A roleplay that mirrors the real conversation lets people build experience before the stakes are real. A rep can run the pricing conversation ten times before the actual call. A manager can rehearse a hard conversation before sitting down with a direct report. The skill carries over when the practice looks like the real job.
AI roleplays make that volume possible. Each learner gets a realistic counterpart who responds to what they say, and they can repeat the scenario as often as they need.
Practice scales the 20
Developmental relationships are limited by manager time. Most managers cannot sit in on every call or rehearse every conversation with every direct report. AI roleplays give each attempt immediate, specific feedback. They also give managers visibility into who is practicing and where each person is struggling.
Formal training carries over better when people apply it soon after. Pair each module with a practice scenario that uses the same content. When a team launches a new product or pitch, have people practice the conversation that same week. Without that step, most of the content fades along the forgetting curve before anyone uses it.
Here is a simple way to plan a learning and development strategy for a customer-facing team using the model.
Start with the conversations
List the three to five conversations that most affect results for the role. For an AE, that might be discovery, demo, pricing, and competitive objections. For a support team, it might be escalations and renewals. For new managers, it might be feedback, performance, and one-on-ones. Yoodli has a set of key roleplays for manager training if you want a starting list.
Keep the 10 short and specific
Formal content should show what good looks like for each conversation. Keep it tight so people move to practice quickly. A short module with a practice rep right after it gives people something they can use the same day.
Build practice for each conversation
Create scenarios that match your buyers, your customers, or your org. Use your own content, your own objections, and your own methodology so practice looks like the job. L&D teams can see how this fits a broader program on the Yoodli learning and development page.
Schedule repetition
One practice session gives people a feel for the conversation, and the skill builds when they come back to it over several weeks. Tie practice to real moments like a launch, a new quarter, or a pricing change.
Give managers a view
Managers should be able to see who has practiced, how each person performed, and where each person needs help. That is how developmental relationships scale without adding hours to a manager’s week.
Measure behavior
Track whether the conversations improve on the job. That is Level 3 of the Kirkpatrick Model, and it is the level that matters for customer-facing roles. Performance-based certification is a stronger signal than a quiz, because people have to show the skill.
FAQ About 70-20-10
What does 70-20-10 stand for?
70-20-10 stands for the share of development that comes from three sources. According to the Center for Creative Leadership, 70% comes from challenging experiences and assignments, 20% from developmental relationships like coaching and feedback, and 10% from coursework and formal training. The numbers describe a general pattern in how people grow at work.
Who created the 70-20-10 model?
The framework comes from the Center for Creative Leadership and its Lessons of Experience research. That work asked successful executives which experiences shaped their development over their careers. The ratio summarizes their answers, and it has since become a common reference point for L&D teams planning on-the-job learning.
Is 70-20-10 backed by evidence?
The ratio is based on executives’ reflections on their own development, so it is best used as a directional guideline. ATD and other practitioners have questioned how precise the ratio is. The core idea holds up well in practice. People build most of their skill through experience and feedback.
How does practice fit into 70-20-10?
Practice adds to all three parts of the model. Realistic roleplay gives people more experience (the 70) without customer risk. It delivers feedback (the 20) on every attempt, at a volume managers cannot match alone. It also helps formal training (the 10) carry over, because people apply the content right after they learn it.
Putting the Model to Work
The 70-20-10 model is a reminder that people develop by doing and by getting feedback. For teams whose work happens in live conversations, the most valuable experiences are also the riskiest ones to learn from in real time. Realistic practice gives people more reps and more feedback before the stakes are real. Yoodli AI roleplays give enablement and L&D teams a way to build that practice around their own conversations, content, and methodology.
How to Practice Multi-Stakeholder Deals Without a Room Full of People
Enterprise deals rarely have one buyer. A typical opportunity involves a champion, an economic buyer, a technical evaluator, someone from procurement, and often a skeptic who would rather keep the current process. Each one wants something different from the conversation. This guide shows sales enablement teams how to practice multi-stakeholder deals so reps walk into those meetings ready for every person at the table.
Reps know the buying group exists. What they rarely get is practice handling it. Traditional roleplay puts one manager across the table playing one buyer. That builds basic skills. It does little to prepare a rep for a call where the CFO wants numbers, IT wants security answers, and the champion wants to look good in front of their boss.
The sections below cover why these conversations are hard, which moments are worth rehearsing, and how to run the practice without booking five colleagues for an afternoon.
Why Multi-Stakeholder Sales Conversations Are Hard
Research from Harvard Business Review on the new sales imperative describes how B2B purchases now run through groups of people with different jobs and different definitions of success. That shift changes what a rep has to do in the room.
Priorities conflict
The economic buyer cares about cost and return. The end user cares about daily workflow. IT cares about risk and integration. A message that lands with one person can push another away, so reps need to adjust the same story for each listener.
Reps default to their favorite stakeholder
Most reps spend the call talking to the person they know best, usually the champion. The quieter stakeholders often hold veto power, and they get less airtime than they should. A rep who never practices drawing out the quiet person in the room will keep making the same mistake on live calls.
New objections show up late
Procurement and security questions often appear after a rep believes the deal is won. Reps who have never heard those questions before tend to answer them slowly or overpromise. Both responses cost time at the stage where time matters most.
The stakes are high
These calls usually happen late in large deals. There is little room for a rep to learn by trial and error with a real buying committee. Practice is the only safe place to make the early mistakes.
The Buying Committee Conversations Worth Practicing
You do not need to rehearse an entire buying committee in one session. Break the deal into the moments that most often go wrong, then build practice around each one.
The economic buyer meeting
The rep has 20 minutes with a senior leader who did not attend discovery. Practice framing the business case in that leader’s terms, briefly, without a feature tour. The MEDDICC framework treats the economic buyer as its own element for this reason, and it is a useful lens when you write the persona.
The technical or security review
A technical evaluator asks detailed questions about integration, data handling, and security. Reps should practice answering clearly, knowing when to bring in a specialist, and staying honest about what the product does today.
The skeptic
One stakeholder prefers the status quo or another vendor. Practice acknowledging the concern, asking what would change their mind, and keeping that person from steering the whole room. The guide to the already using a competitor objection has talk tracks that translate well to this persona.
The procurement conversation
Pricing pressure, contract terms, and timing come together here. Reps should practice holding value instead of discounting on instinct. The post on sales price negotiation practice walks through how to build that scenario.
The champion prep call
The rep coaches their champion on how to sell internally. Practice giving the champion the right language for each stakeholder they will face. If your team needs a shared definition first, start with what a champion is in B2B sales.
How to Practice Multi-Stakeholder Deals Step by Step
The goal is to build skill one stakeholder at a time, then put the stakeholders together. This order makes gaps easy to spot and easy to coach.
Build one persona per stakeholder
Give each persona a role, priorities, typical objections, and a communication style. A CFO persona should be short on time and focused on numbers. A security persona should push on specifics. The post on realistic AI personas for sales roleplay covers the details that make a persona feel like a real buyer.
Practice each stakeholder on their own first
Reps should handle each persona one to one before they try a combined scenario. This isolates the skill gaps. A rep who struggles with the security persona alone will struggle more when that persona is one of four voices.
Then practice the group and the transitions
The hardest moments come when the conversation shifts between stakeholders. Build scenarios where the rep answers a technical question and then ties the answer back to the economic buyer’s priorities. Reps should also practice reading the room when two stakeholders disagree in front of them.
Use your own deal data
Base scenarios on real objections and stakeholder dynamics from recent wins and losses. Generic personas prepare reps for generic buyers. Your CRM notes and call recordings already hold the details that make practice specific.
Review with a manager, selectively
Managers do not need to watch every session. They should review scores and pick the one or two moments where the rep struggled most. The post on how managers can use AI coaching data in 1:1s shows how to turn those scores into a focused coaching conversation.
Where AI Roleplays Fit in Deal Practice
This kind of practice is hard to staff with people. Getting a manager, a sales engineer, and a peer together to play three stakeholders takes planning, and it rarely happens more than once per deal.
Yoodli removes the scheduling problem. Enablement teams can build AI roleplays for each stakeholder around their own methodology and content. Reps can then practice each conversation as many times as they need before the real meeting.
Yoodli also supports multi-persona roleplays, where several AI personas join one conversation. Each persona has its own goals and concerns, and the personas respond to each other as well as to the rep. That gives reps a realistic way to practice a buying committee meeting before they face the real one. For a longer look at the approach, read why multi-persona AI roleplays matter for sales training.
AI roleplays also make deal-specific prep realistic. A rep heading into a meeting with a skeptical CFO can practice that exact conversation the night before. They do not have to wait for a manager to find a free slot.
How to Start a Stakeholder Practice Program
Start small and add stakeholders over time. A focused first quarter tells you more than a big launch that tries to cover every role at once.
Pick one stage in your enterprise deals where stakeholder conversations often go wrong.
Build two or three personas for the people who show up in that stage.
Have reps practice each persona on its own and reach a passing score.
Run a combined multi-persona session once reps pass the individual personas.
Review results with managers and add the next stakeholder conversation next quarter.
Keep the scoring criteria tied to your methodology. If your team runs MEDDPICC, score whether the rep confirmed decision criteria with the technical evaluator and tested the business case with the economic buyer. That keeps practice connected to how your team forecasts deals.
Frequently Asked Questions About Multi-Stakeholder Deal Practice
What is a multi-stakeholder deal?
A multi-stakeholder deal is a sale where several people with different roles and priorities influence the buying decision. It is common in mid-market and enterprise B2B sales. The group often includes a champion, an economic buyer, a technical evaluator, procurement, and end users. Each one judges the purchase against different criteria, so reps have to tailor the conversation to each person.
How do you practice selling to a buying committee?
You practice selling to a buying committee by building one persona per stakeholder and rehearsing each conversation on its own first. Once reps handle each persona well, they practice a combined session where several stakeholders speak in the same meeting. Managers then review scores and coach the one or two moments where the rep struggled most.
Can AI roleplays include more than one buyer?
Yes, AI roleplays can include more than one buyer. Yoodli’s multi-persona roleplays put several AI personas into a single conversation, and each persona has its own goals, objections, and style. The personas respond to each other as well as to the rep. That lets reps rehearse a full buying committee meeting without scheduling colleagues to play each role.
How often should reps practice stakeholder conversations?
Reps should practice stakeholder conversations before every high-stakes meeting in a large deal and on a regular cadence between deals. A short session the day before an economic buyer meeting is more useful than a long workshop once a quarter. Enablement teams can also add stakeholder scenarios to onboarding so new reps learn the buying group early.
Conclusion
Multi-stakeholder deals are won by reps who can speak to every person in the room. The fastest way to build that skill is to practice multi-stakeholder deals one persona at a time, then put the personas together. Yoodli gives enablement teams the AI roleplays to run that practice at scale. Reps meet the CFO, the security reviewer, and the skeptic in practice before they meet them in a live deal.
Three years ago, a company selling AI software to a large enterprise handed the account to a services team after the contract closed. Today, at Palantir, Anthropic, OpenAI, and a growing list of AI vendors, that engineer shows up months before the contract closes, sits in the room during the pitch, and stays embedded through the first stretch of deployment. That person carries the title forward-deployed engineer, and the shift in when and how they show up has changed what it takes to win enterprise AI deals.
The technical seller replaced the technical demo
For most of the SaaS era, sales engineering existed to answer questions in a demo and disappear once the deal closed. Implementation was someone else’s job, usually a professional services team that picked up the account weeks or months later. The forward-deployed engineer model breaks that handoff. FDEs get embedded early, often before a contract is signed, building working prototypes against a prospect’s actual data and actual workflows instead of a generic demo environment.
Palantir built its entire go-to-market motion around this idea long before “FDE” became a job title other companies borrowed. The pitch was never a slide deck. It was a working system, built on site, that solved a version of the customer’s real problem before the contract was signed. Anthropic and OpenAI have adopted a similar model for their own enterprise accounts, and the reason is direct: buyers of AI systems no longer trust a demo to predict what will happen against their own data and their own edge cases.
What winning an enterprise AI deal looks like now
Winning used to mean out-featuring a competitor on a spec sheet or beating them on price per seat. A buying committee evaluating an AI system now wants proof it will work against their data, their compliance constraints, and their existing tools before anyone signs off on a budget line and an executive sponsor. A vendor that can show a working prototype in the first meeting has already cleared a hurdle a slide deck cannot.
This changes the shape of the sales cycle. Buyers evaluate the FDE directly, alongside the product, assessing whether the vendor’s technical team understands their business well enough to build something specific to it, and whether that same team will still be there after the deal closes to make the deployment work. Research on the model from the Alexander Group frames this as a shift from selling a finished product to co-building a proven outcome with the buyer during the sales process itself.
Why this became a competitive advantage instead of a cost center
Pre-sales technical work has always cost money. What changed is where that cost sits on the P&L and what it buys. A company that treats forward deployment as overhead assigns generalist SEs to run demos and hands the hard problems to a services team after signature. A company that treats it as a differentiator hires senior engineers who can build and adjust real deployments in front of the customer, and puts them in the deal from the start.
The second approach costs more per deal. It also closes more of the deals that matter, because the buyers who evaluate enterprise AI carefully, security teams, procurement, technical stakeholders, are the ones who decide whether a six or seven figure contract gets signed. A vendor that can prove technical credibility inside the sales cycle skips months of trust-building that used to happen after signature. That speed compounds across a pipeline. It is hard for a competitor to copy quickly, because copying it means hiring and developing a different kind of person than a traditional AE or SE, and building a sales process that gives that person room to work before the deal closes.
The hiring math backs this up. Strong FDEs are scarce because the role asks for two skill sets that rarely sit in the same person: the engineering depth to build a working system under time pressure, and the presence to do it in front of a skeptical VP of Engineering or CISO who is deciding whether to trust the vendor with production data. Companies that figure out how to find, train, and retain that combination end up with a sales capability a competitor cannot buy off a job board in a quarter. That is the part of the FDE model that holds up as a durable advantage rather than a hiring trend. It takes years to build the internal muscle to identify these people, pair them correctly with the rest of the deal team, and give them enough reps that the pairing works under pressure instead of only in a rehearsal room.
The model breaks if the people around the FDE aren’t ready
An FDE who writes good code and designs a good architecture is not enough by itself. The FDE sits inside a sales motion with an account executive, a solutions consultant, and often a customer success lead, and the deal moves at the pace of the weakest handoff in that group. If the AE cannot speak accurately about what the FDE built, or the FDE cannot translate a technical constraint into an answer a VP will accept, the credibility the model is supposed to buy disappears in the room.
This is where a lot of companies scaling the FDE model run into trouble. They hire strong individual engineers and assume technical skill will carry the deal. It carries the first meeting. The eight or ten touchpoints between discovery and signature take more, since each one brings a different stakeholder asking a different version of the same skeptical question. Teams that handle this well rehearse those conversations before they happen, not just among the FDEs but across the whole deal team, so the AE, the FDE, and the CS lead give the buyer one consistent, credible story instead of three separate ones.
Yoodli built its AI roleplays for sales onboarding around exactly this gap: the difference between a team that knows the material and a team that has practiced saying it out loud, under the kind of pressure a real buyer applies. Standing up an FDE program takes more than a job posting for strong engineers. It takes an AE and an FDE who have rehearsed the handoff enough times that a skeptical question from a CISO does not derail the pitch.
What this means for building and training GTM teams
Companies that want the FDE model to work are rethinking who they hire and how they ramp them. The role sits between engineering and sales, and most engineers have never been trained to handle a room full of stakeholders who are evaluating them as much as the product. Most AEs have never had to co-present with someone writing code live. Onboarding for this hybrid role cannot be a shortened version of a normal SE ramp. It needs its own path.
Each shows what happens when a company stops treating rehearsal as optional and starts treating it as part of the operating model. The same logic applies to a forward-deployed engineering org. A technically strong FDE who has never rehearsed a live objection is a liability in a room where the buyer is testing composure as much as competence.
Model quality alone rarely decides an enterprise AI deal anymore. The vendors winning today have technical and commercial teams that show up together, prepared, and leave the buyer with proof instead of a promise. That is the real moat, and it gets built one rehearsed deal team at a time.