•
•

Summarize blog with








Katie Clark loves all things onboarding! She believes in being an advocate for the customer internally & a champion for the product externally.
At Propel ‘23, she got talking about her experience in scaling the onboarding function at a hyper-growth startup. She shared her insights on:
and more.
One of the best places to start when you want to scale a process is by defining your customer journey.

And onboarding can mean a lot of things for a lot of people. For some, it may mean being more focused on training, while for others it may be more configuration or integration focused. The approach you take with customers during their onboarding, is also something that might change with its purpose, like taking a more consultative approach for long term success. Additionally, you also need to pay attention to what the customer needs to do in order to complete their onboarding and move on to the next phase. This will ultimately boil down to the complexity of your process and what value you are providing for the customer.
Take the time to write out your entire customer journey from start to finish – from the moment the sale closes, until the moment they're ready to leave onboarding. These could include all the touch points you have with customers, project communication plan, and other activities for expectation management with customers. Once you have that all mapped out, you will be able to see and define the overall purpose of onboarding more distinctly.
To ensure you're giving your customers the most value during onboarding, give them opportunities for quick wins, rather than just having them simply learn all that the product or software can do for them. And remember to keep track of their progress. – it will show them that you care about their success.
Zooming out and mapping the whole customer journey from start to finish will help you identify how long it takes to complete your onboarding process. Additionally, it will give you insights you may have otherwise missed. For example, you may identify a three week stint in the middle where only your team is hard at work, say while working on integrations or creating tables and diagrams. From the customer's perspective, this three-week gap might feel like a total waste of time. This way, you will know if you are making the most of your team’s time and learn how to make the process more efficient.
Pay special attention to the number of hours a customer has to dedicate in order to finish the onboarding process.
Figure out exactly who from your team and the customer's side needs to be involved, and when. Once that's done, look at all the different parts of the onboarding process and spot any opportunities to speed things up. It could be shortening calls, replacing certain tasks with emails, or finding other ways to make sure your customers are getting to value quicker.
Wondering how to reduce your time-to-value? Here’s a simple tweak you can do to your customer onboarding process.
Once you’ve all the information about your customer journey mapped out, it’s time to put it to good use.
It's great to take a look at your process, but a fully scaled process won't do you any good unless you have a team that scales with it. To make sure your team is set up to scale efficiently, here’s what you need to do:
Here are some basic metrics to introduce:
Other factors to track and keep tabs on:
Scaling your team and process involves working cross-functionally with:

Onboarding is just a step in the customer's journey and so, as you are trying to scale out your process or scale up your team, it is incredibly important to make sure that there are open lines of communication with all teams in the organization - sales, CSMs, product, support, and engineering. Your aim should be to make sure that the customer's journey is cohesive across every single department.
Working at a hyper-growth startup is conducive for experimentation. But if you don’t measure the success or failure of your experiments, then all that time is wasted. For example, if you can't prove that a low-touch or high-touch process is effective, you won't have any evidence to show whether what you're doing is working or not.
When it comes to revamping your onboarding process, don’t make any assumptions without relevant data to back them up. It’s important to be mindful of why things are a certain way in the organization.
For instance, combining two calls - a project kickoff and a technical kickoff - might seem like a good idea, but it might not be the most effective approach in a given context.
“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)