Skip to content

Calculated property: lead-to-customer conversion time in days

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

Contact4 stepsUpdated for HubSpot seat pricing
OutcomeEvery 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 mapdata-quality-042
Lifecycle stage becomes Customer leads to Custom code: read Lead and Customer date-entered timestamps. Custom code: read Lead and Customer date-entered timestamps leads to Both dates known?. Both dates known? leads to yes: Set Lead to customer days; no: Leave property blank. yes no Lifecycle stage becomes Customer Custom code: read Lead and Customer date-entered timestamps Both dates known? Set Lead to customer days Leave property blank
Lifecycle stage becomes Customer leads to Custom code: read Lead and Customer date-entered timestamps. Custom code: read Lead and Customer date-entered timestamps leads to Both dates known?. Both dates known? leads to yes: Set Lead to customer days; no: Leave property blank. yes no Lifecycle stage becomes Customer Custom code: read Lead and Customer date-entered timestamps Both dates known? Set Lead to customer days Leave property blank

When to use it, when not to

Use it

  • Use it once contacts reliably pass through a Lead lifecycle stage before Customer, and HubSpot is tracking the timestamp of each lifecycle stage change through its native date-entered properties.
  • Use it for cohort-level reporting, average conversion time by source, by campaign, rather than as an individual record's headline metric.
Read more on when to use itShow less

Skip it

  • Do not use it on contacts that skip the Lead stage 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.
  • Do not use it if your lifecycle stages are not applied consistently. A portal where reps freely set Customer without the record ever passing through Lead produces a zero or a wrong short number that looks like an unusually fast conversion instead of a data gap.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 3 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 4 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 3 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library