
•
•

Summarize blog with








In this session of Propel 22, Maranda Dziekonski, Chief Customer Officer at Swiftly, and Kristi Faltorusso, VP, Customer Success at ClientSuccess, shared their learnings and insights on setting up an onboarding motion that grows with the organization.
They discussed:
Here are the takeaways from the session.
Most companies think of onboarding as being limited to a specified period, whereas it needs to be looked at as an ongoing education and engagement activity, to support customers with their needs at the right time.
It helps to look at onboarding as a layer on top of customer experience. Companies should invest in the creation of resources and collateral that customers can access throughout their lifecycle through webinars, videos, enhancement of existing content, etc.
Kristi relies on an approach that outlines the seven core objectives that the product can help customers achieve. The product’s capabilities are mapped to these objectives. Customers are then encouraged to pick their top three. This helps companies focus their onboarding efforts and understand exactly how they can realize value.
The ultimate goal, throughout the customer’s lifetime with the product, is to help them achieve all seven goals.
Change management is a challenge in the case of products that require daily interactions, such as a CRM or BI tool. Since these products are often to be adopted by multiple departments, change management during onboarding needs to focus on answering the WIIFM (What’s in it for me?) question for end-users.
Kristi recommends having a partnership kickoff, right after sale and before the project kickoff, that focuses heavily on change management. As part of this, discussions should revolve around the customer owning change management, and working on an internal plan that focused on making a case for a new product, communication, building alignment across different teams, etc.
Maranda recommends an onboarding reboot for teams that have failed to see product adoption. Onboarding teams should not be afraid to re-onboard to drive adoption or handle internal changes at the customer end. Even in the case of product-led growth where onboarding is built into the product, change management should be an active focus if adoption is low.
Here are the key metrics Maranda and Kristie recommend:
Kristie also organizes a graduation ceremony at the end of onboarding (for each customer) that’s focused on celebrating what was achieved, and outlining the goals and frameworks for the next three to six months.
At Swiftly, customers' quantitative and qualitative goals are captured and tracked in their CX tools and used for regular project check-ins.
At ClientSuccess, Kristi uses a goals tracker that is considered indicative of the customer’s health score. They help customers identify the core objectives that they can achieve with their product, with inputs from other customer journeys.
CS needs to come first. Start with a generalist approach, but as the function grows and things start breaking, companies need to peel layers off and separate them, such as the onboarding layer.
Companies need to understand what the CS team is spending time on, and identify the different layers to separate.
“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)