
•
•

Summarize blog with








In this episode of Implementation Stories, Brittany (Yandura) Preseau, Senior Customer Success Manager at Fieldguide, shares how you can supercharge your customer onboarding journeys with a consultative approach.
Brittany has over 11 years of experience in customer-facing roles at enterprise SaaS companies. Her experience spans the whole gamut of customer onboarding, from self-service and multi-client to one-on-one, high-value implementations. She spent the last year building the customer onboarding process from the ground up at Fieldguide, an enterprise software company building automation and collaboration software for assurance and advisory firms.
In this session, Brittany focused on the following:
Here are our key takeaways from the session.
A consultative approach to onboarding ensures that your customers exit onboarding with an understanding of not just your product but also how it fits into their process. As a consultative onboarding professional, your job is not to tell customers what your product can do but to tell them what they should do to use your product in their workflows.
Consultative onboarding connects the dots between your product and the customer’s process by:
Another key aspect of consultative onboarding is its ability to customize onboarding for each customer while still adhering to a structure.
Consultative customer onboarding comes down to moving from:
The key activities that enable consultative customer onboarding at Fieldguide include:
Onboarding at Fieldguide starts with developing a mutual success plan that establishes the customer’s goals and their goals with the product. This ensures that they can tailor the onboarding around specific priority projects, on top of which other layers can be added at a later stage.
This is generally a one-hour call where customers explain their current processes, pain points, what’s working, and what they’re open to changing. This sets up a clear understanding of the customer’s side of the story while helping the Fieldguide onboarding team speak the same language as them.
The onboarding team shows them what the solution looks like in their workflow with their data. This ensures that they learn contextually – without having to figure out how everything is going to fit together.
The focus is on how the customer can go through their process using Fieldguide, instead of a traditional feature/info dump approach.
This means telling them how they’ll go through their process, the features they're going to use, areas where they’ll find efficiencies, and areas that need further understanding for the onboarding team to make the right recommendations.
Saving training for separate and dedicated training sessions ensures that customer onboarding feels consultative, not prescriptive. All the details, features, and UI-related aspects are left for training sessions, while onboarding focuses on getting the customer’s process into the system.
This means that they often have to explicitly state that future training sessions will focus on the platform/UI-specific aspects. Additionally, the team has different team members handling onboarding and training.
They partner with the customer as they move on to getting their clients on the platform. This ensures that customers feel supported as they interact with their clients, to avoid the risk of them defaulting to old/familiar systems, if and when they are stuck.
The team develops best practices, while also identifying and highlighting common areas of variation or deviation. This aspect is critical to identify key areas where the onboarding team needs to dig deeper to determine the right approach for the client.
Ensure that you follow the same framework and conduct the same sessions – while identifying sessions/aspects that need more time, attention, and support, and balancing them against those that need lesser support.
Set the right expectations right off the bat – and convey that your job as an onboarding expert is to play devil’s advocate, and challenge them when necessary – to ensure that you jointly make the right decision.
Ensure that the customer onboarding process is clearly explained in the pre-sales process.
The Fieldguide team encourages customers to sign the contract only when they are ready to get onboarded. Their approach is also white-glove in that they set up the templates and do the groundwork for their customers, so they don’t have to do much to see their processes in motion.
A key aspect of the consultative/partnership approach is taking a collaborative and invested approach – to understand the reasons for the customer’s constraints and if there’s anything you can do to help.
Another approach could be to get the partners/high-level stakeholders at the customer end to step back and delegate onboarding to someone else.
Helpful additions to supercharge customer onboarding:
Like what you read? Join Preflight, our private, invite-only Slack community and attend the next Implementation Stories session. You will also gain access to peers and share knowledge on customer onboarding, implementation, and customer success.
“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)