
•
•

Summarize blog with








In SaaS, a core focus for Customer Success (CS) teams is ensuring customers achieve value.
Yet, defining "go live" while balancing the onboarding journey with long-term value realization remains a challenge. These decisions impact customer satisfaction, retention, and overall success.
This topic was a recent point of discussion in the Preflight community with industry experts Grant Millington, Alison, Katelyn Fadeev, and Jeff Kushmerek contributing their insights. They shared how their organizations approach defining "live," managing onboarding and navigating multi-product complexities. Their knowledge sheds light on strategies for CS teams to drive meaningful outcomes for customers.
What does it mean for a customer to be "live"?
The answer varies widely based on the product, customer's goals, and organization's processes. For some, a customer is "live" once they complete Phase 1 of onboarding and start using the product. Others define "live" status on a product-by-product basis, especially with multiple modules.
Labeling a customer as "live" doesn't always reflect their readiness or satisfaction. Some organizations have adopted clear pre-sale agreements to define "live" criteria upfront. This ensures alignment between customer expectations and internal processes, preventing misunderstandings during implementation.
While creating "super users" through extended onboarding can be beneficial, it's important not to prolong the process unnecessarily. The general agreement leaned toward getting customers live with core functionalities quickly, followed by a phased approach to deliver additional value.
The onboarding process is crucial in setting the tone for a customer’s journey. However, there is often tension between delivering immediate value and ensuring the customer receives the full product benefit.
Many organizations are adopting an MVP (minimum viable product) implementation model. This approach prioritizes delivering critical functionality early, aligning with the promised value propositions during sales. Advanced features or complex configurations are postponed until the customer is comfortable and ready to expand their usage.
Enablement tools like webinars, self-service guides, and targeted campaigns drive advanced feature adoption post-onboarding. These resources empower customers to explore and implement features at their own pace while equipping CSMs with the tools for additional support.
Another practice discussed was maintaining light-touch onboarding team involvement during the customer’s initial adoption cycle. This ensures a smoother transition and provides context for CSMs and technical support teams to address challenges.
Traditionally, onboarding success has been measured by time to value (TTV). However, the conversation revealed growing interest in time to launch (TTL) as a more practical alternative. TTL measures the time for a customer to fully deploy the product and transition off their previous vendor, a critical milestone for SaaS customers.
TTL offers a clear, tangible metric, unlike TTV, which can be subjective and vary by customer. It aligns with customer priorities, especially in scenarios with multiple products or modules. TTV remains valuable for tracking product success, but TTL provides a more immediate measure of implementation efficiency and customer satisfaction.
Here are some actionable strategies for CS teams to improve customer outcomes:
By establishing clear definitions, focusing on MVP implementations, and investing in effective enablement strategies, SaaS organizations can optimize customer journeys and drive exceptional results.
Want to be a part of more such interesting conversations?
Join Preflight to connect with a global network of post-sale leaders and professionals, share valuable insights, and collaborate on solving real-world challenges.
“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)