What is time-to-first-value (TTFV) and how is it set?

Time-to-first-value (TTFV) is the time from contract signature to the moment the customer experiences the business outcome they bought the product for, even at small scale. Most B2B SaaS companies set TTFV between 30 and 90 days depending on product complexity. The senior craft is engineering the milestone definition itself: 'first value' should be specific to the customer's business outcome, not generic to the product. A customer who 'completed onboarding' but didn't experience the business outcome has not reached first value; a customer who experienced the outcome at small scale (one workflow, one team, one use case) has, even if the broader rollout is incomplete.

Who attends the kickoff call?

Five named roles, minimum: the customer's economic buyer (the executive who has the most to gain from the outcome), the daily-user champion, any technical-implementation lead on the customer side, the CSM, and the AE who closed the deal. Optional but high-value: a backup champion candidate (so they're introduced to the relationship from day one), the customer's analytics lead (so outcome-measurement gets scoped immediately), and the vendor's implementation manager if the project is technically complex. The kickoff without the economic buyer is a kickoff with a structural problem; the CSM should reschedule rather than run the kickoff cold.

What does a bad kickoff look like?

Three failure shapes. (1) Generic agenda: the CSM runs the same kickoff deck for every customer without customizing for the specific outcome. The customer reads it as 'this CSM doesn't know what I'm trying to achieve.' (2) Feature dump: the kickoff turns into a product walkthrough rather than an outcomes conversation. The customer leaves with no clearer sense of how the product addresses their business problem. (3) Missing economic buyer: the kickoff happens without the real decision-maker, which means the outcomes definition and success plan lack the validation they need to be load-bearing for the next three years.

How do you handle a customer who isn't engaged in onboarding?

Customer disengagement during onboarding is the highest-priority early-warning signal in the CSM playbook. Three responses, in order. (1) Diagnose the cause: is the daily champion overloaded (temporary), did the economic buyer lose interest (structural), or did internal priorities shift (strategic)? (2) Re-engage the exec sponsor with a 1:1 conversation naming the disengagement directly and asking what changed. (3) If the answer is structural, the onboarding has to be paused or scoped down, not pushed forward. Pushing through customer disengagement is the most common way an onboarding becomes a year-two churn.

What's the difference between onboarding and implementation?

Implementation is the technical configuration work (provisioning, integrations, data loading, user setup); onboarding is the broader customer-success motion (success plan, outcomes definition, executive sponsor relationship, champion training, change management). At small companies, the CSM owns both; at larger companies (Salesforce, ServiceNow, Datadog), there's typically a dedicated Implementation Specialist or Professional Services team for the technical work and the CSM owns the broader motion. Confusing the two leads to either CSMs doing technical work they're not qualified for, or implementation teams running success-plan conversations they're not trained for.

How long should onboarding take?

The typical answer is 30 to 90 days, but the right answer depends on product complexity and customer maturity. Simple SaaS products with self-serve adoption (think lightweight productivity tools) can onboard in 14 to 30 days; complex enterprise products with deep integrations (think CRM, data-platform, identity-and-access) can take 90 to 180 days. Trying to compress complex onboarding into a 30-day timeline because that's the company's default is a structural mistake; the senior CSM negotiates the timeline with the customer's specific situation in mind, not the corporate default.

What goes wrong if onboarding lacks an executive sponsor?

Three predictable failures, all showing up in year two. (1) The EBR has no real executive in the room and turns into a status meeting, losing its strategic function. (2) When a competitor approaches the customer mid-cycle, there's no exec relationship to anchor the save. (3) When the daily-user champion changes jobs, the relationship is single-point-of-failure and often lost. The engineering of the executive sponsor relationship is the highest-stakes piece of onboarding work and the most commonly skipped because it's uncomfortable for junior CSMs to ask the daily champion 'who's the right exec to bring into this conversation?'

Should the AE stay involved after the kickoff?

Yes, partially. The AE shouldn't drive the day-to-day onboarding (that's the CSM's role), but the AE should remain on the customer exec-sponsor relationship for at least the first 90 days. The structural reason: the exec relationship the AE built during the sales cycle is real social capital, and abandoning it at signature means the CSM has to rebuild it from scratch. The author's observation across companies that handle this well: AEs are compensated partly on year-one outcomes, not just on signature. The RepVue ratings track publishes broad professional-development and culture signals that correlate with healthy CS orgs but does not publish compensation-design as a category; that observation is author analysis. Practitioner discussion of the pattern surfaces in the Bravado War Room, but the page does not cite specific threads as proof.

Customer Success Manager Hub

Customer Onboarding for CSMs: Kickoff, Success Plans, Time-to-First-Value in 2026

By Blake Crosley · Last verified 2026-05-11

In short

Customer onboarding is the first 90 days after a customer signs, and it sets the trajectory for everything that follows. The mid-level CSM motion is running the standard 30/60/90 playbook (kickoff call, technical configuration, training, adoption review). The senior craft is something different: treating onboarding as the construction of the load-bearing artifacts the relationship will run on for the next three years (the success plan, the outcomes definition, the executive sponsor relationship, the champion redundancy, the outcomes-tracking infrastructure). Onboarding decisions made in the first 90 days are amplified in years two and three. Customers who don't reach first value in 90 days have a meaningfully higher churn rate at first renewal; the senior CSM is engineered against that statistic from day one.

Key takeaways

Time-to-first-value (TTFV) is the load-bearing onboarding metric. Most companies set TTFV between 30 and 90 days depending on product complexity. Customers who hit TTFV inside the target window renew at materially higher rates than customers who slip past it. The Gainsight B2B onboarding article documents the pattern across B2B SaaS; the senior craft is engineering the milestone definition itself, not just running the stopwatch.
The sales-to-CSM handoff is where most onboardings get derailed before they start. The AE has spent three to nine months building a relationship with the customer, learning their internal politics, discovering the real economic buyer, and making promises in the sales cycle. A bad handoff loses all of that context; the CSM walks into the kickoff cold and has to rebuild the relationship from scratch. Senior CSMs spend two to three sessions with the AE before the kickoff specifically to extract the unwritten context.
The success plan is the artifact the entire onboarding (and most of years two and three) runs off. A senior-quality success plan names: the business outcome the customer bought us for (in their words, not the vendor's), the measurable milestones at 30/60/90/180 days, the named executive sponsor on the customer side, the named daily-user champion, and the named backup champion in case the primary leaves. Most first-draft success plans miss the backup champion; that omission is where the champion-departure save play (covered in the churn-prevention deep-skill) ends up running in year two.
Customer-maturity assessment in the first two weeks separates senior CSMs from the rest. A Series-B startup customer and a Fortune 500 customer have different onboarding shapes; running the same kickoff agenda for both is the most common junior failure. Senior CSMs assess the customer's CS-side maturity (do they have a named champion infrastructure? is the team expected to drive their own adoption? is the exec sponsor a real exec or a delegated stakeholder?) and reshape the onboarding accordingly.
Onboarding is where the executive sponsor relationship gets engineered, not where it gets discovered. The senior CSM identifies the real economic buyer in the first two weeks (often different from whoever signed the contract), books a 30-minute kickoff call with that exec in the first 30 days, and uses the call to validate the outcomes definition and the success plan. CSMs who skip this step end up running year two with no exec sponsor at all and discovering the gap when the EBR (covered in the executive-business-reviews deep-skill) has no real executive in the room.
Compensation at the senior end of the CSM track tracks onboarding craft because onboarding is the most consequential moment in the customer lifecycle. The levels.fyi Customer Success track reports median total compensation around $132,000 across the track as of May 2026, with senior bands tracking meaningfully higher; the senior bands skew toward CSMs who can land the first 90 days cleanly because that's what compounds across the book.
Onboarding handoff to the steady-state motion is its own craft. At day 90, the CSM transitions from high-touch onboarding cadence (weekly syncs, daily availability) to the steady-state rhythm (monthly check-ins, quarterly EBRs, renewal-quarter intensification). The handoff fails when the cadence drops too fast (customer feels abandoned) or too slow (customer feels the CSM is wasting their time). Senior craft is calibrating the drop based on the customer's actual maturity and outcome-trajectory at day 90.

The sales-to-CSM handoff (the most underweighted onboarding step)

The kickoff call is the visible onboarding moment; the sales-to-CSM handoff is the invisible one that determines whether the kickoff lands. Most CSM training programs spend the bulk of their material on the kickoff and comparatively little on the handoff; in practice, the ratio should be reversed.

The reason is that the AE has built up months of context that doesn't exist anywhere except in the AE's head. The real economic buyer (often different from the contract signer); the internal politics around the purchase decision; the specific competitive alternatives the customer evaluated and why they rejected each one; the unwritten promises made during the sales cycle (performance commitments, professional services scope, integration timelines); the personal relationships the AE has with specific people on the customer side. None of this is in the CRM.

The senior CSM extracts this context in two to three sessions before the kickoff. Session one: a 60-minute structured walkthrough with the AE, running through every named contact on the customer side and what the AE knows about each (role, decision power, personal preferences, internal credibility). Session two: a competitive-context conversation; what alternatives did the customer evaluate, what did each get wrong from the customer's perspective, and what did the AE commit to that the CSM is now responsible for delivering. Session three (optional but high-value): the AE joins the kickoff call as a co-presenter so the customer sees continuity, not abandonment.

The CSM-and-AE partnership during onboarding is one of the structural differences between strong and weak CS organizations. The RepVue ratings track publishes broad professional-development and culture signals across sales-and-CS orgs; the specific compensation-design observation below is author analysis applied to those broader signals, not a category RepVue explicitly publishes. The observation: companies that compensate AEs partly on customer outcomes after the deal closes (vs AEs whose comp ends at signature) tend to invest in better handoffs. The Bravado War Room is the SaaS-sales practitioner community where these discussions surface. The page does not cite specific threads as proof; the pattern is what the author has observed in practitioner conversation and at companies where the comp design has been described publicly.

What goes in a senior-quality success plan

The success plan is the document the entire customer relationship runs on. Most first-draft success plans are two-page templates that the CSM fills out and forgets; senior-quality success plans are five to seven pages, co-authored with the customer, and referenced in every EBR for the next three years.

Six sections, in order:

Section 1: Business outcome. What the customer is actually trying to achieve, in their words. Not 'use the platform.' Not 'increase NPS.' Something like: 'reduce time-to-quote for the field organization so reps can close more business per quarter.' The test: if the outcome doesn't tie to a business metric the customer's exec would defend in a board meeting, it's not a real outcome and the success plan is built on sand.

Section 2: Measurable milestones at 30/60/90/180 days. What does success look like at each checkpoint? At 30 days: typically a configured environment with the first real workflow live. At 60 days: first-value moment hit (the customer experiences the outcome they bought us for, even at small scale). At 90 days: broader rollout to the full team or first business unit. At 180 days: evidence of business-outcome impact (reduction in time-to-quote, increase in close rate, whatever the named outcome was).

Section 3: Named executive sponsor. Who on the customer side has the most to gain from the outcome being achieved? That person is the executive sponsor. Their name goes in the success plan. They get a 30-minute call in the first 30 days. They get the EBR invites quarterly. If they leave the company, the champion-departure save play (covered in churn-prevention) starts immediately.

Section 4: Named daily-user champion. Who on the customer side will be in the product every day and is the relationship-bearing point of contact for the CSM? Not the same person as the exec sponsor; the daily champion is closer to the work. Their name goes in the success plan, along with their working preferences (sync vs async, weekly vs biweekly, formal vs informal).

Section 5: Named backup champion. Who steps in if the primary champion leaves? This is the section most first-draft success plans miss. Champion turnover happens at the rate of normal job turnover (every two to four years for senior IC roles at most B2B SaaS customers); a success plan without a backup champion is a ticking risk.

Section 6: Outcomes-tracking infrastructure. How will the CSM and customer measure progress against the business outcome? This is the section that connects to the CS platform and operations deep-skill. The senior CSM ensures that the outcomes can actually be measured (data is available, dashboards exist, the customer's analytics team can report on the KPI) before the kickoff ends. CSMs who skip this step discover at month six that the outcome is unmeasurable and the customer has been operating on vibes.

Customer-maturity assessment (the first two weeks)

Running the same onboarding for a Series-B startup and a Fortune 500 customer is the most common junior failure. The startup customer typically has a small team, a single decision-maker, light internal process, and an expectation of high product velocity; the F500 customer has a large team, multiple stakeholders, formal change-management process, and an expectation of stability and compliance.

The senior CSM assesses customer-side maturity in the first two weeks across four dimensions:

CS-side org maturity. Does the customer have a named champion infrastructure (a person whose job includes vendor-relationship ownership), or will adoption depend on the CSM driving it? Mature customer orgs (typically larger companies and specific industries like financial services or healthcare) come with their own internal program-management muscle; the CSM's job is to support, not lead. Less-mature customers need the CSM to drive the project itself.

Decision-maker proximity. How close is the day-to-day champion to the economic buyer? At a 50-person startup, the daily user might be the CEO; at a F500, the daily user might be six layers below the CFO who signed the contract. The further the day-to-day champion is from the decision-maker, the more deliberate the exec-sponsor engineering needs to be.

Internal change-management process. Does the customer have formal review boards, security approvals, integration-architecture committees? F500 customers typically have all three, and the CSM has to build the onboarding timeline around those gates. Skipping the assessment leads to a 60-day timeline that turns into 180 days because nobody flagged the security-review queue.

Outcome-measurement infrastructure. Does the customer have the data and dashboards to actually measure the business outcome they bought the product for? If not, building that infrastructure is part of the onboarding work and the timeline has to reflect it. The Gainsight B2B onboarding article covers the broader pattern; the working-CSM version of this assessment is a 30-minute conversation with the customer's analytics team in week two.

Day 90 handoff to steady-state cadence

The transition from onboarding cadence (weekly or biweekly syncs, daily availability, high-touch responsiveness) to steady-state cadence (monthly check-ins, quarterly EBRs, renewal-quarter intensification) is its own craft. Drop the cadence too fast and the customer feels abandoned; drop it too slow and the customer feels the CSM is wasting their time and over-investing without need.

Three calibration heuristics. (1) Drop based on outcome-trajectory, not calendar. If the customer is comfortably hitting the 30/60/90 milestones, the cadence can drop to monthly at day 90. If the customer missed any milestone, the cadence stays high until the milestone is hit. (2) Make the drop explicit, not ambient. Tell the champion: 'we're moving from weekly syncs to monthly starting next month, with quarterly EBRs and async availability between.' Customers who notice the drop without being told read it as disengagement; customers who're told read it as graduation. (3) Maintain async availability even when sync cadence drops. The senior CSM responds to Slack and email within a day for year-one customers regardless of scheduled cadence; the perception of responsiveness is what carries the relationship through the cadence transition.

The handoff also typically marks the transition from onboarding-CSM to steady-state CSM in companies that split the role. At larger companies (Salesforce, ServiceNow, Snowflake; see hub spokes) the customer transitions from an Onboarding Specialist or Implementation Manager to a long-term Customer Success Manager at day 90. That internal handoff has the same dynamics as the original sales-to-CSM handoff and benefits from the same discipline: structured context transfer, customer-visible introduction, and the original onboarder available as a fallback for the first 30 days post-handoff.

Frequently asked questions

What is time-to-first-value (TTFV) and how is it set?: Time-to-first-value (TTFV) is the time from contract signature to the moment the customer experiences the business outcome they bought the product for, even at small scale. Most B2B SaaS companies set TTFV between 30 and 90 days depending on product complexity. The senior craft is engineering the milestone definition itself: 'first value' should be specific to the customer's business outcome, not generic to the product. A customer who 'completed onboarding' but didn't experience the business outcome has not reached first value; a customer who experienced the outcome at small scale (one workflow, one team, one use case) has, even if the broader rollout is incomplete.
Who attends the kickoff call?: Five named roles, minimum: the customer's economic buyer (the executive who has the most to gain from the outcome), the daily-user champion, any technical-implementation lead on the customer side, the CSM, and the AE who closed the deal. Optional but high-value: a backup champion candidate (so they're introduced to the relationship from day one), the customer's analytics lead (so outcome-measurement gets scoped immediately), and the vendor's implementation manager if the project is technically complex. The kickoff without the economic buyer is a kickoff with a structural problem; the CSM should reschedule rather than run the kickoff cold.
What does a bad kickoff look like?: Three failure shapes. (1) Generic agenda: the CSM runs the same kickoff deck for every customer without customizing for the specific outcome. The customer reads it as 'this CSM doesn't know what I'm trying to achieve.' (2) Feature dump: the kickoff turns into a product walkthrough rather than an outcomes conversation. The customer leaves with no clearer sense of how the product addresses their business problem. (3) Missing economic buyer: the kickoff happens without the real decision-maker, which means the outcomes definition and success plan lack the validation they need to be load-bearing for the next three years.
How do you handle a customer who isn't engaged in onboarding?: Customer disengagement during onboarding is the highest-priority early-warning signal in the CSM playbook. Three responses, in order. (1) Diagnose the cause: is the daily champion overloaded (temporary), did the economic buyer lose interest (structural), or did internal priorities shift (strategic)? (2) Re-engage the exec sponsor with a 1:1 conversation naming the disengagement directly and asking what changed. (3) If the answer is structural, the onboarding has to be paused or scoped down, not pushed forward. Pushing through customer disengagement is the most common way an onboarding becomes a year-two churn.
What's the difference between onboarding and implementation?: Implementation is the technical configuration work (provisioning, integrations, data loading, user setup); onboarding is the broader customer-success motion (success plan, outcomes definition, executive sponsor relationship, champion training, change management). At small companies, the CSM owns both; at larger companies (Salesforce, ServiceNow, Datadog), there's typically a dedicated Implementation Specialist or Professional Services team for the technical work and the CSM owns the broader motion. Confusing the two leads to either CSMs doing technical work they're not qualified for, or implementation teams running success-plan conversations they're not trained for.
How long should onboarding take?: The typical answer is 30 to 90 days, but the right answer depends on product complexity and customer maturity. Simple SaaS products with self-serve adoption (think lightweight productivity tools) can onboard in 14 to 30 days; complex enterprise products with deep integrations (think CRM, data-platform, identity-and-access) can take 90 to 180 days. Trying to compress complex onboarding into a 30-day timeline because that's the company's default is a structural mistake; the senior CSM negotiates the timeline with the customer's specific situation in mind, not the corporate default.
What goes wrong if onboarding lacks an executive sponsor?: Three predictable failures, all showing up in year two. (1) The EBR has no real executive in the room and turns into a status meeting, losing its strategic function. (2) When a competitor approaches the customer mid-cycle, there's no exec relationship to anchor the save. (3) When the daily-user champion changes jobs, the relationship is single-point-of-failure and often lost. The engineering of the executive sponsor relationship is the highest-stakes piece of onboarding work and the most commonly skipped because it's uncomfortable for junior CSMs to ask the daily champion 'who's the right exec to bring into this conversation?'
Should the AE stay involved after the kickoff?: Yes, partially. The AE shouldn't drive the day-to-day onboarding (that's the CSM's role), but the AE should remain on the customer exec-sponsor relationship for at least the first 90 days. The structural reason: the exec relationship the AE built during the sales cycle is real social capital, and abandoning it at signature means the CSM has to rebuild it from scratch. The author's observation across companies that handle this well: AEs are compensated partly on year-one outcomes, not just on signature. The RepVue ratings track publishes broad professional-development and culture signals that correlate with healthy CS orgs but does not publish compensation-design as a category; that observation is author analysis. Practitioner discussion of the pattern surfaces in the Bravado War Room, but the page does not cite specific threads as proof.

Sources

About the author. Blake Crosley founded ResumeGeni and writes about customer success, hiring technology, and ATS optimization. More writing at blakecrosley.com.