
•
•

Summarize blog with








Every year, we run a survey report on the latest trends in customer onboarding and implementations. This year, with 850+ responses, we launched the State of Customer Onboarding report for 2024 recently!
We hosted Emilia D’Anzica, Founder, Managing Partner, Growth Molecules for the launch and boy, was it insightful! We also received a plethora of questions during the session, which we've compiled with detailed responses from our CEO Srikrishnan Ganesan, for your easy reference.
In case you missed the session, you can access the recording here.
Not enough companies invest in making this possible. No reason not to invest in making more self-service experiences and resources available to customers. Build them out, even if it is for a small portion of the onboarding. Every little contribution matters and builds towards easier / faster onboarding.
We hope these insights provide clarity and guidance on optimizing your onboarding processes.
Should you have any further questions or require additional assistance, please don't hesitate to reach out to our team on care@rocketlane.com.
Interesting take. I agree we need more focus on:
At Rocketlane, we heavily invested in automation last year, and the results have been significant. Many aspects of our onboarding process are now automated, leading to smoother operations and improved customer experiences. Would you be interested in a demo to see how automation can benefit your onboarding process? (purely to educate you, no hard sell)
Let's explore the possibilities together!
Time-based onboarding, typically divided into weekly segments, can be effective for shorter onboarding durations, providing clarity and structure. It helps to have a theme for each week too. So it is clear who is involved during which week, and what high level focus and clarity you need to make progress each week. The prerequisite could also be that time-based onboarding should have a very linear flow. If you have complex projects where people can pick on and do activities out of order or in parallel, it makes it harder to do time-based onboarding.
On the other hand, milestone-based onboarding, often preferred for more complex projects, breaks the process into phases with key milestones. It is also valuable to map the phases into weeks. For example, Week 7 to 9 can be indicated to be when you need your Salesforce admins to be available.
Both approaches have their merits, and the choice depends on factors like project complexity and customer preferences.
Certainly! We'll be happy to share the presentation deck with you. Please reach out to our team on care@rocketlane.com, and we'll share the PDF with you.
I wouldn't worry about that. There's always a unique reason you can provide for why you discounted the implementation charges for someone. It could be their overall spend level with you, or the complexity of their implementation being lesser, or just a month-end offer that they availed. Just always make sure the number is quoted and then discounted even when you are giving it away. The reality is - many larger customers will think you aren't serious enough if you aren't charging. They worry about the quality of implementation if it is free.
Make sure you are getting the exec sponsor to align on making your launch and adoption a shared KPI with someone on their team. They are successful if you are successful, and this isn't a side gig for them. They aren't ‘helping’, this is their job. And they should also understand the importance of the initiative: What does this do for the business? Why did we invest in this technology? All of this should be discussed before kick-off. Emphasize the significance of the initiative and its impact on their business, fostering a sense of ownership and commitment.
Surface this to the sales team and leadership earlier than later. Typically there is clawback on sales commissions if there's early churn or churn during onboarding. So the sales rep and leadership will be aligned on trying their best to bring back the customer - calling, referencing the original value prop, etc.
Also, surface risks early if you see a lack of readiness or maturity on the customer side. That's the most common reason they disengage. They realize they aren't ready.
Two things you could do in such instances:
1. Have an intake form to assess their readiness. If they aren't ready, offer additional services to bridge the gap that they need to buy.
2. Ask their leadership the question at kickoff or before: "What should we do if your team isn't moving fast enough or isn't able to complete the activities on their plate? How important is this to you?"
This helps the team also understand how you will have to act if they aren't making progress.
Agreed! It needs commitment from leadership to make this change happen.
Agree to offer ‘x’ dollars worth of implementation time towards sales and customer success each year. Let that be 40% of your team's time. But account for the time. Ensure the sales leaders know they have that limit and hence they need to charge for most of the deals and be careful which ones they are discounting. Help the sales team also understand how much value they are giving away.
Have a clear hand-off which includes a sign-off from the customer. Have a hand-off form that needs to be filled, along with documentation of what has been set up for the customer, any workarounds, details of integrations, etc. Ensure customer sign-off includes feedback from the customer.
Yes, hybrid models are common. You can have a standard free service offering too, along with paid add-ons - for example, paid services can be: custom reporting, additional integrations, customized training and education, adoption and change management services, etc.
Haha. We've sourced swag from various vendors in the past (like Printful, CustomInk, 4imprint, etc.) You should also check out our swag store here for more!
This is just a glimpse of all that the report offers. For more nuanced findings and interesting data about how much onboarders are looking to leverage and use AI and automation for their everyday onboarding activities, access the full report here.
Hope you find it insightful!
“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)