The Workflow Library

Library / Customer onboarding / customer-onboarding-010

Onboarding start date property set on deal closed won

Customer onboardingDealSales Hub ProfessionalSimple~15 min to buildFull spec

Outcome. Every closed-won deal gets a single, reliable timestamp for when onboarding began, so reporting on time-to-value and onboarding duration has a consistent anchor without depending on any other onboarding workflow being active.

Workflow map Enrollment, branches and actions at a glance customer-onboarding-010
flowchart TD
    A[Deal stage = Closed Won, Onboarding Start Date not yet set] --> B[Set Onboarding Start Date = current date]
action or delay branch public on every spec, paid or not

When to use it, when not to

  • UseUse it as the minimum viable version of the onboarding-tracking pattern, when a full handoff task (customer-onboarding-001) or ticket (customer-onboarding-005) is more than the team needs yet, but reporting still matters.
  • UseUse it alongside those larger fiches too, since they reuse the same property, this one just isolates the single step for teams that want to build it in isolation first.
  • SkipDo not use it if Close Date already serves this purpose well enough for your reporting, adding a duplicate property with no distinct meaning is not worth the extra field.
  • SkipDo not use it if onboarding for some deals starts materially later than the close date, for example waiting on a signed order form, a manually set date closer to the true start is more accurate than an automated one.
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.1 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.1 numbered action
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 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.