Skip to content

Company rollup property: date of most recent deal stage change

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: Sales Hub Professional.

Company3 stepsUpdated for HubSpot seat pricing
OutcomeEvery company record shows the date its associated deals most recently changed stage, so account managers can see pipeline momentum, or the lack of it, without opening every associated deal.
Workflow mapreporting-alerts-046
Deal stage changes leads to Set last_stage_change_date = now, on the deal. Set last_stage_change_date = now, on the deal leads to Company rollup recalculates automatically. Company rollup recalculates automatically leads to most_recent_deal_stage_change_date reflects the latest across all associated deals. Deal stage changes Set last_stage_change_date = now, on the deal Company rollup recalculates automatically most_recent_deal_stage_ change_date reflects the latest across all associated deals
Deal stage changes leads to Set last_stage_change_date = now, on the deal. Set last_stage_change_date = now, on the deal leads to Company rollup recalculates automatically. Company rollup recalculates automatically leads to most_recent_deal_stage_change_date reflects the latest across all associated deals. Deal stage changes Set last_stage_change_date = now, on the deal Company rollup recalculates automatically most_recent_deal_stage_ change_date reflects the latest across all associated deals

When to use it, when not to

Use it

  • Use it to flag accounts whose deals have gone quiet, no stage movement in a while, as candidates for a manual check-in.
  • Use it alongside reporting-alerts-021 and reporting-alerts-022 for a fuller account-level pipeline visibility set: open count, total value, and now recency of movement.
Read more on when to use itShow less

Skip it

  • Do not use it if deals move through stages very frequently as a side effect of automation rather than genuine progress; in that case this date reflects automation noise, not real momentum.
  • Do not use it as a substitute for reviewing deal-level stage history when the actual sequence of stage changes matters, not just the most recent one.
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 · 3 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

The properties JSON creates the fields in one call. The workflow JSON documents the build.

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 Reporting and alerts 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