Which customer onboarding track should I use?

Which customer onboarding track should I use?

Decision tree customer successonboardingimplementationcustomer experience

Determine which onboarding track a new customer should follow based on their contract size, technical profile, and implementation complexity. Routing a customer to the right track from day one directly impacts time-to-value, adoption rates, and long-term retention. Use this tree as soon as a deal is closed and before the kickoff call is scheduled.

Overview

Type
Decision tree
Tags
customer success, onboarding, implementation, customer experience
Entry
Q1
Questions
4
Outcomes
4
Author
Andrew
Last updated
2026-05-12

Decision Tree

Start: What is the customer's annual contract value (ACV)?

A: Under $10,000

  • Outcome: Self-Serve Onboarding

B: $10,000 – $75,000

  • Continues to question: Does the customer have strong technical sophistication—meaning their team includes engineers, IT administrators, or dedicated operations staff who will own the implementation?

C: Above $75,000

  • Continues to question: Does the implementation require integrations with existing systems, data migrations from another platform, or custom configuration beyond standard out-of-the-box setup?

Machine-Readable JSON (Canonical Model)

View JSON
{
  "_meta": {
    "schema": "https://www.drawdecisiontree.com/decision-dag.schema.json",
    "source": "https://www.drawdecisiontree.com",
    "description": "DrawDecisionTree.com is a free tool for building, sharing, and embedding interactive decision trees. This file is the machine-readable export of a published decision tree. The `dsl` field contains the original source in the Decision DAG DSL; the `dag` schema is documented at the URL in `schema` above.",
    "links": {
      "interactive": "https://www.drawdecisiontree.com/t/drawdecisiontree/cs-onboarding-track.html",
      "embed": "https://www.drawdecisiontree.com/embed/path/drawdecisiontree/cs-onboarding-track",
      "dsl_reference": "https://www.drawdecisiontree.com/decision-tree-dsl-reference.html",
      "guides": "https://www.drawdecisiontree.com/guides",
      "schema_docs": "https://www.drawdecisiontree.com/decision-dag.schema.json",
      "author_trees": "https://www.drawdecisiontree.com/trees/drawdecisiontree"
    },
    "generated_at": "2026-05-29T12:05:39.264Z"
  },
  "author": {
    "handle": "drawdecisiontree",
    "first_name": "Andrew",
    "last_name": null,
    "avatar_url": "1d32d828-b6ca-40ec-bdd7-771fe7b9c36a/avatar-1778531481027.svg",
    "display_name": "Andrew"
  },
  "file": {
    "id": "d3061401-88ba-4748-87d5-4d9363a0e661",
    "name": "Which customer onboarding track should I use?",
    "public_slug": "cs-onboarding-track",
    "updated_at": "2026-05-12T16:53:43.587978+00:00",
    "url": "https://www.drawdecisiontree.com/t/drawdecisiontree/cs-onboarding-track.html",
    "json_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/cs-onboarding-track/tree.json",
    "dsl_url": "https://www.drawdecisiontree.com/t/drawdecisiontree/cs-onboarding-track/tree.dag"
  },
  "meta": {
    "description": "Determine which onboarding track a new customer should follow based on their contract size, technical profile, and implementation complexity. Routing a customer to the right track from day one directly impacts time-to-value, adoption rates, and long-term retention. Use this tree as soon as a deal is closed and before the kickoff call is scheduled.",
    "mode": "decision",
    "entry": "Q1",
    "tags": [
      "customer success",
      "onboarding",
      "implementation",
      "customer experience"
    ],
    "image": "https://images.unsplash.com/photo-1531497865144-0464ef8fb9a9?w=1200&q=80"
  },
  "questions": [
    {
      "id": "Q1",
      "text": "What is the customer's annual contract value (ACV)?"
    },
    {
      "id": "Q2",
      "text": "Does the customer have strong technical sophistication—meaning their team includes engineers, IT administrators, or dedicated operations staff who will own the implementation?"
    },
    {
      "id": "Q3",
      "text": "Does the implementation require integrations with existing systems, data migrations from another platform, or custom configuration beyond standard out-of-the-box setup?"
    },
    {
      "id": "Q4",
      "text": "Is the customer's ACV above $150,000, or do they have more than 200 users who will need to be onboarded and trained?"
    }
  ],
  "outcomes": [
    {
      "id": "SELF_SERVE",
      "label": "Self-Serve Onboarding"
    },
    {
      "id": "GUIDED_ONBOARDING",
      "label": "Guided Onboarding (CSM-Led)"
    },
    {
      "id": "HIGH_TOUCH",
      "label": "High-Touch Implementation"
    },
    {
      "id": "ENTERPRISE_PS",
      "label": "Enterprise Onboarding with Professional Services"
    }
  ],
  "dsl": "dag: Which customer onboarding track should I use?\nversion: 1.0.0\nimage: https://images.unsplash.com/photo-1531497865144-0464ef8fb9a9?w=1200&q=80\ndescription: Determine which onboarding track a new customer should follow based on their contract size, technical profile, and implementation complexity. Routing a customer to the right track from day one directly impacts time-to-value, adoption rates, and long-term retention. Use this tree as soon as a deal is closed and before the kickoff call is scheduled.\ntags: customer success, onboarding, implementation, customer experience\nentry: Q1\n\nQ1: What is the customer's annual contract value (ACV)?\n  hint: Contract value is the primary proxy for the level of onboarding investment your company can sustainably provide and what the customer expects based on what they paid. Higher ACV customers typically have more complex use cases, larger user populations, and stronger expectations around dedicated support during onboarding. Use the exact ACV from the closed-won opportunity in your CRM—not an estimate—to ensure the routing is accurate. If the customer is on a month-to-month or pilot arrangement, use their projected annual spend.\n  A: Under $10,000 -> [SELF_SERVE]\n  B: $10,000 – $75,000 -> Q2\n  C: Above $75,000 -> Q3\n\nQ2: Does the customer have strong technical sophistication—meaning their team includes engineers, IT administrators, or dedicated operations staff who will own the implementation?\n  hint: Technical sophistication determines how much hand-holding the customer will need during the configuration and integration phases of onboarding. A technically strong team can follow structured documentation and complete most setup tasks independently with asynchronous support, while a non-technical team typically needs synchronous guidance and more frequent check-ins to avoid stalls. Assess this during the pre-kickoff discovery call by asking who will own the technical implementation and whether they have experience with similar SaaS tools. When in doubt, assume less sophistication and route to a higher-touch track.\n  yes -> Q3\n  no  -> [GUIDED_ONBOARDING]\n\nQ3: Does the implementation require integrations with existing systems, data migrations from another platform, or custom configuration beyond standard out-of-the-box setup?\n  hint: Integration and migration requirements are the single largest source of onboarding delays and early-stage churn. Even a technically sophisticated customer will struggle without structured support if they need to connect your product to a CRM, ERP, data warehouse, or identity provider. Ask the customer to enumerate every system they expect your product to connect with and whether any historical data needs to be migrated. A \"yes\" here does not necessarily mean Professional Services—but it does mean the onboarding plan must explicitly account for integration complexity with milestones, owners, and acceptance criteria.\n  yes -> Q4\n  no  -> [GUIDED_ONBOARDING]\n\nQ4: Is the customer's ACV above $150,000, or do they have more than 200 users who will need to be onboarded and trained?\n  hint: Large user populations and very high ACV contracts typically require a coordinated implementation program that exceeds what a standard CSM can run alongside their full book of business. At this scale, customers expect a dedicated implementation manager, a formal project plan with executive sign-off, change management support, and often customized training materials. Failing to staff onboarding appropriately for these accounts is one of the most common causes of executive escalation in months two through four. If the customer's contract is large but their user count is low, consider whether complexity and integration requirements warrant Professional Services involvement anyway.\n  yes -> [ENTERPRISE_PS]\n  no  -> [HIGH_TOUCH]\n\n[SELF_SERVE]: Self-Serve Onboarding\n  color: #22c55e\n  description: This customer is well-suited for a self-directed onboarding experience supported by your product's in-app guidance, documentation library, and automated email sequences. Send a curated onboarding email sequence within 24 hours of account activation, with direct links to the top five resources that drive fastest time-to-value for this use case. Schedule a single optional 30-minute orientation call at the two-week mark to surface any blockers and confirm the customer is progressing. Monitor product activation metrics in your analytics platform and trigger a proactive outreach if the customer has not reached key milestones within the first 14 days.\n  code: CS_OB_SELF_SERVE\n\n[GUIDED_ONBOARDING]: Guided Onboarding (CSM-Led)\n  color: #3b82f6\n  description: This customer will benefit from a structured, CSM-led onboarding program with a defined kickoff call, a milestone-based success plan, and regular check-in cadence over the first 60–90 days. Schedule the kickoff call within five business days of contract signing, and arrive prepared with a draft success plan that includes the customer's stated business goals, key milestones, and a timeline to first value. Run biweekly check-ins during the active onboarding phase and document milestone completion in your CRM for internal visibility. Transition the customer to a standard ongoing engagement cadence once all kickoff milestones are achieved and confirmed in writing.\n  code: CS_OB_GUIDED\n\n[HIGH_TOUCH]: High-Touch Implementation\n  color: #f59e0b\n  description: This customer's contract value or implementation complexity warrants a dedicated, high-touch onboarding program with a structured project plan, defined RACI, and weekly steering cadence involving both technical and business stakeholders. Deliver a formal implementation plan within five business days of kickoff, covering workstreams, owners, dependencies, and a go-live target date with clear success criteria. Maintain a shared project tracker that both your team and the customer can update in real time, and escalate any milestone slippage immediately rather than absorbing delays silently. Conduct a formal go-live review call to confirm the customer has achieved their initial success criteria before transitioning to steady-state account management.\n  code: CS_OB_HIGH_TOUCH\n\n[ENTERPRISE_PS]: Enterprise Onboarding with Professional Services\n  color: #7c3aed\n  description: This is a large, complex implementation that requires a dedicated Professional Services engagement alongside the CSM to ensure the customer reaches go-live successfully and on schedule. Engage your PS team during the pre-kickoff period—before the customer kickoff call—so the implementation scope, pricing, and resource allocation are agreed internally before commitments are made to the customer. Create a full implementation workbook covering technical requirements, data migration plan, training curriculum, and executive governance checkpoints. Maintain weekly executive sponsor alignment on both sides and establish a clear escalation path within the PS engagement so issues are surfaced and resolved before they impact the go-live date.\n  code: CS_OB_ENTERPRISE_PS\n"
}

DSL Representation

dag: Which customer onboarding track should I use?
version: 1.0.0
image: https://images.unsplash.com/photo-1531497865144-0464ef8fb9a9?w=1200&q=80
description: Determine which onboarding track a new customer should follow based on their contract size, technical profile, and implementation complexity. Routing a customer to the right track from day one directly impacts time-to-value, adoption rates, and long-term retention. Use this tree as soon as a deal is closed and before the kickoff call is scheduled.
tags: customer success, onboarding, implementation, customer experience
entry: Q1

Q1: What is the customer's annual contract value (ACV)?
  hint: Contract value is the primary proxy for the level of onboarding investment your company can sustainably provide and what the customer expects based on what they paid. Higher ACV customers typically have more complex use cases, larger user populations, and stronger expectations around dedicated support during onboarding. Use the exact ACV from the closed-won opportunity in your CRM—not an estimate—to ensure the routing is accurate. If the customer is on a month-to-month or pilot arrangement, use their projected annual spend.
  A: Under $10,000 -> [SELF_SERVE]
  B: $10,000 – $75,000 -> Q2
  C: Above $75,000 -> Q3

Q2: Does the customer have strong technical sophistication—meaning their team includes engineers, IT administrators, or dedicated operations staff who will own the implementation?
  hint: Technical sophistication determines how much hand-holding the customer will need during the configuration and integration phases of onboarding. A technically strong team can follow structured documentation and complete most setup tasks independently with asynchronous support, while a non-technical team typically needs synchronous guidance and more frequent check-ins to avoid stalls. Assess this during the pre-kickoff discovery call by asking who will own the technical implementation and whether they have experience with similar SaaS tools. When in doubt, assume less sophistication and route to a higher-touch track.
  yes -> Q3
  no  -> [GUIDED_ONBOARDING]

Q3: Does the implementation require integrations with existing systems, data migrations from another platform, or custom configuration beyond standard out-of-the-box setup?
  hint: Integration and migration requirements are the single largest source of onboarding delays and early-stage churn. Even a technically sophisticated customer will struggle without structured support if they need to connect your product to a CRM, ERP, data warehouse, or identity provider. Ask the customer to enumerate every system they expect your product to connect with and whether any historical data needs to be migrated. A "yes" here does not necessarily mean Professional Services—but it does mean the onboarding plan must explicitly account for integration complexity with milestones, owners, and acceptance criteria.
  yes -> Q4
  no  -> [GUIDED_ONBOARDING]

Q4: Is the customer's ACV above $150,000, or do they have more than 200 users who will need to be onboarded and trained?
  hint: Large user populations and very high ACV contracts typically require a coordinated implementation program that exceeds what a standard CSM can run alongside their full book of business. At this scale, customers expect a dedicated implementation manager, a formal project plan with executive sign-off, change management support, and often customized training materials. Failing to staff onboarding appropriately for these accounts is one of the most common causes of executive escalation in months two through four. If the customer's contract is large but their user count is low, consider whether complexity and integration requirements warrant Professional Services involvement anyway.
  yes -> [ENTERPRISE_PS]
  no  -> [HIGH_TOUCH]

[SELF_SERVE]: Self-Serve Onboarding
  color: #22c55e
  description: This customer is well-suited for a self-directed onboarding experience supported by your product's in-app guidance, documentation library, and automated email sequences. Send a curated onboarding email sequence within 24 hours of account activation, with direct links to the top five resources that drive fastest time-to-value for this use case. Schedule a single optional 30-minute orientation call at the two-week mark to surface any blockers and confirm the customer is progressing. Monitor product activation metrics in your analytics platform and trigger a proactive outreach if the customer has not reached key milestones within the first 14 days.
  code: CS_OB_SELF_SERVE

[GUIDED_ONBOARDING]: Guided Onboarding (CSM-Led)
  color: #3b82f6
  description: This customer will benefit from a structured, CSM-led onboarding program with a defined kickoff call, a milestone-based success plan, and regular check-in cadence over the first 60–90 days. Schedule the kickoff call within five business days of contract signing, and arrive prepared with a draft success plan that includes the customer's stated business goals, key milestones, and a timeline to first value. Run biweekly check-ins during the active onboarding phase and document milestone completion in your CRM for internal visibility. Transition the customer to a standard ongoing engagement cadence once all kickoff milestones are achieved and confirmed in writing.
  code: CS_OB_GUIDED

[HIGH_TOUCH]: High-Touch Implementation
  color: #f59e0b
  description: This customer's contract value or implementation complexity warrants a dedicated, high-touch onboarding program with a structured project plan, defined RACI, and weekly steering cadence involving both technical and business stakeholders. Deliver a formal implementation plan within five business days of kickoff, covering workstreams, owners, dependencies, and a go-live target date with clear success criteria. Maintain a shared project tracker that both your team and the customer can update in real time, and escalate any milestone slippage immediately rather than absorbing delays silently. Conduct a formal go-live review call to confirm the customer has achieved their initial success criteria before transitioning to steady-state account management.
  code: CS_OB_HIGH_TOUCH

[ENTERPRISE_PS]: Enterprise Onboarding with Professional Services
  color: #7c3aed
  description: This is a large, complex implementation that requires a dedicated Professional Services engagement alongside the CSM to ensure the customer reaches go-live successfully and on schedule. Engage your PS team during the pre-kickoff period—before the customer kickoff call—so the implementation scope, pricing, and resource allocation are agreed internally before commitments are made to the customer. Create a full implementation workbook covering technical requirements, data migration plan, training curriculum, and executive governance checkpoints. Maintain weekly executive sponsor alignment on both sides and establish a clear escalation path within the PS engagement so issues are surfaced and resolved before they impact the go-live date.
  code: CS_OB_ENTERPRISE_PS

Machine Access

Questions in this decision tree

Possible outcomes

How to use this decision tree

Click "Open interactive version" to step through the questions. Your answers narrow the tree until a recommended outcome is reached. You can also embed this tree on your own site.

More decision trees by Andrew

Which API design pattern is right for my project?
Which API design pattern is right for my project?
Determine the right API design style for your integration scenario.
Authentication Method Selection
Authentication Method Selection
Authentication is a security-critical, high-friction decision to reverse — migrating users from one auth method to another requires coordinated password resets or credential migration campaigns. This tree eliminates methods that don't match your user type, enterprise requirements, and security posture, giving you a clear shortlist before you write a line of code.
Caching Strategy Selection
Caching Strategy Selection
Premature or misapplied caching adds complexity — stale data bugs, invalidation logic, and distributed consistency problems — without solving the actual bottleneck. This tree routes you to the caching pattern that matches your data access profile, so you apply the right tool to the right problem rather than defaulting to Redis for everything.
CI/CD Pipeline Tool Selection
CI/CD Pipeline Tool Selection
Choosing a CI/CD platform is a long-term infrastructure commitment — pipelines accumulate config, custom scripts, and team muscle memory that make switching painful. This tree eliminates tools that don't fit your source control host, infrastructure model, or team scale, leaving only the options genuinely viable for your situation.
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Which cloud provider should I use — AWS, Azure, or Google Cloud?
Answer a few questions to identify the most suitable cloud platform for your workload.
Container Orchestration Platform Selection
Container Orchestration Platform Selection
Container orchestration is foundational infrastructure — the platform you choose shapes how you deploy, scale, network, and operate every service you run. This tree eliminates options that don't match your operational maturity, cloud provider commitment, and workload complexity, so you land on the platform that fits your team today without over-engineering for a scale you haven't reached.