The Workflow Library

Library / Customer onboarding / customer-onboarding-016

Branch onboarding path by deal size (high-touch vs low-touch)

Customer onboardingDealSales Hub ProfessionalIntermediate~30 min to buildalso needs Marketing Hub ProfessionalFull spec

This spec is filed under Sales Hub Professional, and one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written.

Outcome. A closed-won deal is routed to a hands-on onboarding path or a self-serve path based on its amount, so the CS team spends dedicated time where the deal size justifies it.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-016
flowchart TD
    A[Deal stage = Closed Won, path not yet set] --> B{Amount >= threshold?}
    B -->|Yes| C[Set Onboarding Path = High-touch]
    C --> D[Create kickoff task for Onboarding Owner]
    D --> E[Send internal notification]
    B -->|No| F[Set Onboarding Path = Low-touch]
    F --> G[Add to Low-touch Onboarding list]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it when the same onboarding process today gets applied to every new customer regardless of size, wasting CS time on small accounts or under-serving large ones.
  • UseUse it when deal amount is a reasonable proxy for onboarding complexity in your business.
  • SkipDo not use it if plan or product purchased is a better predictor of onboarding complexity than deal amount, use customer-onboarding-017 instead, or combine both branches.
  • SkipDo not use it for Enterprise deals that need a named specialist rather than a two-way split, see customer-onboarding-039.
The preview ends here. Six sections are in the library. counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.3 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.6 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.5 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library, 149 EUR

or the customer onboarding pack, 39 EUR

One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.