Outcome. Every contact that becomes a customer carries a single number for how many days the lead-to-customer journey took, so sales cycle reporting stops depending on a manual date-diff pulled separately for every cohort.
Workflow map
Enrollment, branches and actions at a glance
data-quality-042
flowchart TD
A[Lifecycle stage becomes Customer] --> B[Custom code: read Lead and Customer date-entered timestamps]
B --> C{Both dates known?}
C -->|yes| D[Set Lead to customer days]
C -->|no| E[Leave property blank]
When to use it, when not to
- UseUse it once contacts reliably pass through a
Leadlifecycle stage beforeCustomer, and HubSpot is tracking the timestamp of each lifecycle stage change through its native date-entered properties. - UseUse it for cohort-level reporting, average conversion time by source, by campaign, rather than as an individual record's headline metric.
- SkipDo not use it on contacts that skip the
Leadstage entirely, a direct signup with no prior lead stage. The calculation needs both timestamps to mean anything, and the code should leave the property blank rather than compute a wrong number from a missing starting point. - SkipDo not use it if your lifecycle stages are not applied consistently.
A portal where reps freely set
Customerwithout the record ever passing throughLeadproduces a zero or a wrong short number that looks like an unusually fast conversion instead of a data gap.
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.4 numbered actions
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, and the custom coded action ships as a ready-to-paste .js file.PDF, Markdown, JSON, code
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 data quality 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.
