Skip to content

Weekly Slack digest: deals closed lost this week with reasons

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.

Deal2 stepsUpdated for HubSpot seat pricing
OutcomeOnce a week, the sales channel gets one message listing every deal closed lost that week along with its loss reason, so the team spots patterns without opening a report.
Workflow mapreporting-alerts-011
Weekly schedule: Friday 16:00 leads to Dashboard report renders: Closed Lost deals, last 7 days. Dashboard report renders: Closed Lost deals, last 7 days leads to Includes loss reason, amount, owner per deal. Includes loss reason, amount, owner per deal leads to Email sent to Slack channel inbound address. Weekly schedule: Friday 16:00 Dashboard report renders: Closed Lost deals, last 7 days Includes loss reason, amount, owner per deal Email sent to Slack channel inbound address
Weekly schedule: Friday 16:00 leads to Dashboard report renders: Closed Lost deals, last 7 days. Dashboard report renders: Closed Lost deals, last 7 days leads to Includes loss reason, amount, owner per deal. Includes loss reason, amount, owner per deal leads to Email sent to Slack channel inbound address. Weekly schedule: Friday 16:00 Dashboard report renders: Closed Lost deals, last 7 days Includes loss reason, amount, owner per deal Email sent to Slack channel inbound address

When to use it, when not to

Use it

  • Use it when sales leadership wants a recurring, low-effort read on why deals are being lost, not just how many.
  • Use it to feed a weekly pipeline review conversation with real, current examples instead of a stale quarterly summary.
Read more on when to use itShow less

Skip it

  • Do not use it if Closed Lost deals do not reliably have a loss reason filled in. A digest full of "reason: blank" lines is not useful; fix data capture on the Closed Lost stage first, for example a required "Closed Lost Reason" property, before building this.
  • Do not use this as a substitute for a proper win/loss analysis process. This is a lightweight visibility digest, not root-cause analysis.
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 · 2 numbered actions

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

Known pitfalls · 5

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

Test plan and UAT script · 2 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