SALES

Weekly Stalled-Deal Triage Digest with Recommended Next Actions

Each week it audits every open deal, scores stall risk, classifies why each one stalled, and posts a prioritized triage digest to Slack with a recommended next move per deal.

CategorySales
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule starts audit
  • ActionPull all open deals from HubSpotHubSpotHubSpot
  • LogicScore stall risk and filter to riskiest deals
  • ActionClassify stall reason and recommend next actionOpenAI
  • OutputPost ranked triage digest to Slack channelSlack

What it does

Produces a single weekly view of your at-risk pipeline. It reviews all open HubSpot deals, ranks them by how badly they've stalled (days in stage, last touch, close-date slippage), has an LLM classify the likely reason each one is stuck, and assembles a ranked digest with a concrete recommended action for the top deals — revive, renegotiate, or close-lost.

When to use it

Use it for pipeline reviews and forecast hygiene. Rather than a flat CRM report, managers and reps get an opinionated, prioritized list of which stalled deals deserve effort this week and what to do about each.

How it works

  1. 1A weekly schedule starts the audit.
  2. 2All open deals are pulled from HubSpot with stage, activity, and close-date fields.
  3. 3A logic step computes a stall score and filters to the riskiest deals.
  4. 4An LLM classifies each deal's stall reason and recommends a next action.
  5. 5The ranked digest is posted to the sales channel in Slack and written back as a note on each deal.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HubSpotCRM, deals, marketing, support.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.