Home/Blog/7 Onboarding Metrics Every VP of Customer Success Should Track
Metrics

7 Onboarding Metrics Every VP of Customer Success Should Track

VP CS dashboards are often long and shallow. Twenty metrics, most decorative, three actually predictive. Here are the seven that matter, with definitions precise enough to actually instrument.

What is time-to-first-value and how do you measure it?

Time-to-first-value (TTFV) is the number of days from contract signature to the customer completing a defined "first value" event. Not first login, not "setup complete." A specific product event that proves the customer used the product for its intended purpose.

  • Definition. Days between opportunity closed-won and first-value event.
  • Benchmark. 14 to 30 days for SMB, 30 to 60 for mid-market, 60 to 90 for enterprise.
  • How to instrument. Product analytics event tied to the account, joined with CRM close date.
  • Signal. Long TTFV predicts churn better than NPS. Cohort it by segment, template, and IM.

If your TTFV definition is longer than one sentence, it is probably wrong. Trim until it names one specific event.

What is time-to-full-value and why does it matter?

TTFV-1 is first value. TTFV-2 is full value: the customer using the product at the depth they bought it for. Both matter, and tracking only one hides different problems.

  • Definition. Days between close and the customer using the product across the roles or workflows in the deal.
  • Benchmark. 60 to 120 days for mid-market, 120 to 180 for enterprise.
  • How to instrument. Product analytics on multi-role or multi-workflow usage.
  • Signal. A short TTFV-1 with a long TTFV-2 means the customer is stuck at the pilot layer. That is a common churn setup.

Most CS teams track TTFV-1 and stop. The gap between first value and full value is where retention lives.

What is go-live slip percentage?

The percentage of onboardings that miss the go-live date committed in kickoff. Measured against the kickoff-committed date, not a rebaselined date.

Segment Best-in-class Median Poor
SMB Under 15% 25-35% 50%+
Mid-market Under 20% 35-45% 55%+
Enterprise Under 30% 45-55% 65%+

Slip percentage is the single strongest external signal that the plan is not being used as a plan. Above 50%, the plan has become theatrical. It exists but does not steer.

Cohort by IM, by template, by segment. If slip is concentrated in one IM, that is a coaching problem. If it is concentrated in one template, that template is broken. If it is even across everything, the process is the issue.

What is phase-gate completion rate?

Percentage of accounts that pass each phase gate on the originally scheduled date. A gate is a formal transition between phases (kickoff done, data phase done, training done, go-live).

  • Definition. For each phase gate, percentage of accounts hitting the gate on the committed date.
  • Benchmark. 70%+ on the first gate, degrading to 50 to 60% by go-live is typical. Best-in-class holds 70%+ across all gates.
  • How to instrument. Log the committed and actual date for each gate in your onboarding system.
  • Signal. The first gate that dips below 60% is where compression pays off. Fix it and the downstream gates improve automatically.

Track this per gate, not just aggregate. The aggregate hides which specific phase is dragging.

What is customer-side task turnaround?

Average days between a customer-side task being assigned and being completed. The most under-instrumented metric on this list.

  • Definition. For every customer-side task, days from assignment to completion. Averaged per account and per template.
  • Benchmark. Under 4 days is best-in-class. Median is 7 to 10. Anything above 14 signals a plan the customer is not opening.
  • How to instrument. Task-level timestamps from the shared onboarding system.
  • Signal. High turnaround with low task counts means the customer is disengaged. High turnaround with high task counts means the plan is overloaded. Both need response, and the response is different.

If you do not track this, you do not know which side of the boundary is causing your slip.

What is IM utilization and how do you use it?

Percentage of an implementation manager's working time spent on actual customer work, as opposed to coordination overhead, meetings, and internal ops.

  • Definition. Direct customer work hours divided by total working hours.
  • Benchmark. 60 to 70% is healthy. Below 50% means the team is drowning in coordination. Above 80% means the team has no slack for incident response.
  • How to instrument. Either time-tracking (unpopular but accurate) or activity-based estimation from meetings, tasks completed, and emails sent.
  • Signal. Falling utilization while headcount is flat means the coordination overhead of running more accounts is growing faster than the account count. That is the moment to invest in tooling.

This metric is uncomfortable because it names a fixable operational cost. Track it anyway.

What is first-90-day churn and why does it belong here?

Percentage of new customers who churn or downgrade within 90 days of contract start. The lagging indicator that closes the loop.

  • Definition. New customers who cancel, downgrade, or fail to activate within the first 90 days, as percentage of new customers in the cohort.
  • Benchmark. Under 5% for SMB, under 3% for mid-market, under 2% for enterprise, is healthy.
  • How to instrument. Cohort analysis on CRM plus billing data.
  • Signal. A rising first-90-day churn rate with stable close rates means AEs are closing customers onboarding is not converting. That is a CS problem, not a sales problem, and it belongs to VP CS.

Any onboarding metric that does not tie back to first-90-day churn is running on faith.

How do you actually run these seven together?

Weekly, monthly, quarterly. Different metrics answer different questions at different cadences.

  • Weekly (portfolio health). Go-live slip, phase-gate completion, customer-side task turnaround, IM utilization. These are operational levers, checked with a five-minute look at the portfolio.
  • Monthly (cohort trends). TTFV-1, TTFV-2, first-90-day churn, cohorted by segment and template. This is where you find pattern breakdowns before they become NRR problems.
  • Quarterly (benchmark shifts). Compare all seven to the previous quarter, to your best quarter, to industry benchmarks. Answer: are the fixes working.

If your weekly review is looking at TTFV-1, you are using a monthly metric weekly and you will chase noise.

The mistake to avoid

The mistake is treating the metric list as a menu instead of a system. Each of these seven metrics hides a different failure mode, and skipping any one means you have a blind spot in a specific direction. TTFV-1 alone does not tell you that customers are stalling in the pilot layer. Go-live slip alone does not tell you if the slip was on your side or theirs. First-90-day churn alone tells you what happened but not why. The seven work as a system because they triangulate the actual health of onboarding. Pick any three and you have opinions. Track all seven and you have answers.

customer success metricsonboarding kpistime-to-valuevp customer successimplementation metrics

Frequently asked questions

What is the single most important onboarding metric?

Time-to-first-value is the leading indicator, first-90-day churn is the lagging one. If you can only track two, track those. First-value proves the customer got something. First-90-day churn proves onboarding created a customer who wanted to stay. Everything else is diagnostic on why one moved without the other.

How do you define 'first value' for a B2B SaaS product?

It is product-specific but always concrete. For an analytics tool, first dashboard shared with an executive. For a sales tool, first pipeline review run inside it. For an accounting product, first monthly close completed. Vague definitions like 'first login' or 'setup complete' are not first value. Ask yourself: what proves the customer used the product for its actual purpose.

What is a reasonable benchmark for go-live slip percentage?

Under 20% for mid-market, under 30% for enterprise, is best-in-class. Industry median is 40 to 50%. Anything above 60% means the plan is not being used as a plan, it is being used as a wish. Slip is measured against the go-live date committed in kickoff, not against a date that got rebaselined mid-rollout.

How often should VP CS review onboarding metrics?

Weekly for portfolio health, monthly for cohort trends, quarterly for benchmark shifts. Weekly review catches drift on individual accounts. Monthly review catches pattern breakdowns by segment or template. Quarterly review compares to the last quarter and answers whether the fixes worked.

Should CSMs see these metrics on their own accounts?

Yes, all of them. Hiding portfolio metrics from the IMs and CSMs who run individual rollouts guarantees the wrong feedback loop. Every IM should see their portfolio version of every one of these metrics, updated at least daily. The head of CS sees the aggregated version. Same data, different roll-up.

Know a go-live will slip early

Clarari runs every onboarding on one shared plan both sides use, with live go-live projections and CRM sync.

Request early access