
•
•

Summarize blog with








In this session of Preflight UK’s Office Hours, James Stuart, CSM at hackajob spoke to Oliver Plane from Confluent and Markus Rentsch from Remark-able about product value, how customers can achieve value realization with your product, and how value realization can help find better solutions for customers.
Oliver, a top 100 CS Strategist 2021, currently works as an Enterprise Customer Success Executive at Confluent, a foundational platform for data-in-motion. Before Confluent, Oliver worked with Growth Molecules, a customer success consultancy, after working in the telecommunications, finance, and transport business sectors with companies such as Oracle, Logica, and others.
Markus is a customer success consultant and keynote speaker who helps SaaS companies use a Customer-Value-Led-Growth business model to eliminate churn, drive expansions, up-and cross-sells, and build better customer relationships.
The discussion focused on finding the answers to:
Here are our top takeaways from the session.
Different personas on the customer side perceive value differently. Knowing and understanding the ‘human’ outcome that these personas want and value the most is essential.
For example, the C-suite could value ROI while department heads could find value in freed up resources and fewer processes for innovation or other important projects; an individual contributor may see value in improving their day-to-day performance or productivity.
So while different personas may have aligned or similar goals, they view them differently, and it’s important to understand each of these perceptions.
A mistake that companies often make is assuming they know what customers want.
Conduct a thorough discovery discussion with the customer to get answers to these two questions:
This creates a sense of accountability at the customer end and provides clarity and responsibility to the CS team.
And in cases where customers don’t have a concrete answer to these questions, it’s the CS team’s job to guide them to find this answer – drawing from their product expertise and experience with other/similar customers.
Here are four steps the CS team must take to understand the customer’s needs, nail down their perception of value, and validate the value thus identified:
Though not always feasible, involving the CS team during the sales journey can be extremely helpful.
This way, customer value can be defined pre-sale – as a joint effort by Sales and Customer Success – so the CS team can:
a) Have the proper context and understanding of the customer’s needs
b) Set the right expectations for the customer
This can help minimize the risk of customers dropping off during onboarding – for no fault of the onboarding process.
Value is continuously changing throughout that customer journey, and identifying the key phases in this journey can help identify what to deliver and when.
Remember that the customer’s goals and visions will change over time. Validate the definition of value to the customer at every opportunity, especially critical ones like executive business reviews (EBRs).
The metrics that CS teams track and measure often have little to do with customer value.
For instance:
The key is to demonstrate success in terms of the value customers receive. Simply put, always look at success as how the customer measures it, not necessarily how you measure it internally.
The customer champion has a crucial role to play here. In addition to helping you understand what value means to their organization, they need to:
While it can be challenging to manage and match up to different personas’ value perceptions, there is always a connection. The key is to explain and articulate how the different kinds of value add up.
A combination of solid leadership and deliberate communication can make this happen.
For instance, the internal leadership team can set up systems to:
If you want to learn more about Customer Onboarding, Implementation, and Professional Services in-depth, join the Preflight Community.
“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)