
•
•

Summarize blog with








Eric Letourneau, Senior Implementation Manager, Vidyard, joined us at Propel23 to share learnings and insights from the journey of implementing a new customer onboarding system at Vidyard.
In the session, Eric talked about:
Here are Eric’s takeaways from being on the other side – a customer in the onboarding journey.
The onboarding team at Vidyard was looking for a new tool to manage and track their customer onboarding process for a few reasons:
The team then came up with six primary goals for Onboarding 2.0.

That’s when the team came across Rocketlane and decided to give it a shot.
Here are the challenges Eric's team faced as they adopted Rocketlane for their customer onboarding needs.
For users, provide resources that educate and inform users on why they should use the new tool, the parts of the tool that are particularly useful to them, the outcome of the implementation, etc. This could be a mix of resources that use different mediums - text-based, video walkthroughs, webinars, etc.
The Vidyard team handles this aspect of change management in two ways:
They also share a short video on Rocketlane for customers to view later. Additionally, they track how the customer team uses/interacts with it (number of partial and full views, portions being rewatched, etc.).

This process of diving into the details can be complex and time-consuming.
Make sure to account for time to do this.
There’s always a tradeoff to make.
Focus on finding a fine balance while iterating/improving and making progress towards adoption and usage.

A year after implementing Onboarding 2.0 to adopt Rocketlane, the Vidyard team has been able to
“Speeds up CSV importing and saves me from having to get customers to use a template file or create mapped data exports. Quick to integrate and flexible outside the happy path. We found defining workbooks and templates confusing; at a prior job it was configured through code, which I preferred.”
Source: G2 review


AI that executes your delivery work (Add to any plan)
Most popular
Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.
Most popular
Great for teams desiring tailored workflows with comprehensive reporting capabilities.
Most popular
Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.





70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.

70–85% utilization. 94% G2 rating.
One platform does what the entire table above tries
to split across tools.
Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.
Implementations fail because complex environments need real-time technical problem-solving. FDEs unblock workflows, integrations, and unknown constraints that traditional onboarding teams can’t resolve on their own.
Get a better all-in-one PSA
Get a better all-in-one PSA
Companies that embed engineers directly with customers see significantly higher enterprise retention compared to traditional post-sales models — because embedded engineers uncover “unknowns” that never surface in ticket queues.

VP Sales, Intercom

A Forward Deployed Engineer (FDE) embeds in the customer environment to implement, customize, and operationalize complex products. They unblock integrations, fix data issues, adapt workflows, and bridge engineering gaps — accelerating onboarding, adoption, and customer value far beyond traditional post-sales roles.






.webp)