Creating a customer onboarding motion that'll scale with you

Published in March
21 March 2022
Published in March

21 March 2022

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:

  1. A common mistake in the way companies perceive onboarding
  2. The different types of onboarding motions
  3. Change management challenges and approaches
  4. Successful onboarding: indicators and metrics 
  5. CS or onboarding: which comes first?

Here are the takeaways from the session.

1. The three different types of onboarding motions

  1. High-touch: Typically, for customers who need a lot of change management (or in cases where change management isn’t happening as expected). 
  2. Digital touch: For long tail-low ARR accounts
  3. Hybrid (digital-led): High-touch where needed and digital in areas that need minimal change management 

2. A common mistake that companies make in their approach to onboarding

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.

3. Helping customers define their goals for onboarding 

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.

4. Change management: challenges and approaches

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.

5. Successful onboarding: indicators and metrics

Here are the key metrics Maranda and Kristie recommend: 

  1. Time to first value 
  2. Post-implementation survey (questions focused on how enabled and empowered users feel to independently use the product)
  3. Usage and module adoption (3-6-9 months after onboarding)
  4. Tickets and type of tickets raised after onboarding
  5. Participation in post-onboarding meetings 
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.

6. Measuring ROI for customers

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.

7. CS on onboarding: Which comes first for startups?

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.

More resources from industry leaders and experts

  1. Propel22 recordings
  2. Implementation Stories
  3. Preflight Conversations
  4. The Launch Station - a podcast for all things customer onboarding
  5. Customer onboarding resources from Rocketlane

FAQs

“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

Sebastian
Intercom

AI that executes your delivery work (Add to any plan)

Most popular

Standard

Ideal for expanding organizations needing more in-depth capabilities and integration for scaling.

$49

per team member/
month billed annually

*minimum of 5 team members

  • Full partner ecosystem support
  • Dynamic templates for any project
  • Milestone CSAT for customer pulse
  • Docs, forms, projects in one place
  • Docs, forms, projects in one place
  • Approval-governed time tracking
  • 200 Automations/user/month
  • Native HubSpot, Jira, Slack Integration

Most popular

Premium

Great for teams desiring tailored workflows with comprehensive reporting capabilities.

$69

per team member/month billed annually

*minimum of 5 team members

  • Real-time project profitability
  • AI resourcing and capacity planning
  • All revenue recognition models
  • Centralized rate cards and budgets
  • Portfolio reporting for leaders
  • Bill faster & improve cash flow
  • Native Salesforce integration

Most popular

Enterprise

Tailored for large enterprises requiring a fully customizable, comprehensive delivery engine.

Custom Pricing

*minimum of 5 team members

  • SAML SSO and role-based access
  • Unlimited, hands-off automations
  • Soft-allocate pipeline deals early
  • Skills matrix for smarter staffing
  • Staff global teams ahead of demand
  • Multi-currency global delivery
  • Snowflake data + custom reports

Full reviews for all 11 tools below

<TL;DR>

Best all-in-one Certinia alternative for B2B SaaS and technology PS teams with 25 to 150 consultants. Delivery, resource management, project financials, client portal, and agentic AI in one PSA, with no Salesforce dependency. From $49/user/mo (full PSA from $69) · 4.7/5 on G2 · 4 to 12 week go-live

<TL;DR>

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.

Trusted by top companies

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

One platform does what the entire table above tries
to split across tools.

Myth

Enterprise implementations fail because customers don’t follow the process or provide clean data on time. Most delays are purely “customer-side” issues.

Fact

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

Did you Know?

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.

Sebastian mathew

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.